> Bron: https://neuralex.nl/en/blog/meertalige-site-en-ai > Keep language versions of your site from competing in search. Learn how to structure URLs, hreflang, canonicals, translations, and internal links so search engines and AI assistants can identify the right version. [Back to Insights](/en/blog) GEO ·6 October 2026 ·5 min read # Multilingual Sites and AI: How to Stop Your Translations Competing with Each Other Keep language versions of your site from competing in search. Learn how to structure URLs, hreflang, canonicals, translations, and internal links so search engines and AI assistants can identify the right version. To stop language versions of your site from competing with each other, give each version its own clear URL and connect the pages with hreflang. Write a translated title and description for every version, and remove pages that are duplicated or only partly translated. This helps search engines understand which version belongs to which language. Cannibalisation happens when two pages on the same site compete to answer the same question. On a multilingual site, this can happen when translations overlap, search engines cannot see a clear relationship between languages, or several versions contain nearly identical material. AI assistants may also encounter different language versions. No one knows exactly how every assistant handles them, but a clear structure makes it easier to identify the right page. ## Give each language its own URL Use a stable web address for every language version. You can put the language in a path, such as **/nl/** and **/en/**, or use separate subdomains. Choose a structure you can maintain consistently. If a page is available in more than one language, give each translation its own URL. Let visitors switch languages using a clear link. Do not automatically send them to another version based on their browser language. That can prevent visitors from seeing the version they want and make it harder to crawl or share language pages separately. You can offer a language preference, but keep each version directly accessible. Give every page a canonical URL that points to itself. The Dutch page should have the Dutch URL as its canonical, and the English page should have the English URL. Do not point every translation’s canonical to a single language version: that signals that the other versions are not independent pages. ## Show the language relationship with hreflang Hreflang tells search engines which language or regional versions of a page belong together. On every version, include links to all available alternatives, including the page itself. These links must work both ways: if the Dutch page points to the English one, the English page must point back to the Dutch one. Check that each link leads to the correct, accessible URL and that its language code matches the content. A link to a missing page or one that redirects elsewhere makes the relationship unclear. Hreflang is a signal for search engines, not a guarantee about which version they will display. Clear URLs and content still matter. ## Translate the meaning, not just the words A good translation reads naturally to someone who speaks the language. Unedited machine translation can produce awkward wording, ambiguity, or terms that do not fit your field. That can undermine readers’ trust and leave a page poorly matched to the question they are asking. Keep important terms, product names, and organisation names consistent across languages. If useful, create a terminology list that records which names stay as they are and which terms have different versions in each language. Translate the page title, description, and headings too. A Dutch title above English text sends mixed signals, as do headings in one language and body copy in another. If you cannot translate a page properly, it is better to hold back a complete translated version than to publish a partly translated one. You can tell visitors that the information is not yet available in their language and point them to the existing version. This reduces the chance that empty or partial translations will be mistaken for complete pages. ## Keep page structure and links together by language Use schema markup that matches the visible content and the page’s language. Structured data can clarify information about a page, but it cannot replace a good translation or a clear language relationship. Include language versions in your sitemap with the correct URLs and any alternatives. You can also read [how schema.org gives AI and search engines context](/en/blog/schema-org-voor-ai). Where possible, keep internal links within the same language. Readers on a Dutch page will usually expect a Dutch follow-up. Link related articles using descriptive anchor text so it is clear what the linked page covers. That helps readers navigate and makes the relationships between pages easier to understand. See also [how internal links connect related topics](/en/blog/interne-links-clustermodel) and [how AI assistants cite sources](/en/blog/geo-geciteerd-door-ai). Check that translated pages really serve the same purpose. An article may need a different title or angle in another language. That is fine as long as the pages address the same core question and their language relationship is correct. Do not force identical search terms or headings if they sound unnatural in the target language. ## Test what search engines and assistants can see Check each language page’s URL, canonical, hreflang links, title, description, headings, schema markup, and internal links. Make sure the sitemap lists the existing versions and that removed or replaced pages are no longer presented as current language alternatives. You can also run a simple practical test: ask an AI assistant the same question in Dutch and English. Note which pages the assistant mentions or uses, whether they match the language of the question, and whether the links work. Repeat the test after you change the content or structure. Results may vary by assistant and over time, so use the test to spot issues, not to make a fixed prediction. Use this checklist when adding a translation or reviewing your site: - Does each language version have its own directly accessible URL? - Do hreflang tags on every version point to the alternatives and to the page itself? - Does each version have a self-referencing canonical and its own title, description, and headings? - Is the text naturally translated, with consistent terms and names? - Does the schema markup match the page, and is the language version in the sitemap? - Do internal links stay within the same language where possible? - Are missing translations clearly identified instead of partly filled in? - Have you asked an assistant the same question in both languages and recorded what happened? AI visibility ## Do AI assistants understand the language versions of your site? We help you review URLs, language references and translations on your site — without invented claims. Curious what that means for your multilingual site? [Ask your question](/contact) [Read about being cited by AI](/blog/geo-geciteerd-door-ai) --- Volledige (opgemaakte) versie: https://neuralex.nl/en/blog/meertalige-site-en-ai