Hello dear community! I’m running a multilingual Discourse forum in English, Russian, and Italian using Content Localization with content_localization_crawler_param enabled. AI translations are working well. Crawlers receive translated content via ?tl=, and the forum correctly outputs hreflang tags for those URLs. However, on translated pages like ?tl=ru, the canonical still points to the base URL instead of to itself. That seems to create an SEO conflict. Google’s hreflang documentation says not to canonicalize to a page in a different language, and many SEO sources say hreflang on non-canonical pages may be ignored. So the concern is simple: ?tl=ru is treated as a duplicate only the base URL is canonical the Russian page is not indexed as its own page so its hreflang may have no practical effect My main question is: Is the intended goal of Content Localization + crawler param to let translated pages rank in Google for their respective languages? If yes, shouldn’t ?tl= pages use self-referencing canonicals? If not, then what is the purpose of outputting hreflang tags and serving translated crawler content on those URLs? For comparison, Reddit uses a similar ?tl= approach, but their translated pages appear to use self-referencing canonicals, which is why they can rank in local-language search results.

Hey, agree with you. Each language variant should be self-canonical. We’ll have a look.

We’ve added a fix - FIX: Self-canonicalize tl= translated pages by nattsw · Pull Request #39494 · discourse/discourse · GitHub - and it’s available in our newest build. You can update your site - we’ll also be monitoring here for meta.

Great! So if I just update the discourse from the admin panel, I will get this fix in my Dicourse? Is this correct?

Le pagine tradotte non possono essere classificate su Google. Uccise dal CANONICAL. Localizzazione dei contenuti + ?tl=

Assistenza prodotto

nat (Natalie T) 24 Aprile 2026, 7:07am 7

Sì, è corretto.

Argomento		Risposte	Visualizzazioni
Translated pages (?tl=) not indexed by Google due to canonical tag pointing to original URL instead of self-referencing Product Support content-localization	2	179	Marzo 9, 2026
AI translations + crawler indexing = any SEO payoff? General content-localization	3	350	Luglio 1, 2026
?tl parameter behaving oddly Bug content-localization	4	327	Novembre 11, 2025
Does Discourse support ChatGPT or Gemini AI translations? Product Support translator , ai	5	455	Giugno 26, 2024
Content Localization and Automatic Translations for Your Community Announcements ai , dynaloc , content-localization	25	3652	Settembre 1, 2025

Le pagine tradotte non possono essere classificate su Google. Uccise dal CANONICAL. Localizzazione dei contenuti + ?tl=

Argomenti correlati