Customers

Blog

Magento SEO: An Adobe Commerce Guide for Catalog Teams

The admin settings to change on day one, layered navigation that doesn't flood Google with filter URLs, and the attribute work that decides whether product pages rank. Plus multi-store setup.

Alberto Barberis

By Alberto Barberis, Founder and CEO, AndromedAI · Updated October 2026

The short answer

Magento SEO is the work of configuring Adobe Commerce (or Magento Open Source) so search engines and AI agents can crawl a store's catalog and understand it. On a real store it comes down to four jobs: correct URL and canonical settings, controlled layered navigation, complete product attributes, and reciprocal hreflang across store views.

01

Magento SEO: the short answer

Adobe Commerce ships with most of the SEO controls a catalog needs, yet several defaults work against a large store. Fix canonicals first, then layered navigation, then product data.

  1. 01

    Most Magento SEO problems are configuration and data problems. Extensions only help at the edges.

  2. 02

    Layered navigation is the biggest source of crawl waste on the Magento stores we audit. Decide which filters deserve an indexable page and block the rest.

  3. 03

    The attributes you fill in the admin feed your product pages and your Merchant Center feed at the same time, along with your structured data. Thin attributes hurt every channel.

  4. 04

    Multi-store setups break quietly. A missing hreflang return link can sit unnoticed for years.

02

The Adobe Commerce SEO settings we change first

Most of the configuration sits under Stores > Settings > Configuration > Catalog > Catalog > Search Engine Optimization. Turn on both canonical tags, keep category paths out of product URLs and check the robots default before anything else.

Open the admin before the crawler. A few settings apply to every product at once, and Magento exposes far more of them than plugin-based platforms (compare our WooCommerce SEO guide).

SettingWhere to find itWhat we set and why
Use Canonical Link Meta Tag for CategoriesCatalog > Catalog > Search Engine OptimizationYes. Sorted and filtered category URLs then point back to the clean category.
Use Canonical Link Meta Tag for ProductsSame sectionYes. The canonical becomes domain/url-key whichever category the shopper came from.
Use Categories Path for Product URLsSame sectionNo, which is the default. One URL per product beats a keyword in the path.
Create Permanent Redirect for URLs if URL Key ChangedSame sectionYes. Without it, every renamed product turns into a 404.
Default RobotsContent > Design > Configuration > Search Engine RobotsINDEX, FOLLOW on production. Recheck it after every staging copy.

Adobe recommends switching on the canonical tag for both categories and products (Adobe Experience League). Clear "Use system value" first, or the change won't stick.

Where we disagree with most Magento guides

Plenty of guides tell you to turn on Use Categories Path for Product URLs because /women/jackets/ridge-shell.html looks keyword rich. We'd leave it off. A product in three categories then gets three URLs, and internal links split across them. Adobe's own default keeps the category path out of product URLs (Adobe Experience League).

Skip the meta keywords field too. Google stopped reading it long ago.

Meta fields and the auto-generation trap

Adobe's guidance is a unique meta title under 70 characters and a meta description of 150 to 160 characters; the field accepts 255 (Adobe Experience League). Check Catalog > Catalog > Product Fields Auto-Generation too. Adobe documents the default Mask for Meta Description as the product name plus the description, {{name}} {{description}} (Adobe Experience League), so new products launch with snippets that repeat the name and cut off mid-sentence.

Generate one XML sitemap per store view under Marketing > SEO & Search > Site Map (Adobe Experience League).

The strategy behind these settings is in the ecommerce SEO guide.

03

Layered navigation SEO: filters without index bloat

Layered navigation turns every filter click into a crawlable URL. Keep most of them out of the index and turn the few filters people actually search for into real landing pages.

Layered navigation only runs on anchor categories. An attribute appears as a filter when its Use in Layered Navigation property is set to a filterable option under Stores > Attributes > Product > Storefront Properties (Adobe Experience League). Out of the box the filters write query parameters, so /women/jackets.html?color=49&size=172 is a new URL as far as Googlebot is concerned. Those numbers are option IDs, meaningless to shoppers and search engines alike.

Watch the "Filterable (no results)" option. It lists values with zero matches, so a big catalog links to hundreds of empty pages. Google asks for a 404 on filter combinations with no results (Google Search Central). We use "Filterable (with results)" almost everywhere.

