Canonical Conflicts

Why It Matters for AI Visibility

How We Score It

How to Improve

• 1

  Fix protocol mismatches between page and canonical

  If your page loads on HTTPS but your canonical tag points to HTTP, that is a high-severity conflict costing 3 points. Update the canonical to use `https://`. This is the most common conflict on sites that migrated to HTTPS but did not update their canonical tags.

• 2

  Remove duplicate canonical tags

  Having more than one `<link rel="canonical">` tag on a page is a high-severity conflict. Search your HTML output for multiple canonical tags -- this often happens when a CMS adds one and a plugin adds another. Keep only one self-referencing canonical tag per page.

• 3

  Consolidate www and non-www URLs

  If your page is at `https://example.com/page` but your canonical points to `https://www.example.com/page`, that is a medium-severity mismatch. Pick one format (www or non-www) and enforce it site-wide with 301 redirects. Update your canonical tags to match the chosen format.

• 4

  Remove query parameters from canonical URLs

  Canonical URLs should be clean, without query strings. If your canonical is `https://example.com/page?utm_source=twitter`, the query parameter triggers a medium-severity conflict. Set canonical tags to the clean URL path without tracking or filter parameters.

• 5

  Ensure your canonical URL appears in your sitemap

  The analyzer cross-references your canonical URL against your sitemap.xml. If the canonical URL is missing from the sitemap, that is a medium-severity conflict. Add all canonical URLs to your sitemap and remove non-canonical variants to send consistent signals.

Before & After

<!-- HTTPS page with HTTP canonical (protocol mismatch) -->
<link rel="canonical" href="http://www.example.com/products/widget">
<!-- Second canonical tag added by plugin (multiple canonicals) -->
<link rel="canonical" href="https://example.com/products/widget/">

<!-- Single, self-referencing HTTPS canonical -->
<link rel="canonical" href="https://example.com/products/widget">

Code Examples

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

server {
    listen 80;
    listen 443 ssl;
    server_name www.example.com;
    return 301 https://example.com$request_uri;
}

# Remove trailing slashes (choose one standard)
RewriteEngine On
RewriteRule ^(.+)/$ /$1 [R=301,L]

Frequently Asked Questions