Duplicate and near-duplicate pages quietly split your ranking power across URLs that all could have ranked, leaving you with thinner authority than the underlying content actually deserves and confusing search engines about which version represents the real page.
Loading Meta Tags…
Generates rel=canonical link tags
Absolute URL format (required)
Self-referencing canonical guidance
Pagination canonical support
Drop the Meta Tags into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.
Embed code
<iframe
src="https://www.fixtools.io/seo-tools/meta-tags?embed=1"
width="100%"
height="780"
frameborder="0"
style="border:0;border-radius:16px;max-width:900px;"
title="Meta Tags by FixTools"
loading="lazy"
allow="clipboard-write"
></iframe>Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.
Duplicate content is far more pervasive on real-world sites than most owners realise, and the damage compounds silently until an audit surfaces the scale of the problem. URL parameter proliferation is the single most common cause of accidental duplication: every filter, sort option, tracking parameter, session identifier, or A/B test variation creates a new URL that may serve identical or near-identical content to the canonical version. A product category page for women's shoes can multiply into hundreds of indexable URLs including /womens-shoes?color=red, /womens-shoes?size=8, /womens-shoes?sort=price_asc, /womens-shoes?utm_source=email, and dozens of combinations in between, each potentially crawlable and each duplicating the core content. Without canonical tags, Google must decide which URL represents the real page, and its choice may not match yours. The canonical tag restores your control by adding rel canonical on all variant URLs pointing to /womens-shoes, signalling definitively which URL Google should index and consolidate ranking signals around rather than scattering them across hundreds of near-identical paths.
Correct canonical implementation requires both self-referencing canonicals on the primary page and pointing canonicals on all duplicate pages, applied consistently across the entire URL family without exceptions or accidental gaps. A self-referencing canonical on /womens-shoes pointing to itself reinforces it as the preferred URL and protects against accidental duplicates created later by URL parameters you may not anticipate when first building the page. Canonical tags on all /womens-shoes parameter variants point back to /womens-shoes, consolidating the entire family onto the single preferred URL. Critical implementation rules apply universally: always use absolute URLs including protocol and domain such as https://www.example.com/womens-shoes rather than relative paths, because some crawlers fail to resolve relative canonicals correctly and produce ambiguous signals. Place the canonical tag inside the head section, never in the body. Avoid chained canonicals where A points to B and B points to C, because Google follows chains but reduces signal strength with each hop. Never set canonicals pointing to noindex pages, because the resulting conflicting directives confuse Google about what you actually want.
Cross-domain canonical usage is also valid and highly underutilised by most publishers, despite being explicitly endorsed by Google for managing syndicated content. When you syndicate your articles to Medium, LinkedIn, Substack, or news aggregators that republish your content, ask those platforms to add a canonical tag pointing back to your original URL on your own domain. This preserves your ranking credit rather than splitting it with the syndication partner, ensuring the original source remains the dominant search result for the content. Medium supports canonical tags for imported articles directly in their import settings, LinkedIn supports them for newsletter-published content, and most modern syndication platforms include canonical configuration as a standard option. Google explicitly supports cross-domain canonicals as a legitimate duplicate content management strategy, documented in their Search Central guidance, so there is no risk of penalty or signal loss from using the feature correctly across domain boundaries.
Beyond the obvious duplicate content scenarios, canonical tags solve several less visible but equally damaging problems that affect almost every site over time. HTTP versus HTTPS variants of the same URL count as duplicates if both are crawlable, and the canonical tag is one of the cleanest ways to consolidate ranking signals onto the HTTPS version during a migration. Trailing slash versus no-trailing-slash variants like /about and /about/ create accidental duplicates on many platforms unless you enforce one format and canonical the other. Uppercase versus lowercase URL variants like /About and /about can serve identical content on platforms that treat URLs case-insensitively at the server but case-sensitively at the indexing layer. Print versus screen versions of articles often need canonicals to consolidate the readable version onto the primary URL. AMP pages need canonical tags pointing from the AMP version back to the canonical desktop version. Each of these scenarios benefits from explicit canonical handling rather than leaving Google to guess.
Enter the preferred (canonical) URL for your page to generate the correct <link rel="canonical"> HTML tag.
Step-by-step guide to canonical tag generator:
Identify the preferred URL
Determine which URL is the canonical or authoritative version of the page family, usually the version you want to rank in search results, the one you link to from primary navigation, and the one that represents the cleanest path without parameters, session identifiers, or tracking codes. For e-commerce category pages, the canonical is typically the unfiltered base URL. For articles, it is the original publication URL on your own domain. Document the canonical choice in a spreadsheet alongside the URL family it covers.
Enter the full absolute URL
Paste the complete URL including the https protocol, the www or non-www subdomain choice that matches your site convention, and any trailing slash that your URL structure uses consistently across the rest of the site. Use the exact format you want indexed, because the canonical URL becomes the authoritative reference for the entire URL family and any inconsistency between the canonical and the actual served URL can confuse the indexing signal. Double-check the URL resolves to a 200 status without redirects before submitting.
Generate the canonical tag
Click Generate to produce the link rel canonical href YOUR_URL HTML tag in the exact format expected by every major search engine and crawler. Copy the resulting block, which can be pasted directly into the head section of any page that needs to canonical to the URL you specified. The tag format is identical across content management systems, frameworks, and static site generators, so the same generated tag works whether your site is built on WordPress, Next.js, Shopify, Webflow, or any other platform.
Add to every page variant
Place the canonical tag inside the head section of the canonical page itself as a self-referencing canonical and on every duplicate or near-duplicate URL that should point to it. For dynamically generated parameter variants, implement the canonical via a template change in your CMS or framework so the correct canonical is automatically added to every variant without manual intervention. After deployment, validate the canonicals across a sample of URLs using Search Console's URL Inspection tool to confirm Google sees the expected canonical for each variant.
Common situations where this approach makes a real difference:
E-commerce filtering pages
A clothing retailer with hundreds of product category pages discovers via Search Console that filtered URL variants like /shoes?size=10&color=black are being indexed alongside the main /shoes category page, splitting ranking authority across dozens of near-identical URLs that each rank weakly for the same target keywords. The technical SEO team uses the generator to add canonical tags on every filtered URL pointing back to the main /shoes page, consolidating link equity onto the preferred URL. Within six weeks of the rollout the main category page climbs measurably for its target queries, organic traffic to the canonical URL increases noticeably, and the previously fragmented ranking signals coalesce into a stronger overall position for the category.
HTTP to HTTPS migration
A publisher midway through migrating from HTTP to HTTPS adds canonical tags on all HTTP pages pointing to the HTTPS versions during the transition period, signalling the preferred URL to Google while the team works through the longer process of implementing comprehensive 301 redirects across the entire site. The canonicals provide an immediate consolidation signal that prevents ranking dilution during the migration window, and once the 301 redirects are fully in place the canonical tags continue to serve as a defensive measure protecting against any redirect that might silently break later. The combined approach preserves organic traffic continuity through what is often a risky technical project.
Content syndication
A publisher syndicating long-form articles to industry partner sites and Medium asks each syndication partner to add a canonical tag pointing back to the original publication URL on the publisher's own domain, preserving the original site's ranking credit even when the syndicated copies pick up significant inbound links of their own. Medium handles this natively through their import settings, and most partner sites implement the canonical via a simple template change once asked. The publisher continues to dominate organic search results for the article topics even though the syndicated copies are indexed and discoverable, because the canonical signal directs ranking authority back to the source on every variant.
Use this when you have multiple URLs serving the same or very similar content, such as paginated pages, filtered e-commerce views, HTTP/HTTPS duplicates, or content syndicated across domains.
Get better results with these expert suggestions:
Add self-referencing canonicals to every page
Even pages with no known duplicates should carry a self-referencing canonical tag pointing to themselves as a defensive measure against accidental duplicates that may appear later. URL parameter injection by third-party tools, session IDs added by user state systems, tracking parameters appended by ad platforms, and case-sensitivity quirks can all create unanticipated duplicates without warning. A self-referencing canonical reinforces the preferred URL whenever any of these scenarios occur. The cost of adding the tag is essentially zero because it can be templated across every page in the CMS, and the protection it provides against future accidental duplication is substantial across any active growing site.
Always use absolute URLs in canonical tags
Canonical tags must use the complete absolute URL including protocol and domain, for example https://www.example.com/page/, rather than relative paths like /page/ or protocol-relative formats like //example.com/page. Some crawlers including older versions of certain syndication tools fail to resolve relative or protocol-relative canonicals correctly and produce ambiguous signals about the actual canonical URL. Using the full HTTPS URL eliminates the ambiguity entirely and ensures every crawler interprets the canonical signal exactly the same way. Standardise the format including www versus non-www subdomain and trailing slash conventions across the entire site for consistent signal strength.
Check for canonical chains in your site crawl
A canonical chain occurs when page A canonicals to page B and page B canonicals to page C, creating an indirect signal that Google follows but with reduced effectiveness at each hop. Use Screaming Frog's canonical report or Sitebulb's canonical analysis to identify and collapse any chains so each non-canonical URL points directly to its final canonical destination in a single hop. Chains commonly appear after URL restructuring, site migrations, or filter system changes where the canonical configuration was not updated to reflect the new URL hierarchy. Collapsing chains is usually a five-minute fix that meaningfully improves the canonical signal strength across affected URL families.
Include only canonical URLs in your sitemap
Your XML sitemap should list only canonical URLs, never parameter variants, duplicate pages, redirect sources, or non-canonical alternatives. Including non-canonical URLs in the sitemap creates a direct conflict because the sitemap implies these URLs are indexable while the canonical tags simultaneously indicate they are not, leaving Google to interpret contradictory signals. Align your sitemap generation logic with your canonical configuration so the sitemap output is automatically restricted to canonical URLs only, and audit the sitemap quarterly against Search Console's Coverage report to confirm no non-canonical URLs are slipping through into the submitted sitemap by accident.
Always use absolute URLs in canonical tags
Canonical tags must use the full URL including protocol and domain (e.g., https://www.example.com/page/) rather than a relative path. Relative canonical URLs can cause indexation errors.
Add self-referencing canonicals to every page
Even if a page has no known duplicates, adding a canonical tag pointing to itself prevents issues if a duplicate is accidentally created and protects against URL parameter variations.
Ensure canonical and hreflang point consistently
If you use hreflang for international SEO, make sure the canonical URL on each page matches the hreflang href for that page's language/region. Mismatches cause indexation confusion.
More use-case guides for the same tool:
Open the full Meta Tags — free, no account needed, works on any device.
Open Meta Tags →Free · No account needed · Works on any device