Give each language version a clear, durable place.
An international website needs useful translations and URL rules that match the content. ImbaHub can map language paths, equivalent pages, canonical, hreflang and internal language links, documenting exceptions where a translation does not exist.
Start with the actual relationship between pages
A URL list does not show which pages are true translations of one another. Record each page ID, language, purpose and language-switch destination. If a translation is missing, do not connect it to a page that merely sits nearby in the navigation.
Google describes hreflang as a way to identify localized page versions. Each page should list itself and its genuine alternatives, and those pages should link back to one another. An accurate content map is therefore part of the technical implementation.
Keep canonical and hreflang consistent
Each indexable language version would normally have a canonical pointing to its own preferred URL. Hreflang identifies language alternatives; canonical identifies a preferred address among similar or overlapping URLs. Do not canonicalise an English or Spanish page to Swedish.
Language codes should match the language and, when appropriate, region. ImbaHub uses sv-SE, nb-NO, da-DK, es-ES and en. Use fully qualified URLs and verify that each one reaches the intended page without an unintended redirect chain.
Apply one consistent URL model
Swedish remains directly on imbahub.com. Norwegian uses /no/, Danish /da/, Spanish /es/, British English /en/ and American English /us/. Each market owns its canonical address; only genuine equivalent topics share hreflang references.
Define what the selector does when a translation is missing. It may use a clear fallback to the selected language’s homepage, but hreflang should connect only pages that genuinely correspond.
Check markup and the visitor journey
Review the HTML head, sitemap and selector on desktop and mobile. Verify self-referencing canonical, reciprocal hreflang, the intended destinations and that switching language does not send someone to an unrelated topic. Pages should also be discoverable through crawlable HTML links.
A scoped engagement may include a URL matrix, technical checks and a record of missing translations. Rankings and AI citations cannot be guaranteed; localization, content and search-engine interpretation also matter.
| Check | Ready when |
|---|---|
| Page equivalent | The topic and user task correspond across languages |
| Canonical | Each language points to its own preferred URL |
| Hreflang | Alternatives are genuine, complete and reciprocal |
| Selector | Leads to the equivalent page or a documented fallback |
Sources and further reading
Questions, answered
Should every translation have hreflang?
Only genuine equivalents should be linked. A false relationship does not improve the setup.
Is using the same layout across languages duplicate content?
No. A shared design is normal. The main content still needs accurate translation and localization.
Can a blank page be generated for the language selector?
No. Do not create a false translation. Use a clear fallback and add the page when its own content is complete.