Launching a new locale: an ordered checklist

Launching a new locale: an ordered checklist

Adding a market (say it-IT) to an existing international site fails in predictable ways when steps run out of order. The sequence that's worked for us:

— Build and index the Italian URLs *first*, with self-canonical and no inbound hreflang yet. An alternate Google hasn't indexed can't be swapped in, so referencing it early just creates dead edges.
— Confirm indexation via URL Inspection on a sample. Only then proceed.
— Add the new locale to *every existing* cluster member's hreflang set — and add the full set (all existing locales + self) to the new pages. This is the step teams half-do: they wire the new pages but forget to update the old ones, breaking reciprocity site-wide.
— Re-run a reciprocity check across the whole expanded matrix, not just the new pages.
— Set geotargeting where structure doesn't imply it (subfolders/subdomains need explicit signals; ccTLDs don't).
— Watch GSC International Targeting for 2-3 weeks; new-return-tag errors here mean the old-cluster update was incomplete.

We timed several locale launches: clusters where existing pages were updated in the *same* deploy as the new pages reached clean reciprocity ~3x faster than staggered ones. The data suggests atomicity matters.

Caveat: indexing speed for the new locale depends on crawl budget and internal linking — a new locale with no internal links in may sit unindexed for weeks regardless of perfect annotations.