Multilingual SEO for Web Developers Using Hreflang and Sitemaps
- May 15, 2023· Article by David Brown
- multilingual seo , hreflang
Many developers build a multilingual site, publish it and then wonder why the German pages never show up in German search results. Multilingual SEO is mostly technical hygiene: the right signals in the right place for every language. When those signals are missing or inconsistent, a perfect translation can stay invisible.
What search engines need to see
A search engine has to understand which page belongs to which language and which version to show to which visitor. The basics of search engine optimization still apply, but translated pages add a few signals of their own.
- Hreflang annotations tell the engine that several pages are versions of one another.
- Canonical links point to the preferred version of each page.
- Localized title tags and descriptions make results readable in the visitor's language.
- Per language sitemaps help crawlers find every version.
Each one is simple alone. Across hundreds of pages and several languages, the chance of a gap grows quickly.
Where multilingual projects go wrong
Common mistakes are easy to recognize. Titles stay in the source language. Hreflang points to pages that no longer exist. Canonical links send all versions to the English page, which tells the engine to ignore the rest. New pages are published in English and forgotten in other languages.
Most of these happen because the technical layer is handled by hand, after the translation, by someone with little time. Developers know the pain: a launch date, a long list of pages and a spreadsheet of tags.
Generating the signals automatically
Wordbeam treats search signals as part of multilingual SEO delivery and not an afterthought. Title tags, descriptions, hreflang and canonical links are localized and validated, so every language can rank on its own merits. Hreflang and canonical links are generated automatically, meta and Open Graph tags are localized, and per language sitemaps are submitted for you.
Search signals are only reliable when they are generated from the same source as the translation, not typed in by hand afterwards.
Serving your existing site
You do not have to rebuild the site to get these benefits. Wordbeam offers dynamic proxy translation: point a subdomain or subdirectory at the proxy and your existing site is served fully translated. It works with pages rendered by JavaScript and with single page applications, which covers many modern builds. Visual in page editing on a live preview lets reviewers fix wording where it appears.
Keeping up with change
Sites change daily. A scheduled crawler discovers new and changed pages and queues only the strings that actually moved. Translation memory fills repeats, so small edits do not trigger large translation jobs. The result is that translated pages stay current without a developer opening a ticket each time marketing changes a headline.
Structure choices that help
Developers can make decisions early that simplify everything later. Choose subdirectories or subdomains per language and keep the pattern consistent. Keep URL slugs readable in each language when it makes sense for users. Avoid redirecting visitors by location alone, because that can block crawlers and frustrate people who want another language. Offer a visible language switcher instead.
If you work with a JavaScript framework, our guide to Next.js i18n explains routing, message files and locale detection, and shows how the structure of a project supports clean hreflang output.
Quality that readers and engines notice
Search engines reward pages that people find useful, so poor translation is an SEO problem too. Wordbeam provides translation memory and a term base to keep wording consistent, real time quality checks for tags, numbers and syntax, and AI engines such as GPT, Claude, Grok and DeepL for first drafts that a person can review. Consistent keywords across pages also help each language build topical strength.
Reporting closes the loop. Track impressions and clicks per language in your search console, and compare them with the pages you translated first. If a language gets visibility but few clicks, the title and description probably need work, and those are quick to update because the strings live in one place.
Content planning benefits too. Once the technical base is stable, you can decide which new articles deserve translation based on real demand in each market, rather than translating everything by default and hoping for the best.
A short audit checklist
Before launch, open five pages in each language and verify the title, description, canonical link and hreflang set. Check that every language has a sitemap and that new pages appear in all of them. Compare a page in a live preview with the source to see whether layouts hold up. Fix patterns, not single pages, because the same gap usually repeats.
The 14 day free trial includes 10,000 words, which is enough to test a real section of a site end to end.
Multilingual SEO is not magic. It is a set of signals that must be correct and consistent, and automation makes them far easier to keep that way as your site grows.