OnSumoTools

Canonical URL Generator

The Canonical URL Generator cleans any URL by stripping UTM parameters, tracking strings, and optional elements like trailing slashes or the www subdomain, then outputs a properly formatted canonical link tag and XML sitemap loc element ready to copy. view.

Before (normalized)

https://example.com/page?utm_source=newsletter&page=2

After (canonical)

https://example.com/page?page=2

Stripped: utm_source

Canonical tag

<link rel="canonical" href="https://example.com/page?page=2">

XML sitemap loc

<loc>https://example.com/page?page=2</loc>

Canonical tags should point at the preferred URL for that content. When in doubt, match the URL users see in the address bar without campaign parameters.

How does the Canonical URL Generator work step by step?

The canonical URL generator builds a link rel='canonical' tag that tells search engines which version of a URL is authoritative when multiple addresses serve identical or near-identical content. Before building the tag, the tool applies three normalization rules: it strips tracking parameters (utm_source, utm_medium, utm_campaign, fbclid, gclid) from the query string, normalizes the protocol to https, and removes default ports since they are redundant in canonical declarations. It also flags four common canonical mistakes: trailing-slash inconsistency, www vs non-www mismatch, http vs https mismatch, and session or variant parameters that should not appear in the canonical URL. The output is ready to paste into the HTML head. Key assumption: the tool normalizes the URL you enter and cannot detect whether a conflicting canonical already exists in your CMS output or in an HTTP response header. Edge case: canonical tags in HTTP Link response headers take precedence over in-page canonical tags in most search engines. If your server emits a Link: rel='canonical' header, the in-page tag generated by this tool will be ignored by Google. Verify response headers with a header checker before deployment.

What does a typical Canonical URL Generator result look like?

A blog post is shared as https://www.example.com/post?utm_source=twitter&ref=home#comments. With strip UTM enabled, ref added to the custom strip list, and www removal on, the tool outputs the canonical as https://example.com/post. Both the HTML link tag and the sitemap loc snippet are ready to copy.

Frequently asked questions

  • What is a canonical tag?

    A canonical tag in the HTML head tells search engines which URL is the preferred version of a page. When multiple URLs serve the same content, canonical tags consolidate ranking signals to the preferred version. Tracking this metric alongside conversion data gives a more complete picture of how changes affect actual business outcomes.

  • Should I include UTM parameters in my canonical?

    No. Your canonical URL should always be the clean, parameter-free version of the page. UTM parameters are tracking codes for analytics. Including them in canonicals splits your ranking signals across tracked and untracked URLs.

  • Can I canonicalize to a different domain?

    Yes. Cross-domain canonicals are fully supported by Google. This is used for content syndication: if your article is published on another site, adding a canonical pointing to your original URL tells Google to attribute rankings to your site.

  • What is the difference between a canonical tag and a 301 redirect?

    A 301 redirect sends users and bots to the new URL automatically. A canonical tag leaves the URL accessible but tells search engines which version to prefer for indexing. Use 301 redirects when content has permanently moved; use canonicals when multiple URLs must remain accessible. Tracking this metric alongside conversion data gives a more complete picture of how changes affect actual business outcomes.

  • What happens if I have a fragment (#) in my canonical URL?

    Google strips fragment identifiers from URLs when processing canonicals. Including a fragment in your canonical is harmless but pointless. The tool warns you if a fragment is present and strips it from the output.

  • What is an XML sitemap loc tag?

    The loc element in your XML sitemap should contain the canonical URL of each page. This tool generates both the HTML canonical link tag and the XML sitemap loc snippet so you can keep both in sync. Tracking this metric alongside conversion data gives a more complete picture of how changes affect actual business outcomes.

Related tools

One page, one address

Search engines treat each URL as a separate page. Add a tracking parameter, a trailing slash or a www, and you've created a new address with the same content. Ranking signals split across them.

A canonical tag tells Google which version you prefer. This generator takes any URL and gives you the clean one to put in that tag.

What the cleanup does

It strips UTM parameters and any custom ones you list. It forces HTTPS. You can choose to add or drop www, and add or remove the trailing slash. Pick one style and apply it across the site.

Fragments, the part after a hash, are dropped. Search engines ignore them for indexing anyway.

You also get a ready sitemap loc line, since the canonical and the sitemap entry should match exactly.

Canonical versus 301

A 301 redirect sends users and bots to a new address. A canonical is a hint. The visitor stays on the page they opened, and the search engine decides what to index.

Use a redirect when the old URL shouldn't exist. Use a canonical when both must stay live, such as a filtered product list or a campaign link.

Common mistakes

Cross-domain canonicals are allowed, and they're useful for syndicated content. But Google treats them as a hint, not an order.

  • Pointing the canonical at a redirected URL
  • Mixing http and https across pages
  • Canonicalizing paginated pages to page one
  • Setting a canonical to a page that returns an error
  • Leaving tracking parameters in the tag

Keep it consistent

Match the canonical to your internal links, your sitemap and your redirects. When they all agree, crawlers trust the signal. When they don't, it gets ignored.

Check a few key pages after each release. Your URLs stay in your browser.