Canonical Tag Generator

Our Canonical Tag Generator turns any list of URLs into ready-to-paste rel="canonical" tags. Paste up to 500 URLs at once, pick your HTTPS, www, and trailing slash preferences, and copy clean tags for every page. The tool also works as a canonical checker; it flags URLs that need review before you publish the tag. Everything runs in your browser, so nothing you paste is uploaded or stored.

What Is a Canonical Tag?

A canonical tag is an HTML element that tells search engines which URL is the preferred version of a page. It is placed within the page’s <head> section and looks like this:

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

Why it matters: one page can be accessible at several addresses. These URLs all display the same content to Google:

• http://example.com/page
• https://www.example.com/page
• https://example.com/page?utm_source=newsletter

Without a canonical tag, Google selects one version on its own, and it may not select the one you want. The tag consolidates ranking signals, links, and crawl attention into the single URL you choose.

How to Use This Canonical Tag Generator

You can generate canonical tags in four steps:

1. Paste your URLs: Enter one URL per line, or separate them with commas. The tool accepts up to 500 URLs and converts URLs without a protocol to HTTPS automatically.
2. Apply your options: Open the advanced options to set your protocol, www preference, trailing slash, and URL parameter handling. These settings apply to every URL in your list at once.
3. Copy or download the output: Each URL gets its own clean canonical tag. Use the Copy Tags button or download the list as a file.
4. Place each tag in the correct page: Paste each tag into the <head> section of its own page only. One page should contain exactly one canonical tag.

Canonical URL Options: HTTPS, WWW, Trailing Slash, and Parameters

The advanced options normalize every URL in your list so your canonicals follow one consistent format. Mixed formats split ranking signals, so these settings matter.

• Protocol: The tool recommends HTTPS, and for good reason, Google prefers HTTPS pages over HTTP pages as canonical URLs. If you enter a URL without a protocol, it is converted to HTTPS automatically.
• www preference: Your site should treat one host as standard, either www.example.com or example.com. Choose the version that matches your live setup and keep it consistent across internal links, redirects, and canonical tags.
• Trailing slash and duplicate slashes: /page/ and /page are different URLs to search engines. Pick the style your site actually uses. The tool also collapses duplicate slashes, so example.com//page becomes example.com/page.
• URL parameters: This is where care matters most. Tracking parameters such as utm_source, gclid, and fbclid add no unique content, so removing them is safe and usually correct. Content-changing parameters are different. A URL like example.com/blog?page=2 displays different content than the base page, so stripping page=2 would point the canonical at the wrong target. The tool warns you each time it removes a parameter that may change content, so you decide URL by URL.

Canonical Tag Formats: HTML Tags, Plain URLs, and HTTP Link Headers

Different pages need canonical signals in different forms. This tool generates all three:

HTML canonical tags are the standard format for web pages. Place the tag in the <head> section of the duplicate page, and search engines treat the linked URL as the preferred version.

Plain canonical URLs strip the tag markup and leave only the final URLs. Use this output for sitemaps, SEO audit reports, or anywhere you need a clean URL list rather than code.

HTTP Link headers serve PDFs, Word documents, and other non-HTML files. These files have no <head> section, so they cannot carry a standard canonical tag. Google supports the rel=”canonical” HTTP header for exactly this purpose. The output looks like this:

<https://example.com/white-paper.pdf>; rel="canonical"

Your server returns this header with the file response, which tells Google which HTML page, if any, should be treated as the original. Choose this format only when canonicalizing non-HTML documents, since regular pages should use the standard HTML tag.

When to Use a Canonical Tag

Canonical tags solve specific URL problems. Use one in these situations:

• Tracking parameters: URLs with utm_source, gclid, or similar campaign tags create unlimited duplicate versions of one page. Canonicalize them to the clean URL.
• www vs non-www: If both www.example.com and example.com serve your pages, pick one version and canonical every page to it.
• HTTP vs HTTPS: Running both protocols creates two versions of every page. Canonicals should point to the HTTPS version.
• Trailing slash differences: /product/ and /product can both get indexed. Canonicalize to whichever format your site uses.
• Filtered or sorted pages: E-commerce category pages with filter or sort options, such as ?color=red or ?sort=price, often duplicate the main category. Point them to the unfiltered version.
• Syndicated content: If another site republishes your article, its canonical tag should point back to your original so your page keeps the ranking credit.

Canonical Check: 7 Common Mistakes to Avoid

Run a canonical check on your pages after implementing tags, because these errors are easy to make and easy to miss:

1. Pointing to a redirecting or dead URL: A canonical should lead directly to a live page with a 200 status. A tag that points to a redirect or a 404 wastes the signal.
2. Adding multiple canonical tags to one page: When two tags conflict, search engines may ignore both. Themes and plugins sometimes add a second tag without your knowledge.
3. Using relative URLs: href="/page/" depends on the page’s location, which can break on staging sites or subdomains. Always use the full absolute URL with the protocol.
4. Mixing HTTP and HTTPS: If your site runs on HTTPS, every canonical must use HTTPS too. An HTTP canonical splits signals and can even cause Google to prefer the HTTP version.
5. Canonicalizing every page to the homepage: This tells Google your entire site is a copy of the homepage. Only group pages that are genuinely duplicates.
6. Combining canonical with noindex: These directives contradict each other. Google recommends rel=”canonical” alone for consolidating duplicates.
7. Blocking the canonical URL in robots.txt: A blocked page cannot be crawled, so Google never sees its canonical tag. Use redirects or canonicals, not disallow rules, for this purpose.

Canonical vs Redirect vs Noindex

These three tools look similar but do different jobs. Here is how to choose:

How to Check Canonical URL After Implementation

Generating tags is only half the job. Verify them on the live page using any of these methods:

• View page source: Open the page, right-click, and select “View Page Source.” Search for rel="canonical" with Ctrl+F (or Cmd+F on Mac). The tag should appear exactly once, inside the <head> section.
• Browser DevTools: Press F12, open the Elements panel, and inspect the <head>. This shows the rendered HTML, which is useful for confirming that JavaScript or an SEO plugin did not modify your tag.
• Google Search Console URL Inspection: Enter the page URL in Search Console and check the “Page indexing” report. It displays both the user-declared canonical URL and the version Google actually selected. These two should match.

FAQs