Exact Duplicate Content

What This Means

Two or more pages in the audited site have content that is effectively identical after normalization — the same body text, with at most trivial differences like whitespace variation, minor punctuation differences, or boilerplate that appears on both. The pages may have different URLs but serve the same content.

Why It Matters for SEO

When search engines encounter exact duplicates, they consolidate their ranking signals around the version they consider canonical — which may not be the version you prefer. Inbound links to the non-canonical version contribute less effectively to rankings; crawl budget is divided between the duplicates instead of being concentrated on unique pages; and the indexed version may not be the one with the correct canonical URL or the best user experience.

Exact duplicates are most commonly caused by: protocol variants (http:// vs. https://), subdomain variants (www vs. non-www), trailing slash variants (/page vs. /page/), session IDs appended to URLs, or printer-friendly page versions.

What the Platform Checks

After a full crawl, the platform computes a normalized content fingerprint for each page's body content. Pages with matching (or near-100% similar) fingerprints are grouped. Any group with more than one member generates this issue for all members.

How to Fix It

Resolve the duplication by choosing one canonical version and eliminating or redirecting all others:

• 301 redirects: Redirect all non-canonical URLs to the preferred version. This is the strongest signal and consolidates all link equity to the preferred URL.
• Canonical tags: Add <link rel="canonical" href="..."> to all duplicate versions pointing to the preferred URL. Use this when redirecting is not possible (e.g., for syndicated content).
• Address the source: Implement HTTPS and www/non-www redirects at the server level. Use consistent URL patterns (with or without trailing slash). Disable printer-friendly page versions or noindex them.
• Session IDs: Configure your server to not append session IDs to URLs for crawlers, or use canonical tags on session ID URLs pointing to the clean version.

After implementing redirects or canonicals, verify the fix using the coverage report in Google Search Console.