Short answer: publish each translated Umbraco variant at its own stable URL, render a self-referencing canonical and the correct language metadata, connect equivalent variants with reciprocal hreflang, and include only indexable language URLs in the sitemap. Translation creates the content; the front end still has to expose it correctly to search engines.
Does translating content automatically make it rank?
No. Search engines must be able to crawl a distinct URL, understand its language and recognise its relationship to the other variants. A translated value hidden behind a selector on one URL, loaded only after interaction or canonicalised back to English may never become an independent search result.
Choose a stable URL strategy
| Pattern | Example | Considerations |
|---|---|---|
| Language folders | example.com/de/produkte/ | Simple to operate on one domain and commonly suitable for Umbraco variants |
| Subdomains | de.example.com/produkte/ | Clear separation but additional hosting, verification and authority considerations |
| Country domains | example.de/produkte/ | Strong market separation with greater operational and domain overhead |
Whichever pattern is selected, keep it predictable. Avoid using cookies or browser language as the only route to translated content, because crawlers and shared links need a durable address.
Use the correct canonical URL
Each substantially translated page should normally canonicalise to itself. Do not point every language variant at the original English page: that tells search engines the translated URL is a duplicate candidate rather than the preferred page for its audience.
Canonical URLs should match the protocol, hostname, path and trailing-slash convention used in navigation and the sitemap.
Connect equivalent pages with hreflang
Add one hreflang entry for each published equivalent, including the current page itself. Every member of the set should return the same reciprocal set. Use valid language or language-region codes such as en, en-GB, de or fr-CA.
<link rel="alternate" hreflang="en-GB" href="https://example.com/en/products/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/produkte/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/" />Google's localized-version guidance covers the supported implementation methods and reciprocity rules.
Translate the complete search result
For each published culture, render an appropriate:
- HTML
langattribute; - page title and meta description;
- H1 and visible headings;
- navigation and breadcrumb labels;
- Open Graph locale and social copy;
- image alternative text when its meaning changes by language; and
- structured data whose visible claims match the translated page.
Build a language-aware sitemap
Include canonical, indexable language URLs. Do not list drafts, redirects, error pages or variants that intentionally use noindex. A sitemap can also carry alternate-language relationships, although HTML annotations are often simpler to inspect during development.
What should be tested before launch?
- Every language URL returns a successful response without requiring a cookie.
- The page source contains the intended language, title, canonical and alternates.
- All
hreflangreferences are reciprocal and resolve successfully. - Language switcher links point to the equivalent page where one exists.
- The sitemap contains the same canonical URLs used by the pages.
- Fallback content is intentional and does not create thin mixed-language pages.
- Google Search Console is configured for monitoring indexing and international URLs.
Common questions
Should translated pages use the English canonical?
No, not when they are genuine localized pages intended for search. Use self-referencing canonicals and connect equivalents with hreflang.
Does Diplo Translator Omni add hreflang?
No. Omni translates and manages Umbraco content variants. Public routing, canonical links, language selectors and hreflang belong to the website's front-end implementation.
Do language variants need different URLs?
They need independently crawlable URLs if each variant should appear as its own search result. The exact folder, subdomain or domain pattern is an architectural choice.
Build the content foundation first
Start with the multilingual Umbraco setup guide, then use the post-launch maintenance workflow to keep indexed languages current.