Duplicate Content in WordPress and How to Fix It

• URL variations of the same page: with and without www, HTTP and HTTPS, with and without a trailing slash, and the /?p=123 form alongside the pretty permalink.
• Category, tag, author and date archives, which all list the same posts in different groupings — often with full content rather than excerpts.
• Paginated archives, where the second and subsequent pages can carry the same title and meta description as the first.
• Attachment pages: a page per uploaded image, containing an image and almost nothing else.
• Print and AMP variants, if a plugin generates them.
• Search result pages, which are infinite and thin by nature.
• Query parameters from filters, sorting, tracking and session IDs, each producing a new URL for the same content.

Three concrete costs, none of which is a penalty.

First, signals split. If five sites link to one version and three to another, you have two pages with partial authority instead of one with all of it.

Second, Google picks the canonical, and it may not pick the one you want. A tag archive outranking the article it lists is a common and annoying outcome.

Third, crawl budget. On a large site, a crawler spending its time on attachment pages and filter combinations is a crawler not fetching your new content promptly.

These three tools solve different problems, and using the wrong one is where most fixes go astray.

• Canonical — 'this page is a version of that one'. Both remain accessible, and signals consolidate on the canonical. Right for URL variations, filter parameters and syndicated content.
• noindex — 'don't index this, but it's a legitimate page'. Right for thin archives, search results and anything useful to a visitor but not worth a search result.
• 301 redirect — 'this URL is gone, go there instead'. Right when the duplicate shouldn't exist at all: attachment pages, an old URL structure, a merged page.
• The common error is canonicalising something that should be redirected, or blocking something in robots.txt that should be noindexed — which prevents Google reading the noindex at all.

This is the highest-value fix and the easiest. Pick one canonical form — HTTPS, one hostname, one trailing-slash convention — and enforce it.

Set WordPress Address and Site Address in Settings → General to that form. Add server-level redirects from every other variation to it. Then confirm every page emits a self-referencing canonical tag pointing at the canonical form.

Test it by requesting several variations and confirming each 301s in a single hop to the same final URL. Two systems both trying to enforce this is how redirect loops happen, so decide which layer owns it.

Categories, tags, authors and dates all list the same posts differently. Most sites need far fewer of these indexed than they have.

• Keep well-populated categories indexed — they're useful landing pages with a real purpose.
• Noindex tag archives with one or two posts each. They're thin and they compete with the posts themselves.
• Noindex author archives on a single-author site, where they duplicate the blog index entirely.
• Noindex date archives, which are almost never a useful landing page.
• Show excerpts rather than full posts on archives, so the archive isn't a verbatim copy of the article.
• The test for each: would you be happy for a search visitor to land there? If not, noindex it and remove it from the sitemap.

Google no longer uses rel prev/next, and the current guidance is straightforward: paginated pages should be indexable with self-referencing canonicals.

The common misconfiguration is canonicalising every paginated page to page one. That tells Google pages two onwards don't exist as distinct URLs, which means the content only reachable from them may never be discovered.

Do give each paginated page a distinguishing title — 'Page 2 of 6' — so they aren't duplicates of each other in the results. And make sure important content isn't buried on page fourteen with no other route to it.

WordPress creates a page for every uploaded file. On a site with a thousand images, that's a thousand pages containing an image and no content.

They are never useful and they're a pure liability. Either disable them entirely, or redirect them to the post the image is attached to. Most SEO plugins have a single setting for this.

This is one of the highest-ratio fixes available: one setting, and a large number of thin pages stop existing.

Filters, sorting, tracking parameters and session identifiers all produce distinct URLs for the same content. On a WooCommerce store with faceted filtering, the combinations can be effectively infinite.

Canonicalise parameterised URLs to the clean version. For genuinely useless combinations, disallow the pattern in robots.txt so crawlers don't waste time on them — but only where you don't need the page indexed at all, since a blocked page can't have its canonical read either.

Be careful not to canonicalise away something that should rank. A filtered category that people genuinely search for may deserve its own indexable page with its own content.

The kind that isn't WordPress's fault: near-identical service pages for different locations, product variations with the same description, or the same boilerplate on fifty pages.

Location pages generated from a template with the place name swapped are doorway pages, and they're treated as spam rather than as duplicates. Either write something genuinely specific for each, or consolidate into one good page.

For product variations with identical descriptions, consider whether they should be variations of one product rather than separate products.

Where two pages genuinely compete for the same term, merging them into one stronger page and redirecting is almost always better than trying to differentiate them.

• Search Console's Pages report: look for 'Duplicate without user-selected canonical' and 'Alternate page with proper canonical tag'.
• Crawl the site and look for pages sharing a title or meta description.
• Search for a distinctive sentence from one of your pages in quotes, restricted to your own site, and see how many URLs come back.
• Check the indexed page count against the number of pages you believe you have. A large gap in either direction is informative.
• Look at your sitemap for post types and taxonomies you didn't intend to publish.