Google shows the wrong language version? Check the page pair first
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.
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. Open both URLs without relying on the language switcher
Paste the full English URL into a fresh browser session. Then paste the full French URL. Record the final address and read the main content on each page, not just the navigation labels.
For each version, ask:
- Does this exact URL load successfully without a login or a redirect to the other language?
- Is the main explanation, product information or service offer actually in the intended language?
- Can a visitor reach it through an ordinary link from the site?
- Does the language switcher lead to the equivalent page, rather than always sending people to a homepage?
A translated menu around an unchanged English article is not the same as a translated article. Google says it identifies a page's language from its visible content, rather than using lang or hreflang to detect it. Keep lang correct for accessibility and browser behavior, but do not treat it as a substitute for useful translated content. Google's multilingual-site guidance
If one address changes its main content according to cookies, browser language or location, record that behavior separately. Google may not discover every locale-adaptive version. Stable URLs for individual language versions make the relationship easier to inspect. An optional suggestion to change language is less restrictive than a forced redirect that prevents access to the requested page. Locale-adaptive pages
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 and the small checker to reproduce the findings with Node.js. Save the checker as checker.mjs beside the examples file, then run node checker.mjs.
5. Verify the repair without confusing live and indexed states
After deployment, revisit the exact URLs and rerun the failed check. For example, a corrected French canonical must be visible on the production French page, not only in a CMS preview.
In Search Console, inspect both URLs. The indexed report describes Google's recorded state; a live test checks the currently accessible version. They answer different questions. A live test that succeeds is not confirmation that Google has updated the index or selected your preferred canonical. Use the available indexed data to investigate canonical selection. URL Inspection help
For an eligible changed page, request indexing and keep your sitemap current. Record the request date, then monitor the actual page and relevant country/query performance. Repeating the request does not guarantee faster inclusion. Requesting a recrawl
If Google chooses another canonical despite your declaration, inspect inconsistent redirects, template output and competing duplicate URLs before repeatedly changing tags. Google's canonicalization troubleshooting guide is a useful next reference.
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
Choose one page pair today. Capture the two final URLs, read the two main bodies, and record the canonical and alternate references. Hand over the first concrete mismatch with its expected result. That is more actionable than asking someone to “fix all international SEO.”
If you are planning a multilingual site, explore AISEO Site's platform capabilities and integration approach. For a specific review, send the affected page pair. Bring the evidence record; it makes the conversation about your actual visitor journey.