Canonical Tag Generator

Generate the correct HTML canonical tag to prevent duplicate content issues. Works for standard pages, paginated pages, and AMP pages.

Canonical URL * The preferred, canonical version of this page's URL

Options

Generate AMP canonical tag

This is a paginated page

Include self-referencing canonical

Generated Tags

Bulk Canonical Generator

Paste multiple URLs (one per line) to generate canonical tags for all of them at once (self-referencing).

0 URLs

Frequently Asked Questions

A canonical tag (<link rel="canonical" href="...">) tells search engines which URL is the authoritative/preferred version of a page when multiple URLs serve similar or identical content. It was introduced by Google, Bing, and Yahoo in 2009 and is the standard solution for managing duplicate content without redirects.

Use a 301 redirect when the old URL should no longer be accessible at all — it sends users and bots directly to the new URL. Use a canonical tag when both URLs should remain accessible (e.g., URL with tracking parameters) but you want to tell search engines which one is the "real" version for indexing purposes.

Yes. Adding a self-referencing canonical to every page is a best practice. It explicitly signals the preferred URL (including http vs https, www vs non-www, trailing slash or not) and prevents problems if scrapers republish your content — Google can still identify your URL as the original.

Google treats canonical tags as hints, not directives. If the specified canonical URL has significantly different content, is not crawlable, or is part of an inconsistent signal cluster, Google may override it and choose a different canonical. Consistent canonical signals (canonical tag + sitemap inclusion + internal linking + 301s) ensure Google respects your preferred URL.

Yes — adding a self-referencing canonical tag to every page is a best practice, even when there is no duplicate content risk. It prevents ambiguity about your preferred URL when scrapers republish your content, explicitly signals http vs https preference, www vs non-www, and trailing slash conventions. Google recommends self-referencing canonicals and many technical SEO audits flag pages that are missing them. The implementation cost is minimal and the benefit — a clear, unambiguous signal to Google — is worth it on every page.

Google may override your canonical tag when: the specified canonical URL is not crawlable (blocked by robots.txt or returning an error); the content differs significantly between the two pages; there are conflicting signals — e.g., your canonical points to URL A but your sitemap only includes URL B, or internal links predominantly link to URL B; the page has hreflang annotations that conflict with the canonical; or the canonical URL itself redirects to somewhere else. The more consistent your signals (canonical + sitemap + internal linking + 301 redirects), the more reliably Google respects your choice.

For paginated series (/page/2, /page/3…), Google's current recommendation is to use self-referencing canonicals on each paginated page — don't canonical all pages to page 1, as that may cause Google to exclude page 2+ from indexing. The deprecated rel=prev/next pagination signals were officially dropped by Google in 2019. If individual paginated pages have low standalone value, consider using noindex on pages beyond the first, but only if users don't need to land on those pages directly from search. For large e-commerce category pages, having each paginated page indexed is often valuable.

No — Google does not penalize duplicate content in the sense of a manual or algorithmic penalty. Instead, Google automatically filters duplicates: it selects one version to index as canonical and suppresses the others from search results. The SEO impact is that your ranking signals (backlinks, PageRank) become diluted across duplicate URLs rather than consolidated on one. The goal of canonical tags is to tell Google which version to consolidate signals onto, not to avoid a penalty. The exception: deliberately scraped or spun content intended to manipulate rankings can trigger a manual action.

Cross-domain canonicals allow content syndicated on a third-party site to point back to the original publisher as the canonical source. For example, if your article is republished on a partner site, the partner's version can include <link rel="canonical" href="https://yoursite.com/original-article">. Google then consolidates ranking signals to your domain rather than the republishing site. This is widely used in news syndication (e.g., AP articles republished by newspapers) and content partnerships. The third-party site must agree to implement the canonical tag — you cannot set it on someone else's pages.

