The shop page and a category share one heading
Both say Sale or All products. Both rank for the same query. Neither has a unique job. We split them, or we noindex one. Leaving both live is how the catalog looks empty.
WooCommerce SEO
WooCommerce SEO to Hold WordPress Product URLs
WooCommerce lives on WordPress. Products are posts. The shop is a page. Categories, tags, and attributes can each make archives. Plugins can add more URLs on top. We hold the product slug. We say which archives may be real pages. We stop leftover image URLs and filter plugins from ranking as the shop.
- Slug
- Template
- Plugin
- Archive
Position
The shop is WordPress. The product URL is WooCommerce.
A Woo store is not a flat list of SKUs. It is a product post type, a shop page, category archives, optional tags, attributes, and whatever the last plugin decided to publish. Search intent has to show up in the HTML a crawler gets. A logged-in block editor is not that HTML.
WordPress with no cart
Posts, pages, and CMS plugin fights belong on WordPress SEO. A product slug, a shop archive, and a Woo filter stay here. An image attachment that is not a product goes back to that page once we close the shop leak.
Open WordPress SEOCatalog rules that travel
Ecommerce SEO writes which product and filter classes may be documents on any stack. Stay here when the leak is a Woo permalink, a Woo plugin, or the shop page fighting a category. Open that page when the rule would still be true off WordPress.
Open ecommerce SEOA Shopify Online Store
Shopify uses theme output, apps, collection handles, and Markets. This page assumes WooCommerce on WordPress. A move onto or off Woo is migration work, not a theme lecture here.
Open Shopify SEOAdobe Commerce
Magento SEO owns that platform's rewrites and store views. Woo product slugs and WordPress plugins are a different job. Open Magento SEO if that is the stack you run.
Open Magento SEOWe start with the product slug. Then we look at the shop page versus product categories. Then we look at plugins that print URLs, robots, or schema. WordPress blogs and leftover media that are not commerce stay on WordPress SEO. Catalog rules that would be true on any platform stay on ecommerce SEO. Shopify keeps its own page.
We will not change the whole permalink pattern to chase a nicer looking URL. We will not index every color and size because a filter plugin can. We will not run Yoast and Rank Math as two speakers on the same product. If the stack is Magento, open that page.
When this fits
When leftover shop URLs outnumber products
This page fits when WordPress is publishing shop URLs nobody listed on purpose. Product slugs, the shop page, category archives, attributes, or plugins. If you needed a catalog rule that travels, a blog pass, or Shopify theme work, start there instead.
A filter plugin built a page for every color
Layered navigation, FacetWP, or a similar plugin now indexes size, color, and price copies. Search Console is full of parameters. The money categories are not. We write which archives may stay. The rest stay tools.
Someone changed Permalinks to tidy titles
Settings, Permalinks, or a product slug edit moved paths. Ads and reviews still hit the old URL. We treat that as a same-week redirect job. A title change is not a reason to move the slug.
Image attachment pages rank as products
WordPress left media URLs in the index. They reuse the product name. Crawl hits the photo page, not the buy page. We close that leak here. Other leftover CMS objects still belong on WordPress SEO.
Process
Hold the slug. Then choose what else may index.
Slug, then template, then plugins, then archives. Each step ends with a note you can keep in wp-admin. The last step is not a Magento rewrite. It is a yes-or-no list for shop URLs WordPress already publishes.
-
Slug
We map how products, the shop page, and categories are addressed today. Pretty permalinks, trailing slashes, leftover ?p= IDs, attachment paths, and redirects already in place. This step is not copy. It is whether a crawler can keep a stable product URL. A wp-admin preview is not a fetch.
Outcome A dated map of live product and shop URL patterns, including leaks.
-
Template
We name the unique blocks merchandising can keep on product and category templates. Specs you sell. Fit. Materials. Care. Not a keyword paragraph above a grid. Keyword targeting is one job per money template. Keyword density in the short description is not a Woo score. Variations get a written rule: parent page, or a real buying URL.
Outcome Template blocks merchandising can maintain, plus a variation rule.
-
Plugin
We list plugins that emit URLs, robots, canonicals, or JSON-LD. Woo core already prints product facts. An SEO plugin may add a second Product graph. We pick one speaker. Topical relevance is not a reason to let a filter plugin publish every combination. We will not write a Yoast versus Rank Math essay. We will say which plugin may speak.
Outcome A plugin list that says what may publish URLs, and what must stop.
-
Archive
We write yes or no for the shop page, product categories, tags, and attributes. Semantic keywords belong only when they are still the same shopping job. Internal search and sort parameters stay tools. Coverage on the yes list is the watch. A ranking report for every tag is not.
Outcome An archive list the navigation and filters can follow.
Deliverables
What stays in wp-admin after we leave
You leave with a path map, a variation rule, a plugin speaker, and an archive yes-or-no list. You do not leave with a Shopify theme pass, a Magento rewrite, or a ranking date.
Path map
Product, shop, category, attachment, and leftover parameter URLs you actually publish. Dated. A screenshot from last season is not this map.
Parent versus variation
When a variation is its own page, and when it stays on the parent. Indexing every SKU Woo can generate is not a rule.
Schema speaker
Which system may print Product JSON-LD. Woo core, Yoast, Rank Math, or another add-on. Two graphs on one path are named and stopped.
Archive yes-or-no
Shop page, categories, tags, and attributes. Navigation should match. A tag that exists only to complete a box in wp-admin is named.
Slug-change log
Paths that already moved, plus the redirect that should have shipped the same week. A title tidy is not a reason to skip the log.
Benefits
What a theme update should not undo
The shop page stops fighting categories
Each has a job, or one is closed. Shoppers and crawlers stop landing on two empty grids.
Product slugs stop moving with titles
Editors can rewrite a heading. The URL stays. When a slug must move, the redirect ships in the same week.
One set of product facts in the HTML
Woo and the SEO plugin stop arguing. Extractors get one name, one price, one stock state.
Photo URLs stop ranking as SKUs
Attachment pages leave the product index. Crawl goes back to the page that can sell.
Methodology
Who can change a product slug
This works when one person can freeze Permalinks, and one person can refuse a new plugin. If both are missing, we are browsing the plugin directory. We are not holding a shop.
We start with the products that must work this month, the plugins already on, and the person who can edit a slug. If any of those is missing, we name it first. We do not spend the week touring other SEO specialties.
We fetch published HTML. We do not trust the editor while you are logged in. Does this category match a real assortment people search for? Is an attribute archive worth keeping, or should it stay noindex?
You may rename the roles below. You may not leave plugin installs implied. An implied FacetWP or layered-nav setting is how a shop grows tens of thousands of thin URLs overnight.
- WooCommerce SEO lead SEOConsultants.ai writes the path map, the schema speaker, and the archive list. We do not become your WordPress agency because the plugin list was long.
- Whoever owns wp-admin Can edit slugs, templates, and plugins, and can recheck after a theme update. A locked admin with no editor is a finding, not a delay we ignore.
- Merchandising Names real categories and whether a product slug may move. A category nobody will maintain is a candidate to close.
- Whoever adds plugins Stops URL generators the list did not approve. They do not need to write PHP. They do need to stop treating an SEO plugin as a plan.
- Leadership Funds template work or refuses another plugin this period. An unread coverage sample is not a failure of this page. A ranking promise would be.
First working session
Start with the last product that lost its URL
The first hour is the last slug change, the last plugin, and what Search Console already shows. It is not a tour of the WordPress plugin directory.
We ask which products and categories have to work now. Index everything Woo made is not an answer until those templates are listed. If two live categories share one unique paragraph, we merge or rewrite before we touch titles. If the real question is catalog classes that would be true off WordPress, that is ecommerce SEO. If the store is mid-cutover, that is migration SEO.
Then we fetch published HTML, robots, and a sample of plugin URLs. We compare that to coverage and to the last permalink change. The gap is usually the job. A Gutenberg layout that looks finished while you are logged in is not evidence.
We leave with a first list or a stop. A list names the template, the plugin, and who may install the next one. A stop names what is missing: wp-admin, a merch owner, or a store that is actually moving platforms. Both are outcomes. A pile of SEO plugin names is not.
AI search
Woo schema will not place a SKU in AI Overviews
Clean product HTML can help later extraction. This page cannot sell AI Overviews, a shopping-chat mention, or LLM visibility as a score.
People ask whether Yoast Woo, Rank Math, or another add-on will land products in Google AI Overviews (AIO). If the product body is manufacturer paste, or if attribute archives have exploded, generative search has nothing honest to lift, or too many near copies. That is ours to tidy. If the shop already tells the truth and models still invent SKUs you do not sell, that is an AI search audit. A program across search UIs is AI SEO.
The spec has to be in the first HTML
AI search needs a page it can fetch. A custom field the template never prints does not help. We do not sell Overview presence.
The name on the page should match the product you sell
We check brand and product names in the published HTML. That is entity optimization as a shop input. It is not a Knowledge Graph project from this page.
Measuring model answers is another URL
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. Unique product HTML can make a SKU look real. It does not sample answers. Extra synonyms in a category intro are not that work.
Schema
One Product block. One plugin.
JSON-LD helps a machine read a product the page already states. This work stops Woo and an SEO plugin from injecting two blocks. It is not a schema campaign as the whole job.
Name the speaker
If WooCommerce and an SEO plugin both inject Product markup, we pick one. Valid types still need facts that match the HTML you publish.
No fake FAQ above a category grid
We refuse FAQ blocks that exist only to host more terms. A real fit or care question can live on the product template. Stuffing is not a module.
Extra fields do not buy a shopping mention
Markup will not force generative search to cite the SKU. A paid Shopping placement is a different job. Eligibility is not a purchased mention.
Who we work with
The person who can freeze Permalinks
Someone has to refuse the next URL generator. We work with that person. We do not replace them with a second WordPress retainer.
wp-admin owner
Ships slugs, templates, and plugin settings. Rechecks after a theme update. They print the unique spec. They do not need to become writers overnight.
Merchandising
Names real categories and whether a product slug may move. Holds the archive list when a campaign wants every attribute indexed.
Plugins or ads already in motion
Can keep going once URL generators are honest. If they try to run this as Merchant Center only, two jobs collide. Paid Shopping still belongs on shopping ads.
Questions
Frequently asked questions
Is the shop page the same job as a product category?
No. The shop page is a WordPress page that lists products. A product category is a taxonomy archive. They can share a heading and fight. We give each one a job, or we close one. Mixing them is how both stay thin.
Should every product tag and attribute archive stay indexed?
No. A category people actually shop can be a page. A color or size archive that only repeats the grid usually should not. Tags that exist to fill a box in wp-admin are not documents. We write a yes or no list. We do not index every term Woo can make.
What if we change the product permalink structure in Settings?
That move can rewrite every product path at once. Ads, reviews, and old links still hit the old slug. Do not do it to tidy a title. If it already happened, we need the old pattern, the new pattern, and redirects in the same week. Waiting a month is how Shopping ads land on 404s.
Do color and size variations need their own URLs?
Only when the variation is a real buying page with its own facts. A swatch that changes a photo on the parent should not compete with that parent. Woo can expose variation links. That does not mean each one should index. We write the rule from the catalog, not from a slogan to index every SKU.
Will a second SEO plugin get our products into AI Overviews?
No. Yoast, Rank Math, or a schema add-on cannot buy a place in Google AI Overviews (AIO). Honest product HTML can help AI search later. It does not sell a generative-search mention or an LLM visibility score. If the shop already tells the truth and a model still invents a SKU you do not sell, that work sits on an AI search audit and on LLM SEO.
After the last slug change
Are media pages still ranking as your products?
Send the shop URL, a wp-admin login we can use, and the last plugin that went live. We will say if the leak is attachment URLs, a filter archive, a slug that moved, or a second Product graph. Then we name the next edit.
- Product slugs that stay put
- Shop page and categories with different jobs
- One Product graph per path
- Attachments out of the product index
Slugs held. Archives chosen. One schema speaker.