WordPress SEO: What Plugins Fix and What They Can't

Jul 21, 2026 · Platform SEO

There's a myth that refuses to die: install WordPress and you're most of the way to good rankings. It powers roughly 43% of the web, so it must be optimized by default, right? Not quite. WordPress SEO out of the box gets you clean-ish markup and not much else — no meta description fields, no schema, no redirect management, and a very real chance you've launched with search engines blocked entirely.

I've built dozens of WordPress sites, and the pattern is always the same: the platform gives you a solid skeleton, then leaves every SEO decision to plugins and your theme choice. That flexibility is the whole appeal. It's also where most sites go wrong.

Two settings to check before you install a single plugin

First: Settings → Reading. There's a checkbox labeled "Discourage search engines from indexing this site". Developers tick it during staging and forget to untick it at launch. I've audited live sites six months old with zero organic traffic because of this one box. Check it today.

Second: Settings → Permalinks. WordPress still defaults some installs to the "Plain" structure (?p=123). Switch to Post name so your URLs read /your-post-title/. Do this before you publish anything — changing it later means setting up redirects for every existing URL. If you do have to change it later, our guide to 301 redirects explains how to do it without bleeding rankings.

Yoast vs Rank Math: the plugin decision

You need one SEO plugin — exactly one. Running two causes duplicate meta tags and conflicting sitemaps. The realistic shortlist is Yoast SEO and Rank Math:

Rank Math packs more into its free tier; Yoast has been around longer and breaks less often on unusual setups. Either works. What matters more is what you do inside it: write real meta descriptions, set your homepage title under the plugin's Search Appearance settings, and disable indexing for thin archives. Speaking of which — WordPress auto-generates category, tag, date, and author archives, plus a separate "attachment page" for every image you upload. Yoast and Rank Math both let you set attachment pages to redirect to the file itself. Turn that on; those pages are pure index bloat.

One housekeeping detail people miss: WordPress core has shipped its own basic sitemap at /wp-sitemap.xml since version 5.5, and your SEO plugin generates a better one (Yoast's lives at /sitemap_index.xml). Both plugins disable the core sitemap automatically when theirs is active, but if you ever see two sitemaps in Search Console, that's what happened. Submit the plugin's version and make sure it's the one referenced in your robots.txt — details on how these files work are in our XML sitemap guide.

Taxonomy discipline: the part no plugin fixes

Plugins manage your metadata; they don't manage your information architecture. WordPress makes it effortless to create a new tag for every post, and five years later you have 800 tags, most attached to one post each — hundreds of thin archive pages competing with your actual content. Pick a small set of categories that mirror what you want to rank for, treat tags as optional seasoning, and noindex tag archives entirely if you're not curating them (a one-click setting under Search Appearance → Taxonomies in either plugin). While you're at it, check for the classic ?replytocom= comment-pagination URLs on older sites; modern plugin defaults handle them, but legacy installs still leak thousands of these into crawl budgets.

Where WordPress SEO actually falls apart: speed

The platform's biggest ranking liability isn't metadata — it's what themes and page builders do to load times. A multipurpose theme from a marketplace ships with sliders, icon packs, and three bundled builders whether you use them or not. Stack Elementor on top and you're loading its widget CSS and JavaScript on every page. Gutenberg (the native block editor) produces dramatically lighter markup — on identical content I've measured Elementor pages shipping several times the DOM size and blocking scripts.

That gap shows up directly in Core Web Vitals, which feed into rankings. The fixes, in order of impact:

1. Pick a lean theme. GeneratePress, Kadence, or a block theme. Skip anything advertising "900+ demos".
2. Add caching. WP Rocket if you'll pay, or LiteSpeed Cache if your host runs LiteSpeed. Page caching alone often halves server response time.
3. Compress images on upload. ShortPixel or Imagify, with WebP conversion enabled.
4. Audit your plugin list quarterly. Every active plugin is potential frontend weight. Deactivate anything you can't justify.

Hosting deserves a line too: WordPress is the only platform on this list where server response time is your problem. Cheap shared hosting adds hundreds of milliseconds before a single byte of HTML moves. If your time-to-first-byte is consistently poor with caching enabled, the fix is a better host, not another plugin.

Structured data without writing JSON-LD

Both major SEO plugins output basic Article and Organization schema automatically. For anything beyond that — recipes, FAQs, reviews, events — Rank Math has built-in schema blocks, and Yoast offers FAQ and How-To blocks inside Gutenberg. If you run WooCommerce, it emits Product schema on its own; just don't double it up with a schema plugin or you'll send Google conflicting price data.

When WordPress is the right call — and when it isn't

Choose WordPress when you need content flexibility: custom post types, complex category structures, editorial workflows, or a site that'll grow past a few hundred pages. The plugin ecosystem means almost any SEO requirement has a solution.

Skip it if you want a site you never maintain. WordPress demands updates — core, theme, plugins — and neglected updates cause both security holes and SEO regressions. If you're publishing a straightforward blog and dread maintenance, something like Ghost handles the fundamentals with far less ongoing work.

Whichever way you build, verify the output rather than trusting the plugin settings screen. Run a crawl of your site after launch and after any theme change — it'll surface the noindexed pages, duplicate titles, and redirect chains that WordPress quietly accumulates.