Category path is on for products
The same SKU is /mens/shirts/blue-oxford.html and /sale/blue-oxford.html. Crawl hits both. We pick one path. We 301 the rest. Crumbs can stay in the template.
Magento SEO
Magento SEO to Control Catalog URL Rewrites
Magento builds a public URL from a URL key, a store view, and a rewrite row. One SKU can land at many paths if category paths are on. Layered navigation can add more. We pick the product URL that should live. We name which store views are real catalogs. We stop filter mixes from becoming a second index.
- Rewrite
- View
- Facet
- Index
Position
Magento invents a URL. The rewrite table keeps it.
Adobe Commerce is not a simple folder tree. Each product has a URL key. Each store view can change that key. Magento can also prepend the category path. Search intent has to live on the HTML for the one path you keep. Five rewrite rows for the same SKU are not five shopping jobs.
Catalog rules on any stack
Ecommerce SEO writes which product and filter classes may be documents, platform aside. Stay here when the leak is a Magento rewrite, a store view, or layered navigation. Open that page when the rule would still be true off Magento.
Open ecommerce SEOA WooCommerce shop
Woo holds WordPress product slugs and plugins. Magento holds URL keys, rewrites, and store views. If the cart is Woo, open that page.
Open WooCommerce SEOA Shopify store
Shopify uses theme HTML, apps, handles, and Markets. Magento uses rewrites and store views. They are not the same admin.
Open Shopify SEOHosts and return tags
International SEO owns the host model and hreflang. Magento store views that clone a catalog stay here. We will not write a second hreflang treatise on this URL.
Open international SEOWe start in Catalog, URL Rewrites. Then store views. Then layered navigation. Catalog rules that would be true on Shopify or Woo stay on ecommerce SEO. Shopify and WooCommerce have their own pages. Hosts and hreflang stay on international SEO. Fetch after a deploy stays on technical SEO.
We will not turn on category paths for products to make crumbs look nicer. We will not index every layered mix because a module can. We will not treat Magento 1 as a living platform. If the cart is WooCommerce, open that page. If the store is Shopify, open Shopify SEO.
When this fits
When one SKU has many public paths
This page fits when Magento itself is making extra URLs: category paths on products, store views that copy the tree, or layered navigation that indexes mixes. If you needed a catalog rule that travels, a Woo shop, or a host contract, start there instead.
A new store view copied the catalog
Marketing wanted a language or a brand site. Magento cloned products. Canonicals and sitemaps now disagree. We name which views are real catalogs. The rest stop publishing.
Layered navigation indexes every mix
Color, size, and price stack as crawlable URLs. Search Console is full of filter copies. Money categories are not. We write which facets may stay. The rest stay shopper tools.
The rewrite table is a graveyard
Old keys, old categories, and old views still have rows. The sitemap lists paths Magento no longer means. We clean the table against live URL keys. A leftover 301 is not a strategy.
Process
Rewrite, store view, facet, indexer
Four Magento jobs in order. Each one ends with a note admin can keep. We do not start a Hyva rebuild inside the indexer step. The point is one public path per product you mean to sell.
-
Rewrite
We export how products and categories are addressed now. URL keys. Suffix. Category path on or off. Rows already in Catalog URL Rewrites. This step is not copy. It is whether Magento is minting extra product URLs. Admin preview is not a fetch.
Outcome A map of live product paths, including duplicate rewrite rows.
-
View
We list websites, stores, and store views. Which ones are real catalogs. Which ones only change currency or a banner. Keyword targeting stays on the view that must rank, not on a clone. A view that copies every product needs a job or a stop.
Outcome A store-view list that says which catalogs may publish.
-
Facet
We write yes or no for layered navigation. Magento native, ElasticSuite, or another module. Topical relevance is the test: does this mix match a real shopping job, or is it a convenience filter? Keyword density on a filter landing page is not a Magento score.
Outcome A facet list the navigation and filters can follow.
-
Index
We check Catalog URL Rewrites and related indexers after a key change. Semantic keywords belong only on the kept product or category template, not as extra rewrite rows. Sitemap URLs must match the kept paths. Coverage on that set is the watch.
Outcome Indexer and sitemap notes that match the rewrite map.
Deliverables
What Magento admin can keep after we leave
You leave with a rewrite map, a store-view list, a facet yes-or-no, and indexer notes. You do not leave with a Shopify theme pass, a Woo plugin list, or a ranking date.
Rewrite map
Product and category paths Magento actually publishes, including category-path duplicates. Dated. Last season's spreadsheet is not this map.
Canonical product path
The one URL a SKU should keep. Other category paths 301. Crumbs can stay. A new category assignment must not mint a new public product URL.
Store-view list
Which views are real catalogs. Which only change price or language chrome. A clone with no unique assortment is named.
Facet yes-or-no
Layered navigation mixes that may be documents. The rest stay tools. Navigation should match.
Indexer note
Which Magento indexers must finish after a key or category change, plus sitemap URLs that must match. Pending rewrites are named.
Benefits
What a new category should not create
One SKU stops living at five URLs
Category assignment still works for merchandising. The public product path stays one. Ads and reviews stop splitting.
Store views stop cloning the tree
A real market view can publish. A banner-only view does not get a second sitemap.
Filter mixes stop filling Search Console
Shoppers can still filter. Crawlers get the mixes you named. Money categories get crawl back.
The rewrite table matches the sitemap
Old keys and dead categories leave. Coverage reports get easier to read.
Methodology
Who can change a URL key
This works when one person can edit Catalog URL Rewrites, and one person can refuse a new store view. If both are missing, we are touring Magento settings. We are not holding a catalog.
We start with the products that must work this month, the store views already live, and the person who can change a URL key. If any of those is missing, we name it first. We do not spend the week touring other SEO specialties.
We fetch published HTML on the public path. We do not trust the admin product screen. Does this category match a real assortment? Is a store view a catalog, or only a price list?
You may rename the roles below. You may not leave store-view creation implied. An implied view is how a brand site copies fifty thousand product URLs overnight.
- Magento SEO lead SEOConsultants.ai writes the rewrite map, the view list, and the facet list. We do not become your Magento agency because the catalog is large.
- Whoever owns Magento admin Can edit URL keys, rewrites, and store views, and can reindex after a change. A locked Cloud project with no deployer is a finding.
- Merchandising Names real categories and whether a product may move. Assigning a SKU to a new category must not mint a new public path.
- Whoever adds Magento modules Stops layered-nav or SEO modules from publishing URLs the facet list did not approve. They do not need to write PHP for that.
- Leadership Funds rewrite cleanup or refuses another store view this period. An unread coverage sample is not a failure of this page. A ranking promise would be.
First working session
Start with one SKU that has two URLs
The first hour is one product with more than one public path, plus the store views already live. It is not a tour of every Magento module.
We pick a money SKU. We list every URL Magento currently serves for it. Category paths. Old keys. Store-view copies. If two of those pages share one unique paragraph, we keep one path before we touch titles. If the real question is catalog classes that would be true off Magento, that is ecommerce SEO. If the store is mid-cutover, that is migration SEO.
Then we fetch those URLs, robots, and the sitemap. We compare that to Search Console by path pattern. The extra rows are usually the job. A Hyva or Luma preview while you are logged in is not evidence.
We leave with a first map or a stop. A map names the kept product path, the views that may publish, and who may add a store view. A stop names what is missing: admin access, a merch owner, or a platform that is not Magento. Both are outcomes. A list of Magento SEO extensions is not.
AI search
A Magento SEO module is not an AI Overview
Honest product HTML on one path can help later extraction. This page cannot sell AI Overviews, a shopping-chat mention, or LLM visibility as a score.
People ask whether a Magento SEO extension will land SKUs in Google AI Overviews (AIO). If the same product exists at five URLs, or if layered mixes have exploded, generative search has too many near copies, or nothing honest to lift. That is ours to tidy. If the kept page already tells the truth and models still invent SKUs, that is an AI search audit. A program across search UIs is AI SEO.
The kept path has to print the spec
AI search needs one page it can fetch. Attributes that live only in admin do not help. We do not sell Overview presence.
The name on that path should match the SKU you sell
We check brand and product names in the published HTML. That is entity optimization as a catalog 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. One clean Magento product URL can make a SKU look real. It does not sample answers.
Schema
Markup follows the kept product URL
JSON-LD helps a machine read a product the kept page already states. This work can stop Magento and an SEO module from injecting two Product blocks. It is not a schema campaign as the whole job.
One Product block on the kept path
If Magento and an SEO module both inject markup, we pick one. Valid types still need facts that match the HTML.
No FAQ stuffing on a category grid
We refuse FAQ blocks that exist only to host more terms. A real fitment question can live on the product template.
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.
Who we work with
The person who can edit URL Rewrites
Someone has to refuse a new store view. We work with that person. We do not replace them with a second Magento retainer.
Magento admin owner
Ships URL keys, rewrites, and store-view settings. Rechecks after a reindex. They keep the public path stable.
Merchandising
Names real categories and whether a SKU may move. Holds the rewrite rule when a campaign wants every category path live.
Modules or ads already in motion
Can keep going once public paths 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
Should product URLs include the category path?
Usually no. Magento can put a product at /shoes/running/sku.html and also at /sale/sku.html. That is two public URLs for one SKU. We pick one canonical path. Category crumbs can still show in the template. The rewrite table should not invent a new product URL for every category you assign.
Is a Magento store view the same as international SEO?
No. A store view is how Magento serves language, currency, or catalog differences. International SEO owns hosts, folders, and hreflang when markets need a return-tag contract. We set Magento views so they do not clone the same product tree. We do not rewrite the host model on this page.
Do you still work on Magento 1?
Only as a move off it. Magento 1 is end of life. Living work here is Magento 2 and Adobe Commerce: URL keys, store views, layered navigation, and the rewrite table. A cutover off Magento 1 is migration SEO, not a Magento 1 tutorial.
Should every layered navigation mix be indexed?
No. A filter people actually shop, with unique facts, can be a page. Color plus size plus price stacked as crawlable URLs usually should not. Magento, ElasticSuite, or an Amasty module can publish those mixes. We write which facets may index. The rest stay tools.
Will a clean rewrite table get us into AI Overviews?
No. Stable product HTML can help AI search later. It does not buy a place in Google AI Overviews (AIO), a generative-search mention, or an LLM visibility score. If the catalog already tells the truth and a model still invents a SKU, that work sits on an AI search audit and on LLM SEO.
From Magento admin
Does one SKU live at five category paths?
Send the storefront, Magento admin or a staging login, and whether category paths are on for products. We will say if the leak is rewrites, a store view clone, or layered navigation. Then we name the next row to change.
- One public path per product
- Store views that are real catalogs
- Facets with a yes or no
- Rewrites that match the sitemap
Rewrites held. Views named. Facets chosen.