A WordPress SEO plugin gives you fields to fill in and generates a sitemap. That is genuinely useful and it is close to the whole of what it does. It cannot create demand, cannot write anything worth ranking, and cannot fix a theme that produces unusable page structure — which is where most WordPress SEO problems actually originate.
What the plugin handles
- Metadata fields. Title and description per page, which would otherwise require editing templates.
- XML sitemaps. Generated and updated automatically.
- Basic structured data. Article and organisation markup, generally competently.
- Canonical tags and indexing directives. Exposed as settings rather than code.
- Social preview fields. Useful, though not an SEO function.
Choosing between the mainstream plugins is one of the lower-stakes decisions in SEO. They are close in capability, and using whichever you already have properly beats migrating to another and using it just as loosely.
What the plugin cannot touch
| Problem | Origin | Where the fix actually is |
|---|---|---|
| Slow pages | Theme, hosting, images, plugin load | Hosting and build, not settings |
| Poor heading structure | Theme or page builder output | Templates |
| Content that renders only in JavaScript | Builder or theme | Build approach |
| Duplicate URLs | Archives, tags, pagination, search pages | Site configuration |
| Thin or generic content | Editorial decisions | The content itself |
| No search demand | The market | Nothing on the site |
Every row in that table is more consequential than any plugin setting, and none of them are addressed by installing something.
The WordPress-specific traps
Archive pages nobody intended to publish. WordPress generates archives for categories, tags, authors and dates by default. On a site using tags liberally, this can produce hundreds of thin pages competing with the content they list. Most sites should index far fewer of these than they do.
Page builders and heading structure. Builders let anyone style text as large and bold without it being a heading, and equally let a heading be used for visual emphasis. The result is pages with several H1s, or headings used for visual emphasis in an order that makes no semantic sense. Google handles imperfect heading structure without penalty, but clear hierarchy is what lets a section be understood as a self-contained answer — which matters more now that answer engines extract sections as citable units and rely on structure to know where a section begins.
Plugin accumulation. Sites acquire plugins over years and rarely shed them. Two plugins both generating structured data will produce conflicting markup, and the accumulated loading cost falls on every page.
Theme quality. The largest single technical variable on a WordPress site and the one least often examined. A poorly built theme imposes performance and structural problems that no amount of configuration resolves.
The order worth working in
- Check what is actually indexed. Usually more than expected, and often includes archives nobody meant to publish.
- Check heading structure on key pages. One H1, sensible hierarchy beneath it.
- Check rendering. Is the content in the raw HTML, or does it require JavaScript?
- Audit plugins. Remove anything unused; resolve overlaps.
- Then fill in the plugin fields properly. Last, because it matters least.
Most WordPress sites we look at have the last step done thoroughly and the first four not at all. That order is precisely backwards, and it is understandable — the plugin has a dashboard that shows green lights, and the other four require someone to go looking.
The one change worth making today
If you do nothing else: look at how many tag archives your site has indexed. On a blog that has used tags freely for a few years, this is routinely several hundred pages, each listing a handful of posts and containing no original writing at all.
Those pages compete with the posts they link to, dilute the site’s apparent focus, and give an answer engine assessing your site a great deal of material with nothing quotable in it. Setting tag archives to noindex takes about a minute in any of the major plugins, and on content-heavy sites it is frequently the highest-return single change available.
Category archives are a different matter and often worth keeping indexed, because they usually have genuine descriptions and correspond to how people actually browse. The distinction is whether the archive is a real destination or an accident of how someone once tagged a post.
Frequently asked questions
Which SEO plugin is best for WordPress?
The mainstream options are close enough that the choice rarely decides anything. They handle metadata, sitemaps and basic structured data competently. Switching between them is far less valuable than using whichever one you have properly.
Can an SEO plugin fix my rankings?
No. A plugin provides fields to fill in and generates a sitemap. It cannot create demand, produce content worth ranking, or repair a site structure that does not work. It removes friction rather than adding capability.
Do too many plugins hurt SEO?
Indirectly, through performance and conflicts. Each plugin adds code that loads on your pages, and several overlapping plugins frequently produce duplicate structured data or conflicting directives.
Is WordPress good for SEO?
It is capable and unopinionated, which cuts both ways. Everything needed is achievable, and nothing is enforced – so outcomes depend far more on the theme, the hosting and the discipline applied than on the platform.
Does page builder software hurt SEO?
It can. Heavy builders add markup and scripts that slow pages, and some generate heading structures that make no semantic sense. Neither is fatal, but both need checking rather than assuming.
If your WordPress site has every plugin field filled in and still is not ranking, the cause is further down. Send us the domain and we will find it. See how we work on WordPress sites, message us on WhatsApp, or send an enquiry.
Sources
Written by Charlotte Zhang, Operations Partner at Kaizenaire Pte Ltd (UEN 201932071D). Charlotte co-founded Kaizenaire with Ken Tan in 2019 and runs client delivery, after four years in operations at OCBC and HSBC.