A canonical tag tells Google "this page exists but prefer this other URL — consolidate signals there." The page itself may still be crawled and even indexed as a non-canonical. A noindex tag (<meta name="robots" content="noindex">) tells Google "do not include this page in the index at all." Use canonical when you want the preferred version indexed and ranking signals consolidated. Use noindex when the page should not appear in search at all (thin content, internal search results, staging pages). Do not combine canonical + noindex on the same page — these are contradictory signals that confuse crawlers.

About This Canonical Tag Generator

This free canonical tag generator creates the <link rel="canonical"> HTML tag for any URL. Paste the canonical URL, click Generate, and copy the ready-to-paste tag into your page's <head>.

A canonical tag tells search engines which version of a URL is the authoritative one, preventing duplicate-content issues caused by URL parameters, trailing slashes, HTTP vs HTTPS, or paginated content.

When to use this tool

Preventing duplicate content issues from URL parameters or session IDs
Consolidating link equity from near-duplicate pages
Setting the canonical for paginated or filtered catalogue pages
Fixing HTTP/HTTPS or www/non-www canonicalization issues

Standards & References

How It Works

Enter the Preferred URL

Enter the canonical URL — the exact version of the page you want indexed, including protocol, www/non-www, and trailing slash preference.

Configure Options

Enable AMP canonical or paginated page options for special cases. The output updates to include all necessary link tags automatically.

Add to <head>

Copy the tag and place it inside the <head> of each page. For bulk generation, paste multiple URLs and copy all tags at once.

Common Use Cases

UTM Parameter URLs

Pages accessed via UTM tracking URLs (e.g., ?utm_source=email) should have canonical tags pointing to the clean URL to avoid duplicate content issues.

Filtered & Sorted Pages

E-commerce category pages with sort/filter parameters (?color=red, ?sort=price) should canonicalize to the base category URL.

Print-Friendly Pages

Print versions of pages (e.g., /page?print=1) should canonicalize back to the standard page URL to consolidate ranking signals.

AMP Pages

AMP versions of articles must include a canonical tag pointing to the canonical (non-AMP) URL, while the canonical page should link to the AMP page with <link rel="amphtml">.

Paginated Content

For paginated series (page-1, page-2, page-3…), consider having page 2+ canonicalize to page 1 or use self-referencing canonicals per Google's current guidance.

HTTP to HTTPS Migration

During migration, use canonical tags on HTTP pages pointing to HTTPS equivalents as an additional signal alongside 301 redirects.

Related SEO Tools

View all articles

Pagination, Canonical Tags, and rel=prev/next: What Changed and What Still Matters

Google stopped using rel=prev/next for pagination in 2019 — but the canonicalization question for paginated content didn't disappear. Here's why self-referencing canonicals are generally correct for paginated listings with unique items per page, when "view all" pages should be the canonical target instead, and how infinite scroll fits into this.

Jun 17, 2026

Cross-Domain Canonical Tags: Telling Search Engines "The Real Version Is on a Different Domain"

A canonical tag's target doesn't have to be on the same domain — cross-domain canonicals are the standard mechanism for content syndication, telling search engines "this content also exists at [original publisher's URL], and that's the version to treat as canonical." Here's how this works for syndication and multi-domain organizations, the historical AMP precedent, and why the canonical target must actually exist and contain matching content for the signal to be honored.

Jun 13, 2026

Canonical Tags in JavaScript Frameworks: SPAs, Next.js, and E-Commerce Faceted Navigation

React and Vue SPAs often inject canonical tags via JavaScript — which Googlebot sees only after rendering, with a processing delay. Here's how Next.js SSR handles canonicals correctly, how to manage e-commerce faceted navigation, and how to verify what Google actually sees.

Jun 10, 2026

Canonical Tags vs. 301 Redirects: A Decision Framework for Duplicate Content

Canonical tags and 301 redirects both solve duplicate content problems — but through different mechanisms with different trade-offs. Here's the decision framework for when to use each, common canonical mistakes, and the belt-and-braces approach for domain canonicalisation.

Jun 8, 2026