Help for owners
Google shows the wrong language version of my website to visitors
Short answer
Hreflang annotations tell Google which language or region version of a page to show. They fail when the pages do not link back to each other, when a language or region code is wrong, or when addresses are not full URLs. Google says tags without return links are ignored. Check one page pair first.
Does this sound like your situation?
- Visitors from one country find my pages in another language in Google.
- Search Console or an audit tool reports hreflang errors.
- My English page appears for searches in another language.
- I added languages and nothing changed in Google.
- My translation plugin said it handles this, but results look wrong.
Why does this happen?
Pages do not point back to each other
Google states that if page X links to page Y, then Y must link back to X, otherwise the tags are ignored. Each version must also list itself and all other versions.
Confirmed by developers.google.com
Language or region codes are wrong
Codes use a language, such as en, optionally followed by a region, such as GB. A region alone is invalid, and codes like UK or EU have no effect, because GB is the right one.
Confirmed by developers.google.com
Addresses are not complete
Google requires fully qualified URLs including https. Addresses beginning with a slash or two slashes are not valid.
Confirmed by developers.google.com
No fallback page is set
Google describes an x-default value for a page used when no other version matches, such as a language selector. Without one, visitors outside your languages get whichever page Google picks.
Confirmed by developers.google.com
Annotations come from several places at once
A plugin, the theme and the sitemap may each add tags and disagree. Google says one method is enough and that using more than one adds no benefit.
Confirmed by developers.google.com
What can I do about it today?
- List your language versionsFor one important page, write down the address of each language version.
- Open the page source and look for hreflangRight-click, view source, search for hreflang. Send what you find to your developer.
- Check that both versions list each otherA version that lists the others but is not listed back will be ignored.
- Do not change addresses to fix thisMoving pages creates new problems. Hreflang can be corrected without changing addresses.
- Be patient after a fixGoogle needs to recrawl the pages before results change.
When should I bring someone in?
- You have more than a few pages in each language.
- Several plugins or a sitemap add language tags.
- Wrong-language results cost you customers.
How do I handle it?
- Choose one source of tagsI decide whether annotations come from the page, a header or the sitemap, and switch the others off.
- Generate them from one listAll versions of a page are built from the same list, so return links and self-references cannot be missed.
- Check codes and addressesEvery code and every full address is validated, and a fallback page is added where it makes sense.
- Sample and re-checkI test key pages and look at Search Console after a recrawl.
- Keep expectations honestGoogle decides what to show, and I cannot promise a result.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Do I need hreflang for every site?
It is for sites with the same content in several languages or regions. A one-language site does not need it.
Can the sitemap carry hreflang instead?
Yes. Google lists page tags, HTTP headers and a sitemap as equivalent ways, and says to use one.
How long until Google shows the right page?
It depends on recrawling. I cannot give a date.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.