hreflang: The SEO Tag Half of Sites Get Wrong — Bidirectional References and x-default Mistakes
hreflang looks like a tag you can drop into <head> in a few lines and be done with, but it's actually a signal that only works when pages are correctly "paired." Add it to one page and forget the other side, and nothing looks wrong in the browser — Google doesn't throw an error either. It just quietly ignores the entire hreflang relationship. This guide walks through why hreflang matters, why the most common mistake — a missing bidirectional reference — is so dangerous, and what we found when we actually checked whether modoohub.com itself follows these rules.
1. Why hreflang matters — duplicate content vs. regional targeting
Say you offer the same tool in Korean, English, Chinese, and Japanese. If you split that across separate URLs by domain or path alone, Google can end up seeing "several pages with nearly identical content." Without hreflang, Google might index only one of them as the canonical version, or show a Korean user the wrong language version in search results. hreflang explicitly tells Google "these URLs aren't duplicates — they're language/regional versions of the same content." That prevents ranking loss from perceived duplication while making sure the version matching each visitor's language shows up correctly.
2. The most common mistake — missing bidirectional references (return tags)
The core rule of hreflang is: "if page A points to page B, page B must point back to page A." For example, if a Korean page's head includes hreflang="en" pointing to an English URL, that English page's head must in turn include hreflang="ko" pointing back to the original Korean URL for the relationship to hold. This is called a return tag, or bidirectional reference. The problem is that when it breaks, nothing visibly signals it. Crawling tools, browsers, and even Search Console often don't flag it as a clear error. Google simply treats the signal as untrustworthy and silently discards the entire hreflang set, falling back to treating each URL as an independent page. So even after carefully tagging every language version, forgetting to add the return link on just one page invalidates the whole effort.
3. Does modoohub.com actually follow these rules?
While writing this guide we checked the site's own code directly. The result was half reassurance, half discovery. All 394 tool pages carried the 5 hreflang entries (ko/en/zh/ja/x-default) correctly matched to their canonical URLs, with zero missing x-default cases across any file. Since each tool page is physically a single HTML file and language switching is handled via the ?lang= query parameter and JS, the hreflang block in the head is identical no matter which language the page is loaded in — meaning bidirectional references hold automatically by construction.
index.html, the site's front door, told a different story. Its hreflang block includes ko, en, zh-Hans, zh-Hant, hi, de, fr, and x-default, but of the 4 languages the site's UI actually supports (ko/en/zh/ja), the hreflang="ja" tag was missing. On top of that, the hreflang="de" and hreflang="fr" entries didn't point to any German or French content — both pointed at the same English URL (?lang=en). That effectively tells Google "this URL is the German/French version," which is inaccurate. It's unlikely to cause an immediate ranking drop, but it also can't deliver the targeting effect it's supposed to. This was flagged during this review and left on the fix backlog.
4. Summary — the order to check hreflang in
- Start with self-reference: does every page include itself in its own hreflang set?
- Confirm it's bidirectional: if A→B exists, check that B→A also exists, pair by pair.
- Is x-default set: if not, add it to your language-selection screen or default-language page.
- Consistent code format: decide whether to use language codes only (en) or region codes too (en-US), and stay consistent site-wide.
- Matches actually supported languages: make sure you haven't added a language your UI doesn't support, or left out one it does.
Frequently Asked Questions
Q. Why do I need hreflang tags?
A. If the same content is split across multiple URLs by language or region, Google can mistake them for duplicate content and lower their visibility. hreflang tells Google that these URLs are actually translated or localized versions of the same content, so the right version is shown to each user's language.
Q. What happens if I forget the bidirectional reference?
A. If page A points to page B via hreflang but page B doesn't point back to page A, Google doesn't show an error — it just silently ignores the entire hreflang relationship. Because no warning shows up in crawl reports, this is especially hard to diagnose.
Q. When is x-default actually required?
A. x-default specifies the default version to show when a visitor's language doesn't match any of the hreflang values a site provides. It isn't strictly mandatory, but without it Google picks a version on its own, so it's safer to explicitly mark a language-selection screen or your default-language page as x-default.
Q. Does modoohub.com itself follow these rules?
A. All 394 tool pages consistently carry 5 hreflang entries (ko/en/zh/ja/x-default) that match their canonical URLs, with no issues found. However, index.html supports a Japanese UI but was missing the hreflang="ja" tag, and its de and fr codes pointed to the English page instead of actual German or French content — both were discovered during this review and left on the fix list.