A WordPress canonical URL indicates the address you consider the primary version of content. It is expressed by a tag placed in the page’s HTML head: <link rel="canonical" href="https://exemple.com/page/" />.
This signal becomes useful when the same page is reachable by multiple addresses. For example, a URL can contain a tracking parameter, use HTTP instead of HTTPS, or exist with and without www. Google then groups identical or very similar pages and chooses a canonical version. Your tag is a strong signal, but it remains a preference: Google may choose a different URL if other signals conflict.
The goal isn’t to add a canonical everywhere at random. You must verify that the declared address truly corresponds to the page you want indexed and shared.
What WordPress adds by default
Core WordPress outputs a tag rel="canonical" for singular requests, such as posts, pages, and custom post types. The native function rel_canonical() retrieves the canonical URL of the displayed object and writes it into the page’s code.
However, your theme, an SEO plugin, or a code snippet may modify this behavior. That’s why it’s not enough to assume WordPress sends the correct signal. Always check the HTML actually delivered to the visitor.
How to check a page’s canonical URL
First inspect the source code
Open the public page in your browser, then view its source. Search for rel="canonical". You should find a single canonical tag in the <head>.
Copy the address shown in href and compare it to the desired URL. Check every element: HTTPS protocol, presence or absence of www, path, slug accents, trailing slash, and any parameters.
- The homepage should generally declare its own full address.
- A truly duplicate variant may declare the primary address.
- A tag that points to a 404 page, a redirect, or another unrelated page must be corrected.
- Two different canonical tags often indicate a conflict between the theme, a plugin, or custom code.
Google recommends an absolute URL in this tag and specifies it should be placed in the HTML head. The documentation on duplicate URL consolidation also recommends a self-referencing canonical on the main page.
Then check the URL in Search Console
The source code shows your declared canonical. Google Search Console shows what Google kept after crawling and processing.
In the URL Inspection tool, check the Indexing section. Compare «User-declared canonical URL» and «Google-selected canonical URL.» If they match, your signals are consistent. If they differ, don’t change the tag immediately: start by understanding why Google prefers the other address.
Google specifically advises using the URL Inspection tool, checking for technical issues, and confirming that grouped pages are sufficiently different when they should be indexed separately. See its guide to resolve canonicalization issues before requesting reindexing.
If your property isn’t set up yet, follow this guide first to adding your WordPress site to Google Search Console.
Most common incorrect signals
Inconsistent URL settings and internal links
Parameters like ?utm_source= can lead to the same content as the clean URL. In that case, the parameter-free version is often the right canonical candidate. Sorting and filtering functions can also create multiple URLs for the same content.
However, don’t force a canonical to the base page if the parameter actually changes the product list, displayed content, or the visitor’s intent. Compare what each URL returns before grouping them.
Next, fix navigation links, in-article links, and links added by your templates. They should point to the chosen URL. Google says consistent internal links help clarify your canonical preference. A stable structure also starts with clear and consistent WordPress permalinks.
HTTP, HTTPS, www and domain variants
Choose a single public version of the domain. For example, avoid having http://, https://, www and non-www all return a 200 response for the same page.
Set the chosen address in WordPress, then apply permanent redirects from the variants to that address at the appropriate hosting or delivery level. The canonical tag complements this work, but it doesn’t replace a redirect when an old variant should no longer be accessible.
Redirects, the canonical tag, and inclusion in the sitemap are signals that can reinforce each other. So check that your WordPress XML sitemap contains only the primary URLs, not their variants.
Pagination, translations and similar pages
An archive page 2 isn’t automatically a duplicate of page 1. It usually shows a different set of posts. So don’t point all paginated pages to the first page without confirming they present exactly the same content.
For a multilingual site, each substantially different translation should usually keep its own canonical URL. Language or regional versions also require annotations hreflang appropriate. Google recommends pointing the canonical to a page in the same language, or to the best alternative when one does not exist.
How to fix a canonical in WordPress
Before making any changes, identify the source generating the tag. Check the theme, active SEO plugins, and code snippets. Your goal is simple: a single rule should control a page’s canonical tag.
- Determine the primary URL that best meets the visitor’s needs.
- Ensure that this URL responds correctly, without unnecessary redirects or unwanted tag
noindexpresent. - Fix internal links, the sitemap, and redirects so they all support the same address.
- Remove the competing tag from the theme, plugin, or custom code that adds it.
- Clear site and CDN caches, then recheck the public source code.
With Yoast SEO, you can edit a canonical on a case-by-case basis in the editor’s advanced tab. The documentation from Yoast on editing a canonical URL asks you to enter the full address, including HTTPS and the www or non-www variant. Use this field only for a justified exception. For a normal page, let the plugin generate the self-referencing canonical.
Finally, re-inspect the important URL in Search Console. Re-evaluation can take time, even after a fix. Avoid making multiple changes during this period: stable, consistent signals give Google a better basis for selecting the correct URL.









