You have translated your site into English, Spanish or German to reach new markets. On paper, every visitor should automatically land on the version that matches their language and country. In practice, that rarely happens: a recent study of multilingual sites found that 75% of international sites carry at least one hreflang error, fragmenting rankings badly enough to cost between 20% and 40% of potential traffic in the affected languages. Hreflang remains one of the most poorly implemented technical SEO signals, even though it directly controls the visibility of your translated pages. Here are the 5 most common mistakes seen in 2026, and how to fix them before they cost you customers.
Hreflang: a powerful signal that breaks easily
The hreflang tag tells Google which language or regional version of a page to serve a given user. Contrary to what many assume, it is not a decorative piece of metadata — it is a signal Google interprets across an entire cluster of pages. Every page in the cluster must reference all the other versions and be referenced back, with exact codes and URLs that respond correctly. A single inconsistency in that system is enough for Google to disregard the whole annotation set for the entire cluster, not just the faulty page. That is why so many multilingual sites, well translated on the surface, remain invisible in foreign search results.
Mistake #1: Missing or inconsistent return tags
Reciprocity is the golden rule of hreflang: if the French page links to the English version, the English version must link back to the French one. This rule is broken constantly on e-commerce sites running multiple stores or subdomains per country, particularly on WooCommerce or multi-store Shopify setups where tags are generated independently for each market.
How to fix it
Use a crawler (Screaming Frog, Sitebulb) to extract every hreflang relationship on the site and flag one-way links. On WordPress with Polylang, confirm every translation is properly linked in the post’s language settings, since that link is what auto-generates the return tags.
Mistake #2: Missing self-referencing tags
An often-forgotten rule: every page must not only reference its alternate versions but also reference itself within its own hreflang block. This gets skipped frequently when tags are hardcoded or copy-pasted from page to page without adjustment.
How to fix it
Automate hreflang generation through your CMS rather than entering tags manually. On a Polylang or WPML site, self-referencing tags are generated natively — a quick check with the code inspector is enough to confirm they’re present on every translated page.
Mistake #3: Incorrect language or region codes
The hreflang format is strict: the language code must follow ISO 639-1 (two letters), and the optional region code must follow ISO 3166-1 Alpha-2. Classic errors still persist in 2026: using “en-uk” instead of the correct “en-gb” for British English, or using “eu” as a region code, which does not exist in the ISO standard. These typos, invisible to the naked eye in source code, silently invalidate the tag.
How to fix it
Systematically validate your codes with a dedicated tool (such as Merkle/DeepCrawl’s hreflang validator) before launching any new language or geographic market.
Mistake #4: Misusing x-default
The x-default tag tells Google which page to show when none of the targeted languages match the visitor — typically a language selector or your default international page. It should appear only once per cluster. Yet many sites mistakenly add it to every language version, or omit it entirely, leaving Google without a fallback for out-of-target visitors.
How to fix it
Define a single x-default page per translation cluster — ideally your international homepage or a language selector — and verify its uniqueness during every technical audit.
Mistake #5: Canonical conflicts and non-200 URLs
Two pitfalls often stack up here. First, if a page’s canonical tag points to a different URL than the one declared in hreflang, Google follows the canonical and simply ignores the hreflang annotation. Second, every URL referenced in a hreflang block must return an HTTP 200 status: if any of them redirects (301) or returns a 404 or 500 error, Google discards the entire hreflang cluster for that page, not just the broken link.
How to fix it
Keep canonical and hreflang tags consistently aligned on the same URLs, and build an HTTP status check into your monthly crawl routine to catch dead links before they penalize the whole cluster.
Auditing your hreflang in practice
Three habits are enough to secure your implementation long-term: regularly check the “International Targeting” report in Google Search Console, which explicitly surfaces detected hreflang errors; run a full crawl before and after adding any new language; and document your cluster’s structure (which URLs, which codes, which x-default page) to avoid drift as the site evolves.
Hreflang is a technical detail with a direct business impact on the international markets you’re targeting. If you’re not certain your multilingual site is correctly tagged, a full technical review often unlocks traffic that is already there but invisible. Discover how seoforge.io can audit your hreflang implementation and your overall technical SEO to turn your translations into real international traffic.
