WordPress turns on a lot of things by default. Some of them quietly work against your SEO — spawning thin, near-duplicate pages, or loading scripts you never use. You don’t need to disable everything, but a handful of defaults are worth switching off on most sites. Here’s the shortlist, grouped by why.
Not every default is a problem, and the impact varies by site — a busy multi-author magazine wants author archives; a solo evergreen blog usually doesn’t. The rule is disable what creates thin pages or loads resources you don’t use, not “turn everything off.” Below, the candidates in three buckets.
Uncurated author / date / tag archives + attachment pages. Each spawns thin, near- duplicate URLs that split your ranking signal. noindex/redirect.
Emoji scripts, embeds, unused image sizes, redundant built-in search. Loads resources you don't use. Dequeue what you never rely on.
Core XML sitemap when your SEO plugin already makes one; pingbacks/trackbacks (spam magnet). Let one owner generate it.
Table of Contents
Bucket 1: duplicate-content sources
WordPress auto-generates several archive pages that list the same posts different ways. Left uncurated, they compete with your real content for ranking signals — the kind of duplicate URLs Google asks you to consolidate:
- Author archives — on a single-author site,
/author/you/just duplicates your blog index. Disable ornoindexit unless individual author pages add real value. - Date archives —
/2024/03/pages rarely help evergreen content and split signals. Usually safe to disable. - Tag archives — useful only if tags are a deliberate, curated taxonomy. A sprawl of one-off tags creates thin listing pages; disable or
noindexthose. - Attachment pages — a whole thin page per uploaded image. This one has its own deep-dive: why most sites should disable attachment pages.
Every uncurated archive is a thin page competing with your real content — you’re splitting your own ranking signal.
Most SEO plugins (Yoast, Rank Math) let you noindex or redirect each of these from one settings screen — the cleanest way to handle the whole bucket.
Bucket 2: performance bloat
These don’t create duplicate pages; they just add weight to every load, and page speed is itself an SEO and AI-citation factor:
- Emoji scripts — WordPress loads an emoji script and stylesheet on every page. If you don’t rely on them, dequeue them.
- oEmbed / embeds — the embed discovery script and external requests can be trimmed if you rarely embed.
- Unused image sizes — WordPress generates several thumbnail sizes per upload; drop the ones your theme never displays (this pairs with the REST image-sizes deep-dive).
- Built-in search — if you run a dedicated search solution, the default search can surface thin
?s=result pages; restrict ornoindexthem.
Bucket 3: redundant once a plugin owns it
Some defaults simply duplicate what a plugin already does better:
- WordPress core XML sitemap — if Yoast or Rank Math generates your sitemap, disable WordPress’s own so search engines aren’t handed two.
- Pingbacks and trackbacks — a spam magnet with little upside for most sites; turning them off streamlines comments without SEO cost.
Two sitemaps aren’t twice the coverage — they’re a conflict. Let one owner generate it.
What to leave alone (and how to do this safely)
Don’t disable on reflex. XML sitemaps themselves are good — you’re only turning off the duplicate source, not sitemaps entirely. Author archives matter on genuine multi-author sites. Minification and concatenation help performance but occasionally break a theme or plugin, so change them one at a time.
Whatever you turn off: back up first, change on a staging site, and re-check your rankings and Core Web Vitals afterwards. Most of bucket 1 is a few toggles in your SEO plugin; buckets 2 and 3 are small snippets or plugin settings — a good case for a snippet over a plugin when it’s a one-line dequeue.
The short version
WordPress enables defaults that can hurt SEO or add weight. Turn off the ones that spawn thin, duplicate URLs (uncurated author/date/tag archives, attachment pages), the ones that load resources you don’t use (emoji scripts, embeds, unused image sizes, redundant built-in search), and the ones a plugin already owns (WordPress’s XML sitemap when your SEO plugin makes one; pingbacks/trackbacks). Keep what you actually rely on — author archives on real multi-author sites, sitemaps in general — and back up and test on staging before flipping anything, then watch your SEO and speed metrics.
Frequently Asked Questions
Which WordPress features hurt SEO the most?
The ones that create thin, near-duplicate pages: uncurated author, date and tag archives, and attachment pages. They split your ranking signals across low-value URLs. noindex or disable the archives you don’t actively curate, and redirect attachment pages to their parent posts.
Should I disable author archives?
On a single-author site, yes — the author archive just duplicates your blog index. On a genuine multi-author site where author pages add value (bios, topic authority), keep them. When in doubt, noindex rather than fully removing.
Do emojis and embeds really slow WordPress down?
A little — WordPress loads an emoji script and stylesheet on every page, and embeds add discovery scripts and external requests. Dequeuing what you don’t use removes small, needless weight; it’s a minor speed win, not a transformation.
Will disabling these features break my site?
It can if you disable something you rely on (author archives on a multi-author site) or if minification conflicts with a theme. That’s why you back up, change on staging, and test one thing at a time — then confirm rankings and Core Web Vitals held or improved.
Should I turn off XML sitemaps for SEO?
No — sitemaps help. You only disable WordPress’s built-in sitemap when an SEO plugin (Yoast, Rank Math) is already generating one, so search engines get a single authoritative sitemap instead of two competing ones.
