The short version
- The same content at several URLs splits the ranking signals that should have pooled on one page.
- Every page should carry a self-referencing canonical pointing at itself — one line, and it protects you the moment a variant appears.
- A canonical is a hint, not an instruction. Google can ignore it if other signals disagree.
- The five common failures: pointing everything at the homepage, relative URLs, protocol mismatches, canonicalising to a redirect, and canonicalising a blocked page.
- Generate a correct tag free, with the usual mistakes flagged.
Why one page becomes six URLs
Take a single article. Now count the addresses it can be reached at:
https://example.com/articlehttps://example.com/article/— with the trailing slashhttps://www.example.com/article/— with wwwhttp://example.com/article/— if the old protocol still resolveshttps://example.com/article/?utm_source=newsletter— every time somebody shares a tagged linkhttps://example.com/article/?ref=partner&sessionid=x— whatever your platform appends
To a search engine those are six documents with identical content. The links pointing at them are divided six ways. The engagement signals are divided six ways. And the version chosen to represent the group is chosen by Google, not by you — frequently the one with a tracking parameter attached, because that is the one people shared.
Nothing is broken and nothing is penalised. Your page is just weaker than it should be, for reasons that never appear in any report.
What the tag actually does
<link rel="canonical" href="https://example.com/article/">, placed in
the head of every variant, says: this content should be indexed and credited as that
URL. Signals consolidate onto the canonical version, and that is the one shown in
search results.
Two properties are worth internalising, because most confusion comes from missing them.
It is a hint, not a command. Google treats it as a strong suggestion and weighs it against other evidence — internal links, sitemap entries, redirects. If everything else on your site points at a different URL, the canonical loses. Consistency is what makes it work.
It is not a redirect. The visitor stays exactly where they are. Both URLs continue to work and to serve content. That is precisely why it is the right tool when both URLs need to keep functioning — a print view, a tracked link, a syndicated copy — and the wrong tool when one of them should simply cease to exist.
The self-referencing canonical
The single most useful application, and the one most often skipped because it looks pointless. Every page carries a canonical pointing at itself.
It looks like a no-op. It is not, because it does its work later:
- Somebody shares your page with a UTM string attached, and that variant gets crawled. The canonical folds it back into the original.
- A scraper republishes your article. If they copy the head too — and lazy scrapers do — they have credited you.
- Your platform starts appending a parameter after an update. Already handled.
- Somebody links to you with the wrong trailing slash. Consolidated.
One line, written once per template, that removes an entire category of future problem. There is no page on which it is wrong.
Free tool · One line, done right
Get the tag right, including the parts people get wrong
Paste the URL you want indexed. The generator normalises it and flags the usual killers — http instead of https, tracking parameters left on, a trailing slash that does not match your site.
Five ways canonicals get written wrong
1. Every page pointing at the homepage
The most damaging, and it happens whenever a canonical is hard-coded into a shared template rather than generated per page. You are telling Google that every page on your site is a duplicate of your homepage, and that it should index none of them. Sites have lost almost all of their organic traffic to this single template bug.
2. Relative URLs
href="/article/" is technically permitted and resolves unpredictably in
practice — particularly when the page is being read by something that is not a
browser, or when it has been syndicated onto another domain. Always absolute, always with
the protocol.
3. Protocol and subdomain mismatches
A canonical pointing at http:// on an HTTPS site, or at the non-www version
when your site serves www. The canonical then names a URL that immediately redirects,
which weakens the signal and can cause Google to disregard it altogether.
4. Canonicalising to a URL that redirects or 404s
The target should return 200. This breaks most often after a URL structure change, when the canonicals still name the old paths — every one of them now pointing at a redirect, or at nothing.
5. Canonicalising a page that is blocked in robots.txt
The tag lives in the page. If the page cannot be crawled, the tag cannot be read, and it does nothing at all. This is the same trap as blocking a page you also marked noindex, and it catches people for the same reason.
Where it matters most
Ecommerce with filters and sorting
The hardest case. Colour, size, price and sort-order combinations generate effectively unlimited near-identical URLs. Filtered views that show genuinely distinct content and attract their own searches deserve their own canonical; sorted and paginated variants of the same set generally point at the base category.
Syndicated and republished content
This is what cross-domain canonicals are for. Republishing an article on Medium, LinkedIn or a partner site? The copy should carry a canonical pointing back to your original, so the ranking credit comes home. Ask for this explicitly when negotiating a republication — most platforms support it and almost none volunteer it.
Campaign landing pages
One page, a dozen tagged variants, all consolidated by a self-referencing canonical to the clean URL. This is why the UTM builder and the canonical generator belong together: tagging links is safe precisely because the canonical is there.
Print views, AMP pages and PDFs
Alternative renderings of the same content. Each points at the primary HTML version.
Use these together
- Meta Tag Generator — Generate title, description, canonical, robots, Open Graph and Twitter card tags with live length checks.
- SEO Page Checker — Check any live page for title, description, headings, canonical, robots, alt text and internal links.
- UTM Builder — Build correctly encoded campaign links so Google Analytics attributes every click to the right source.
- The full set of twelve — free, no signup, and for nine of them nothing you type leaves your browser.
Why generate it
A canonical tag is one line, and it fails in ways that produce no visible symptom whatsoever. There is no error, no warning, no missing page — just a signal that quietly does not consolidate. That combination, trivial to write and impossible to eyeball, is exactly what a generator is for.
The generator here takes the URL you
want indexed, normalises it, and flags the specific things that make canonicals useless:
http where the site serves https, tracking parameters left on
the end, a trailing slash that does not match your site's convention. Then it hands you
the tag, ready to paste.
It runs entirely in your browser and stores nothing. After you deploy, verify it on the live page with the SEO page checker, which reports the canonical actually being served — because plenty of CMS platforms and SEO plugins write their own on top of yours, and two canonicals is functionally the same as none.
If you are choosing between a canonical, a redirect and a noindex, that decision has its own guide — picking the wrong one of the three is a more expensive mistake than writing any of them badly.
FAQ
Should every page have a canonical tag?
Yes. Even with no duplicates today, a self-referencing canonical costs one line and protects you the moment a URL variant appears — a tracking parameter, a print view, a scraped copy. There is no page where it is the wrong thing to have.
Is a canonical tag the same as a redirect?
No. A canonical is a hint that Google can override, and the visitor stays on the page they requested. A 301 redirect is an instruction and moves the visitor too. Use a redirect when the duplicate should not exist; use a canonical when both URLs need to keep working.
Can a canonical point to a different domain?
Yes, and that is how syndication is meant to work. If you republish an article on Medium or a partner site, the copy should carry a canonical pointing back to your original so the ranking credit returns to you. Agree it before you publish.
What happens if I get the canonical wrong?
Nothing visible, which is the problem. The worst case is every page pointing at the homepage, which tells Google your entire site is duplicate content and can remove nearly all of it from the index. Milder errors just weaken a signal quietly for months.
Does the canonical URL have to match exactly?
It should point at a URL that returns 200, not one that redirects. If your site
serves /page/ with a trailing slash, the canonical needs the slash too.
Mismatches on protocol, www and trailing slash are the three most common ways a
technically present canonical achieves nothing.
Thejas Acharya
Digital growth consultant based in Bangalore, working with founders and marketing teams across India and the US. I build websites, landing pages, Meta Ads campaigns and AI automation that are judged on one thing: whether they generate leads. The free tools on this site are the checks I run on client work, opened up.