Six countries, one language Google would serve. The hreflang loaded too late.

Six countries, one language Google would serve. The hreflang loaded too late.

A travel SaaS ran six localized versions — US, UK, DE, FR, ES, IT. Their hreflang tags were injected client-side by a localization library after the framework mounted. Localization worked for users. In the SERP, German searchers kept getting the English page.

The symptom: international organic flat despite the localized content existing, and Search Console's International Targeting report showing 'no return tags' errors across thousands of URL pairs.

Turns out Google parses hreflang from the initial HTML response during the first crawl wave. The tags only appeared after JS ran — by which point the relationship wasn't reliably picked up, and the reciprocal 'return tags' often weren't there when the partner page was crawled. The whole hreflang cluster failed to form. Google defaulted to serving one version.

We moved hreflang into the server-rendered — present in the raw HTML for every locale, reciprocal and complete on first byte.

'No return tag' errors fell from ~8,000 to zero in four weeks. Localized pages started serving to their correct markets. DE/FR/ES/IT organic combined: +96% over three months. US traffic unchanged — it just stopped eating the other markets' impressions.

Hreflang is a first-byte signal. Inject it late and Google never sees the relationship.