H
Hreflang Generator

How Google Determines a Page's Language and Region

How Google figures out what language a page is in and which country it targets. Covers content analysis, hreflang, URL signals, Search Console settings, and common issues.

Google needs to know two things about every page it indexes: what language it is written in and which country (if any) it targets. These two signals determine where and for whom a page appears in search results. If Google gets them wrong, your French content shows up for English users, or your UK-specific page appears for searches in Australia.

Understanding how Google makes these determinations helps you send the right signals and avoid the situations where Google guesses incorrectly. For a general overview of international SEO, see our complete introduction.

How Google Determines Language

Google uses the visible content of a page to determine its language. This is the primary signal and overrides most other indicators.

Content analysis

Google's language detection runs against the actual text content rendered on the page. It does not rely on the HTML lang attribute, the Content-Language HTTP header, or any meta tag to make this determination. Those elements are hints, but the text itself is what Google trusts.

This means:

  • A page with lang="en" in the HTML but French text on the page will be classified as French
  • A page with a Content-Language: de header but English text will be classified as English
  • A page with mixed languages (navigation in English, body in Spanish) may confuse Google's detection

Google's language classification system is sophisticated. It can identify the language of a page from relatively short text samples and distinguishes between closely related languages like Portuguese and Spanish, or Norwegian and Danish. But it works best when pages are clearly in one language.

What content does Google analyze?

Google looks at the visible, rendered text of the page. This includes:

  • The page title and headings
  • Body paragraph text
  • Image alt attributes
  • Text rendered via JavaScript (after Googlebot renders the page)

It does not weight these equally. The body text carries the most influence because it provides the largest and most representative language sample.

The HTML lang attribute

The lang attribute on your <html> element is not how Google determines language, but it is still worth setting correctly. It helps screen readers and other assistive technologies, and it serves as a secondary signal that can reinforce Google's own analysis. Just do not rely on it as your primary language signal.

<html lang="fr">

The Content-Language header

The Content-Language HTTP header tells the client what language the response is in. Google has explicitly stated that it does not use this header for language or region detection. It is still good practice to set it for browsers and other clients, but it will not influence how Google classifies your page.

Mixed-language pages

Pages with content in multiple languages create problems. If your navigation, footer, and UI elements are in English but the main content is in German, Google will usually classify it as German because the body content is the dominant signal. But if the ratio is close to 50/50, Google may not classify the page confidently.

Best practice: keep each page in one language. If you have boilerplate elements (navigation, footer) that are hard to translate, at least make sure the main content area is entirely in the target language.

How Google Determines Region

Region (country targeting) is a separate determination from language. A page can be in English without targeting any specific country. Or it can be in English and specifically target Australia.

Google uses several signals for region, and unlike language detection, no single signal dominates. It is a combination.

Hreflang tags

Hreflang tags are the most explicit signal for regional targeting. When you specify hreflang="en-AU", you are directly telling Google that this page is the English version for Australia. Google trusts hreflang annotations as the primary control mechanism for which version to show in which market.

Hreflang does not change how Google indexes your page or what language it detects. It controls which alternate version Google serves in search results based on the user's language and location. For implementation details, see our hreflang guide.

Country-code top-level domains (ccTLDs)

A .fr domain is a strong signal that the site targets France. A .co.uk domain signals the United Kingdom. A .de domain signals Germany. Google treats ccTLDs as inherent country targeting signals.

Some ccTLDs have been genericized. Google treats .co, .me, .io, .app, .tv, and several others as generic TLDs, not country-specific ones. Using .io does not target the British Indian Ocean Territory.

Google Search Console International Targeting

For sites on generic TLDs (.com, .net, .org), you can set a target country in the International Targeting section of Google Search Console. This is a direct instruction to Google about which country your site (or a specific subdirectory) targets.

This setting only works with generic TLDs. If you use a ccTLD, Google already knows the target country and ignores Search Console targeting settings.

Server location

Server location used to be a meaningful signal. With CDNs and cloud hosting serving content from edge locations worldwide, it has become much less relevant. Google has confirmed that server location is a minor signal at best. Do not choose your hosting location based on SEO targeting.

Backlink profile

If a page has many backlinks from .de domains and German-language sites, Google may interpret this as evidence that the page is relevant to a German audience. This is not something you can directly control as a targeting mechanism, but it is a signal Google considers.

Local business information

For local businesses, your Google Business Profile listing, NAP (name, address, phone) data, and mentions in local directories help Google associate your site with a specific location. This is more relevant for local SEO than international SEO, but it contributes to Google's overall understanding of your geographic relevance.

On-page signals

