Subdirectory routing with EN at root and /{locale}/ for all other languages. Bidirectional hreflang across all locales including x-default and self-referential annotations. Static generation per locale at build time. AI translation pipeline with human review gates. Supabase locale column for content storage with unique slug/locale constraint.
Where enterprise projects fail
But Google's either indexing the wrong language version or serving users in, say, Frankfurt or São Paulo the English page instead. That's not a content problem. It's a configuration problem, and nine times out of ten it comes down to misconfigured hreflang. Google doesn't give you the benefit of the doubt when hreflang signals are ambiguous. It just consolidates or ignores them entirely. So those translated pages you paid to build? They're generating zero ranking benefit. And here's the real kicker -- while the SEO issue sits there unfixed, you're probably running paid search to cover the gap in those markets. That spend adds up fast. In practice, we've seen companies where the ongoing paid search cost to compensate for broken international SEO has already exceeded what the original translation build cost. That's a painful situation that's also entirely preventable.
Spreadsheets appear. Someone's maintaining a separate Google Sheet for German translations. There's a manual upload process that one person understands. It works at two languages, barely. Try it at five and things start breaking. At fifteen, it breaks badly and consistently. Missed updates, stale translated metadata, localization that never got applied to the French version of your pricing page -- these aren't edge cases, they're the normal failure modes of fragmented multilingual operations. And each one creates real ranking damage and user experience problems in the affected market.
Honestly, this is a structural problem, not a content problem. Google treats each subdomain as a separate site. So the backlinks pointing to yoursite.com don't pass authority to de.yoursite.com. You're essentially starting from zero in each market from a domain authority standpoint. Subdirectory architectures don't have this problem -- everything concentrates in one origin, and head-to-head tests back this up consistently. But migrating isn't trivial. Get the redirect mapping wrong, miss hreflang updates during the move, and you'll see ranking instability across every market at once. Temporarily. Which is a fun conversation to have with stakeholders.
What we deliver
See this capability in action
Frequently asked
Should we use subdomains or subdirectories for international SEO?
Subdirectories outperform subdomains in international SEO. We've seen this consistently, and the reason is pretty straightforward: domain authority consolidation. Backlinks to any URL on your domain pass authority to the whole site under a subdirectory structure. Subdomains split that authority -- each one's essentially starting fresh. Now, Google has technically said subdomains and subdirectories are equivalent. And maybe in a low-competition niche that's true enough. But in competitive markets -- think financial services in Germany, e-commerce in France -- the authority concentration advantage of subdirectories shows up in rankings. So we build on subdirectories by default. The only exception is when there's a genuinely compelling operational reason specific to the organization's setup.
How do you implement hreflang at scale across 20+ languages?
Programmatically -- always. Every page template includes a hreflang generation function that queries the full locale set from the database and outputs complete bidirectional annotations, self-reference included, x-default included. So when you add Spanish to the system, hreflang updates across every existing page in the cluster automatically. No one has to touch 4,000 individual pages. No risk of missing reciprocal links because someone forgot to update the German template. We also validate the output against Google's hreflang specification before every deployment. It's a boring check that's caught real problems.
How do you handle content that should not be translated into certain markets?
Not every page should exist in every locale -- and we handle that explicitly. Any page or content type can be marked with locale exclusions at the content level. The generation pipeline respects those exclusions in both static output and sitemap generation, so you won't end up with an excluded locale appearing in a sitemap submitted to the wrong Search Console property. Google Search Console verification is handled per locale, and excluded locales simply don't get submitted to the corresponding property. Clean separation, no accidental signals sent to markets you haven't actually launched.
What is the quality standard for translated content?
Claude generates the base translation. Then that content gets scored against a Flesch-Kincaid equivalent calibrated for the target language -- because readability heuristics for Japanese are different from those for Portuguese, and treating them the same produces garbage quality signals. Pages that come in below threshold get flagged for human review before publication. But some pages skip the scoring entirely and go straight to a native speaker or professional translator regardless of what the machine output looks like -- homepage, core service pages, pricing. Those are too important to rely on a quality score. The score's a triage tool, not a replacement for human judgment on the pages that actually matter.
Is SEO dead or evolving in 2026?
SEO is far from dead in 2026; it is evolving to meet the demands of a rapidly changing digital landscape. As search engines become more sophisticated, focusing on user intent and context, enterprises must adapt by prioritizing high-quality, relevant content and technical optimization. Voice search, AI-driven algorithms, and mobile-first indexing are reshaping SEO strategies, making adaptability crucial. According to industry experts, future SEO will emphasize user experience and personalization, ensuring that businesses stay competitive in global markets.
What is international SEO?
International SEO is the process of optimizing a website so that search engines can easily identify which countries and languages your content is targeting. This involves structuring site architecture, using hreflang tags, and tailoring content to consider linguistic and cultural differences. For enterprise websites, effective international SEO ensures that users across different regions have a relevant and localized experience, boosting search visibility and engagement in global markets. As Moz explains, "It's about creating a unified strategy that aligns with both local search engines and consumer behavior.
Browse all 15 enterprise capability tracks or compare with our SME-scale industry solutions.
Schedule a 60-minute discovery call
We map your platform architecture, surface non-obvious risks, and give you a realistic scope — free, no commitment.
Schedule Discovery Call
Let's build
something together.
Whether it's a migration, a new build, or an SEO challenge — the Social Animal team would love to hear from you.