Going international is the classic "looks simple on the whiteboard" trap.
You spin up a subfolder structure, throw hreflang tags in the <head>, and assume the CMS handles the rest. Then the crawl errors start piling up: Google treating your German pages as English duplicates because the content similarity threshold tripped, or Baidu ignoring your sitemap entirely because the XML namespace doesn't match their spec.
The copy side is worse. a CTA that fits a 240px button in English wraps to three lines in Finnish. french demands 20% more characters for the same semantic load, Japanese needs half. You end up building a dynamic character-count validator into the component library just to keep the design system from collapsing.
Then there's the feature-flag matrix. "Random 4 countries" usually maps to GDPR, LGPD, PIPL, and whatever California updated last Tuesday. legal shows up because your HubSpot forms still drop hubspotutk cookies before consent in regions where that's a six-figure fine. i've seen teams maintain separate Marketo workspaces per jurisdiction just to keep the suppression lists compliant.
The fix isn't translation - it's a localization pipeline with automated QA gates: visual regression for button overflow, schema validation per locale, and a consent-mode wrapper that respects every TCF 2.2 vendor spec. Anything less ships broken.