Do you really need separate URLs by country to appear in multilingual Google News?

Why does Google enforce this strict URL separation?

Google News operates with distinct national and linguistic editions. Each edition (Google News France, Google News UK, etc.) must be able to clearly identify relevant content for its audience. The URL separation allows the algorithm to automatically classify articles into the correct edition without ambiguity.

This technical constraint avoids duplicates and language mixing within a single edition. An article in French with a dedicated URL (/fr) will be directly associated with the French edition. Without this structure, Google would need to analyze the content of each page to determine its language and target market, which would slow down crawling and indexing in a news context where speed matters.

What URL structures are accepted by Google News?

The official documentation mentions subdirectories (example.com/fr, example.com/en) as the recommended format. But in practice, subdomains (fr.example.com, en.example.com) and country-specific domains (example.fr, example.co.uk) also work, provided each language version is hosted in a distinct space.

The critical point: a single URL cannot serve multiple editions simultaneously. Sites that utilize automatic language detection (the same URL displaying different content based on user geolocation) do not meet the criteria. Google News needs stable and unambiguous URLs for each market.

Does this rule also apply outside of Google News?

No, and this is where it gets interesting. For traditional organic SEO, Google fully accepts monolingual sites or structures with hreflang tags on the same URLs. The requirement for distinct URLs is specific to Google News, presumably for reasons of accelerated algorithmic processing.

A site can rank well on google.com/search with a unified architecture but be excluded from Google News if it does not segment its URLs. This is a difference in product logic between the two services, even though they share the same underlying engine.

• Mandatory Separation: each targeted language and country must have its own URL path (subdirectory, subdomain, or distinct domain)
• No Dynamic Content: URLs that display different content based on user location are not eligible for multilingual Google News
• News-Specific Rule: this constraint does not apply to traditional organic SEO where hreflang may suffice
• Automatic Identification: the URL structure allows Google News to instantly route an article to the correct edition without deep content analysis

Is this statement consistent with real-world observations?

Yes, completely. Tests show that sites with a unified architecture (the same URL for all languages + server-side detection) never appear in multiple editions of Google News simultaneously. Even with perfectly implemented hreflang tags, Google News seems to ignore these signals and prioritize the direct reading of the URL.

International media that succeed in multilingual Google News all use segmented structures without exception. BBC with bbc.com/news (English) and bbc.com/afrique (French), Le Monde with lemonde.fr and lemonde.fr/en for its English version. No major player bypasses this rule, which validates its non-negotiable technical nature.

What nuances should be added to this seemingly simple rule?

The devil is in the details. Google talks about distinct URLs "by country and by language," which can create an explosive multiplication of versions. Should a media outlet targeting 5 French-speaking countries create /fr-fr, /fr-be, /fr-ca, /fr-ch, /fr-sn? The documentation does not clarify this. [To verify]: does a single /fr suffice for all French-speaking editions, or must it really be segmented by country?

Another gray area: sites with partially translated content. If only 30% of your articles exist in English, do you need to create a complete /en, or does Google News accept a partial structure? Real-world feedback is contradictory. Some publishers report acceptance with limited linguistic sections, while others have been rejected. Google does not communicate a minimum content threshold per language.

In what cases does this architecture pose problems?

Digital pure players often launch with a unified technical stack where language detection is managed on the application side, not on the URL side. Redesigning this architecture for Google News involves significant infrastructure work: routing, CDN, asset management, possibly dedicated servers by market.

Sites using headless CMS with client-side rendering may also struggle. If your content is served via API and routing is done in JavaScript, Google News may not correctly identify your language editions. You must then resort to server-side rendering with clean URLs, adding technical complexity and hosting costs.

How to ensure your current structure is compliant?

First step: map out your current URLs and their linguistic content. Use a crawler (Screaming Frog, Oncrawl) to extract all your pages with their declared language (lang tag, hreflang). If identical URLs serve content in multiple languages based on geolocation, you are not compliant for Google News.

Second check: test access to your content from different countries. Use a VPN or Chrome's inspection mode with location emulation. If the URL changes when you switch countries (for example, automatic redirection to .fr from France), that's a good sign. If the URL remains the same but the content changes, you need to redesign.

What mistakes to avoid when ensuring compliance?

Classic mistake: creating subdomains without properly registering them in Search Console and Google Publisher Center. Each language subdomain or subdirectory must be registered as a distinct property and submitted individually to Google News. Don’t assume Google will automatically discover them.

Another pitfall: not implementing hreflang between your language versions. Even though Google News doesn’t seem to utilize it for routing, traditional organic SEO requires it. Without hreflang, you risk cannibalization issues between your editions in traditional SERPs. Both systems (News and Search) coexist, so both must be satisfied.

Should you also segment by country within the same language?

This is the million-dollar question. Google's statement mentions "by country and by language," suggesting fine segmentation. In practice, a /fr often works for all French-speaking editions (France, Belgium, Switzerland, Canada). But if you aim for an ultra-optimized SEO News with geolocalized content (regional news, local events), creating country-specific sub-sections may improve your visibility in each national edition.

The ROI depends on your model. A global media outlet with a single newsroom will probably produce a generic /fr. A network of local media with teams by country will benefit from segmenting /fr-be, /fr-ch, etc., to maximize editorial relevance and performance in each Google News edition.

• Audit your current architecture: does each language have a distinct and stable URL path?
• Ensure your URLs do not change content based on user geolocation
• Register each language version as a separate property in Search Console and Google Publisher Center
• Implement hreflang between all your language versions for organic SEO
• Test the indexing of each edition in Google News via targeted searches on news.google.com
• Document your geographic segmentation strategy (one global /fr or country-specific /fr-XX)