Modifier le code ISO de la langue sur une seule page

On my forum we have created a section for Chinese Posts. Everything is working as desired, however the ISO code for the pages still shows English as that is the site setting. Does anyone know if there is a way we can set the category or individual pages to show that they are a different language?

Interesting, what are your thoughts on this @sam

I have not been able to see a way to change this in the existing software. Anyone have an idea if this could be built? I think it could help with traffic on our site as well as many others that have additional languages on one instance. Any direction would be helpful!
-Robert

Not that I’m an expert or anything, but shouldn’t that be possible with JavaScript or something similar?

I agree that it should be possible. I am trying to find a solution or suggestion on how I might implement this as we have multiple languages and I am not sure how I change the language code when someone posts in the Chinese category, however leave it as english when in the other categories. I also want to make sure this is not going to cause any issues elsewhere if we try to implement it. I know there are other forums that run multiple languages, however it looks like all the ones that run more than one language all show an “en” source code when you look at non english pages. Only the forums that are based in another language change. From my limited understanding this will mean that information is harder to find on google and if an english speaking person finds my chinese content google will not offer to translate as it shows english.
-Robert

Unfortunately this isn’t a built-in feature of Discourse. Theme components (javascript) wouldn’t work either, because the page language is set way before any javascript is loaded.

Having separate languages per-category would technically be possible using a plugin. This would work for crawlers like google, and would also trigger browser auto-translation features.

One issue with this is that Discourse is a ‘single page application’, and browsers only seem to check the lang attribute on the initial page load. That means that a user browsing the forum will be ‘stuck’ on the language of the first page they viewed. That may or may not be an issue depending on your use case.

I think the SEO and initial translation benefits of seeing it on a search would outweigh any issues I am seeing once on the forum. I am certainly interested in speaking with someone on what it might take to get this made and what it would look like currently and what might be needed if in the future we add more languages. Would the plugin be set per category or per post etc.
-Robert

Having done some further experimentation, this might not be completely true. Googlebot does render simple javascript when crawling the web, so we should be able to use javascript to modify the language.

To change the language for topics in a specific category (and its sub-categories), you can add something like this to the </head> section of a theme:

<script>
	if(document.querySelector("#breadcrumb-0 a[href='/c/chinese']")){
		document.documentElement.lang = "zh"
    }
</script>

I can’t find any specific documentation from google about whether this is acceptable, but I can see that it works when I “fetch as googlebot”:

@Robert_Fay let us know if you would like a hand adding this to your site.

I’m a bit confused, in looking at the code, there is no #breadcrumb-0 on our page.
image

image

I had tried using

<script>
if(document.querySelector("a.bullet[href='/c/chinese']")){
	document.documentElement.lang = "zh"
}
</script>

but that didn’t seem to do the trick. I have a feeling those elements are loaded later, because the code works in in the browser console, but not in a component /head. Any pointers?

This code is specifically for the crawler view of the site which googlebot sees. It has a different html structure to the regular view.

If you change your browser’s user agent to googlebot then you will see it take effect.

David,

I am still not seeing the change even as google bot. Could the issue be that my category name is actually 中文 技术论坛 and we use chinese as a category slug? Here is the page

 https://forum.digikey.com/c/chinese

中文 技术论坛 - Engineering and Component Solution Forum - TechForum │ Digi-Key
Thank you
-Robert

Ah, I should have specified that the code needs to go in the </body> section of the theme. Alternatively, you can leave it in the </head>, and wrap it like this:

<script>
    document.addEventListener('DOMContentLoaded', function(){
    	if(document.querySelector("#breadcrumb-0 a[href='/c/chinese']")){
    		document.documentElement.lang = "zh";
    	}
    });
</script>

If you would also like the <html lang= to be updated for non-googlebot views, you can add this. Google chrome doesn’t seem to detect the ‘live’ change in language, but other browsers might:

<script type="text/discourse-plugin" version="0.8">
    api.onPageChange(()=>{
        const body = document.documentElement.querySelector("body");
        if(body.classList.contains("category-chinese")){
            document.documentElement.lang = "zh";
        }else{
            document.documentElement.lang = I18n.locale;
        }
    });
</script>

This is in and looks like it is working in the googlebot views.
Thank You for all the help!
-Robert

Bonjour @david

Lors d’un audit récent, j’ai remarqué que ce bout de code pour nos catégories chinoise, espagnole et hébraïque ne fonctionne que de manière intermittente. Les seules pages sur lesquelles il fonctionne affichent désormais une erreur dans notre console. Les pages sans erreur apparaissent maintenant comme des pages en anglais dans le moteur de recherche.

Avez-vous des idées ?

Voici l’erreur.

Code de la catégorie chinoise utilisé.

<script>
    document.addEventListener('DOMContentLoaded', function(){
    	if(document.querySelector("#breadcrumb-0 a[href='/c/chinese']")){
    		document.documentElement.lang = "zh";
    	}
    });
</script>

Une petite remarque. Lorsque je réalise un test en direct sur les pages comportant des erreurs, celles-ci disparaissent. Cependant, elles passent alors d’une page affichée en chinois ou en espagnol à une page affichée en anglais.

  • Robert

L’avertissement data-vocabulary.org devrait être résolu dans la dernière version de Discourse selon

Votre site dispose de cette mise à jour, nous devons donc simplement attendre que Googlebot se mette à jour. Comme vous l’avez constaté, effectuer un test en direct résoudra l’avertissement.

Malheureusement, cette restructuration des filières a brisé le petit script de langue que nous avions créé. Les filières n’ont plus l’identifiant #breadcrumb-0, nous avons donc besoin d’autre chose. Je pense que ceci devrait fonctionner :

<script>
    document.addEventListener('DOMContentLoaded', function(){
    	if(document.querySelector("#breadcrumbs a[href*='/c/chinese']")){
    		document.documentElement.lang = "zh";
    	}
    });
</script>

Faites-moi savoir si cela résout le problème lors d’un test en direct.

Cela semble avoir résolu le problème pour les éléments de la catégorie chinoise, mais les sous-catégories ne fonctionnent pas. Devrais-je en créer une séparée pour mon /c/chinese/FAQ, par exemple ?

-Robert

Hmm, cela devrait fonctionner pour les sous-catégories aussi. La récupération de ce sujet en tant que Googlebot me renvoie les métadonnées lang=zh.

Est-il possible que Google ait mis en cache le sujet que vous avez essayé ? De plus, rappelez-vous que ce script ne fonctionne que sur les sujets, pas sur les pages de catégories elles-mêmes.

Je ne suis pas sûr de ce qui s’est passé lors du premier test. J’ai créé quelques pages de sous-catégories supplémentaires et elles fonctionnent.

Merci encore pour votre temps.
-Robert

Bonjour @david,

J’ai examiné notre site avec mon équipe SEO et il semble que ces éléments ne fonctionnent plus.

Exemple de publication dans notre catégorie allemande :

Lorsque j’examine la page explorée dans la Google Search Console, elle s’affiche en anglais.

Voici le code que j’utilise actuellement :

<script>
    document.addEventListener('DOMContentLoaded', function(){
    	if(document.querySelector("#breadcrumbs a[href*='/c/german']")){
    		document.documentElement.lang = "de";
    	}
    });
</script>

Toute aide ou orientation serait appréciée.
-Robert