Hreflang Tags: Getting the Basics Right
The hreflang attribute tells Google which version of a page is intended for which audience. Get the fundamentals right first.
Hreflang errors can silently tank your international rankings. We walk through how to audit your implementation, spot problems, and fix them before they impact your visibility.
Editorial Team
Written by the Global Reach SEO editorial team, focused on practical, honest guidance for multilingual search success.
Most companies don't realize their hreflang setup is broken until traffic suddenly drops. By then, it's too late — Google's already indexed the wrong pages for the wrong regions. The good news? It's fixable if you catch it early.
We've seen this pattern over and over. A site launches with hreflang, gets indexed, then someone makes a "quick fix" that introduces circular references. Or the implementation worked fine until the site migrated to a new domain. Suddenly, half your international traffic evaporates.
That's why auditing matters. You need to know exactly what's happening with your hreflang tags before it becomes a crisis. And honestly, most of the errors we find are preventable — they're just mistakes people didn't know to look for.
The most common mistake. Page A points to Page B, which points back to Page A. Google gets confused and sometimes ignores all the tags. This happens when you're using self-referential hreflang — which you should, but you've got to get it right.
Using "en_US" instead of "en-us", or inventing codes that don't exist. You've got to follow ISO 639-1 for languages and ISO 3166-1 for regions. It's specific, and Google's strict about it.
You've got hreflang on the German version pointing to English, but nothing pointing back. Hreflang needs to work both directions. If Page A says "see Page B," then Page B should say "see Page A."
Results vary depending on many factors — your site's existing authority, how long the hreflang has been in place, and how aggressively Google crawls your content. Fixing hreflang isn't a guaranteed quick fix. It's a necessary foundation that helps Google understand your site structure correctly.
You don't need expensive tools for this. Google Search Console shows hreflang errors right in the International Targeting section. Start there — it'll flag obvious issues like syntax problems or broken language codes.
Then do a manual check. Pick a few pages from each language version and verify the hreflang tags are correct. Check the source code, not what you think should be there. You're looking for three things:
Remove duplicates, fix the language codes, and make sure every page has a complete set of hreflang tags. Include a self-referential tag — the page should point to itself. It seems redundant, but Google expects it.
Don't use relative paths. Write out the full URL with protocol: https://example.com/de/page not /de/page. This removes ambiguity and prevents crawl errors.
Use Search Console's URL inspection tool to check your pages. It'll show you exactly what Google sees, including the hreflang tags. Spot-check at least 10 pages across different language versions.
Hreflang issues pop up when you least expect them. After a site redesign, domain migration, or CMS update, check Search Console again. It's a 15-minute task that prevents hours of debugging later.
You don't need premium software. Google Search Console is free and catches most issues. But if you want deeper analysis:
Hreflang isn't complicated once you understand it. The most common errors — circular references, wrong language codes, missing return links — are all preventable. Audit your site now, fix what's broken, and then check it quarterly. It's the unglamorous foundation that makes international SEO actually work.
Don't wait until traffic drops to discover your hreflang is broken. A 30-minute audit today saves weeks of debugging later.
Explore More International SEO Guides
The hreflang attribute tells Google which version of a page is intended for which audience. Get the fundamentals right first.
You can target by country, by language, or both. Each approach has different implications for your hreflang structure.
Beyond hreflang, there's a lot to get right when serving multiple countries. Here's a complete checklist.