Canonical Tag Generator
Generate the correct HTML canonical tag to prevent duplicate content issues. Works for standard pages, paginated pages, and AMP pages.
Options
Paste multiple URLs (one per line) to generate canonical tags for all of them at once (self-referencing).
Frequently Asked Questions
<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.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.