Index the filters people search for, block the rest

The usual Magento advice is to noindex every filtered page. That's half right. A filter like waterproof on jackets or linen on dresses often matches real searches, and blocking it throws away a page you'd otherwise build by hand.

  1. 1

    List filter values with demand

    Pull keyword data for category plus attribute pairs, such as "waterproof hiking jacket women". Keep the ones with real search volume.

  2. 2

    Promote the winners to categories

    Give each its own url_key and H1, plus intro copy and meta fields, linked from the parent category.

  3. 3

    Block the long tail

    Disallow sort and display parameters in robots.txt, for example Disallow: /*?*product_list_order= and Disallow: /*?*product_list_limit=, plus multi-filter combinations.

  4. 4

    Pick one method per parameter

    A URL blocked in robots.txt can't show Google its canonical tag, so don't rely on both for the same URL.

  5. 5

    Check the Page indexing report

    In Search Console, "Duplicate without user-selected canonical" full of ? URLs means filters are leaking into the index.

Google calls robots.txt the most effective long-term option for filtered URLs (Google Search Central).

More on filter strategy in faceted navigation SEO, and on landing page copy in category page optimization.

04

Product attributes: the data that ranks Magento product pages

Attributes are where Magento stores win or lose product page rankings, Shopping reach and AI recommendations. Fill them, show the important ones on the page, and the markup and feed improve with them.

In Magento, almost everything a search engine learns about a product comes from attributes in its attribute set. The most common gap we see is attributes that exist in the set but sit empty, or live only as a sentence inside the description HTML. A shopper can read "made from recycled nylon". An AI agent comparing ten jackets needs material to hold the value.

Set "Visible on Catalog Pages on Storefront" to Yes for the attributes shoppers compare, so they appear in the More Information tab.

Configurable products and variant markup

A configurable product shows one URL, with the color and size values held on simple children that are usually "Not Visible Individually". Google's variant guidance needs one canonical URL for the group and a distinct, preselectable URL for each variant, typically with query parameters (Google Search Central). Adobe's default schema.org markup is a start (Adobe Experience League); check it in the Rich Results Test before assuming variants or GTINs are covered. The full ProductGroup setup is in the structured data guide.

693.4%

increase in generative AI traffic to US retail sites, 2025 holiday season

AI assistants now send real shoppersSource: Adobe
31%

higher conversion for AI referrals than other traffic sources, 2025 holiday season

Those shoppers arrive ready to buySource: Adobe for Business
20%

more clicks on average for retailers who added correct GTINs

One attribute, measurable liftSource: Google Merchant Center Help

Google says there are no extra requirements for AI Overviews or AI Mode beyond being indexed and eligible for a snippet (Google Search Central). Attributes then decide whether an assistant can match your jacket to a detailed request.

Google AI
Illustrative demo
Writing prompt
Illustrative example

Every fact in that answer is an attribute:

AndromedAI / OptimizerAI Readiness 31/100

name

BeforeRidge Jacket

AfterValtorre Ridge Women's Waterproof Hiking Shell, Packable, 310 g

meta_title

BeforeRidge Jacket, Valtorre Store

AfterWomen's Waterproof Packable Hiking Jacket, Valtorre Ridge Shell

meta_description

BeforeRidge Jacket Our best jacket for the mountains.

AfterPackable women's hiking shell with a 20,000 mm waterproof rating and taped seams. Weighs 310 g and stuffs into its own pocket.

attributes

Beforecolor: Blue; material: (empty); activity: (empty)

Aftercolor: slate blue; material: recycled nylon, 2.5-layer; waterproof_rating: 20,000 mm; weight: 310 g; activity: hiking, trekking

Illustrative example, AI Readiness Score from 31 to 89
05

Multi-store and multi-language Magento SEO

Adobe Commerce runs languages as store views, which makes translation easy and hreflang easy to get wrong. Translate the url_key along with the copy, give each language its own URLs and output reciprocal hreflang for every view.

Adobe Commerce stacks websites, stores and store views, and store views mostly serve locales: each one is usually a language or regional version of the storefront (Adobe Experience League). Fields like name and description, plus url_key and the meta fields, can be set per store view.

The classic bug is a missing translation that quietly inherits the default value. The Italian store then serves English copy, often under /it/waterproof-hiking-jacket.html because nobody translated the url_key either. We check for this in every store view before touching hreflang.

hreflang on Magento

Don't assume your store outputs hreflang. On Luma-based builds it usually comes from an extension, the theme or the XML sitemap, so check the page source of each store view before you trust it. Google's rule is strict: each version must list itself and every other version, and annotations that aren't reciprocal are ignored (Google Search Central). Add x-default for the country selector or your main store. On the Edge Delivery storefront, Adobe documents hreflang in its sitemap guidance and recommends prerendering when product details load client-side (Adobe Commerce Storefront).

SetupFits whenWatch out for
Store code folders (/en/, /it/)One domain serves several languagesAdd Store Code to URLs is a global setting, so it changes URLs on every store
Separate domain per websiteCountries differ in currency, catalog or legal entityEach domain needs its own Search Console property and sitemap

Adobe warns against Auto-redirect to Base URL on multi-store setups (Adobe Experience League). Avoid IP-based redirects too. Google says Googlebot's default crawl IPs appear to be based in the USA and it sends no Accept-Language header (Google Search Central), so a geo redirect can keep it from ever reaching your other store views. Translation itself is covered in the ecommerce localization guide.

06

How AndromedAI helps Magento stores

Your developers own the configuration. AndromedAI fixes the product data across every store view and publishes it back to Adobe Commerce.

AndromedAI doesn't touch your Magento configuration or layered navigation; that stays with your developers. We handle the catalog data those settings expose, which is the part of Agentic Commerce Optimization most Magento stores fall behind on.

Magento SEO taskAndromedAIWhat it does
Find thin productsAI Readiness AuditScores products on Product Data Completeness, Keyword Coverage, Customer Intent Match and Shopping Metadata
Fill attributes, rewrite names and meta fieldsOptimizerRewrites titles, descriptions, bullets and FAQ; extracts attributes; adds use cases and intents
Build promoted filter pagesCategory page optimizerBuilds category pages around real search demand
Write every store viewCreatorCreates complete product pages from brand or supplier data in 12 languages
Publish backIntegrationsPublishes to Adobe Commerce (Magento) and Google Merchant Center, among others

Every change follows your Brand Kit and passes AI checks and approval before going live.

+160%

organic traffic, with sales up 46.9%

Semprefarmacia
+80%

add-to-cart in two months

Altaforma Milano
+1,800%

clicks from AI chats

Bomboogie
07

FAQ

Yes. Adobe Commerce and Magento Open Source include canonical tags, URL rewrites, meta fields, XML sitemaps and robots controls in the admin. Most ranking problems on Magento stores come from two places: layered navigation creating thousands of filter URLs, and product attributes left empty. Both can be fixed with configuration and better catalog data, without changing platform.

Leave it off, which is the Adobe default. With it on, a product that sits in several categories gets several URLs, internal links split across them, and you depend on the canonical tag to consolidate the signals. One clean URL per product, with the product canonical tag switched on, is simpler and safer.

Set filterable attributes to Filterable (with results), keep the category canonical tag on, and disallow sort, display and multi-filter parameters in robots.txt. Then turn the few filters with real search demand, such as waterproof jackets, into proper categories with their own url_key, H1 and copy, and check the Page indexing report in Search Console.

Don't assume it does on your build. On Luma-based stores, hreflang usually comes from an extension, the theme or the XML sitemap, so check the page source of each store view. Whatever the method, every version must reference itself and all other versions, or Google ignores the annotations. Add x-default for your main store or country selector.

Yes. Google says AI Overviews and AI Mode need nothing beyond a page being indexed and eligible for a snippet, so the same crawl and canonical work applies. AI assistants then compare products on their attributes, such as material, weight or waterproof rating, so complete attribute data in Magento gives them more facts to match against a shopper's request.

08

Glossary

Layered navigation
Magento's filter panel on category and search pages, built from attributes set as filterable.
Store view
The Adobe Commerce level used for languages or regional versions of a store, below website and store.
url_key
The editable URL slug of a product or category, which can differ per store view.
Canonical link meta tag
The rel canonical tag Magento can add to category and product pages to name the preferred URL.
hreflang
An annotation that tells Google which language or regional version of a page to show each user.

Featured in