Content references to local entities (currencies, phone number formats, addresses, local institutions) serve as minor signals. A page that mentions prices in euros, references the GDPR, and provides a Berlin phone number sends regional signals that reinforce Germany as a target.

The Interaction Between Language and Region

Language and region are independent dimensions, but they interact in search results.

When a user in France searches in French, Google considers both:

  1. Pages in French (language match)
  2. Pages targeting France (region match)

A page that matches on both dimensions has the strongest chance of appearing in results. A page that matches on language but not region (French content targeting Canada) may still appear, but with lower priority. A page that matches on region but not language (English content targeting France) is unlikely to appear for a French-language query.

Hreflang tags help Google handle these intersections correctly. Without them, Google makes its best guess, which is often right but sometimes wrong -- especially for languages spoken in multiple countries (English, Spanish, French, Portuguese, Chinese).

Common Problems and How to Fix Them

Google shows the wrong language version

Symptom: Users in Germany see your English page instead of your German page in search results.

Likely causes:

  • Missing or incorrect hreflang tags
  • The German page has thin content or technical issues that prevent Google from indexing it properly
  • Missing return links between the English and German pages
  • The German page redirects to the English page for Googlebot (IP-based redirects)

Fix: Verify your hreflang implementation. Make sure the German page is accessible, indexable, and properly linked in both directions. Check for IP-based redirects that might affect Googlebot. See our troubleshooting guide for step-by-step diagnosis.

Google classifies your page in the wrong language

Symptom: Google Search Console shows a page as "English" when it is actually in Dutch.

Likely causes:

  • Too much English-language boilerplate (navigation, footer, UI text) relative to the Dutch body content
  • The page has very little text content overall, making language detection unreliable
  • JavaScript-rendered content that Google has not fully processed yet

Fix: Increase the amount of target-language text. Translate boilerplate elements. Make sure the main content area has substantial text in the correct language. If content is JavaScript-rendered, verify in Search Console that Googlebot's rendered version shows the correct language.

Google ignores your regional targeting

Symptom: Your site targets the UK with en-GB hreflang tags and a .co.uk domain, but Google keeps showing your US competitor's page to UK users instead.

This is not a language/region detection issue. Google correctly identifies your page as targeting the UK. The US competitor ranks higher because of content quality, authority, or other ranking factors. Hreflang controls which version of your content is served, not whether it ranks at all.

Multiple versions compete in the same market

Symptom: Both your en-US and en-GB pages appear for the same query in the UK.

Likely causes:

  • Missing or incomplete hreflang tags
  • One page is missing the self-referencing hreflang tag
  • The hreflang tags are present but contain errors (wrong URLs, wrong codes)

Fix: Audit your hreflang tags for completeness and accuracy. Every page in the set needs the full list of alternates, including itself. For a code reference, see hreflang language codes.

Google does not use the meta content-language tag

Despite common belief, Google does not use <meta http-equiv="Content-Language" content="en"> or the Content-Language HTTP header for language or region detection. These are useful for browsers and accessibility tools, but Google relies on actual page content and hreflang tags. Do not depend on them as SEO signals.

What You Can Control vs. What You Cannot

You can control:

  • Hreflang tags (the strongest explicit signal)
  • URL structure (ccTLD, subdirectory, subdomain)
  • Google Search Console targeting settings
  • The language of your page content
  • On-page regional signals (currency, local references)

You cannot directly control:

  • How Google's language detection algorithm classifies your page (but you can influence it with clean, single-language content)
  • How Google weighs different signals against each other
  • How quickly Google processes changes to your signals
  • Whether backlinks from regional sources reinforce your targeting

Focus on the things you can control. Implement hreflang tags correctly, write clean single-language content, and set up Search Console targeting. These are the highest-leverage actions for ensuring Google understands your page's language and region.

Testing and Verification

Google Search Console

The URL Inspection tool shows how Google has indexed a specific page, including the detected language. Use this to verify that Google's classification matches your intent.

The International Targeting report (under Legacy tools) shows hreflang errors and language/country targeting status.

Site: queries with language filters

Search site:example.com in Google while changing your search settings to different languages and regions. This shows you which pages Google surfaces for each market.

Third-party tools

Crawling tools like Screaming Frog can audit your entire site's hreflang implementation and flag missing tags, broken return links, and inconsistent language codes.

Summary

Google determines language primarily from page content and region from a combination of hreflang tags, URL structure, Search Console settings, and secondary signals. The most effective approach is to write clean, single-language content and implement hreflang tags that explicitly define the relationships between your language and regional variants. Do not rely on HTTP headers or HTML attributes as your primary signals.

Generate correct hreflang tags

Make sure Google knows exactly which language and region each page targets.

Try Hreflang Generator

Related Articles