Best SEO plugin for WordPress: how to choose one and set it up

What a WordPress SEO plugin actually changes

Strip away the dashboards and scores, and an SEO plugin changes a small number of things in the HTML Google receives. Knowing the list makes the choice much easier, because it shows that the plugins compete on convenience and extras, not on ranking power.

• The title tag and meta description for every post, page, product and archive, from templates you set once and override per page.
• The canonical tag, which tells Google which address is the main version of a page.
• The robots meta tag, so you can set whole content types or single pages to noindex.
• An XML sitemap index, which replaces the WordPress core /wp-sitemap.xml.
• Structured data as a JSON-LD graph describing the site, the business or person behind it, the page and, for posts, the article and author.
• Open Graph and social tags for link previews, and breadcrumbs if your theme supports them.

The on-page analysis, the traffic-light scores and the focus keyword box are writing aids. They are useful prompts for beginners, but Google never sees them, and a green light is not a ranking signal. Plenty of pages with an orange score rank well because they answer the search better than anything else.

Yoast SEO vs Rank Math vs All in One SEO

All three have free versions that cover the core output listed above. The differences are in what is free, how much structured data control you get and how the interface is organised. Plugin features change between versions, so treat this as a guide and check the current feature list before you commit.

Which one to choose

• Small business site or new blog: Yoast SEO or All in One SEO. Fewer decisions, sensible defaults, and the free version is enough.
• You want redirects and schema control without paying: Rank Math, but switch off the modules you do not need so the admin stays manageable.
• You want something very light: lighter plugins such as The SEO Framework output the same core tags with almost no interface, which suits developers.
• The site already runs one and ranks: keep it. Switching gains little and risks losing titles and descriptions if the import misses something.

Why running two SEO plugins breaks things

The most common plugin problem is not a bad choice, it is two choices at once. A site moves from one plugin to another and the old one stays active, or a theme or page builder bundles its own SEO module. The result is two sets of everything in the head of the page:

• Two <title> tags or two meta descriptions, and Google picks one, not always the one you wrote.
• Two JSON-LD graphs describing the same page in different ways, which confuses rich result eligibility. See plugin schema conflicts.
• Two sitemaps submitted in Search Console, one of which may include pages you set to noindex in the other.
• Conflicting canonical or robots tags, where one plugin says index and the other says noindex. Google treats noindex as the stronger instruction.

Check for it with one command per page type. Each count below should be exactly 1:

URL=https://example.com/sample-post/
curl -s "$URL" | grep -o '<title' | wc -l
curl -s "$URL" | grep -o 'name="description"' | wc -l
curl -s "$URL" | grep -o 'rel="canonical"' | wc -l
curl -s "$URL" | grep -oE 'yoast-schema-graph|rank-math-schema|aioseo-schema'

The last line shows which plugin's structured data is on the page. More than one name means two plugins are writing schema. On the server, wp plugin list --status=active lists every active plugin so you can see the culprit.

The settings that matter after installing

Whichever plugin you choose, the set-up wizard covers most of this, but check each item by hand afterwards:

1. Site representation. Say whether the site represents a business or a person, and add the name and logo. This feeds the structured data on every page.
2. Search appearance per content type. Posts, pages, products and categories should normally be shown in search. Tags, date archives, format archives and, for a one-author blog, author archives are usually better set to noindex. See how to noindex a page.
3. Attachment pages. Make sure they redirect to the file or parent post rather than existing as thin pages.
4. Title templates. A good default for posts is the post title, a separator and the site name. Keep the site name short so the important words stay visible.
5. Sitemap. Confirm the index loads, lists only the content types you want indexed, and submit it in Search Console. The WordPress sitemap index guide covers 404s and blank sitemaps.
6. Modules you do not need. In plugins with many modules, switch off the ones you will not use, such as local SEO or analytics, to keep the admin and page output lean.

Switching from one plugin to another

Before you switch, record what you have. Titles and descriptions are stored in post meta or the plugin's own tables, so count them first:

wp db query "SELECT meta_key, COUNT(*) FROM wp_postmeta
  WHERE meta_key IN ('_yoast_wpseo_title','_yoast_wpseo_metadesc','rank_math_title','rank_math_description')
  GROUP BY meta_key"

Replace wp_ with your table prefix if it differs. Run the new plugin's importer, compare a sample of pages before and after with the curl checks above, then deactivate the old plugin. Keep it installed but inactive for a few weeks in case you need to import again.

Themes, builders, WooCommerce and multilingual sites

• Themes with built-in SEO options. Some themes add their own title and description fields. Turn them off if your plugin handles the same output, then run the duplicate check.
• Page builders. Builders generally leave the head to your SEO plugin, but their content analysis integration varies. If the plugin's score cannot see your text, the analysis is wrong, not the page. Judge from the rendered HTML.
• WooCommerce. Product structured data comes from WooCommerce itself and from your SEO plugin, and the two are usually merged. Check a product page with the Schema Markup Validator for one Product item, not two. The WooCommerce crawl guide covers filters and pagination.
• Multilingual plugins. Translation plugins need to tell the SEO plugin about each language so titles, sitemaps and hreflang are written per language. Use a combination both vendors document as compatible. See hreflang in WordPress.
• Caching and CDNs. After changing plugin settings, purge the page cache. Otherwise visitors and Googlebot can keep receiving the old tags for days.

A worked example: two plugins on one site

Example Bakery switched from All in One SEO to Rank Math to use its free redirect manager. The import ran, but the old plugin stayed active. Two months later Search Console showed product pages listed as Duplicate, Google chose different canonical than user, and some search snippets showed old descriptions.

The duplicate check on a product page returned two description tags, and the schema line returned both rank-math-schema and aioseo-schema. Search Console had two sitemaps submitted: /sitemap.xml from the old plugin and /sitemap_index.xml from the new one. The old sitemap still listed tag archives that the new plugin had set to noindex.

The fix was to compare twenty pages to confirm the import was complete, deactivate All in One SEO, purge the cache, remove the old sitemap from Search Console and resubmit the new index. Every count in the check returned 1, and within a month the canonical warnings had cleared as Google recrawled the pages.

The fix, step by step

Edge cases worth knowing

• The plugin's score disagrees with Google. Readability and keyword scores are rules of thumb. Do not stuff a phrase into a page to turn a light green; write for the reader and judge by impressions and clicks.
• Google ignores your meta description. Google rewrites many snippets based on the search. That is normal and not a plugin fault. See Yoast or Rank Math description not working.
• Sitemap returns 404 after installing. Save Settings, Permalinks once to rebuild the rewrite rules, then check that a caching or security plugin is not blocking the address.
• Plugin errors in the editor. If the plugin panel will not load or saving fails, the cause is usually the REST API being blocked. The Yoast SEO errors guide covers the fixes, which apply to the other plugins too.
• Headless WordPress. If your front end is built in a separate framework, the plugin's tags are not printed automatically. You fetch them through its API and render them yourself.

Keeping your SEO plugin set up correctly

Plugin updates occasionally change defaults or add modules, and new plugins can bring their own SEO features. Once you have one plugin configured:

1. Run the duplicate tag check on a post, a page and a product after major plugin, theme or builder updates.
2. Review the sitemap index every few months to confirm it still lists only the content you want indexed.
3. Keep the plugin updated, but read the changelog for changes to schema or sitemap output before updating a busy shop.
4. Read the reasons in the Search Console Pages report monthly, so a wrong noindex setting is spotted within weeks, not months.

For the wider picture, the WordPress SEO guide covers the settings, content and speed changes that the plugin cannot make for you.