I was wondering the same thing about duplicate synchronized WP/Discourse content from this topic: https://meta.discourse.org/t/risk-of-duplicate-content-with-synchronized-wp-posts-discourse-topics/91737
But it got closed by Jeff Atwood saying there are already existing topics. I couldn’t find any topics that addressed this question. Please advise.
I searched before posting and I didn’t find any either, a bit confused. Maybe I didn’t use the right keywords?
It’s been brought up a few times, but I don’t think there is a topic dedicated to it. There is a topic on Feverbee that I contributed to: https://experts.feverbee.com/t/is-it-possible-for-the-feverbee-blog-posts-to-be-pulled-in-full/6192. It is possible to set the Canonical URL of a WordPress post so that it matches the Discourse topic. Beyond that, I don’t think there is anything the plugin can do about the duplicate content issue.
Covered here: Embedding Discourse Comments via Javascript
Maybe one year later: is there any other solution for the duplicate content issue?
Like add a canonical url in the discourse forum post or no-index the forum post.
Maybe 9 months later: this is something that keeps coming up with us too. We started posting only the excerpt to Discourse, but our members don’t like to be bounced back to the site to read the full article.
Well, you can’t have it both ways, so I’m not sure what you’re proposing here.
My proposal would be to offer some flexibility, so there is a choice of what type of community to make without getting dinged by Google for duplicate content:
The first option would require a canonical url pointing to the blogpost that is not on Discourse. The easiest way to offer this flexibility imho is an option to set the canonical url for a topic.
Yes, this is a thing. Google don’t like duplicate copies of articles.
Your options here seem pretty simple:
Right?
An embed set canonical url site setting was recently added to Discourse. When this setting is enabled, the canonical URL for topics that have an embed URL will be set to the topic’s embed URL. For sites using the WP Discourse plugin, enabling this setting will cause the canonical URL of any posts published from WordPress to be set to the WordPress post’s URL.
This turned out to work great. It was just not obvious to me how to create a topic with a canonical URL. After some experimentation I found out you have to enter the original URL as topic title.
@simon ¿Qué es exactamente una “URL de incrustación”? También he visto el término “temas incrustados”. Simplemente no estoy seguro de qué significan.
La URL incrustada es un atributo que se puede asociar con un tema. El plugin WP Discourse establece la URL incrustada en el permalink de la publicación de WP. Por lo tanto, si utiliza el ajuste del sitio embed set canonical url, el permalink de la publicación de WP será la URL canónica del tema de Discourse (es decir, aparecerá en el head como el enlace canónico).
Gracias. ¿El atributo embed_url solo se puede establecer mediante la API?
Sí, solo puedes configurarlo a través de la API. Es utilizado por varias funciones que implican la importación de contenido de un servicio de terceros.
¿cerrado o eliminado? ¿embed set canonical url resuelve completamente el problema de SEO de contenido duplicado?
Sí, lo hace si se usa correctamente. Por favor, revise lo anterior, en particular la publicación de Simon, y háganos saber si tiene alguna pregunta o problema específico.
Mi caso de uso sería crear discusiones en Discourse automáticamente desde WordPress usando el plugin de Discourse para WordPress con la opción embed set canonical url habilitada.
Una vez que conecto WordPress a Discourse y los nuevos temas se crean automáticamente, ¿tengo que hacer algo más además de habilitar esa opción embed set canonical url?
Sí, eso es todo lo que necesitas hacer.