# Duplicate Content

**URL:** https://meta.discourse.org/t/duplicate-content/91745
**Category:** WordPress
**Created:** [July 7, 2018, 12:16am UTC](https://meta.discourse.org/t/duplicate-content/91745 "2018-07-07T00:16:19Z")
**Posts on this page:** 14
**Page:** 2

<div class="post-metadata">

### Author: ![haydenjames](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/haydenjames/32/255678_2.png) [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [April 12, 2022, 2:19pm UTC](https://meta.discourse.org/t/duplicate-content/91745/23 "2022-04-12T14:19:03Z")

</div>

Prefect! Thanks for confirming. I will setup after a bit more research on any impact on seo for blog articles.t

---

<div class="post-metadata">

### Author: ![haydenjames](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/haydenjames/32/255678_2.png) [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [April 15, 2022, 8:02pm UTC](https://meta.discourse.org/t/duplicate-content/91745/24 "2022-04-15T20:02:26Z")

</div>

Ok I got that working.

Now, if I enable the **“Use Full Post Content”** setting, will that get rid of the canonical links?

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [April 16, 2022, 8:16am UTC](https://meta.discourse.org/t/duplicate-content/91745/25 "2022-04-16T08:16:26Z")

</div>

No, it just sends all of the post HTML instead of an excerpt. It has no effect on the canonical link.

---

<div class="post-metadata">

### Author: ![Andrew\_Kirkcaldy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andrew_kirkcaldy/32/378293_2.png) [@Andrew\_Kirkcaldy](https://meta.discourse.org/u/Andrew_Kirkcaldy)
#### Post date: [April 12, 2024, 10:54am UTC](https://meta.discourse.org/t/duplicate-content/91745/26 "2024-04-12T10:54:19Z")

</div>

Thanks for sharing all your insights. I would love to know from people have implemented this what impact it has had on SEO.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [April 12, 2024, 1:19pm UTC](https://meta.discourse.org/t/duplicate-content/91745/27 "2024-04-12T13:19:17Z")

</div>

Nothing. There is no duplicate content situation. It doesn’t increase SEO either.

---

<div class="post-metadata">

### Author: ![Andrew\_Kirkcaldy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andrew_kirkcaldy/32/378293_2.png) [@Andrew\_Kirkcaldy](https://meta.discourse.org/u/Andrew_Kirkcaldy)
#### Post date: [April 19, 2024, 10:02am UTC](https://meta.discourse.org/t/duplicate-content/91745/28 "2024-04-19T10:02:18Z")

</div>

@Jagster Thanks for coming back to me on this. With the recent update from Google with pushing discussions and perspectives we are looking at building engagement behind each article.

I did have a question re: implementation of this. When I enable the embed URL Canonical the Source code shows the WP Post URL but when I review the page via the Inspect tool / Canonical checker tool it shows the Forum URL. It looks like there is something happening when the page is rendering.

I am concerned that this will lead to duplicate content.

Any insight into what is going on?

thanks

---

<div class="post-metadata">

### Author: ![haydenjames](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/haydenjames/32/255678_2.png) [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [November 10, 2024, 11:10pm UTC](https://meta.discourse.org/t/duplicate-content/91745/29 "2024-11-10T23:10:04Z")

</div>

Turned out to be a thread hijack. Will start a new topic.

---

<div class="post-metadata">

### Author: ![tyler.lamparter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler.lamparter/32/485862_2.png) [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [February 6, 2025, 7:19pm UTC](https://meta.discourse.org/t/duplicate-content/91745/30 "2025-02-06T19:19:27Z")

</div>

@Andrew_Kirkcaldy did you figure this out? We’re testing this out and the SEO tool we’re using isn’t saying the Canonical is set. When I look at the page source, it looks like it’s maybe due to the head containing `<meta property="og:ignore_canonical" content="true" />`. I added a head override to set it to false, but then both true and false are there so I’m assuming true is prevailing. It looks like I can’t remove the other head tag without some javascript.

 ![The image shows a blog post titled "Streamlining EDI integration with Celigo's 2B2B Manager" on the CeligoConnect website, with an SEO tool showing a summary, SEO metrics, and analysis on the page's elements. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/7/a/c/7ac15beb649c376e1a6d96fb2e9d521ff80a7518.png)  
 ![The image shows a code snippet displaying HTML head elements, specifically a "meta color-scheme" attribute, viewport settings, and two links for "search" and "walkthrough," including their respective URLs and attributes. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/c/1/8/c1878708f2303bd81748b1d2aa52ac7047c9ee75.png)

 ![The image displays a code file containing HTML meta tags with content and data attributes that reference a web assets connection, including meta properties like "og:title" and "og:image," as well as host and application settings. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/9/d/5/9d5f0f03fa689a046872ed2101ba9562616332c4.png)

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 6, 2025, 8:35pm UTC](https://meta.discourse.org/t/duplicate-content/91745/31 "2025-02-06T20:35:49Z")

</div>

Hey there @tyler.lamparter, can you confirm the following?

1. You’re using the [WP Discourse](https://github.com/discourse/wp-discourse) Plugin to publish articles from Wordpress to Discourse.
2. You want the Wordpress article to be the canonical link.
3. The site setting `Embed set canonical URL` is set to true.

---

<div class="post-metadata">

### Author: ![tyler.lamparter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler.lamparter/32/485862_2.png) [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [February 6, 2025, 8:50pm UTC](https://meta.discourse.org/t/duplicate-content/91745/32 "2025-02-06T20:50:36Z")

</div>

@angus

1. We haven’t installed the plugin for WP just yet because I wanted to validate this would work before we installed it. What I did to test was set the `embed_url` [via api](https://docs.discourse.org/#tag/Topics/operation/createTopicPostPM) when creating a topic. I assume doing it this way wouldn’t make a difference?
2. Yes, that is correct.
3. Yes, this is enabled.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 7, 2025, 7:22am UTC](https://meta.discourse.org/t/duplicate-content/91745/33 "2025-02-07T07:22:06Z")

</div>

Thanks for confirming that.

> [@tyler.lamparter](#):
>
> I assume doing it this way wouldn’t make a difference?

If you’ve used the API appropriately it won’t make a difference. If a topic has a `topic_embed` record and the site setting `Embed set canonical URL` is true, then the canonical url will be the topic embed url.

> [@tyler.lamparter](#):
>
> it looks like it’s maybe due to the head containing `<meta property="og:ignore_canonical" content="true" />`

This is a custom open graph tag that was invented by Discourse to improve oneboxing between different Discourse instances. It’s not going to impact the canonical url vis-a-vis SEO because it won’t mean anything to any other platform besides Discourse.

In your screenshot of the HTML I see that the canonical URL is indeed being set correctly. Perhaps the tool you’re using needs to be configured or used differently?

---

<div class="post-metadata">

### Author: ![tyler.lamparter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler.lamparter/32/485862_2.png) [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [February 7, 2025, 5:04pm UTC](https://meta.discourse.org/t/duplicate-content/91745/34 "2025-02-07T17:04:44Z")

</div>

> [@angus](#):
>
> Perhaps the tool you’re using needs to be configured or used differently?

I was thinking that as well. Do you have another tool you use to check SEO metadata on webpages? Or another way we can verify this is working as it should.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 8, 2025, 7:52am UTC](https://meta.discourse.org/t/duplicate-content/91745/35 "2025-02-08T07:52:33Z")

</div>

If the canonical link is in the HTML, it is working. You have already verified it is working as it should 🙂

I don’t mean to be difficult. I do appreciate that SEO is a sensitive and important question for many sites.

However, an SEO tool is just going to do the same check you’ve already done. It’s not going to tell you anything more than what you already know.

---

<div class="post-metadata">

### Author: ![tyler.lamparter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tyler.lamparter/32/485862_2.png) [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [February 8, 2025, 3:40pm UTC](https://meta.discourse.org/t/duplicate-content/91745/36 "2025-02-08T15:40:11Z")

</div>

You’re not being difficult 🙂, I’m just being cautious. Thank you for confirming!

[Previous page](https://meta.discourse.org/t/duplicate-content/91745.md?page=1)
