Build a canonical tag that points at the right URL
Turn a messy URL into the clean canonical it should name, stripping tracking parameters, fragments and default documents, with every change explained. Or audit a live page: is its canonical present, absolute, self-referencing, and does it resolve? Build runs in your browser; the audit is one server call.
A canonical tag names the one true URL among duplicates, so search engines consolidate ranking signals onto it instead of splitting them across variants. The tag itself is one line, which is why it goes wrong: it fails silently when the URL it names is itself a variant. A canonical that still carries utm parameters, points to an http version, keeps a #fragment, or names a URL that redirects or 404s does the opposite of its job, and because nothing throws an error, you find out only when the duplicates keep ranking and the traffic stays split.
What a canonical actually does
When the same content is reachable at more than one URL, with and without a trailing slash, with tracking parameters, http and https, a print version, search engines treat them as competing pages and split the ranking signals between them. A canonical tag on each variant points to the single version you want indexed, so the links and authority all count toward one URL. It is a hint, not a command, but a clear, consistent one is usually followed.
The canonical has to be clean itself
The mistake that quietly breaks canonicalization is pointing the tag at a URL that is itself non-canonical: one with utm or gclid tracking parameters, a #fragment, an index.html, or http instead of https. This tool takes the URL you paste and normalizes it, removing exactly those, and lists every change it made so you can see why the canonical it produces is the clean one. A canonical should also be self-referencing on the master page, not only on the duplicates, and the tool reminds you.
Audit what is really on the page
Generating the tag is half the job; the other half is confirming the live page uses it correctly. The audit fetches a URL and checks the things a generator cannot: that there is exactly one canonical, that it is absolute, that it is self-referencing, that the URL it names actually resolves to a live page rather than a redirect or a 404, and that the page does not carry a contradictory noindex. These are the failures that keep duplicates ranking.
How to use it
- 1
Paste the URL
Drop in the page URL exactly as it appears, tracking parameters, fragment and all. The tool works from the messy version on purpose.
- 2
Choose how to normalize
Force https, strip tracking parameters, remove the fragment and default document, and set a trailing-slash policy. The defaults are the safe choices for most sites.
- 3
Read what changed
The tool lists every transform it applied and why, so the canonical is not a black box. Confirm the result is the URL you actually want indexed.
- 4
Add the tag, then audit
Copy the HTML tag into the page head, or use the HTTP header form for non-HTML files. Then switch to Audit and check the live page once it is deployed.
Common mistakes
Canonicalizing to a URL with tracking parameters
A canonical that still carries utm_source, gclid or fbclid points at a variant, not the clean URL, so the consolidation fails. Strip tracking parameters from the canonical, which this tool does by default.
Canonical plus noindex on the same page
They contradict each other: noindex says drop this page, canonical says index this URL. Google gets mixed signals and may ignore both. Use one or the other, not both.
Pointing the canonical at a redirect or a 404
The canonical must name a live, final, 200-status URL. If it points to a URL that redirects or errors, the signal is wasted. The audit checks that the target actually resolves.
Using canonical instead of hreflang for languages
Do not canonicalize your French page to your English one; they are not duplicates. Different-language versions need hreflang, not a canonical. Canonical is for true duplicates of the same content.
Questions
- Does a page need a canonical if it has no duplicates?
- Yes, a self-referencing canonical is still recommended. It tells search engines the exact URL you consider primary and pre-empts them picking a parameter or variant version if one ever gets linked or crawled.
- Canonical or 301 redirect?
- A redirect removes the duplicate entirely and sends users and crawlers to one URL; a canonical keeps both reachable but consolidates ranking. Use a redirect when the duplicate should not exist, and a canonical when both need to stay live, like a product reachable under two categories.
- Where does the canonical tag go?
- In the head of the page, once. For non-HTML files like PDFs you cannot add a head tag, so send it as an HTTP Link header instead, which this tool also generates.
- Is the canonical guaranteed to be followed?
- No, it is a strong hint, not a directive. Google usually respects a clear, consistent, self-referencing canonical, but it can override one it thinks is wrong, for example if the canonical points at a very different page or a broken URL. Keeping the signal clean is how you make it stick.
- Should the canonical include query parameters?
- Only if the parameters change the content in a way you want indexed. Tracking, sorting and filtering parameters should be stripped so the canonical names the clean URL. Parameters that select genuinely different content, like a product variant, can stay.
Need this done properly, at scale?
The tool handles the one-off. When it's a system you're building, that's the paid version of the job, and we do that too.
SEO Services