How to keep language routes, canonical URLs, hreflang, navigation and a sitemap aligned when a service website grows.
Write the route table first
For each page, record its purpose and the URL for every language that actually exists. Treat this as a content contract used by navigation and metadata. If a translation is missing, do not manufacture its URL in hreflang. A language switch should reach the equivalent page where possible, and any fallback to an index should be explicit.
Separate a URL label from a language code
A useful example is the Nataliyahutsul.es repository: Spanish pages use /es/ and Ukrainian pages use /ua/, while Ukrainian HTML and hreflang use uk. Aksiandr uses /uk/ for Ukrainian public pages. These projects have different established URL conventions. Copying one site's folder names into the other's metadata would introduce errors; a route registry should preserve each site's actual canonical namespace.
Canonical and alternates answer different questions
A canonical identifies the preferred URL for a page; language alternates connect equivalent versions. Give a translated page its own canonical rather than pointing all translations to the English page. Include reciprocal alternate links only for available versions. The x-default target should be the deliberate default destination for that cluster, not an old alias.
Make migrations a single step
Map a retired URL directly to its relevant destination. Test the first response without following redirects, then verify that the destination returns the intended content. Specific migrations can be lost behind broad normalisation rules. Aksiandr's legacy /en/portfolio-paginas-web needed to reach /projects directly rather than first shedding /en/ and creating another hop.
Validate the deployed sitemap
Generate the sitemap from public canonical pages, then request every listed URL after deployment. A locally correct sitemap can still publish routes blocked by old web-server rules. These checks establish technical consistency; they do not guarantee indexing, rankings or traffic. Content relevance and Google's indexing decisions remain separate questions.
Explore the Nataliyahutsul.es implementation