Quick answer — List the canonical URLs of your language pages in a sitemap. Use hreflang to describe language alternatives through HTML, HTTP headers or the sitemap itself. None of these steps guarantees indexing.
Vitra Universe website translation connects the content work. Your website's URLs, metadata and release checks still need a clear owner.
What a multilingual sitemap actually does
A sitemap provides a list of URLs for discovery. Language annotations describe relationships between versions. They solve different jobs.
For example, an English product page and its German version can appear in an ordinary sitemap while hreflang lives in each page's HTML. You don't need to duplicate those annotations across all three supported methods. Google's localized-version guidance describes the alternatives.
Decide where the relationship is maintained before building the export. If the CMS owns the language links, a separate manually maintained spreadsheet is another place for the two lists to disagree.
A worked language-URL example
Suppose a product has these two published pages:
- English:
https://example.com/en/products/charge - German:
https://example.com/de/produkte/charge
Those addresses are illustrative, not Vitra pages. The translated slug can differ. What matters is that the pair represents the same product and each address serves the intended content.
If you use HTML annotations, put the same pair on both pages:
<link
rel="alternate"
hreflang="en"
href="https://example.com/en/products/charge"
/>
<link
rel="alternate"
hreflang="de"
href="https://example.com/de/produkte/charge"
/>
Each set includes the current page and its alternative. Use complete URLs and return links. A link from English to German without the corresponding language relationship on the German page is an incomplete implementation.
The canonical on the German page would normally point to the German URL, not automatically back to English. A canonical describes the preferred URL for duplicate or equivalent content; it doesn't replace language annotations.
Check the page before checking the XML
A correct XML file can't fix a language URL that redirects, is blocked or only displays the source text.
| Check | What to inspect |
|---|---|
| Response | The final language URL returns a usable page rather than an unexpected redirect |
| Indexing controls | The page is not unintentionally blocked or marked noindex |
| Canonical | It identifies the intended preferred URL |
| Visible content | Navigation, primary copy and key transaction steps are in the intended language |
| Language links | Visitors and crawlers can reach the alternatives through actual links |
| Metadata | The title and description match the translated page |
| hreflang | The language set is complete and reciprocal where annotations are used |
Use the localized website testing guide for layouts and customer journeys. The translation brief template gives the team somewhere to record the audience, URLs and reviewer.
Language, region and fallback
Use de for German generally; use a language-region value when the page targets a specific regional audience. Don't create separate regional pages merely to multiply the URL count. A genuinely different offer, delivery area or required notice gives the local page a reason to exist.
A language selector or suitable fallback page can use x-default. Choose that destination deliberately rather than sending every unsupported audience to an unrelated campaign. See Google's multi-regional site guidance for the wider URL and audience decisions.
Split files for maintenance, not a ranking trick
A sitemap file can contain up to 50,000 URLs and must stay within the 50 MB uncompressed limit. Use a sitemap index when splitting files. Those are format limits, not traffic targets. Google's sitemap documentation explains the requirements.
Grouping by language or content type can make debugging easier. Keep the URL inventory generated from the same published content that serves the pages. Only update last-modified dates when the relevant content has actually changed.
After launch, submit the sitemap, inspect representative URLs in Search Console and investigate exclusion reasons. A low number of indexed pages is a finding to diagnose, not proof that hreflang alone is broken.
FAQ
Does every multilingual sitemap need hreflang? No. You can provide hreflang through HTML links, HTTP headers or XML sitemaps. Choose a supported method and keep it consistent. A sitemap can list language URLs without carrying the annotations.
Should translated pages canonicalize to the English page? Usually not. If a translated page is intended to be indexed separately, its canonical should normally identify that language page. Check canonical handling alongside language annotations rather than treating one as a substitute for the other.
Does submitting a sitemap guarantee indexing? No. A sitemap helps search engines discover URLs. Crawling and indexing still depend on access, page content and search engine decisions. Inspect important URLs and the reported exclusion reasons.
Can multilingual sitemaps be split by language? Yes. Grouping files by language can make maintenance and monitoring easier, but it is not mandatory. Keep each file within the sitemap limits and reference the files from a sitemap index.
