Where exactly does the canonical tag go in WordPress?

Inside the head section of every page you want it to apply to. In practice that means the element is rendered by your theme's header.php, by a wp_head hook in a child theme, or by an SEO plugin that injects it into the head for you.

Should I use a plugin or edit header.php directly?

Use a plugin if non-technical editors need to change canonicals per post, and edit header.php (in a child theme) if you want one stable site-wide canonical with no plugin dependency. Both approaches produce the same final HTML.

Can I use a relative URL in the canonical tag?

It is strongly discouraged. Search engines may resolve the relative path against the wrong host, including a staging or development domain. Always use an absolute URL with http or https, the host, and the path.

What happens if I have more than one canonical tag on a page?

Crawlers are inconsistent when they see conflicting signals. Most will ignore all of them or pick one arbitrarily. Always serve exactly one rel=canonical element per page.

Does the canonical tag remove duplicate pages from search results?

It consolidates signals so search engines treat the preferred URL as the master and attribute links and rankings to it. The duplicates may still be crawled, but they will not compete with the canonical page in search results.

How is this different from a 301 redirect?

A 301 redirect sends visitors and crawlers to the preferred URL automatically. A canonical tag is a hint for crawlers only and does not affect what human visitors see. Use a redirect when you want to retire the old URL and a canonical when both versions need to remain live.

How to Create a Canonical Tag in WordPress: A Practical Guide

A canonical tag in WordPress is a single HTML <link rel="canonical" href="https://example.com/preferred-page/" /> element placed inside the document <head> that tells search engines which absolute URL is the master version of a page you want them to index. The element is one line, it lives in the head, and it must point to an absolute HTTP or HTTPS URL with the correct host, path, and any intentional query string, with fragments such as #section removed before the tag is generated. Because WordPress often serves the same content under several URLs (with and without trailing slashes, with and without www, with tracking parameters, or through category and tag archives), the canonical tag is the cleanest way to consolidate duplicate signals into one preferred address.

Most WordPress installations end up with duplicate or near-duplicate URLs in search results because the platform allows the same post to be reached through multiple paths. A single post can appear at /post-name/, /category/news/post-name/, /?p=123, and any number of campaign-tagged variants. Without a clear canonical signal, crawlers may pick any one of those addresses as the canonical themselves, which fragments link equity and dilutes ranking potential. That is why Canonical Tag Generator exists: it turns a single preferred URL into a ready-to-paste, HTML-escaped rel=canonical link element that follows browser-standard normalization rules and strips fragments, so the same canonical element behaves predictably regardless of which WordPress editor or SEO plugin you use to deploy it.

how to create canonical tag in wordpress

What the Canonical Tag Generator Produces

The tool accepts one absolute URL and outputs one HTML link element. Behind the scenes it runs the input through the same kind of normalization a browser applies when resolving a URL: lowercasing the host, removing default ports, collapsing path dots and slashes, sorting query parameters, and stripping any fragment. The result is wrapped as <link rel="canonical" href="..." /> with all attributes HTML-escaped so the element can be pasted directly into header.php or a plugin field without breaking markup.

Two design choices matter for WordPress users in particular. First, the tool refuses relative URLs, so you will never accidentally emit href="/post-name/" and discover later that search engines treated your staging host as canonical. Second, the fragment strip means a deep-linked #faq from a marketing email does not leak into your canonical signal — only the clean page URL is preserved.

Generating Your Canonical Tag

Open the Canonical Tag Generator and enter the complete preferred URL, including http:// or https://, the host, the path, and any query string you intentionally want indexed.
Generate the tag and read the normalized version the tool displays alongside the output, then compare it character-for-character against the live 200 page you actually want search engines to prefer.
Copy the generated <link rel="canonical" ... /> element so it sits on one line of escaped HTML ready for the head section.
Paste the element into the head of the relevant WordPress template — for site-wide coverage, the canonical can be set in header.php or through a child theme hook, or supplied per page by an SEO plugin field.
Load the live page in a browser, view source, and confirm there is exactly one rel="canonical" link element whose href matches the normalized URL you generated.

Placing the Tag Inside WordPress

WordPress gives you four realistic paths to deploy the generated element, and the right one depends on whether you want one static canonical for the whole site, per-post control, or theme-level logic. For a static canonical across every page, edit a child theme copy of header.php and paste the element directly above <?php wp_head(); ?>, or use a small wp_head hook in functions.php that echoes the link with esc_url() applied to the href. For per-post control, popular SEO plugins expose a canonical field in the post editor; paste the generated href there and the plugin wraps it into the head on your behalf.

