Wrong Country Version Showing? Hreflang, Done Properly
You built versions for different countries. Google is showing the wrong one to the wrong people, or ignoring most of them.
Why one mistake breaks everything
Hreflang must be reciprocal. If one page does not point back, Google discards the whole relationship rather than part of it.
-
You build country versions
Separate pages for separate markets, each written for the audience it serves.
-
Google shows the wrong one
Tags miss return references, use invalid codes, or point at addresses that redirect. The whole set is discarded.
-
The set gets completed
Every page mapped to its counterparts reciprocally, with self-references and x-default, then checked from each target country.
You built versions of your site for different countries or languages. Google is showing the wrong one to the wrong people, or ignoring most of them entirely.
Hreflang is the instruction that sorts this out. It is also the most commonly broken piece of technical SEO there is, because a single mistake invalidates the whole set.
The Honest Version: Hreflang Does Less Than People Expect
It is not a ranking instruction
Hreflang tells Google which version to show to which audience. It does not make any of them rank better. A page that cannot rank in the UK will not start ranking because you declared it the UK version.
Most sites do not need it
If you have one site, in one language, serving one country, you do not need hreflang at all. It exists for genuinely parallel versions of the same content, and adding it without that creates risk for no benefit.
And it must be reciprocal
This is where nearly everyone fails. If your UK page points at the US page, the US page must point back. If it does not, Google discards the relationship entirely.
That is why partial implementations achieve nothing rather than achieving something small. It is closer to a circuit than a list.
What Usually Breaks
One error invalidates the set, which is why half-finished implementations do nothing at all.
Missing return tags
Page A references B, but B does not reference A. Google ignores both. The single most common failure by a wide margin.
Wrong language or region codes
Using en-UK instead of en-GB, or inventing codes that do not exist. Invalid codes are silently discarded with no warning.
Pointing at redirects or 404s
References to addresses that no longer resolve. The set breaks even though every tag looks correct in the source.
No self-reference
Each page must include a tag pointing at itself. Leave it out and the set is incomplete.
Canonicals fighting hreflang
A canonical pointing at a different language version cancels the hreflang instruction entirely. Common and completely invisible.
No x-default
Nothing declared for visitors matching none of your versions, so Google chooses on your behalf.
What You Can Check Yourself First
1. Open the International Targeting report
Search Console lists hreflang errors directly, including missing return tags and unknown language codes. If it is empty, your implementation is probably fine and you can stop here.
2. Check one page in both directions
View source on your UK page and note which versions it references. Then open one of those and check it points back. If it does not, that pair is broken, and so is everything connected to it.
3. Confirm your codes are real
Language codes are two letters and region codes are two letters, and the combination must actually exist. en-GB is valid. en-UK is not, and it is used constantly by people who assume UK is a country code.
4. Search from the target country
Use a tool that lets you set location. If your German page appears for German searches, it is working regardless of what any audit report claims.
What I Do
1. Establish what you genuinely need
Sometimes the honest answer is that separate versions are not worth maintaining and one well-written page would serve everyone better. I will say that before building anything.
2. Map every page to its counterparts
Including pages that exist in one language and not others, which is exactly where most implementations fall apart.
3. Implement reciprocally, with self-references and x-default
Complete sets only, because incomplete sets do nothing.
4. Validate, then check real results
Search Console confirms the tags parse. Location-based searches confirm the right version actually appears, and that is the part that matters to your business.
When You Do Not Need This
One language, one country. Hreflang has nothing to do. Adding it creates risk with no upside.
Your versions are genuinely different content. Different products for different markets are separate pages, not translations, and hreflang is the wrong tool for that.
The right versions already appear. If searchers in each country see the correct page, it is working. Leave it alone.
The Mistake That Causes Most Hreflang Problems
Almost every broken setup I see fails for one of three reasons, and all of them are mechanical rather than strategic.
The tags do not point back
Hreflang has to be reciprocal. If your UK page names the US page, the US page must name the UK page in return. One-directional tags are ignored entirely, which is why a setup can look complete in the source code and do nothing at all.
Every version must list itself
Each page needs to include itself in its own set. Leaving that out is the second most common failure, and like the first it produces silence rather than an error message.
The language and region codes are wrong
The code for the United Kingdom is not uk, and the code for a language is not the same as the code for a country. A single invalid value can invalidate the whole set for that page, and it is the kind of error that survives review because it looks plausible.
Why nobody notices any of this
There is no warning for these mistakes. Search Console reports what it found, not what it quietly discarded, so a site can run a broken setup for years while the wrong country keeps seeing the wrong page and nobody has a reason to look.
Price and Turnaround
Scope |
Price |
Turnaround |
|---|---|---|
Two or three versions |
$399 |
4 – 7 days |
Four to ten versions |
$699 |
1 – 2 weeks |
Large or ecommerce, many markets |
From $1,199 |
2 – 4 weeks |
Includes the mapping, implementation, validation, and checking that the right version actually appears in each target country.
Common Questions
Does hreflang improve rankings?
No. It decides which version is shown to whom. Ranking is decided separately and by different things.
Can I use it for the same language in different countries?
Yes, and that is one of its best uses. English for the UK, US and Australia can each be declared separately.
Subdomains, subfolders or separate domains?
Subfolders are usually simplest and keep everything on one domain. Separate country domains are heavier to maintain and split your authority.
What is x-default for?
Visitors who match none of your declared versions. Without it, Google picks for them.
Can I put hreflang in the sitemap instead?
Yes, and on large sites it is often far easier to maintain than tags on every page.
Why does Search Console show no hreflang data?
Usually because the tags are invalid or non-reciprocal, so Google discarded them rather than reporting on them.
Do I need it for the same language across regions?
Only if the content genuinely differs, such as pricing or availability. Identical content in one language does not need it.
Frequently Asked Questions & Practical Implementation Guidance
How quickly will this optimization impact search rankings? Technical fixes (such as repairing canonicals, sitemaps, and server response times) typically reflect within 2 to 4 weeks once Googlebot recrawls the updated pages. Structural content upgrades and topical cluster additions show continuous growth over a 60 to 90 day indexing cycle.
What is the best way to maintain these results over time? Establish a quarterly audit schedule to monitor Search Console performance logs, verify that internal links remain intact, and refresh outdated data points before competitors can capitalize on content decay.
Looking for hands-on technical SEO execution or enterprise audits? Consult with Senior AI SEO Consultant Shahzaib Ul Hassan at ShazzSEO.
Open your International Targeting report
Search Console lists hreflang errors directly. Send me a screenshot and I will tell you free whether it is worth fixing.
Or email info@shazzseo.com