To fix duplicate content, identify every URL that serves the same (or near-identical) content, pick one canonical URL, add rel="canonical" tags pointing to it, set 301 redirects from duplicates, and keep your sitemap and internal links consistent with the canonical URL. Re-scan and check Search Console.
Duplicate content splits ranking signals across multiple URLs — www vs non-www, HTTP vs HTTPS, trailing slashes, tracking parameters, and print versions are common culprits. Consolidating onto one canonical URL recovers that authority.
Check your website
See how your site handles how to fix duplicate content issues — free, no account needed.
Business impact
When Google sees the same content at five URLs, it may index the wrong one or dilute rankings across all of them. Fixing duplication is one of the highest-impact technical SEO fixes because it concentrates link equity on the URL you actually want to rank.
Why this happens
Duplicates arise from: no canonical tags; both www and non-www serving content; HTTP and HTTPS both accessible; parameter URLs (?id=); trailing slash variants; paginated or filtered URLs; and CMS defaults that create multiple paths to one post. Fix with 301 redirects for permanent moves, canonical tags for alternate URLs that must stay reachable, and consistent internal linking.
How to confirm the issue
Manually: search site:yoursite.com "exact phrase from page" and see if multiple URLs appear. Check Search Console → Pages for duplicate without user-selected canonical warnings.
With Plexa Trust: review canonical and SEO findings; re-scan after consolidating URLs.
Step-by-step fix
Audit URL variants: www/non-www, HTTP/HTTPS, slashes, parameters.
Choose one canonical form (usually HTTPS, preferred host, no trailing slash).
301-redirect all variants to the canonical URL.
Add self-referencing
rel="canonical"on every indexable page.Update internal links and the sitemap to use canonical URLs only.
Re-scan and monitor Search Console for duplicate warnings.
Platform-specific fixes
WordPress
Set Site Address to your preferred HTTPS URL in Settings → General.
Use an SEO plugin to set canonical URLs per page.
Redirect www to non-www (or vice versa) via plugin or server rule.
Shopify
Shopify redirects to the primary domain automatically — verify Domains settings.
Avoid duplicate product URLs from collections; Shopify handles most canonicals.
Apache
Force HTTPS and preferred host with mod_rewrite 301 rules.
Example: redirect www to non-www (or reverse) in .htaccess.
Cloudflare
Enable Always Use HTTPS and set a canonical redirect rule for www/non-www.
Use Bulk Redirects for parameter cleanup if needed.
How to verify the fix
Pick one URL format and enforce it everywhere — links, sitemap, canonicals.
Use 301 for permanent consolidation; canonical for pages that must stay accessible.
Re-scan after changes and watch Search Console for a few weeks.
Common mistakes
Canonical tags pointing every page at the homepage.
Mixing www and non-www in internal links.
Leaving HTTP and HTTPS both indexable without redirects.
Frequently asked questions
What counts as duplicate content?
The same or substantially similar content reachable at multiple URLs, including parameter, www, and HTTP/HTTPS variants.
Canonical or 301 — which first?
301 for URLs you can retire; canonical for URLs that must stay live but should not be the indexed version.
Does duplicate content incur a penalty?
Google does not usually penalise it — it splits and dilutes signals instead, which still hurts rankings.
How do I find duplicates?
Search Console, site: searches, crawling tools, and checking www/HTTP variants manually.
Should pagination be canonicalised?
Each paginated page should usually self-canonicalise unless you use view-all or infinite scroll patterns.
What about syndicated content?
The syndicating site should canonical to the original publisher's URL.
Do I need to fix every duplicate?
Prioritise high-traffic and high-value pages first; then systematic host and protocol consolidation.
How do I confirm it worked?
Duplicate warnings in Search Console should decline; re-scan with Plexa Trust.
Think you've fixed it?
Run a free scan to verify the issue is resolved. Upgrade to Pro on Plexa Trust for the full audit, monitoring alerts, and score history.
Verify with a free scan