What an SEO plugin is, on a WooCommerce store
A WooCommerce SEO plugin is a WordPress plugin that adds search controls to your pages: fields for titles and descriptions, a sitemap, rules about what search engines should and should not index, and structured data. It does not rank your store. It gives you the switches and boxes, and you or someone you hire has to fill them in well.
WordPress on its own is fairly basic about this. WooCommerce adds product and category pages on top. An SEO plugin fills the gap so that each product, each category and each article has its own title and description, a clean set of tags in the page head, and a way to tell search engines about the pages you care about.
Several plugins do this, and they overlap a great deal. Well-known ones include Yoast SEO, Rank Math and All in One SEO. We name them as examples only. We do not rank them or tell you one is best, because the right one depends on your store and the jobs below, and because their features and screens change. Each has its own documentation and its own pricing page, which are the places to check what is current.
If you are weighing whether to buy a plugin, hire help or do both, our guide to where a plugin stops and a service starts sets out how the two fit together. This page stays on the plugins themselves.
The jobs an SEO plugin usually does
Plugins differ in polish, but most cover a similar list. Use this as a checklist when you compare them, and confirm each item in the plugin's own documentation.
Titles and descriptions
A plugin gives each page a title and a description field, often with templates so that every product follows a pattern, for example the product name followed by the store name. Templates save time on a large catalog. They also tend to produce bland, repeated titles, so the most important pages deserve hand-written ones.
XML sitemap
A sitemap is a file that lists your pages for search engines. Plugins generate it and update it as you add products. You then submit it in Google Search Console. Our glossary entry on XML sitemaps for WooCommerce explains what belongs in one.
Index and canonical controls
Plugins let you mark a page as noindex, which asks search engines to leave it out of results, or set a canonical address, which says which version of near-identical pages is the main one. Both matter on stores, where filters and variations create many similar URLs. The page on WooCommerce duplicate content goes into when to use each.
Structured data
Most plugins add some structured data, the hidden labels that tell search engines a page is a product, an article or a breadcrumb trail. WooCommerce itself also outputs product data. That overlap is a place where problems start, and the page on WooCommerce schema markup shows how to check it.
Extras
Some plugins add redirect managers, breadcrumbs, social sharing previews and content scoring. These vary a lot from plugin to plugin and from free to paid tiers. Check the current feature list before you assume a feature is included.
What an SEO plugin cannot do
This is the part most plugin pages leave out. A plugin is a tool, and the limits matter more than the features.
It cannot decide what to write. A plugin provides a box for the description. It does not know that your best-selling product has a one-line description copied from the supplier. A green traffic-light score next to a page tells you the page follows the plugin's checks. It does not tell you the page is useful or that anyone searches for what it says.
It cannot fix a slow store. Speed comes from your hosting, your theme, your images and the other plugins you run. An SEO plugin can even add a little weight. Our page on WooCommerce site speed and SEO covers the real causes.
It cannot write product pages or category pages for you. It can show you a field and warn that it is empty. The work of filling a thousand fields with text that helps a buyer is still work.
It cannot build links or reputation. Search engines and AI assistants look at what others say about you. No setting changes that.
It cannot promise rankings. Be wary of any plugin page or review that implies installing it will lift your traffic. The effect of a plugin is to make good work possible and visible, not to replace it. If your store already has no organic traffic, a plugin is rarely the missing piece. Our existing page on why a WooCommerce store gets no organic traffic looks at the more common causes.
None of this makes plugins pointless. A good setup is the foundation for the content work. It is just not the content work.
Why you run only one SEO plugin
Install a single SEO plugin and leave it as the one source of truth for titles, sitemaps and structured data. Running two at once is a common mistake, and it causes concrete problems.
Two plugins each try to output a title tag, a sitemap and canonical tags. You can end up with two sitemaps, two sets of structured data or conflicting instructions in the page head, and search engines have to guess which to follow. The two will also keep separate copies of your settings, so a title you set in one is ignored when the other is the one in control.
The same logic applies to features that overlap with other plugins. A redirect plugin, a schema plugin and a breadcrumbs plugin may all duplicate something your SEO plugin already does. Before adding another, find out whether your current plugin covers it, and turn the duplicate off in one place rather than leaving both on.
You can see what a page actually outputs. Open a product page in your browser, view the page source, and look for how many title tags and how many blocks of structured data there are. Google's Rich Results Test will show what it reads from a URL.
If you are switching plugins, plan it. Most have import tools that carry over titles and descriptions from the old one, but they do not catch everything. Do it on a staging copy first, compare a sample of pages before and after, and check the plugin's documentation for its migration steps. A move from one plugin to another is a small migration, and the page on WooCommerce SEO migration shares the habit of checking before and after.
How to choose by the jobs, not by the name
Comparison pages that crown a winner age quickly. A better method is to decide what you need and check each candidate against it.
Step one: write down your jobs. Most stores need titles and descriptions, a sitemap, index controls, structured data and redirects. A store that sells through several languages or regions has more needs. A store with a few hundred products can live with simple templates. One with tens of thousands needs bulk tools.
Step two: check what is free and what is paid. Free tiers cover the basics. Some features, often redirects, extra schema types or WooCommerce-specific helpers, sit in paid tiers or add-ons. Read each plugin's own pricing and feature pages for the current split. We do not list prices because they change.
Step three: check compatibility. Look at whether the plugin is kept up to date, works with your version of WordPress and WooCommerce, and plays well with your theme and page builder. The plugin's directory page shows when it was last updated and which versions it was tested with.
Step four: check how it handles WooCommerce. Look for how it deals with product titles, product category pages, shop pages, and structured data for products. The vendor documentation will say.
Step five: test on a copy. Install it on a staging site, set it up, and view the source of a product page and a category page. If the output looks clean and matches what you expect, you have a candidate.
If your store already uses one plugin and it works, the case for changing is weak. Change when you hit a clear limit, not because another review ranked a different one first. A specific example of one plugin's WooCommerce add-on is on our page about Yoast SEO for WooCommerce.
The setup choices that matter most
A plugin gives you dozens of settings. A handful of them change what search engines see on a store. Whichever plugin you use, go through these once, using its documentation for where each one lives.
Product and category templates. Set a sensible default title and description pattern for products and for product categories. Then write custom ones for your top pages by hand.
What gets indexed. Decide which kinds of page belong in search results. Product pages, product categories and articles usually do. Cart, checkout and account pages should not. Tag archives and internal search results pages deserve a decision rather than a default. You will find the reasoning on the page about duplicate content.
Sitemap contents. Make sure the sitemap lists the pages you want found and leaves out the ones you excluded. Submit it in Google Search Console and check for errors.
Structured data. Confirm that product pages output product information once, not twice. Test a few product URLs with the Rich Results Test.
Breadcrumbs. If your theme or plugin offers breadcrumbs, they help visitors and search engines see how pages relate. Pick one source for them.
Site identity. Fill in your business name and basic details so the plugin can describe your organization consistently.
That is about an hour of work, and it is the best use of a plugin. Then stop fiddling with settings and move on to the pages, because that is where the traffic comes from. Our WooCommerce SEO guide follows on from here.
Common mistakes with SEO plugins
Most plugin trouble comes from a few repeated habits. Knowing them saves hours.
Chasing green lights. Many plugins show a colored score beside each page. It is tempting to treat green as done. The score checks a handful of rules, such as whether a chosen phrase appears in the title. It cannot tell whether the page is the best answer to the question. Use the score as a prompt and your own judgment as the decision.
Leaving every default on. Defaults are chosen to suit the average site, and your store is not average. Archives, tag pages and attachment pages may all be indexable until you say otherwise. Go through the index settings once and decide on purpose.
Indexing the wrong pages. Cart, checkout and account pages have no place in search results. Thin tag pages and internal search results rarely do either. Check what your sitemap contains and compare it with the pages you want found.
Duplicate structured data. WooCommerce, your theme and your plugin can each add product data. Two competing sets can confuse a validator. Test a product page and trim the overlap.
Never revisiting it. Plugins are updated, and features move between plans. Once or twice a year, read the changelog or documentation for what is new and check your settings still make sense.
Installing a plugin as a substitute for a plan. The plugin is a tool. A plan names which pages to write, in what order and how you will measure. Without a plan, the plugin only tells you what is missing.
Avoid these and a modest, well-configured plugin does its job quietly in the background, which is exactly what you want from it.
How RunOctopus handles this
A plugin sets up the controls and then waits for someone to fill them. If you want the filling done as well, here is how we work.
RunOctopus is a done-for-you service. Its AI, Ollie, researches your business, then writes and publishes pages directly on your own website. A team plans, writes, reviews and publishes alongside Ollie. It works with Shopify, WordPress, WooCommerce and Wix. You install nothing, approve nothing, upload nothing and schedule nothing, and pages go live on their own.
The first week brings 8 long-form articles, 6 pages and a custom interactive tool built for your niche. After that it is 175+ pieces of content a month, written, published and linked. You also get reports on where ChatGPT, Perplexity, Claude and Gemini name your business. The promise is more visibility on Google and in AI answers within 90 days, measured against the 90 days before you joined, or every dollar back.
You can see what Ollie would do for your store before you decide anything. Paste your address into the free site read. Ollie reads the site and shows the plan. No account, no call.