Subfolder, subdomain, or separate .com? A composable-stack call
Summary
An EU fashion retailer with a composable stack (Next.js, Strapi, multi-region backend) needs to choose between subfolder, subdomain, or separate domain for a US storefront. Engineering sees no cost difference, but SEO consequences lock in fast and are hard to reverse.
Hreflang remains a hint, not a directive, so weak authority on a new regional variant can be overridden by Google's relevance signals. Composable stacks make locale routing invisible to Googlebot via headers or cookies, risking inconsistent content from identical URLs and hreflang misconfigurations.
If you choose subfolders, pair hreflang with areaServed structured data and ensure canonicals self-reference correctly within each region's hreflang cluster rather than crossing regions.
What happened
A practitioner post in r/TechSEO laid out a high-stakes architecture decision. An established EU fashion retailer with organic rankings across DACH, UK, France, and Benelux needs a URL structure for a new US storefront. The stack is composable (Next.js, Strapi CMS, multi-region commerce backend), so splitting storefronts per region is cheap on the engineering side. The SEO side is where it gets expensive.
The poster listed four options: subfolder under the existing .com, subdomain (us.brand.com), a standalone .com, or .us ccTLD. Engineering has no strong preference because the composable backend handles regional splitting at the API layer. The SEO call is the deciding factor. The poster mentioned that agencies they’ve consulted are softening the subfolder recommendations they gave two years ago, though that’s one practitioner’s read, not a documented industry shift.
The core question: does hreflang still help Google serve the correct regional variant, or has its reliability eroded under AI Overviews and recent ranking volatility?
Why it matters
The subfolder-with-hreflang answer has been standard for a decade. Google’s multi-regional site documentation presents subfolders, subdomains, and separate domains as valid approaches with different trade-offs, but doesn’t address how AI Overviews interact with multi-region structures.
The basic trade-offs are familiar. Subfolders pool authority but risk geo-intent blurring. Subdomains isolate crawl entities but may be slower to associate with root-domain authority. Separate domains give the cleanest signal separation but start from zero. Google’s documentation lists comparable pros and cons for each without claiming any option performs identically in search.
What makes this thread worth covering is the composable-stack angle. On Next.js, locale state often lives in the routing layer rather than clean URL paths, making hreflang misconfigurations easier to introduce than they look. If the commerce backend handles multi-region logic at the API layer but URLs don’t reflect regional differences, Google sees inconsistent content from identical URLs. If you serve different content on the same URL depending on the visitor’s region or language, Google and AI bots will only see one version. The other versions effectively do not exist in search. Every regional version needs its own crawlable URL path.
Googlebot does not send Accept-Language headers, so header-based or cookie-based locale routing is invisible to it. The W3C notes general limitations with content negotiation for delivering the right language version, and search engines sharpen the problem.
Hreflang has always been a hint, not a directive. Google can override it based on relevance signals. If a new US subfolder has weak authority compared to the established EU parent, Google may serve the EU version for US queries anyway. The practitioner concern is real, but it reflects hreflang working as designed rather than a new degradation.
What to do
Don’t let engineering convenience drive the URL decision. The fact that composable stacks make region splitting cheap in code doesn’t mean the SEO consequences are reversible. Authority flows and crawl patterns lock in faster than a codebase refactor can undo them.
If you choose subfolders, add structured data for regional clarity. Hreflang alone may not be enough. Add areaServed to an Offer entity nested within your Product schema markup (via the offers property) to reinforce which region each product page targets.
Get canonicals and hreflang aligned, not just “redundant.” Each regional URL needs a self-referencing canonical pointing to itself, and that canonical must match the URL listed as the self-reference inside that page’s hreflang cluster. If a canonical on /en-us/ points cross-region to /en-de/, Google will treat /en-de/ as the indexable version and ignore the hreflang annotations on the /en-us/ page entirely. Canonicals and hreflang are complementary signals, but they must be consistent. A mismatch silently breaks the whole regional cluster. (For related canonical override behavior, see how Cloudflare enforces canonical tags as 301s for AI crawlers.)
Audit your locale routing for Googlebot visibility. If your Next.js front-end or Strapi API returns region-specific content based on headers, query parameters, or cookies, Google won’t see the regional variants. Every regional version needs its own crawlable URL path. Verify in Search Console that US and EU variants are indexed separately.
Test with a small category before committing. Launch a limited set of US product pages under your chosen structure and monitor Search Console for several weeks. Check whether Google is ranking the US variant for US queries or falling back to the EU version. If cross-region issues show up in a small test, they will be worse at full scale.
Skip .us entirely. The ccTLD has negligible adoption and low user trust in the US market. ccTLDs are the strongest geo-targeting signal available to Google, but the case against .us is adoption and trust, not signal strength.
If brand independence matters, go separate domain. A standalone .com gives the cleanest long-term signal separation. Budget for dedicated link building to compensate for the authority gap.
Watch out for
AI Overviews may conflate regional content. Some practitioners speculate that subfolder structures rolling all regional signals into one domain could let AI models pull from different regional variants in the same overview. This is unverified hypothesis, not documented behavior. Separate domains remove the structural possibility, but subfolders require extra structured data precision to keep regional content distinct.
Canonical drift during deploys. It’s easy for a templating change or a CMS-side canonical override to push every regional page’s canonical back to a single “primary” locale. The moment that ships, your hreflang cluster goes silent. Add a deploy-time check that asserts each locale’s canonical resolves to itself before any URL structure change goes live.
ISR path invalidation and near-duplicate content. On Next.js with Incremental Static Regeneration, a product update can regenerate both /en-de/ and /en-us/ paths at once. If descriptions are identical across regions, this creates a plausible duplicate content risk. The specific Googlebot impact is not formally documented, but differentiate regional content beyond price and currency as a precaution.