Can you geotarget your Web Stories in country subfolders without risking SEO?

Does geotargeting Web Stories really work like it does for standard pages?

Yes, and this is an important clarification. Google treats Web Stories exactly like any HTML page for geographic geotargeting. Specifically, if you organize your Stories into country subfolders — for example, /UK/ for the United Kingdom, /US/ for the United States — you can set these targets in Search Console, under International Settings.

This statement puts an end to ambiguity: some SEO practitioners believed that Web Stories, due to their specific AMP format and dedicated presentation surface (the Stories carousel), were exempt from the classic geotargeting rules. This is false. Geographic targeting applies in the same way, whether you use subfolders, subdomains, or distinct domains by country.

What happens in countries without a dedicated Web Stories interface?

Google does not deploy its Web Stories UI (the visual Stories carousel) in all countries. In these markets without a dedicated surface, Web Stories are indexed and treated as mere standard AMP pages. They therefore do not appear in a specific carousel, but can show up in regular results if their content and SEO signals warrant it.

This distinction is significant. An optimized Story for the French market may appear in the Stories carousel on Google.fr if it exists. In a market without a carousel, that same Story will compete directly with standard HTML pages, without benefiting from the additional visibility linked to the format. Geotargeting works in both cases, but the visibility impact differs radically depending on the presence or absence of the dedicated UI.

What are the risks of confusing geographic targeting with language targeting?

Be careful not to confuse country targeting with language targeting. Geotargeting by subfolder (/UK/, /FR/, etc.) indicates to Google which country you are optimizing these pages for. But if your content is in English in /UK/ and in /US/, you also need to implement the hreflang tags correctly to distinguish en-GB and en-US.

Search Console geotargeting and hreflang tags complement each other; they do not replace each other. A common mistake is to think that the subfolder /UK/ suffices. No. Google needs both signals to understand that a Story in English /UK/ specifically targets the United Kingdom, and that another Story in English /US/ targets the United States.

• Geotargeting Web Stories works exactly like for standard HTML pages, via subfolders, subdomains, or distinct domains.
• In countries without a dedicated Web Stories carousel, Google indexes this content as standard AMP pages, without specific visibility.
• Geographic targeting via Search Console must be complemented by hreflang tags to avoid any linguistic confusion between English-speaking or Spanish-speaking markets.
• Organizing in country subfolders (/FR/, /UK/, /US/) is the simplest structure to set up for Web Stories geotargeting.
• Badly geotargeted Stories risk appearing in the wrong markets or cannibalizing their local versions in the case of poorly configured multilingual content.

Is this statement consistent with observed practices on the ground?

Yes, and it's reassuring. Sites that have deployed Web Stories in multi-country architectures are indeed finding that geographic targeting works as expected. Stories located in /FR/ do rank on Google.fr, those in /UK/ on Google.co.uk. No aberrant behavior observed.

However, one point remains [To verify]: the exact impact of the AMP format and the absence of Stories UI in certain countries on click-through rate and organic visibility. Google does not provide any numerical data here. It is known that Stories indexed as standard AMP pages lose the carousel effect, but their intrinsic ranking in standard SERPs remains unclear. Field feedback suggests a significant drop in CTR, but this requires statistical confirmation.

What nuances should be added to this rule?

Let's be honest: saying that "it works like for normal pages" does not address all edge cases. If your site uses a generic domain (.com) without forced geotargeting, Google will try to guess the target market of each Story based on language, backlinks, and content. This is not optimal.

Additionally, in a context where you are targeting multiple English-speaking countries (US, UK, AU, CA), the subfolder architecture quickly becomes complex. You not only need to implement /UK/, /US/, /AU/, but also tag each Story with hreflang en-GB, en-US, en-AU. A mistake in this chain — a missing hreflang, an incorrect Search Console declaration — and your Stories start to cannibalize between markets. The problem is that Google will not explicitly alert you to these conflicts.

In what cases does this rule not apply or pose challenges?

If you use a distinct domain by country (example.fr, example.co.uk), geotargeting is automatic and the issue of subfolders does not even arise. But beware: Google does not specify how it handles Stories hosted on a distinct subdomain (uk.example.com, us.example.com). In theory, targeting should work via Search Console, but some practitioners report inconsistencies with AMP subdomains. [To verify] with your own data.

Another gray area: markets where Google has deployed and then removed the Stories UI. What happens to your existing Stories content? Are they downgraded to normal AMP pages permanently, or is there a risk of volatility if Google reactivates the interface? No official data on this. The long-term behavior remains uncertain.

How can I structure my site for effective Web Stories geotargeting?

The most reliable solution remains the country subfolder architecture: /FR/ for France, /UK/ for the United Kingdom, /US/ for the United States. You create your Stories in these subfolders, then declare each subfolder as a geographic target in Search Console, under International Settings. It’s simple, transparent, and Google understands it immediately.

Complement this structure with properly implemented hreflang tags in each Story. If you have a Story in English /UK/ and a similar version /US/, each page must point to the other with hreflang="en-GB" and hreflang="en-US." Never neglect the x-default tag to define the default version in case of an uncovered market.

What mistakes should I avoid when deploying multi-country Web Stories?

A classic mistake: creating multi-country Stories without setting geotargeting in Search Console. Result: Google doesn’t know which market each Story is intended for and may display them in the wrong country. You then lose local relevance and risk cannibalizing your own versions.

Another pitfall: duplicating an identical Story in several country subfolders without adapting it. Even if geotargeting technically works, you end up with multi-country duplicate content that adds no local value. Google may arbitrarily choose which version to display, or worse, downgrade all versions. Always adapt the content, examples, visuals to the local market.

How can I check that my Web Stories geotargeting is properly configured?

First step: open Search Console, under International Settings. Check that each country subfolder is correctly declared with the appropriate geographic target. If you see "No geographic targeting," it means Google doesn’t know which country these Stories are intended for.

Second step: inspect your Stories using the Rich Results Test tool and the URL Inspection Tool. Check that hreflang tags are correctly detected and properly formatted. An error in hreflang syntax (language or region misspelled) renders the tag useless. Finally, monitor your organic positions by market in Search Console for any visibility anomalies.

• Organize Web Stories in clearly identified country subfolders (/FR/, /UK/, /US/)
• Declare each subfolder as a geographic target in Search Console, International Settings
• Implement complete hreflang tags on each Story, including x-default
• Adapt each Story's content to the local market (examples, visuals, cultural references)
• Test each Story with the Rich Results Test tool to validate structured markup
• Regularly audit Search Console to ensure Stories are ranking correctly in the right markets