Magento SEO: An Operator’s Guide to Adobe Commerce

Magento (Adobe Commerce) SEO is mostly about controlling what the platform generates automatically: URL rewrites, canonical tags, meta templates, sitemaps and layered-navigation filter URLs. The…

Quick answer. Magento (Adobe Commerce) SEO is mostly about controlling what the platform generates automatically: URL rewrites, canonical tags, meta templates, sitemaps and layered-navigation filter URLs. The platform ships workable defaults and no product structured data. Rankings usually turn on three things you have to build yourself — a crawl policy for faceted URLs, clean canonical and hreflang handling across store views, and a redirect map that survives migrations.

What matters most
  • Magento already writes URL rewrites, canonical tags and sitemaps; most ranking failures come from configuration and template policy, not missing features.
  • Layered navigation is the biggest crawl risk on a Magento catalogue, and the fix belongs in the layered navigation template, not only in robots.txt.
  • Core Magento does not output Product JSON-LD, so structured data is a deliberate template change built from attributes the page already renders.
  • Multi-store setups break when store codes, canonical tags and hreflang are configured independently of one another.
  • Migrations and headless rebuilds lose the most organic value, because URL rewrites do not survive a catalogue restructure and canonicals move into the front end.
What does Magento (Adobe Commerce) SEO actually cover?

Magento SEO is mostly configuration, not code. The platform writes a URL rewrite every time a product or category is saved. It prints a canonical tag on product and category pages. It builds a sitemap from your catalogue on a schedule. It also turns filterable attributes into indexable URLs, which is where most catalogues get into trouble.

The useful split is between what the admin controls and what the theme controls. Four surfaces do most of the damage:

  • URLs. Product and category URL keys, suffixes, category paths, and the url_rewrite rows that connect old URLs to new ones.
  • Templates. Meta titles and descriptions, heading structure, canonical output, robots meta, hreflang and JSON-LD.
  • Layered navigation. Which attributes are filterable, what URLs those filters create, and which of them are allowed to rank.
  • Infrastructure. Full-page cache, CDN, static content deployment, and the crawl capacity your catalogue actually needs.
Where to go next
Which Magento admin settings actually change anything?

The settings that matter live in two places: Stores > Configuration > Catalog > Catalog > Search Engine Optimization, and Marketing > SEO & Search > URL Rewrites. Start with the first.

URL Rewrites is where you find out whether the configuration worked. Every rewrite Magento generates lands in the url_rewrite table, and the grid shows the request path, the target path and the redirect type. Two things go wrong routinely. Chains form when a product’s URL key changes twice and each change adds a 301 to the previous one. Several live URLs form when a product sits in multiple categories and category paths are part of the product URL, because each path gets its own rewrite to the same product.

robots.txt and the sitemap both have admin screens and both go stale. robots.txt is edited per store view under Content > Design > Configuration > Search Engine Robots. It shapes crawling; it does not remove a page from the index, and a disallowed URL can still be indexed if other pages link to it. The sitemap under Marketing > SEO & Search > Site Map is generated from products, categories and CMS pages per store view, and excludes products set to Not Visible Individually. After a catalogue import, open the generated file and confirm it.

  • Product and category URL suffix. Pick one and keep it across store views. Changing it later rewrites every URL on the site.
  • Use Categories Path for Product URLs. On means /category/product.html, off means /product.html. Decide before launch; switching is a site-wide URL change.
  • Create Permanent Redirect for URLs if URL Key Changed. Leave it on. It is the only thing standing between a renamed product and a 404.
  • Product Fields Auto-Generation. Fills default meta titles and descriptions from attribute patterns such as {{name}} and {{description}}. Useful as a floor, not as a strategy, because the output is thin and repeats across similar products.
How do you stop layered navigation from eating your crawl?

Magento turns every attribute set to Filterable under Use in Layered Navigation into a URL. One filter is usually a query string; several filters, or an SEO-friendly layered navigation extension, produce a path instead. Multiply your filter values together and a mid-sized catalogue exposes far more filter URLs than it has products. Most of those should never be indexed.

There are two honest policies and both work. Either no filter URL ranks, and every filtered view canonicalises to its parent category. Or a small, named set of filter combinations gets its own landing page — a real category with its own URL key, meta, description and copy, not a parameter.

Before you touch a template, check that the filter data is correct. Filter counts come from the catalog_product_attribute and price indexes. If a filter shows zero products for a value that clearly exists, run bin/magento indexer:status and reindex before editing markup.

  • Choose the attributes deliberately. Brand, price band and one or two defining specs are the usual candidates. Size, colour and stock status combined are not.
  • For combinations that should rank, build a category. Parameter URLs inherit weak signals; a category page with copy does not.
  • For everything else, set rel=canonical from the layered navigation template to the clean category URL. Do not pair canonical with noindex on the same URL; the two instructions conflict.
  • Use robots.txt only for patterns you never want crawled, and accept that a blocked URL can still be indexed if something links to it.
  • Check the attribute’s filterable setting. Filterable (no results) keeps values visible when no products match, which produces empty, indexable pages.
What breaks when you run more than one store view?

Magento’s multi-store model is genuinely capable: per-store base URLs, currencies, languages and catalogue scope. The same flexibility produces duplicate content when canonical tags, hreflang and store URLs are configured independently of each other.

Two settings decide the shape. Under Stores > Configuration > Web > Url Options, Add Store Code to URLs puts the store code in the path. Under Catalog > Price > Catalog Price Scope you decide whether prices are global or per website, which determines what your currency and offer markup can honestly say.

