A canonical URL is the single preferred address you want search engines to index when the same page is reachable through several URLs — with and without www, over HTTP and HTTPS, or with tracking parameters appended. This builder normalises any URL you paste and generates the matching <link rel="canonical"> tag, so you can consolidate duplicate variants onto one address and protect your ranking signals.
How it works
The tool parses your URL with the standard URL parser, then applies the normalisation rules you toggle on. It can force the scheme to HTTPS, lowercase the host, drop a leading www., remove the #fragment, and trim a trailing slash. With tracking removal on, it deletes utm_* parameters plus common click and session IDs — gclid, fbclid, msclkid, mc_cid, mc_eid, ref, yclid, igshid, sessionid and similar — while leaving genuine content parameters in place. It then outputs both the clean URL and a ready-to-paste canonical link tag.
Example
Paste:
http://WWW.Example.com/Page/?utm_source=newsletter&id=42#top
With HTTPS, lowercase host, drop-www, strip-tracking and strip-fragment enabled, the result is:
https://example.com/Page/?id=42
and the tag:
<link rel="canonical" href="https://example.com/Page/?id=42" />
The id=42 content parameter is kept while utm_source, the www. and the #top fragment are removed. Everything runs in your browser — nothing is uploaded.
When canonical tags matter most
Duplicate content from parameter variants — E-commerce and CMS platforms generate many URL variants of the same page: sort order, filter selections, page numbers, and session tokens all produce unique URLs for identical content. A canonical tag on each variant points to the clean, parameter-free version so crawl budget is not wasted and link equity consolidates on one URL.
HTTP vs HTTPS — If your server serves the same content on both protocols (even temporarily during a migration), search engines may index both. A canonical on every HTTPS page prevents the HTTP version being treated as a competing duplicate.
www vs non-www — Although most sites redirect one to the other, the canonical provides a belt-and-braces signal during migrations or periods of inconsistent redirect behaviour.
Syndicating content — If your article is published on your own domain and also on a partner site, add a canonical on the partner version pointing back to your original URL. This tells search engines your site is the source of record.
Pagination — For paginated series (/articles?page=2), the current best practice is a self-referencing canonical on each page rather than pointing every page to page 1.
Canonical tag placement rules
The canonical link tag must appear inside the <head> element. Canonicals in the body are ignored. Only one canonical per page — if multiple rel=canonical tags appear, search engines may ignore all of them. Google recommends absolute URLs (including scheme and host), which is what this builder produces.
Canonical vs 301 redirect — when to use each
A canonical tag tells search engines which URL is preferred but allows all versions to remain accessible. A 301 redirect makes one URL inaccessible and automatically sends users and crawlers to the other. Use a redirect when you want the old URL to stop working for users (after a migration, for example). Use a canonical when both URLs need to stay accessible — such as an AMP page alongside the main page — but you want only one to rank.