WordPress SEO Tools: Your Plugin Is Doing Less Than You Think (and That's Fine)

Almost every WordPress SEO guide gives the same advice: install a plugin, fill in the fields, watch for green lights. It is not wrong, and it stops at roughly a third of the job while implying it is the whole thing.

The useful frame is layers. Some SEO work happens inside WordPress and a plugin is genuinely the right tool. Some happens outside it and a plugin structurally cannot reach. Confusing the two is why sites with a perfectly configured plugin still have 60 posts sharing a meta description.

What an SEO plugin actually does

The plugin's real job is writing correct tags into pages WordPress generates, and it matters because WordPress alone does this unevenly:

• Titles and meta descriptions per post, with templates for archives and taxonomies that core does not give you.
• Canonical tags handled consistently across paginated archives, categories and tags, which is where core is weakest.
• A configurable XML sitemap, so you can exclude the tag archives and attachment pages nobody should be indexing.
• Basic schema, typically Article and BreadcrumbList, generated from data WordPress already holds.
• Noindex controls per post type, which is how you stop thin archive pages diluting the site.

That is a real and necessary job. AIOSEO is one of the plugins we have reviewed in this category, and the honest summary of the whole category is that the major options all do this competently.

The three things no plugin can reach

A plugin executes inside the request that renders one page. That single architectural fact creates three blind spots:

1. It cannot crawl your site. Redirect chains, broken internal links, duplicate titles across 400 posts and orphan pages are all properties of the site as a whole, invisible from inside one page.
2. It cannot see what Google indexed. Only Search Console holds Google's verdicts, which is why a green light in the editor and a page missing from the index coexist happily.
3. It cannot judge impact. The plugin does not know which posts earn the traffic, so its recommendations are unranked by definition.

Choosing between the plugins

Less consequential than the internet suggests. The major plugins write correct tags, generate sitemaps and add basic schema. Three things genuinely differentiate them:

• Schema breadth, if you need types beyond Article and breadcrumbs. Check for your specific type rather than the total count.
• Upsell pressure. Some free tiers are usable indefinitely; others gate ordinary settings behind an upgrade prompt on every screen.
• Migration support, since switching means moving saved titles and descriptions. Most offer an importer; confirm it covers your current plugin.

The one rule that matters more than the choice: run exactly one. Two SEO plugins produce duplicate meta tags and conflicting canonicals, which is actively worse than either alone.

The tools that work on WordPress from outside

"Works with WordPress" is usually the wrong question for these, because they do not integrate at all. They crawl your published HTML, which is a feature: they see what Google sees rather than what your CMS intended:

• Search Console, for indexation verdicts and query data. Nothing inside WordPress substitutes for it.
• A crawler, for the site-wide view: duplicate tags, redirect chains, orphan pages, indexability across every post at once.
• Per-page checkers, for verifying a specific fix rendered correctly: the meta checker, canonical checker and indexability checker read your live page, not your plugin's settings screen.

That distinction is worth dwelling on. A plugin can be configured perfectly and a theme or a caching layer can still emit something different. Checking the rendered page is how you find that, and it is the same principle behind judging tools by what they can see.

Core Web Vitals on WordPress: mostly not the plugin

Performance complaints get blamed on SEO plugins more than they deserve. The actual hierarchy, in order of effect:

1. Hosting. Server response time sets the floor everything else builds on.
2. The theme. A heavy page builder generating deeply nested markup is usually the largest single factor.
3. Images. Unsized, uncompressed images drive both LCP and layout shift.
4. Plugin count in aggregate, rather than the SEO plugin specifically.

Measure before optimising: how to check your page speed covers doing it properly, and fixing Core Web Vitals goes metric by metric.

Plugin traps worth knowing about

• Two SEO plugins at once. Duplicate tags, conflicting canonicals. Pick one and deactivate the other properly.
• Indexing tag and author archives by default. Thin pages that compete with your real content. Most sites should noindex both.
• Attachment pages. WordPress can generate a page per uploaded image, each nearly empty. Redirect them to the parent post.
• Verification tags stored in the plugin. Convenient, until you switch plugins and silently un-verify your Search Console property.
• Programmatic post types published at scale before anyone crawls the output, which is how a site gains 3,000 near-duplicate pages in an afternoon.

Every one of those is found from outside WordPress, by crawling the site or reading Search Console. Which is the whole argument of this page: the plugin writes, and something else has to read.