🔗 Canonical URL Generator

A canonical URL generator that strips tracking parameters, normalizes protocol/www/trailing-slash, and outputs a ready-to-paste rel="canonical" tag.

Free No Signup Required Browser-Based

Canonical Tag

<link rel="canonical" href="https://example.com/blog/post?id=42" />
Resolved URL: https://example.com/blog/post?id=42

What Canonical URL Generator Does

Google's own canonicalization documentation is explicit that a rel="canonical" tag is a strong signal, not a directive it is required to follow — Google can and does choose a different canonical URL when it has strong reasons to, such as when the tagged URL redirects, 404s, or conflicts with other signals like a sitemap entry. Getting the basics right (an absolute URL, a working page, no conflicting signals) is what makes the tag actually effective rather than ignored.

The most common way a canonical tag ends up wrong in practice is not a wrong URL — it is an inconsistent one. A page reachable at four URLs (with and without www, with and without a trailing slash, with and without tracking parameters) needs to consistently point at exactly one of them from every version, or Google is left choosing on its own.

How to Use Canonical URL Generator

  1. Paste the page URL, including any query parameters
  2. Choose which normalizations to apply — strip tracking params, force https, strip www, trailing slash handling
  3. Copy the generated <link rel="canonical"> tag into your page's <head>

How to Read Your Result

Use absolute URLs, always

Google's documentation specifically warns that while relative canonical paths are technically supported, they can cause real problems — for example if a staging or testing subdomain gets crawled and its relative canonicals resolve against the wrong host.

Add a self-referencing canonical to the canonical page itself

Google explicitly recommends the canonical page also carry a canonical tag pointing at itself — this removes any ambiguity about which URL is the intended target, even for the page that is already correct.

Only strip parameters that do not change the content

Tracking parameters (utm_*, gclid, fbclid) are safe to strip because they do not change what is shown. A parameter that changes the actual content — a filter, a product variant, a page number — should stay in the canonical, since stripping it would point the canonical at a different page than the one being tagged.

Limitations & Accuracy Notes

  • A canonical tag is a signal, not a guarantee — Google can select a different canonical if the tagged URL is broken, redirects, or conflicts with other signals like your sitemap.
  • Canonical tags only work when they appear in valid HTML in the <head>, or via the equivalent HTTP header for non-HTML files.
  • This tool strips a fixed list of common tracking parameters; a site using a custom or unusual tracking parameter should double-check the output.

Frequently Asked Questions

What is a canonical tag for?
A <link rel="canonical"> tag tells search engines which URL is the "master" version of a page when duplicate or near-duplicate content is reachable at multiple URLs — for example, the same page with and without tracking parameters, or with and without a trailing slash. Google consolidates ranking signals to the canonical URL rather than splitting them across duplicates.
Should I strip every query parameter?
No — only parameters that do not change the page content, like tracking codes (utm_source, gclid, fbclid) or session IDs. A parameter that actually changes what is shown (like a product variant or search filter) usually should stay in the canonical URL, or the canonical would point at the wrong version of the page.
Trailing slash or no trailing slash — does it matter?
Either is fine as a standard, but it needs to be consistent: /page and /page/ can be crawled as two different URLs, and without a canonical tag pointing them at one version, Google may treat them as duplicates. Pick one convention and use this tool to normalize toward it.
Does a canonical tag guarantee that URL gets indexed?
No. A canonical tag is a strong signal, not a directive Google is required to follow — Google can choose a different canonical if it has strong reasons to (for example, if the tag points at a URL that redirects or 404s). It should point at a real, working, indexable URL.
Is my URL sent anywhere?
No. The parsing and tag generation happen entirely in your browser using the standard URL API.

References & Further Reading

By OnlineToolHubs Team • September 2026