If you prefer to keep logic in code rather than rely on a plugin, a minimal filter is enough. The pattern below accepts whatever URL you store in a custom field called _canonical_url and emits a single escaped link element through wp_head, falling back to rel_canonical() only when no override is set. Keep the function in a child theme so theme updates do not erase it, and remember that only one canonical element should ever appear in the head.

Comparing Deployment Methods

The table below compares the three common ways to ship a canonical tag in a WordPress site so you can pick the one that fits your maintenance habits and how often your preferred URLs change.

Method	Where the URL lives	Best for	Effort to change one URL
Edited child theme header.php	Hard-coded line in template	Single preferred URL across the whole site	Edit the file and redeploy
wp_head hook in functions.php	Custom field or option in the database	Programmatic per-post logic with fallback	Update the field or option value
SEO plugin canonical field	Post meta inside the plugin's table	Editors who want a UI and per-post overrides	Edit in the post editor screen

If you maintain a lot of legacy URLs and run marketing campaigns, the per-post method gives the most flexibility; if your site is small and you simply want one canonical host signal, the edited header file is the lowest-overhead choice.

Verifying the Tag After Deployment

Generating the tag is half the job — confirming the served HTML matches your intent is the other half. Open the live URL in a desktop browser, choose View Source, and search the document for rel="canonical". There should be exactly one match, and the href attribute should equal the normalized URL the tool showed you. If your site is behind a cache plugin, purge the cache for that URL before re-checking, otherwise you may be inspecting a stale copy.

For a larger site, crawl a representative sample of pages and assert that every canonical href points to a 200 response on the same host. Mixed http and https canonicals are one of the most common audit findings, so pay particular attention to the scheme. Canonical targets that return 404, redirect, or change host are functionally no canonical at all, because crawlers will either ignore the signal or pick a different URL on their own.

Common WordPress Scenarios That Need a Canonical Tag

Several situations in WordPress routinely produce duplicate content without a manual canonical. Paginated archives, tag and category listings that show full post text, attachment pages for every uploaded image, and search result pages can all index independently. A site-wide canonical set to the post permalink (or to the first page of an archive) gives crawlers a default; per-post overrides handle the exceptions.

Campaigns that append UTM parameters are another frequent culprit. If you build trackable campaign links with a tool such as the UTM Link Builder, the destination URL is the same page but the address bar differs. A canonical tag that strips query parameters keeps the underlying article as the master version, while your analytics still see the tagged variants. Similarly, if you publish syndicated content and want to point crawlers back to the original, the canonical element is the cleanest way to do it without hiding the post from readers.

Pairing the Canonical Tag With Broader SEO Hygiene

The canonical tag is one signal among several. It works best when paired with an XML sitemap that lists only your preferred URLs, a robots.txt that does not accidentally block the canonical target, and a robots meta tag that does not contradict the canonical instruction. If you maintain an XML sitemap alongside your canonicals, keep the URL list in the sitemap in lockstep with your canonical hrefs so the two never disagree.

For sites that publish in multiple languages, a canonical tag handles duplicate versions within the same locale, but cross-locale duplicates belong in hreflang alternates rather than in canonical tags. The Hreflang Generator covers that adjacent case; using both signals correctly is how search engines understand which URL is preferred inside a single language and which alternatives exist across languages. The MDN documentation on the canonical link relation is a good reference for the exact attribute semantics if you want to confirm the behavior you are implementing.

Final Checklist Before Publishing

Before you consider the canonical tag done, walk through five quick checks: the generated href is an absolute URL with the same scheme and host as the live page; the href matches what appears in your XML sitemap; there is exactly one rel="canonical" element in the served head; the canonical target returns a 200 response; and any hreflang alternates on the same page reference URLs that themselves point back via their own canonical elements. When all five pass, the signal is consistent and search engines can collapse duplicates onto the address you actually want ranked.

For a deeper look, see How to Check Hreflang Tags for Multilingual SEO Accuracy.

For a deeper look, see Create a Secure .htaccess File for HTTPS and Custom 404 Pages.

For a deeper look, see How to Extract a Link From an Excel Cell: Practical Methods.