# Multilingual Sitemaps and Getting Indexed | Vitra.ai > A translated page nobody indexes is a page nobody sees. How to structure sitemaps and hreflang annotations so every language actually gets crawled. **Canonical URL**: https://www.vitra.ai/general/multilingual-sitemaps **Source**: This is the Markdown rendering of https://www.vitra.ai/general/multilingual-sitemaps, generated at build time from that page. --- 3 min read # Multilingual Sitemaps and Getting Indexed A translated page nobody indexes is a page nobody sees. How to structure sitemaps and hreflang annotations so every language actually gets crawled. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager , Vitra.ai Updated Aug 17, 2026 ![Multilingual Sitemaps and Getting Indexed](https://www.vitra.ai/static/images/blog/multilingual-sitemaps.jpg) Table of contents [Indexing is the step people assume](#indexing-is-the-step-people-assume) [What the sitemap has to say](#what-the-sitemap-has-to-say) [Region codes are not language codes](#region-codes-are-not-language-codes) [Splitting large sitemaps](#splitting-large-sitemaps) [Check it after publishing, not before](#check-it-after-publishing-not-before) [FAQ](#faq) Contributors [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager Subscribe to our newsletter Subscribe > **Quick answer —** Multilingual sitemaps should list every language version with reciprocal hreflang annotations. The common failures are non-reciprocal hreflang, missing self-references and listing only the source language.[Vitra.ai Universe](https://www.vitra.ai/platform) creates, translates, adapts and publishes from one place. ## Indexing is the step people assume Teams translate a site, submit the same sitemap they had before, and wonder why the new languages get little traffic. The pages exist. Nothing told search engines they exist, or which audience each is for. ## What the sitemap has to say Every language version, with an annotation on each entry listing all the alternatives including itself. Rule Failure if broken List every language URL Unlisted languages crawl slowly or not at all hreflang on each entry No language targeting Include a self-reference Annotations are ignored Reciprocal across all versions Annotations are ignored Use absolute URLs Ignored Correct language-region codes Wrong audience, or ignored The self-reference is the most common omission. A set of annotations that names the other languages but not itself is invalid, and the entire group gets disregarded — silently, which is why it survives for months. Reciprocity is the second. If the German page points at the French but the French does not point back, the pair is not trusted. ## Region codes are not language codes `en` is English. `en-GB` is English for the United Kingdom. `de-CH` is German for Switzerland, which is a different market from `de-DE` with different currency and legal text. Use a region code only when the content genuinely differs by region. Splitting `en` into five near-identical variants creates duplicate-content decisions nobody needs to make. And add `x-default` for the page served to users whose language you do not target, which is otherwise decided arbitrarily. ## Splitting large sitemaps Past fifty thousand URLs, split by language rather than arbitrarily, and index them from a sitemap index. Per-language sitemaps make indexing coverage legible — you can see that Japanese is at 40% while German is at 95%, which is the diagnostic that tells you where to look. Keep the URLs themselves coming from one [website translation](https://www.vitra.ai/features/website-translation) setup so the sitemap and the served pages cannot disagree, and hold titles in [memory](https://www.vitra.ai/features/translation-memory) so metadata matches the page body. ## Check it after publishing, not before Submit, then watch coverage per language for a few weeks. The mechanics interact with rendering and canonicals in ways that only show up in real crawl data — which is why [multilingual SEO](https://www.vitra.ai/general/multilingual-seo-platform) is a set of mechanics rather than a setting, and why [testing before launch](https://www.vitra.ai/general/localized-website-testing) catches the layout problems but not these. ## FAQ **What should a multilingual sitemap contain?** Every language version of every page, each annotated with hreflang listing all alternatives including itself, using absolute URLs and correct language-region codes. **Why are hreflang annotations ignored?** Usually a missing self-reference or non-reciprocal links. A page that names other languages but not itself is invalid, and if one page points at another without a return link the pair is not trusted. **When should a region code be used instead of a language code?** Only when content genuinely differs by region, such as different currency or legal text. Splitting one language into several near-identical regional variants creates duplicate-content problems unnecessarily. **How should large multilingual sitemaps be split?** By language, referenced from a sitemap index. Per-language files make indexing coverage legible, so you can see one language is at 40% while another is at 95%. Our blog ## Lastest blog posts Tool and strategies modern teams need to help their companies grow. Automotive [Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization) A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization) Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation) A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 [View all posts](https://www.vitra.ai/blog/page/1) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "Article", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.vitra.ai/general/multilingual-sitemaps" }, "headline": "Multilingual Sitemaps and Getting Indexed", "image": [ { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/blog/multilingual-sitemaps.jpg" } ], "datePublished": "2026-08-17T00:00:00.000Z", "dateModified": "2026-08-17T00:00:00.000Z", "author": [ { "@type": "Person", "name": "Samhitha J Bhatt" } ], "publisher": { "@type": "Organization", "name": "Vitra.ai", "logo": { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/vitra-v-logo.png" } }, "description": "A translated page nobody indexes is a page nobody sees. How to structure sitemaps and hreflang annotations so every language actually gets crawled." } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "General", "item": "https://www.vitra.ai/general" }, { "@type": "ListItem", "position": 3, "name": "Multilingual Sitemaps and Getting Indexed", "item": "https://www.vitra.ai/general/multilingual-sitemaps" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What should a multilingual sitemap contain?", "acceptedAnswer": { "@type": "Answer", "text": "Every language version of every page, each annotated with hreflang listing all alternatives including itself, using absolute URLs and correct language-region codes." } }, { "@type": "Question", "name": "Why are hreflang annotations ignored?", "acceptedAnswer": { "@type": "Answer", "text": "Usually a missing self-reference or non-reciprocal links. A page that names other languages but not itself is invalid, and if one page points at another without a return link the pair is not trusted." } }, { "@type": "Question", "name": "When should a region code be used instead of a language code?", "acceptedAnswer": { "@type": "Answer", "text": "Only when content genuinely differs by region, such as different currency or legal text. Splitting one language into several near-identical regional variants creates duplicate-content problems unnecessarily." } }, { "@type": "Question", "name": "How should large multilingual sitemaps be split?", "acceptedAnswer": { "@type": "Answer", "text": "By language, referenced from a sitemap index. Per-language files make indexing coverage legible, so you can see one language is at 40% while another is at 95%." } } ] } ```