Hreflang: The Audit That Stops Your Pages Fighting Across Countries
I work at SEOSage, which builds desktop SEO audit software. The steps below work with any crawler. The wrong version of your page is ranking somewhere right now. Hreflang tells Google which language or regional version of a page to show to which audience. When it is wrong — or missing — the US page ranks in the UK, the English page outranks the German one in Berlin, and your own pages cannibalise…
Hreflang tags play a crucial role in ensuring the right version of a webpage is shown to the right audience. However, when these tags are incorrect or missing, it can lead to confusion for search engines like Google, causing your pages to rank in the wrong locations or cannibalize traffic. This audit aims to identify and rectify any hreflang errors before they cause issues for your regional managers or your overall SEO strategy.
The most common error is the lack of reciprocal links, where page A declares itself the alternate of page B, but page B does not declare page A back. Google ignores hreflang tags without reciprocity, making this a prominent issue. Additionally, incorrect language or region codes, such as en-UK instead of en-GB or made-up codes, can also cause issues. Furthermore, omitting the x-default tag, which serves as a fallback for unmatched audiences, can lead to Google guessing the appropriate page.
Another critical aspect is ensuring that hreflang tags are only applied to indexable and self-canonical pages. Tags on non-indexable pages or pages that return a 404 error are ineffective. Conflicting signals also play a role, where hreflang declares pages as alternates, but the canonical tag indicates they are all the same page. In such cases, Google trusts the canonical tag, rendering the hreflang tags redundant.
To conduct the audit, start by crawling the site and exporting all hreflang annotations, including the page URL, declared language/region, and target URL. It's also essential to gather data from the sitemap, as mismatches between header tags and sitemap declarations can lead to further errors. Next, verify the reciprocity of hreflang declarations by confirming that every A→B declaration has a corresponding B→A.
Then, map out the hreflang clusters, ensuring that every page in a language cluster references every other page in that cluster.
Afterward, validate the language and region codes against the standard lists provided by Google. Flag any codes that are not recognized by Google, especially language-only tags where the business serves distinct regions. Also, ensure that every target in the hreflang tags returns a 200 status, is indexable, and carries a self-referencing canonical tag. If any targets fail this step, they are dead signals and should be removed.
Cross-check the crawl findings with Google Search Console's International Targeting report and language report to confirm the errors Google has detected. This step should not be the starting point for your audit but rather a verification tool. Once the crawl and GSC findings are validated, fix the hreflang errors by cluster rather than by individual tags. This approach involves fixing the template or the sitemap generator, addressing the issue at its root.
Prioritize the clusters based on traffic, focusing on the clusters that generate revenue first. Re-run the hreflang extraction after any site changes involving locales, templates, or canonicals, and conduct a quarterly audit of the full cluster map to maintain international SEO health. By following these steps, you can ensure that your language versions link back to each other, preventing silent failures in your international SEO strategy.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.