Canonical generator
Clean any URL into a consistent canonical, then copy the tag.Page URL
www
Trailing slash
Clean up
All checks pass
- Note: Kept 1 param. Only keep ones that change the content, like ?page=2.
- Note: Use the same canonical on every duplicate, and make sure this URL returns 200 and isn't blocked in robots.txt.
- Pass: Switched to https
- Pass: Lowercased host and path
- Pass: Removed www
- Pass: Dropped index file
- Pass: Removed utm_source, gclid
- Pass: Removed trailing slash
- Pass: Removed fragment
<link rel="canonical" href="https://example.com/blog/post-title?page=2" />
What it’s good for
One URL per page, every time.
- Kill duplicatesTracking params, index.html and casing create copies.
- Set a site ruleDecide on www and trailing slashes once.
- Header or tagUse the HTTP header for PDFs and other non-HTML files.
Questions
The short answers.
Should canonicals be absolute?
Yes. Always use the full https:// URL.
Which params should stay?
Only ones that change the content, like pagination or filters you want indexed.
Can a page canonicalise to another site?
Yes, for syndicated content — but it's a strong hint, not a command.
Which parameters count as tracking?
utm_* campaign tags, click IDs (gclid, gbraid, wbraid, fbclid, msclkid, dclid, yclid, twclid), Mailchimp and HubSpot IDs, plus ref, sessionid and sid. Turn on “Strip all params” if none of your parameters change the content.
Is lowercasing the path always safe?
Not always. Hostnames are case-insensitive, but paths can be case-sensitive on some servers. Only lowercase if your site serves the lowercase URL; otherwise switch the option off.