Canonical URL Generator

Generate a clean canonical tag from any URL. Tracking parameters, fragments and the http protocol are stripped out, because none of them belong in a canonical.

Runs entirely in your browser — nothing is uploaded

Page URL

Cleanup options

Force httpsPoint at the secure versionRemove tracking parametersutm_*, gclid, fbclid and similarRemove trailing slashOnly if that matches how your site serves URLs

Canonical tag

<link rel="canonical" href="…" />

Place this inside the <head>. A page’s canonical normally points at itself; point it elsewhere only when this page is a genuine duplicate of that one.

How to use this tool

Paste the page URL, including any parameters it currently has.
Leave the cleanup options on unless you have a reason to change them.
Copy the tag into the head of that page.

What is Canonical URL Generator?

A canonical tag tells search engines which URL is the definitive version of a page. It matters whenever the same content is reachable at more than one address — with and without a trailing slash, with tracking parameters, with different sort orders, on http and https.

Without one, search engines pick for themselves, and may split ranking signals across several versions of the same page instead of consolidating them onto one.

Best practices

Use absolute URLs. Relative canonicals are legal but a frequent source of mistakes.
Every page should normally carry a self-referencing canonical.
Never include tracking parameters — that defeats the purpose of the tag.
The canonical URL must return a 200, not a redirect or a 404.
It is a hint, not a directive: Google can ignore it if your signals contradict it.

Frequently asked questions

Should every page have a canonical tag?

It is good practice. A self-referencing canonical on every page pre-empts duplicate versions appearing later through parameters or session IDs.

Can a canonical point to a different page?

Yes, when this page is genuinely a duplicate or a close variant of that one. Pointing it at an unrelated page tells search engines to ignore this one entirely.

Does the canonical URL need to be https?

It should point at whichever version you actually serve — which for any modern site is https. Pointing at http when your site redirects to https sends a contradictory signal.