Google shows the wrong language: check hreflang
AISEO Site · Published 13 September 2026 · Updated 10 October 2026
When Google shows the wrong language version of your website, first check whether the wrong URL was selected, the snippet is in another language, or your own site redirects the visitor after the click. Those are different problems. Adding another language tag before identifying the failure can leave the real cause untouched.
This guide is for a website owner with two or more published language versions of the same service, product or article. It is not a guide to changing the language of Google's buttons or translating a page in Chrome.
Start with one affected page and its intended counterpart. You do not need to rebuild every language directory to collect useful evidence.
On this page
1. Identify what is actually wrong
Save the search phrase, date, device, selected search language, apparent country, displayed URL and final URL after clicking. A screenshot alone does not establish what every visitor sees.
| What you observe | First place to look | What not to assume |
|---|---|---|
| An English search result links to the French URL | The English page's availability, content and relationship to its French counterpart | That adding x-default will force English to rank |
| The intended English URL appears, but its title or snippet is French | Visible and rendered content, page title, and whether the same URL changes language | That the wrong language URL was selected |
| The correct URL appears, then the browser lands in another language | Redirects, language cookies and location-based rules | That Google's result caused the redirect |
| Only Google's menus are in another language | Search or account display-language settings | That your website needs new canonical tags |
For the second case, inspect the page before changing every description. Google can generate a title link from several sources and a snippet from page content. A meta description is not a fixed instruction to display that exact text. See Google's guides to title links and snippets.
2. Test the two destinations before their annotations
Choose the affected English URL and the actual equivalent French URL. Open each directly in a fresh signed-out session, without using the switcher first. Record the requested address, redirect path, final address and response. Repeat a returning visit only after preserving the first-visit result.
If English redirects to French, identify whether the redirect comes from the server, browser code, a saved cookie or a location rule. The owner must be able to reproduce the rule and state its intended scope. A tag in a page you cannot reach will not solve an unwanted redirect.
If both pages stay accessible, read their main explanations and the action a visitor can complete. A translated header around an untranslated body does not serve a French reader. Compare whether the two pages actually answer the same task; unrelated category or homepage links are not equivalent article counterparts.
Google determines language from content, rather than treating lang or hreflang as a translation. Keep the HTML language correct for accessibility, but repair missing body translation in the editorial source. See Google's multilingual-site guidance.
If one URL changes body language with a cookie or location, record each observed behaviour. Stable, directly accessible language URLs make diagnosis possible; do not force the reader away from a requested version. Locale-adaptive crawling guidance explains why not every adaptive version may be discovered.
3. Check canonical and hreflang as different decisions
Canonical identifies a preferred representative among duplicate or very similar URLs. Hreflang describes equivalent pages for different languages or regions. Neither translates the page.
For a genuinely translated English/French pair that you want available separately, investigate an English canonical accidentally copied into the French template. Do not consolidate every language into English simply because English is your business's primary language.
When using hreflang, Google's canonical guidance recommends a canonical page in the same language, or the best available substitute if one does not exist. Same-language regional duplicates need a separate decision: two nearly identical English pages for different countries are not automatically the same case as a fully translated French page. Canonical URL guidance
Here is a minimal illustrative pair, not a diagnosis of your website. Replace the example addresses with your real, final URLs.
English page: https://example.com/en/service/
<link rel="canonical" href="https://example.com/en/service/">
<link rel="alternate" hreflang="en" href="https://example.com/en/service/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/service/">
French page: https://example.com/fr/service/
<link rel="canonical" href="https://example.com/fr/service/">
<link rel="alternate" hreflang="en" href="https://example.com/en/service/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/service/">
The alternate links describe the same pair on both pages, including each page itself. Use fully qualified URLs and valid language codes. Region targeting is an additional choice, not a reason to invent a language-country variant for every possible market.
Google supports HTML, HTTP headers and sitemap annotations as equivalent implementation methods. You do not gain a Search advantage by maintaining all three. Check the method your site actually uses; absence from the HTML head alone does not prove absence everywhere. Localized-version implementation
4. Use a page-pair record before making changes
Give your developer the two addresses and the completed record below. It turns “the language is wrong” into a repair that can be retested.
| Evidence to record | English page | Other-language page |
|---|---|---|
| Requested URL and final URL | Copy both | Copy both |
| HTTP response and redirect chain | Record actual result | Record actual result |
| Main content language | Read the body | Read the body |
| Canonical URL | Copy exact value | Copy exact value |
| Alternate-language references | Record code and URL pairs | Record code and URL pairs |
| Indexing permission | Check robots meta and response headers | Check robots meta and response headers |
| Search Console status | Record indexed or not indexed | Record indexed or not indexed |
| Google-selected canonical, if available | Copy; otherwise mark unavailable | Copy; otherwise mark unavailable |
| Internal discovery path | Record a working link | Record a working link |
Do not fill an unavailable field with “passed.” Keep a before-and-after copy and change one identified problem at a time. Download the blank page-pair worksheet (CSV).
A small, reproducible example
We checked four constructed page-pair records with a rule-based checker. These are synthetic teaching examples, not customer results or a simulation of Google's ranking system.
| Constructed record | Checker's finding | Useful next action |
|---|---|---|
| Each page has its own canonical and both alternate references | No mismatch in these two checks | Continue with live content, access and indexing checks |
| French page declares the English URL as canonical | Canonical differs from the intended independent URL | Review whether the French page is genuinely translated and intended to stand alone |
| French page omits its English alternate | Missing reciprocal pair reference | Repair that mapping in the site's chosen annotation method |
| French page returns a redirect to English | Requested version is not directly available | Examine the redirect before changing annotations |
The checker tests only the supplied record. It cannot detect translation quality, fetch a live page or determine what Google will index. Download the example records (JSON text) and the small checker to reproduce the findings with Node.js. Save the downloaded example text as language-page-pair-examples.json and the checker as checker.mjs in the same folder, then run node checker.mjs.
5. Choose the repair from the failed check
The requested language redirects away
Give the routing owner the original and final URLs, fresh-session result and relevant preference or location condition. Fix the unintended rule, then directly reopen both versions. Confirm the switcher still goes to the equivalent page and that an optional preference does not block direct access.
The body or annotations are inconsistent
If the French body remains English, repair the article's actual translation. If a genuinely independent French page accidentally points its canonical to English, review and correct that output. If the reciprocal pair is missing, repair the mapping in the chosen HTML, header or sitemap implementation. Retest the exact production pair after deployment.
Use a working sibling pair to determine whether the problem is an isolated record or a shared template. Do not replace the whole language system because one map entry is wrong, or force every same-language regional duplicate into a policy intended for translated pages.
Live pages work, but Google's recorded state is old
Inspect both URLs in Search Console and keep the inspection date, last crawl and available Google-selected canonical. The indexed report describes the recorded version; a live test checks present access and does not establish current indexed canonical selection. URL Inspection help explains these boundaries.
For an eligible changed page, keep the sitemap current and record any recrawl request. Monitor the recorded state later. If selection remains inconsistent, examine redirects, competing duplicates and other signals using canonicalization troubleshooting. Repeated requests do not force a deadline.
The URL is right, but the title or snippet differs
Check the page title, main headings and rendered body in that URL's language, and compare them with the evidence saved from the result. Google may choose other title or snippet text. Repair proven mixed-language content or stale output; do not promise that a particular meta description will be displayed verbatim.
When one page pair becomes a site-wide audit
Keep the first diagnosis narrow. If one pair fails, repair and retest that pair. If the same mismatch appears across templates or language directories, expand the evidence set before changing the whole site.
| What the evidence shows | Scope to use | Next decision |
|---|---|---|
| One equivalent pair has a broken reciprocal link, redirect or canonical | That page pair | Fix the identified owner, then rerun the same check |
| The same failure repeats across one template or language directory | A representative sample plus the affected template | Correct the shared output and verify every sampled pair |
| Different pairs fail for different reasons | A site-wide audit grouped by failure type | Prioritize access and canonical problems before annotation cleanup |
| Every sampled pair passes the defined checks | No expansion unless new evidence appears | Preserve the working implementation and monitor actual search behavior |
That last result matters: an audit can justify leaving working pages alone. See the AISEO Site multilingual SEO audit of 10 English and Chinese page pairs for a first-party example of recording the checks, confirming the page relationships and deciding not to rewrite pages without evidence.
Common questions
Why is Google Search displaying the wrong language?
First distinguish Google's interface language from the language of your website result. For your own site, compare the displayed URL, snippet and final destination. Then inspect the corresponding page pair. There is no single language tag that fixes all three symptoms.
Why are my websites appearing in a different language?
Check whether the requested URL itself changes language or redirects. Also check that each published version contains substantial content in that language. A correct-looking menu or source attribute is not enough evidence to conclude that Google received the intended page.
Will x-default make Google choose my English page?
No. It identifies a fallback for users whose language settings do not match the specified alternatives. It can point to a language selector or suitable fallback page; it is not an instruction that English must win every search. Google's x-default explanation
Should I delete the other language to remove the confusion?
Not as a first response. If that page serves real visitors, deleting it removes that destination too. First identify whether the problem is missing content, access, duplicate-page signals or incorrect alternate links. A decision to retire a language is a business and migration decision, not a routine annotation fix.
Your next step
Complete the page-pair worksheet with your actual URLs, first failing check, responsible owner and expected result. After the repair, attach the same live checks and keep Google's recorded state as a separate dated observation. Close a technical mismatch when the corrected pages pass; keep search-result monitoring pending if it has not yet been observed.
What to keep after following this guide
Preserve the URL-pair record and live checks. Recheck the indexed version later; a working switcher or successful live test is not search-result confirmation.
Reading structure reviewed 10 October 2026. Original source dates and case boundaries remain in the article.
Continue with the relevant tool
Inspect each language page's delivered HTML with the hreflang checker, then verify equivalent translations and reciprocal links across the group.
See how it works →