Canonical Tag Generator
Enter a URL to generate a valid rel="canonical" link tag for your page's <head>.
About the Canonical Tag Generator
Duplicate content shows up more often than expected, tracking parameters, session IDs, printer-friendly versions, and paginated listings can all serve the same content under different URLs. A rel="canonical" link tag tells search engines which of those URLs is the authoritative one, consolidating ranking signals instead of splitting them across near-identical pages.
Add one whenever a page could be reached more than one way, ?utm_source=... query strings, http versus https, www versus the bare domain, or a paginated series like /page/2 and /page/3 that all lead back to the same primary content.
A canonical tag is a hint, not a command
Unlike a 301 redirect or a noindex tag, which Google follows unconditionally, a canonical tag is treated as a strong suggestion Google can override if it disagrees with the stated authoritative URL, based on internal links, sitemap entries, and other signals that point somewhere else. A canonical tag that contradicts every other signal on a site, internal links pointing at one URL while the canonical points at a completely different one, is more likely to get overridden than followed. Keeping canonical tags, internal linking, and sitemap entries all pointing at the same URL gives Google one consistent signal instead of several conflicting ones.
Every page benefits from a self-referencing canonical
Even a page with no obvious duplicate is commonly given a canonical tag pointing at its own URL, this is standard practice specifically because URLs pick up query parameters unpredictably, a tracking parameter from a shared link, a session identifier from an e-commerce platform, an accidental trailing slash. A self-referencing canonical means any of those variants still consolidate back to the clean version automatically, rather than needing a rule written for every possible parameter combination in advance.
Why the URL has to be absolute
This generator requires a full URL starting with http:// or https:// rather than a relative path like /page, because the canonical spec calls for an absolute URL and inconsistent handling of relative canonicals across different crawlers has historically caused problems. Writing it out in full removes any ambiguity about which domain, and which protocol, is the intended canonical destination.
One canonical tag per page, no exceptions
A page with two conflicting canonical tags in its head, sometimes introduced accidentally by a CMS plugin stacking its own tag on top of a manually added one, doesn't average out to a compromise, Google generally ignores both when it detects a conflict and falls back to its own judgment about which URL is canonical. Checking a page's actual rendered HTML for a duplicate canonical tag is worth doing after adding one through a CMS, template, or plugin that might already generate its own.
Cross-domain canonicals, for syndicated content
A canonical tag doesn't have to point at a URL on the same domain, this is the standard way to handle syndicated content, an article republished on a partner site or news aggregator can carry a canonical tag pointing back at the original source, telling search engines to credit the original rather than treating the copy as a competing duplicate. This only works by agreement, the syndicating site has to actually add the tag pointing outward, there's no way to force it from the original publisher's side.
Canonical tags and pagination
A common mistake with paginated content, a blog archive split across /page/2, /page/3, and so on, is pointing every page's canonical back at page 1. That tells search engines the later pages don't have unique content worth indexing on their own, which can prevent posts that only appear on page 3 or 4 from being discoverable through that path at all. Each paginated page generally deserves a self-referencing canonical instead, since each one does contain genuinely different content, only a true duplicate, like a printer-friendly or tracking-parameter version of the same exact page, should canonicalize to something else.
Frequently Asked Questions
Does Google always follow a canonical tag?
Not always. Unlike a 301 redirect, a canonical tag is a strong hint Google can override if other signals, like internal links or sitemap entries, consistently point at a different URL. Keeping every signal aligned with the same canonical URL makes it far more likely to be followed.
Should a page with no duplicates still have a canonical tag?
Yes, this is standard practice. A self-referencing canonical protects against URL variants that appear later, tracking parameters, session IDs, or a stray trailing slash, all of which would otherwise need to be handled as separate cases without one already in place.
Why does this tool require a full URL instead of a relative path?
The canonical tag specification calls for an absolute URL, and relative canonical paths have historically been handled inconsistently across different crawlers. Writing the full URL, including https:// and the domain, removes any ambiguity about the intended destination.
What happens if a page has two canonical tags?
Google generally ignores both when it detects conflicting canonical tags on the same page and falls back to its own judgment instead. This can happen accidentally when a CMS plugin adds its own canonical tag on top of one already set manually, worth checking a page's actual rendered HTML for duplicates.
Should paginated pages all canonicalize to page 1?
Generally no. Each paginated page usually contains genuinely different content and deserves its own self-referencing canonical. Pointing every page back at page 1 signals that later pages aren't worth indexing separately, which can keep content that only appears on those pages from being discovered.