Official statement
Other statements from this video 38 ▾
- 1:08 How does my site get included in the Chrome User Experience Report without signing up?
- 1:08 How does your site end up in the Chrome User Experience Report?
- 2:10 How can you measure Core Web Vitals when your site isn't in CrUX?
- 3:14 Can negative reviews really penalize your Google ranking?
- 3:14 Can negative reviews really hurt your Google ranking?
- 7:57 Should you really separate sitemaps for pages and images?
- 7:57 Does splitting your sitemaps truly impact crawling and indexing?
- 9:01 Could a 304 Not Modified code actually prevent your pages from being indexed?
- 9:01 Is the 304 Not Modified code really a trap for your indexing?
- 11:39 Does Google Cache Really Influence the Ranking of Your Pages?
- 11:39 Is Google Cache really not useful for assessing a page's SEO quality?
- 13:51 Why doesn't your niche change generate any traffic despite all your SEO efforts?
- 14:51 Are link directories truly dead for SEO?
- 17:59 Do translated pages really count as duplicate content in Google's eyes?
- 17:59 Are translated pages really treated as unique content by Google?
- 20:20 Why does Google ignore your canonical tags, and how can you enforce separate indexing for your regional URLs?
- 22:15 Why does Google overlook your canonical on multi-country sites?
- 23:14 Why is your Search Console crawl budget skyrocketing for seemingly no reason?
- 23:18 Why is your Search Console crawl budget skyrocketing for no apparent reason?
- 25:52 Should you really limit the crawl rate in Search Console?
- 26:58 Hreflang and geo-targeting: Can Google really ignore your international signals?
- 28:58 Are Hreflang and Canonical really reliable for geographic targeting?
- 34:26 Why is Search Console showing the wrong URL for Hreflang and Canonical?
- 34:26 Why does Search Console display a different canonical than what appears in the SERP for your hreflang pages?
- 38:42 Should you canonicalize all your country versions to a single URL?
- 38:42 Should you really keep each hreflang page self-canonical?
- 39:13 How can local signals help you prevent canonicalization between your multi-country pages?
- 43:13 Should you really abandon country variations in hreflang?
- 45:34 Is it really necessary to use hreflang for a multilingual website?
- 47:44 Do Facebook comments really impact your site's SEO and EAT?
- 48:51 Should you isolate UGC and News content in subdomains to avoid penalties?
- 50:58 Should you create a lightweight version for Googlebot to speed up crawling?
- 50:58 Should you focus on optimizing your site speed for Googlebot or your actual users?
- 50:58 Should you serve a streamlined version of your pages to Googlebot to improve crawl efficiency?
- 52:33 Can you create local pages by city without risking penalties for doorway pages?
- 52:33 How can you tell a legitimate city page from a penalizable doorway page?
- 54:38 Has Google's manual action for doorway pages disappeared in favor of algorithmic solutions?
- 54:38 Are doorway pages still subject to manual penalties from Google?
Google requires explicit local signals — currencies, local phone numbers, physical addresses — to distinguish linguistically identical pages targeting different countries. Without these markers, algorithms treat the content as a classic duplicate. The stakes: avoid cannibalization between national versions and ensure that each country sees the correct page.
What you need to understand
Why doesn't Google rely solely on language to differentiate pages?
Language alone doesn’t indicate the geographic intent of the content. A text in French may target France, Belgium, Switzerland, or Canada. A text in English might aim at the United States, the United Kingdom, Australia, or India.
Therefore, Google needs local contextual signals to differentiate two pages that share the same language but address geographically distinct audiences. Without these signals, the algorithm considers them duplicates and does not know which version to prioritize in which country.
What local signals does Google actually recognize?
John Mueller highlights three main elements: currencies (€ for France, CHF for Switzerland), local phone numbers (distinct country codes), and local physical addresses (city, postal code, country).
These markers help algorithms understand that two linguistically similar pages are actually country-specific versions. They act as strong geographic indicators, complementing hreflang tags and IP signals.
Is hreflang alone enough to prevent duplicate content?
No. Hreflang tells Google which version to display based on the user's language and country, but it does not guarantee that both versions will be indexed separately. If the content is identical and lacks local signals, Google may consolidate the two pages in the index.
Local signals strengthen hreflang by helping Google legitimize the existence of distinct versions. They transform perceived duplicate content into legitimate local variants.
- Currencies: display CHF on the Swiss version, € on the French version
- Phone numbers: +41 for Switzerland, +33 for France
- Physical addresses: include a city, postal code, and country in the footer or contact pages
- Hreflang: properly implemented tags, bidirectional and consistent
- Localized content: adapt examples, cultural references, legal mentions
SEO Expert opinion
Is this recommendation consistent with what we observe in practice?
Yes, largely. Multilingual and multi-country sites that simply translate content without adapting local signals regularly encounter cannibalization issues. Google often indexes only one version and ignores or deprioritizes others.
Tests show that adding local currencies, phone numbers, and addresses improves differentiation in the index. However, caution: this is not an absolute guarantee. [To be verified] Google has never specified the relative weight of each signal, nor how many are needed to cross the differentiation threshold.
What nuances should be considered in this directive?
First point: these signals must be visible in the HTML, not only in JavaScript or iframes. Google needs to be able to crawl them and associate them with the page's content. Phone numbers or addresses hidden in images do not count.
Second nuance: these markers do not exempt the need for truly distinct content. If two pages display € and CHF but the rest of the text is identical word for word, Google may still treat them as duplicates. Local differentiation must be consistent and visible throughout the entire page.
In what cases does this rule not apply or pose problems?
For sites that sell exclusively online and have no local physical presence, displaying a fictitious address or a non-functional number is risky. Google values authenticity: a fake address can harm credibility and pose issues of legal compliance.
Another case: sites targeting multiple countries sharing the same currency (Eurozone). In this context, the currency alone is not sufficient anymore. It’s essential to focus on phone numbers, addresses, legal mentions and adapt editorial content (cultural references, local examples, idiomatic expressions).
Practical impact and recommendations
What concrete actions should be taken to differentiate two country versions?
First step: audit each country version and identify the local signals present (or absent). Ensure that each page displays at least one local currency, a phone number in the correct national format, and, if possible, a credible physical address.
Second step: implement hreflang correctly across all versions. Each page must point to all other language variants and to itself. The tags must be bidirectional and consistent between the XML sitemap and the HTML.
What mistakes should be absolutely avoided?
Do not simply duplicate content by changing only the currency. Google can spot identical pages and might only index one. It's necessary to adapt vocabulary, examples, legal mentions, and cultural references.
Avoid generic international phone numbers (+1 800 or +44 845) without an associated local number. Google looks for strong national signals, not numbers shared among several countries. The same applies to addresses: a PO box in a shared European business center does not equal a local physical address.
How can I check that my site is correctly differentiated?
Use Google Search Console for each country version (distinct domain, subdomain, or subdirectory). Verify that Google is indeed indexing both versions and that they appear in localized search results.
Test manually with a VPN or a geographic simulation tool: search for the same keyword from two different countries and check that Google displays the correct version. If the French version appears in Switzerland or vice versa, that’s a signal of differentiation issues.
- Display a local currency on each version (€ , CHF, CAD, etc.)
- Include a local phone number in the national format (+33, +41, +1, etc.)
- Add a local physical address in the footer or contact page
- Implement hreflang bidirectionally and consistently
- Adapt the editorial content: examples, vocabulary, cultural references
- Check indexing in Google Search Console for each country version
❓ Frequently Asked Questions
Hreflang suffit-il à différencier deux versions pays partageant la même langue ?
Quels signaux locaux sont les plus efficaces pour différencier deux pages ?
Peut-on utiliser la même adresse physique pour plusieurs versions pays ?
Les signaux locaux doivent-ils être visibles dans le HTML ou peuvent-ils être en JavaScript ?
Comment vérifier que Google différencie correctement mes versions pays ?
🎥 From the same video 38
Other SEO insights extracted from this same Google Search Central video · duration 56 min · published on 04/08/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.