Magento does not generate hreflang. You add it in the head template per store view, or through a module. Whatever you use, keep it consistent with the canonical: each localised page should canonicalise to itself and carry a self-referencing hreflang plus the full set of alternates. Pointing every store view’s canonical at the default store removes the localised pages from consideration altogether.

Check for store parameters in URLs. The store switcher can produce links with ?___store= and ?___from_store= appended, which are duplicates of clean URLs. Either generate clean store URLs or make sure the canonical tag drops the parameters.

Does Magento output product structured data?

No. A stock Magento or Adobe Commerce theme does not print Product JSON-LD. There is no offers, price, availability or aggregateRating markup in the default product template. You add it in the product view template or through a module, built from attributes the page already renders: name, sku, price, special price, stock status and review count.

Two rules keep it out of trouble. The markup must describe what the page shows, because a JSON-LD price that disagrees with the visible price is a rich-result violation rather than a win. And variant handling matters: if configurable children are set to Not Visible Individually, describe the parent and its variants rather than a single child that may not be purchasable.

Performance is the other theme-side job. Magento behaves well when full-page cache is on, Varnish or Fastly sits in front, static content is pre-generated in production mode, and the theme does not ship every JavaScript dependency on first paint. Measure the category and product templates you rank with, not the home page.

What does Magento do out of the box, and what do you build?

The pattern holds across versions: Magento ships the plumbing and leaves policy to you.

SEO elementMagento defaultWhat an operator has to do
URL rewritesGenerated on save; 301 on URL key change when enabledAudit Marketing > SEO & Search > URL Rewrites for chains and duplicates
Canonical tagPrinted on product and category pagesVerify on filtered, paginated and multi-store URLs
Product structured dataNot included in core themesAdd JSON-LD in the product template from existing attributes
hreflangNot generatedBuild per store view and align with the self-canonical
SitemapGenerated per store view on a scheduleExclude noindex pages and recheck after every import
Robots meta on search resultsTheme and module dependentConfirm /catalogsearch/result/ cannot be indexed
What breaks in a Magento migration?

Migrations are where most organic traffic is lost: Magento 1 to Magento 2, Magento to Adobe Commerce Cloud, or Magento to a headless front end. URL keys regenerate, category paths change, suffixes change, and the Data Migration Tool moves url_rewrite rows without inventing redirects for URLs the new catalogue no longer produces.

A redirect map is not optional. Export every URL that received organic entrances over the last twelve months, map each to the closest live equivalent, and 301 to the parent category where there is no product match. Check the map for chains and loops before launch, against a full crawl of the old site rather than a sample.

The part teams underestimate is the headless build. When the storefront runs on PWA Studio or a custom front end over the GraphQL API, the canonical, hreflang and JSON-LD move into the front end. Magento supplies data; it no longer supplies markup. Nothing in the admin warns you when the front end omits a canonical tag. That half of the SEO surface is yours to test.

  • Keep existing URL keys where the platform allows. A product does not need a new URL because the platform changed.
  • Map discontinued products to their parent category rather than to the home page.
  • Resubmit sitemaps per store view and watch coverage reports for 404s in the first weeks.
  • On a headless build, add canonical, hreflang and structured data checks to the front-end release checklist.
Frequently asked questions

Does Magento handle SEO well out of the box?

Partly. Magento handles the mechanical parts: URL rewrites on save, canonical tags on products and categories, per-store sitemaps and editable robots.txt. It does not handle policy. It will happily expose thousands of filter URLs, skip product structured data and leave hreflang to you. Treat the defaults as a starting point you still have to configure. Stores that rank well on Magento are the ones where somebody made those decisions deliberately.

Should I noindex layered navigation URLs in Magento?

Pick one approach and apply it consistently. Either canonicalise every filtered URL to its parent category, or build the filter combinations worth ranking as real categories with their own URL keys, meta and copy, then canonicalise the rest. Avoid placing noindex and a canonical on the same URL, because the signals conflict. Use robots.txt only for patterns you never want crawled, and remember that disallowed URLs can still appear in results when other pages link to them.

How do I add product schema to Magento?

There is no built-in JSON-LD block, so you add it yourself. Put it in the product view template, or in a small module that renders a script block, and build it from attributes the page already has: name, sku, price, special price, stock status and review count. Keep the markup identical to the visible price and availability. For configurable products, describe the parent and its variants rather than one child that may not be purchasable.

Will changing a product’s URL key lose its rankings?

Not if the redirect is generated. Magento creates a 301 when a URL key changes, provided Create Permanent Redirect for URLs if URL Key Changed is enabled in the catalog configuration. The real risk is accumulation: repeated renames build chains of redirects, and a product assigned to several categories can end up with multiple live URLs. Audit Marketing > SEO & Search > URL Rewrites after any bulk import or re-merchandising pass.

Do I need an SEO extension for Magento?

Not for the basics. Canonical tags, meta templates, sitemaps and redirects are all in the core. Extensions earn their place for specific jobs: search-friendly layered navigation URLs, bulk meta editing across large catalogues, or hreflang generation across many store views. If you install one, check that it does not duplicate or override the core canonical output. That is the most common cause of unexpected canonical tags on a Magento site.

Sources
Get your Magento SEO configuration reviewed

The audit checks URL rewrites, canonical output, layered navigation policy, structured data and Core Web Vitals on your live store, and returns a prioritised list of fixes with the templates and admin settings involved.

Request a Magento SEO audit