How should links in multilingual article pages be handled during localization?

When handling links on multilingual article pages, first ensure that each language version has a stable, accessible URL of its own. Then connect in-body links, language switching, and search engine annotations to the correct versions. Translating only the page text while leaving product links in a German article pointing to the English page, or making the canonical URLs for all languages point to the English version, can create conflicts between the reading experience and indexing signals.

A technical assessment of localization for multilingual article pages can start by checking three things: whether different languages correspond to the same article, whether internal links lead to the right pages for readers, and whether search engines can identify the relationships between versions. Whether URLs should be translated into the local language can be decided after these three requirements are met.

Establish article relationships before choosing a URL structure

Language subdirectories, subdomains, and separate domains can all host multilingual content. For example, the same product selection guide might use /en/guides/pump-selection/ and /de/ratgeber/pumpenauswahl/ respectively. The paths do not need to correspond word for word, but the system needs to know that they belong to the same content group.

For a B2B export website managed through a single back end, language subdirectories are usually easier to manage centrally. If different markets are run by separate teams, subdomains or separate domains can also be evaluated. When choosing, consider publishing permissions, redirect maintenance, and data reporting together; do not decide solely based on claims that a particular structure is “better for SEO.”

Do not try to find a translation by replacing the language code in a URL. Different languages may use different slugs, and some articles may not yet be translated, may have been taken down, or may be specific to a particular market. A more reliable approach is to use a stable article group ID to link the versions and record the language, region, publication status, and actual URL. Generate in-body links, language switching, and hreflang from this mapping.

Localized slugs can help users understand links, but they are not required. If an existing website uses consistent English slugs, these can remain in use as long as the URLs for each language are clear and stable. Changing indexed URLs to localize paths requires updating internal links, the sitemap, and language annotations, as well as permanently redirecting old URLs to the corresponding new ones.

Prioritize same-language in-body links, and provide a clear fallback when a translation is unavailable

Links in articles should be handled according to their purpose. For links to product information, selection guides, downloadable resources, and inquiry pages, prioritize versions in the same language that are appropriate for the target market. When citing external standards, research materials, or official documentation, retain the accurate source; do not switch to a page with different content just to maintain language consistency.

Anchor text also needs localization. Even if a German article links to the correct German product page, leaving English anchor text such as “Learn more” interrupts the reading experience. Image links, buttons, related content, and in-page anchors in the body should also be checked, especially heading IDs regenerated after translation.

When the target page is not available in the corresponding language, handle it according to the purpose of the link:

• For supplementary reading, you can keep the version in another language and indicate the language next to the link.
• For links related to product specifications, pricing, or inquiries, confirm that the alternative page is suitable for the target market. If no suitable page exists, provide a clearly labeled contact option.
• For content that is no longer available, remove the link or point it to a clearly identified alternative. Avoid redirecting everything to the home page.

Language switching should preferably take users to the corresponding version of the current article. If no translation is available, you can hide or disable that option, or label it “View the article list in this language.” Do not send users to the home page without warning when they click “Switch language.” This obscures the missing translation and can make the link appear broken.

When evaluating a website platform, ask for a demonstration of an article available in only two of the three languages supported by the site. How the missing version is displayed, and whether publishing a translation automatically creates the relationship, reveal more about the system's capabilities than a demonstration featuring an article available in every language.

hreflang indicates language relationships; canonical specifies the preferred URL

hreflang tells search engines which URLs are language or regional versions of the same content. The English and German articles should each list the published versions in this group, including themselves, and reference one another. If the English page declares the German page but the German page does not make the corresponding declaration, search engines may not apply the annotations correctly.

Use valid codes for language values, such as en and de. Where regional differences matter, you can use language-region combinations such as en-US and en-GB. Do not use a country code on its own as a language code. x-default can be used for a default destination when no language matches, such as a language selection page, but it is not a required setting for every multilingual website.

hreflang does not replace canonical or guarantee that a page will be indexed. When content has been translated and each version is intended to appear separately in search results, each version should generally have a canonical pointing to its own canonical URL. If the canonical on a German page points to the English page, it signals a canonicalization intent that conflicts with indexing the German content independently.

URLs in hreflang should be absolute and point directly to live pages that can be crawled and indexed. Drafts, 404 pages, redirect URLs, and pages set to noindex should not remain in an active language group. Language relationships can be declared in HTML pages, HTTP response headers, or XML sitemaps; choose the method that is easiest to maintain. If declarations appear in multiple places, they must be consistent.

Acceptance testing should cover publishing, missing translations, and changes

Acceptance testing for multilingual links should not stop at checking whether the language switcher can be clicked. Technical staff should select articles with complete translations, missing translations, and changed URLs, then check the rendered pages and actual redirect results. If navigation relies on scripts, ensure that article links still have actual URLs that can be crawled, rather than relying solely on click events.

The checks can be narrowed down to four areas:

• Do in-body links, related content, and conversion links lead to pages in the correct language and market?
• Does language switching preserve the article relationship, and is there a clear notice when a translation is missing?
• Are canonical and hreflang consistent? Do their targets return a normal page directly, and are they indexable?
• When a translation is published, taken down, or renamed, are associated links, caches, and sitemaps updated accordingly?

You can retain an option for users to actively select a version recommended according to their browser language. Forced redirects based on IP or browser language, however, can interfere with access and crawling. In particular, check whether recipients can still open the corresponding content when a user copies and shares a URL in a specific language.

A maintainable implementation should remove the corresponding language switcher option and hreflang declaration when a translation is taken down, and restore the relationship when the translation is added. During evaluation, ask the service provider to complete both steps on the spot, then observe whether the page, in-body links, and annotations are all updated together. This will show whether link localization has been integrated into the content management workflow.