Magento and Adobe Commerce SEO: category paths in product URLs, canonical settings, the rewrite table and layered navigation, and what each one costs.
Magento and Adobe Commerce give you more SEO control than any other mainstream ecommerce platform, and they will punish you for leaving the defaults alone. Four settings decide most of the outcome: category paths in product URLs, canonical tag configuration, layered navigation behaviour, and how the URL rewrite table is maintained. Every large Magento store we have audited had at least two of those wrong.
This is what to check, why each one matters, and what it costs when it is left.
What is different about Magento SEO?
Magento is enterprise software rather than a hosted service, and it behaves like it. Nothing is decided for you. The catalogue, the URL structure, the indexing behaviour, the caching layer and the crawl rules are all configurable, which means they are all capable of being configured badly.
The naming is worth clearing up, because it confuses reporting. Magento Open Source is the free, self-hosted edition. Adobe Commerce is the licensed edition, available self-hosted or on Adobe's cloud infrastructure. They share a codebase and the SEO work is effectively identical. People search for both terms and mean the same thing.
What the platform gives you that others do not: genuine multi-store architecture, so several brands or countries can run from one installation with separate catalogues, separate content and separate URLs. Granular URL rewriting. Layered navigation you can actually control rather than work around. Catalogue tooling built for six-figure product counts. If you need any of that, the alternatives will frustrate you.
Why do Magento stores end up with duplicate product URLs?
Because of one setting, and it is on by default in a lot of installations.
Magento has an option to include the category path in product URLs. With it enabled, a product that appears in three categories is reachable at four URLs: the clean product URL, and one under each category path. On a catalogue of 20,000 products across a deep taxonomy, that is how a store ends up with several hundred thousand crawlable product URLs.
Two things follow:
- Turn category paths off in product URLs unless there is a specific reason not to. Products keep one clean URL, and the rewrite table stops growing every time a product is recategorised.
- Check the canonical settings separately. Magento has distinct options for using canonical link meta tags on products and on categories. Both should be enabled. Neither is on by default in every installation, and a store with category paths enabled and canonicals disabled has genuine, unmanaged duplication rather than a tidy one.
If the setting has been on for years, changing it is a migration in miniature. Export the current URL list, map old to new, and put the redirects in deliberately rather than trusting the rewrite table to do it quietly.
How do you keep the URL rewrite table under control?
The rewrite table is one of Magento's best features and one of its most reliable sources of trouble.
Every time a product or category URL key changes, Magento creates a rewrite. Over years of catalogue work, stores accumulate rewrites that point to rewrites that point to rewrites. The result is redirect chains that waste crawl budget and dilute the signals passing through them, plus occasional loops that produce errors nobody notices until traffic drops.
What we do:
- Export the rewrite table and look for chains longer than one hop, then flatten them so each old URL points directly at the final destination
- Look for loops, which usually come from a URL key being reused after being changed
- Check whether rewrites are being generated on save for changes that do not need them
- Keep the export, because it is the only readable history of what your URLs used to be
How should layered navigation be configured?
This is where Magento's flexibility pays off, if someone uses it.
Layered navigation generates filtered category views as parameter URLs. Left open, every combination of every filterable attribute is crawlable. Magento lets you decide which attributes are filterable at the attribute level, which is a control most platforms do not offer, and it should be used ruthlessly.
The approach that works:
- Make an attribute filterable only if customers filter by it. Internal attributes used for merchandising or logistics should not be in layered navigation at all.
- Promote the filtered views with real search demand to landing pages. If "waterproof walking boots" has volume, that should be a category or a curated landing page with content, not a parameter URL.
- Keep the rest out of the index. Robots rules can be managed from the admin, and the design configuration lets you set the robots meta directive per page type.
- Watch multi-select filtering. Allowing several values of the same attribute at once multiplies the URL count sharply.
Does Magento have a page speed problem?
Magento is heavy, and the difference between a fast Magento store and a slow one is almost entirely infrastructure and front end rather than the platform itself.
What actually moves it: a properly configured full page cache with Varnish in front, Redis for sessions and cache storage, indexers running on schedule rather than on save, production mode with compiled and minified assets, and a CDN. Those are baseline requirements, not optimisations, and a surprising number of live stores are missing one of them.
On the front end, the default Luma theme is not fast. Lighter alternatives have become the standard answer for stores that care about performance, and a front-end rebuild on an otherwise healthy Magento install is usually a better investment than replatforming.
The commercial point matters more than the ranking one. Slow category pages lose sales at a rate that is easy to measure and hard to ignore.
How does Magento handle international stores?
Better than any other mainstream platform, through store views.
A single Magento installation can run separate store views per country or language, each with its own catalogue, content, currency, pricing rules and URL structure. That is genuine multi-market capability rather than a translation layer.
What needs attention:
- Hreflang must be complete and reciprocal. Magento can generate hreflang for store views, and the output needs checking, particularly where store views share products but not content.
- Canonicals should be self-referencing per store view, not pointing back at a single master version, which would remove the local pages from the index.
- Automatic redirection by visitor location must exclude crawlers, or only one version will ever be seen.
- Currency and pricing differences belong in structured data, so each market's product markup reflects what that market actually pays.
Our hreflang implementation guide and our international SEO service cover the wider multi-market question, which is where most of the value sits for stores at this scale.
What structured data does Magento produce?
Less than you would expect, and it varies by theme.
Default installations often emit incomplete Product markup, missing availability, currency or brand. Breadcrumb markup is frequently absent even when the visible breadcrumb trail is there. Since Magento stores tend to be large, the fix is a template change rather than a page-by-page job, which makes it one of the higher-return technical tasks available: one template edit, applied across tens of thousands of products.
Validate a product template, a category template, a content page and the homepage. Do not assume the theme handles it.
Questions we get asked about Magento SEO
Is Magento good for SEO?
Very, in capable hands. It gives you control that hosted platforms do not, including per-attribute filtering, granular URL rewriting and true multi-store architecture. It also assumes you know what you are doing, and the defaults are not optimal.
What is the difference between Magento SEO and Adobe Commerce SEO?
Nothing meaningful. The editions share a codebase. Adobe Commerce adds licensed features and support, and the technical SEO work is the same.
Should I turn off category paths in product URLs?
In almost all cases, yes. It prevents a large class of duplication and stops the rewrite table growing every time a product moves category. On an established store, treat the change as a migration and map the redirects deliberately.
Why is my Magento store not being fully indexed?
Usually crawl budget spent on layered navigation and duplicate product paths rather than a crawling restriction. Compare your sitemap URL count with what Google reports discovering. When the gap is large, filters are almost always the reason.
How much does Magento SEO cost?
More than the equivalent work on a hosted platform, because the technical scope is larger and changes usually need developer time. The upside is that fixes apply at template and configuration level, so a single change can affect the entire catalogue.
Should I migrate off Magento?
Only for commercial reasons. If the catalogue complexity, B2B rules or multi-market structure that took you to Magento still apply, moving to a hosted platform will trade one set of problems for a more constrained set. If they no longer apply, that is a genuine conversation, and our guide to website migration SEO covers protecting rankings through it.
Where this usually leads
Magento stores rarely need more SEO work. They need the existing configuration corrected and the accumulated debt cleared, in an order that reflects revenue rather than tool severity scores. That is usually a smaller project than the store expects and a larger result.
Our ecommerce SEO service covers Magento and Adobe Commerce alongside Shopify and WooCommerce, and we are happy to review a technical audit you already have.
