Guide Magento SEO

TL;DR — Magento SEO is à propos de helping a Magento store rank in search. Premier, know votre version: Magento 1 is dead (aucun updates since June 2020), and Magento 2 comes in a paid edition (Adobe Commerce) and a free un (Magento Ouvrir Source). The chose que breaks SEO on Magento plus que anything sinon is its filter system — “layered navigation” — qui peut créer thousands of duplicate page addresses. La plupart of votre fonctionner is keeping ceux sous contrôler.

Ce que Magento is (and qui version vous have)

Magento is a platform pour building online stores. Unlike Shopify, où the company hosts everything pour vous, Magento is something vous (or votre developers) install and run yourself. Que donne vous a lot of contrôler — and a lot of rope.

Avant vous do anything, figure out qui Magento you’re on:

• Magento 1 — the old version. It reached end-of-life in June 2020 and aucun plus long obtient security updates. Si you’re ici, votre réel SEO project is migrating to Magento 2 (do it carefully, with redirections).
• Magento 2 — the current version. It comes as Adobe Commerce (the paid, enterprise edition) and Magento Ouvrir Source (the free, community edition). Ils share the même core code, so the SEO advice is the même.
• Adobe Commerce as a Cloud Service (ACCS) — a newer, separate SaaS product (launched June 2025) que runs on différent infrastructure and doesn’t prise en charge the classic Luma theme at tout. Si votre store is on ACCS, treat theme/schema advice written pour “regular” Magento as a starting point, pas a direct match.

Don’t mix ces up. A lot of old “Magento SEO” tutorials online are written pour Magento 1 and the menus and settings simply don’t match anymore.

The un big problem: filters

Quand a shopper lands on a category page — dire, “Running Shoes” — Magento montre filters bas the side: size, color, brand, price. Que fonctionnalité is appelé layered navigation, and it’s great pour shoppers.

The SEO problem is que chaque filter someone clicks usually creates a brand-new web adresse, comme /running-shoes?color=blue&size=10. Multiply colors × sizes × brands × price ranges and a unique category peut spin off thousands of slightly différent pages — tout showing basically the même products. Moteur de recherches voir a mess of near-duplicate pages, obtenir confused à propos de qui un to montrer, and waste temps exploration junk au lieu de votre réel products.

The fix is to tell moteur de recherches “ces filtered pages aren’t the important ones — the clean category page is.” Vous do que with a balise canonical (a pointer to the principal version) and by marking low-value filter pages noindex (don’t put ce in résultats de recherche). Magento has settings pour ce, and SEO extensions faire it easier.

The autre choses to définir up

• Friendly URLs. Magento peut produce clean addresses comme /running-shoes/nike-pegasus/ au lieu de a long code. Assurez-vous the “search-engine-friendly URLs” setting is on.
• Titles and descriptions. Every product and category has fields pour une page title and meta description — fill les in au lieu de leaving Magento’s defaults.
• Données structurées (schema). Ce is le code que powers the price and star ratings vous voir in Google results. Magento doesn’t ajouter ce automatically, so you’ll besoin an extension or a developer to ajouter it.
• Product variants. Si a product comes in multiple sizes or colors, Magento usually stores chaque combination as its propre “simple product” lié to a parent. Left alone, ceux peut obtenir indexé as separate near-duplicate pages — point les back to the parent product with a balise canonical à la place.

Vouloir the detailed, technical version — exact settings, l’URL-rewrite table, and how to handle filters at scale? Switch to the Avancé tab.

TL;DR — Magento SEO is dominated by two duplicate-content generators: layered navigation spraying parameter URLs, and configurable/simple product variants spraying near-identical SKU pages. Canonicalize les deux back to leur clean parent (category or configurable product) and noindex the low-value combinations; reserve indexable pages pour filters or variants with réel search demand. Settle the version question premier — Magento 1 is EOL (June 2020); Magento 2 ships as Adobe Commerce (paid, self-hosted), Magento Ouvrir Source (free), or Adobe Commerce as a Cloud Service (ACCS — a separate SaaS product since June 2025 que drops Luma entirely). SEO-friendly URLs run via the url_rewrite table — distinct from HTTP redirections, qui Magento peut auto-create as 301s. Structured-data output varies by storefront theme and extensions, so inspect rendered pages avant planning custom fonctionner.

Step zero: obtenir the version straight

Half the bad Magento SEO advice online is bad parce que it’s aimed at the incorrect version. Lock ce bas avant anything sinon:

• Magento 1 hit end-of-life on June 30, 2020. Aucun security patches, aucun updates. Si a client is encore on it, the SEO fonctionner is a Magento 2 migration — with a complet redirection map and a crawl-based QA réussir, treated comme quelconque platform migration où ranking authority is on the line.
• Magento 2 is the live codebase. It ships in two editions: Adobe Commerce (paid; B2B fonctionnalités, page builder, hosted PaaS option) and Magento Ouvrir Source (free; community edition). Même core, même SEO surface area. Adobe’s branding shift signifie “Magento,” “Adobe Commerce,” and “Magento Open Source” tout montrer up pour the même underlying platform — don’t let the naming fool vous into thinking the SEO model differs.
• Adobe Commerce as a Cloud Service (ACCS) is a third, separate product — a SaaS deployment launched June 2025 with a storefront construit on Edge Delivery Services plutôt que the traditional Commerce/Luma stack. Luma isn’t pris en charge on ACCS at tout, so si a store is on it, the Luma-specific theme and schema notes ci-dessous don’t carry over — you’re rebuilding que couche from scratch, pas tweaking it.

Everything ci-dessous assumes self-hosted Magento 2 (Adobe Commerce or Magento Ouvrir Source, on Luma or Hyvä) unless ACCS is appelé out specifically.

Layered navigation is the whole game

Si vous seulement fix un chose on a Magento store, fix layered navigation. It’s Magento’s term pour faceted filtering on category pages, and by par défaut chaque filter selection appends a requête parameter:

/running-shoes
/running-shoes?color=159
/running-shoes?color=159&size=42
/running-shoes?color=159&size=42&price=50-100
/running-shoes?size=42&color=159        ← same filters, different order = new URL

Un clarification avant vous copy quelconque explorer/index strategy onto a store: Adobe documents standard layered navigation and Live Search (Adobe Commerce’s paid, AI-powered facet fonctionnalité) as distinct implementations with différent filter/URL behavior. The canonical and noindex guidance ci-dessous is written pour standard layered navigation — si a store runs Live Search, confirmer the réel URL patterns it generates avant assuming the même rules appliquer.

The combinatorial explosion is the problem. A catalog of a few thousand SKUs peut generate tens of thousands of crawlable, near-duplicate URLs. Ce is the canonical faceted-navigation échec mode, and Gary Illyes has put numbers on how beaucoup grief it causes Google — faceted navigation is the largest unique source of crawl-waste complaints ils recevoir (voir the Quotes tab). The damage on votre side: duplicate/near-contenu dupliqué, index bloat, budget d’exploration burned on junk, and internal PageRank diluted à travers hundreds of filter liens per category page.

The decision is binary, per URL pattern: fait ce filtered page deserve a placer dans l’index, or pas?

Pour the ~99% que don’t (la plupart color/size/price/sort combinations have aucun search demand):

• Canonical the filtered URL to the clean category URL. Magento 2’s “Use Canonical Link Meta Tag for Categories” setting (Stores → Configuration → Catalog → Catalog → Moteur de recherche Optimization) helps, but on its propre it points a category to itself, pas filtered variants to the parent — so pour parameter URLs vous typically lean on an SEO extension or template logic to emit the correct canonical.
• noindex the low-value filter combinations so ils drop out of the index. Remember the rule from Google: noindex exige lune page to be crawlable — jamais pair noindex with a robots.txt Disallow on the même URL, or Googlebot can’t lire the tag.
• Considérer robots.txt disallow pour purely combinatorial parameter spaces si budget d’exploration is the acute problem — but know it contrôle exploration, pas indexation, and won’t supprimer already-indexed URLs.

Pour the minority que DO have demand (e.g. a “/running-shoes/nike/” type page où the brand filter is a réel requête): promote ceux to indexable, clean-URL landing pages — unique intro copy, self-referencing canonical, lien internes, sitemap inclusion. That’s où Magento faceted nav turns from liability into long-tail asset. (Complet treatment in the faceted navigation hub, the canonical home pour ce topic on the Ecommerce side; the crawl-side mechanics live with URL parameters and budget d’exploration.)

URL rewrites and SEO-friendly URLs

Magento generates clean URLs via URL rewrites, stored in the url_rewrite database table and managed in Admin sous Marketing → SEO & Search → URL Rewrites. Adobe’s propre docs draw a sharp line entre two terms que obtenir utilisé loosely: a rewrite is a server-side mapping que changements ce que loads sans touching le navigateur’s adresse bar, pendant que a redirection sends the navigateur an HTTP réponse telling it to navigate to a différent URL — the adresse bar updates. Magento’s automatic 301-on-URL-key-change is a redirection; the url_rewrite table aussi stores internal rewrites que jamais surface to the visitor. Two settings do la plupart of the heavy lifting:

• “Use Web Server Rewrites” (Stores → Configuration → General → Web → Search Engine Optimization) strips index.php from URLs.
• URL suffixes / category-path-in-URL. Magento peut inclure the category chemin in product URLs (/men/shoes/nike-pegasus). Be deliberate: notamment the category chemin signifie a product in multiple categories peut resolve at multiple URLs, recreating duplication — qui is exactly pourquoi Magento adds canonical options pour products aussi (“Use Canonical Link Meta Tag for Products”). Nombreux Magento SEOs définir product URLs without the category chemin to sidestep ce entirely.

Quand vous modifier a product or category URL clé, Magento peut auto-create a 301 in the url_rewrite table (“Create Permanent Redirect for old URL”). Confirmer que toggle is on avant quelconque bulk URL edits, or you’ll strand indexé URLs on 404s. Avant modification category-path or suffix settings on a live store, inventory the affected URL patterns per store view and stage a redirection/canonical plan plutôt que flipping the toggle and hoping — Adobe’s propre docs warn que regenerating rewrites pour categories with nombreux assigned products peut be a réel performances hit, pas simplement an SEO un.

Configurable and simple products: the autre duplicate-content driver

Layered navigation isn’t the seulement façon a Magento catalog sprays near-duplicate URLs. Configurable products (the parent — “Running Shoe”) construit from simple products (the réel purchasable size/color combinations) créer the même échec mode at catalog scale. Vervaunt’s Paul Rogers frames the math bien: a fashion store with 3 000 parent products, chaque in 8 sizes and 6 colors, peut generate 144 000 simple-product combinations. In Magento ceux combinations are a catalog relationship, pas an indexation decision — sans an explicit canonical policy, Googlebot peut trouver tout of les as separate, indexable URLs pointing to near-identical content.

The fix practitioner guides converge on: canonical chaque simple product to its parent configurable product, and don’t rely on catalog visibility settings alone — a simple product définir to “Not Visible Individually” is encore reachable by direct URL, sitemap, or lien interne, so Googlebot peut index it même though it’s hidden from on-site navigation. An explicit balise canonical pointing to the parent is the réel fix, and it’s server-side rendered, so it isn’t dependent on JavaScript.

Index a variant on its propre seulement quand it has réel, independent search demand vous peut differentiate with unique content — a spécifique color/size combination personnes search pour by nom, pas every SKU by par défaut.

Vérifier sous Stores → Configuration → Catalog → Catalog → Moteur de recherche Optimization que “Use Canonical Link Meta Tag for Products” is on, alors confirmer — on the réel rendered page, pas simplement the setting — que simple product URLs carry the canonical back to the parent.

The JSON-LD gap

Ce un trips personnes up parce que ils assume a platform ce grand handles schema. Magento 2 ne fait pas generate JSON-LD données structurées out of the box. Some themes emit microdata on product pages, but:

• Google recommends JSON-LD as the implementation format over microdata/RDFa (voir the Official Docs tab).
• To qualify pour product résultats enrichis vous besoin Product schema with name, image, description, offers (price, priceCurrency, availability), and — pour the star ratings — aggregateRating/review, qui doit come from réel reviews.

So getting résultats enrichis on Magento is an extension or custom-development task: a dedicated structured-data extension, a schema-aware theme, or template fonctionner que outputs JSON-LD. Quand vous ajouter it, audit pour duplicate schema — si a theme’s leftover microdata and an extension’s JSON-LD les deux décrire the product, vous pouvez ship two conflicting Product blocks. Pick un source of truth.

The rest of the technical surface

• Balise canonicals. Au-delà categories/products, watch the homepage (/ vs ?___store= and similaire store-view params), pagination, and the store-view/locale parameters Magento appends. Voir canonicalization and the balise canonical deep dives.
• Pagination. Magento paginates categories with ?p=2. Give chaque page a unique, self-referencing canonical — do pas canonical page 2+ back to page 1, and don’t noindex the sequence (que peut cut popularité des liens to products seulement listed deep in lune pages). rel=prev/next is dead; don’t rely on it.
• Store views (multi-language / multi-site). Magento’s store-view architecture is powerful pour international setups but is a classic source of contenu dupliqué and manquant/mismatched hreflang. Si vous run multiple store views off un catalog, hreflang is manual fonctionner and partial deployment is worse que none.
• Out-of-stock and disabled products. Decide a policy: garder ranking pages live with stock status, or 404/410 + redirection permanently gone SKUs. Don’t silently disable products and leave leur URLs 404ing with inbound liens.
• Core Web Vitals. Self-hosted Magento’s performances is entirely on votre infrastructure. Full-page cache (Varnish), a CDN, image optimization (WebP), and disciplined extension/JS hygiene are the levers. Two différent headless paths obtenir conflated ici, so be precise à propos de qui un you’re evaluating: PWA Studio is Adobe’s older React-based storefront layered on votre existing Commerce infrastructure, pendant que Adobe Commerce as a Cloud Service (ACCS) is a separate SaaS product on Edge Delivery Services où Luma isn’t pris en charge at tout. Soit peut lift the CWV ceiling, but les deux ajouter rendering and indexation considerations of leur propre — confirmer qui un (or neither) a store is en réalité running avant planning a headless migration pour CWV.

Ce que to en réalité prioritize

On la plupart Magento audits the order of impact is:

1. Layered navigation — canonical + noindex strategy pour parameter URLs. Ce is the biggest share of the SEO technique valeur.
2. Configurable/simple product canonicalization — canonical simple SKUs to leur parent configurable product; vérifier it on rendered pages, pas simplement the admin setting.
3. URL rewrites & redirections — friendly URLs on, redirect-on-change on, aucun stranded 404s.
4. Schema — ajouter JSON-LD (aucun native prise en charge), éviter duplicate blocks.
5. Titles/meta + category copy — fill the fields; categories ship blank.
6. Performances — cache, CDN, images.

Everything sinon is refinement. Magento donne vous total contrôler, qui signifie almost every SEO problem on a Magento store is a configuration choice vous pouvez fix — and almost every un starts with the filters.

AI summary

A condensed prendre on the Avancé version:

• Magento SEO is dominated by two duplicate-content generators. Layered navigation (faceted filtering) appends filter parameters to category URLs; configurable/simple product variants spray near-identical SKU URLs. Les deux besoin the même treatment: canonical to the clean parent (category or configurable product) and noindex the low-value combinations; promote seulement the filters/variants with réel search demand to indexable pages.
• Version matters: Magento 1 is end-of-life (June 2020) — migrate. Magento 2 ships as Adobe Commerce (paid, self-hosted) and Magento Ouvrir Source (free) from un codebase, plus a separate SaaS product, Adobe Commerce as a Cloud Service (ACCS, since June 2025), qui drops the Luma theme entirely.
• Layered navigation vs. Live Search: Adobe documents standard layered navigation and the paid, AI-powered Live Search facets as distinct implementations with différent URL behavior — confirmer qui un a store en réalité runs avant applying explorer/index rules.
• Configurable/simple products: canonical simple SKUs to leur parent configurable product; catalog-visibility settings alone don’t arrêter Google from finding and indexation les via sitemap or direct URL.
• URLs: SEO-friendly URLs run via the url_rewrite table (Admin → Marketing → SEO & Search → URL Rewrites) — distinct from HTTP redirections, qui Magento peut auto-create as 301s. Enable web-server rewrites and redirect-on-URL-change; inventory affected URL patterns avant modification category-path or suffix settings.
• Schema gap: Magento 2 emits aucun JSON-LD by par défaut (microdata in some themes seulement). Google recommends JSON-LD, so rich-result schema is an extension/ custom-dev task — and watch pour duplicate Product blocks.
• Aussi handle: pagination (unique self-referencing canonicals, jamais noindex the series), store-view duplication + hreflang pour multi-locale stores, out-of-stock policy, and Core Web Vitals — noting PWA Studio and ACCS are two différent headless paths, pas interchangeable.
• Priority order: layered navigation → configurable/simple product canonicalization → URL rewrites/redirections → schema → titles/meta/category copy → performances.

Documentation officielle

Primary-source documentation. Magento’s propre docs cover the platform settings; Google’s cover the SEO behavior ceux settings besoin to satisfy.

Adobe / Magento

• Adobe Commerce / Magento Ouvrir Source — SEO meilleur practices — the official SEO configuration guide (URLs, metadata, sitemaps, robots.txt).
• URL rewrites — how the url_rewrite system fonctionne in Admin.
• Moteur de recherche Optimization (config référence) — web-server rewrites, URL suffixes, and SEO settings sous Stores → Configuration.
• Layered navigation — Adobe’s documentation of the filtering fonctionnalité at the heart of Magento SEO.
• Software lifecycle / Magento 1 end-of-life — version prise en charge and the June 2020 Magento 1 EOL.

Google — ce que votre Magento config has to satisfy

• Intro to Product données structurées — requis/recommended Product fields; JSON-LD recommended.
• Données structurées pour ecommerce sites — the ecommerce schema types Google supports.
• Pagination & incremental page chargement — unique URLs, self-canonical pages, noindex pour filters pas pagination.
• Managing exploration of faceted navigation URLs — Google’s official guidance pour the layered-navigation problem.
• Optimize votre budget d’exploration — pourquoi parameter sprawl matters at scale.

Quotes from the source

On-the-record statements relevant to the parts of Magento SEO que en réalité déplacer the needle — faceted navigation, données structurées, and pagination. Chaque lien is a deep lien que jumps to the quoted passage où the source supports it.

Google — données structurées (the schema Magento doesn’t ajouter pour vous)

• “Merchant listings: For pages where customers can purchase products from you. This markup has more options for specifying detailed product information, like apparel sizing, shipping details, and return policy information.” — Recherche Google Central, Intro to Product données structurées. Jump to quote
• “Providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.” Jump to quote

Google — pagination (Magento’s ?p= category pages)

• “Give each page a unique URL” — and assign chaque page its propre canonical plutôt que pointing les tout at page un. — Recherche Google Central, Pagination and incremental page loading. Jump to quote
• “Apply noindex meta tags to filter variations or alternative sort orders” — i.e. to facets, pas to the paginated sequence itself. Jump to quote

Gary Illyes, Google — on pourquoi layered navigation is the core risk

• On faceted/parameter URL spaces: “Once it discovers a set of URLs, it cannot make a decision about whether that URL space is good or not unless it crawled a large chunk of that URL space.”

  Relayed via Moteur de recherche Land’s coverage of the Search Off the Record 2025 year-end explorer report; confirmer contre the source episode avant treating as final. Per que coverage, faceted navigation is the unique largest source of crawl-issue reports Google receives (~50%).

  Lire the coverage
• “Sometimes you might create these new fake URLs accidentally, exploding your URL space from a balmy 1000 URLs to a scorching 1 million, exciting crawlers that in turn hammer your servers unexpectedly.”

  Relayed from Gary Illyes’ LinkedIn post (August 2024) via Moteur de recherche Journal.

  Lire the coverage

Practitioners — configurable/simple product canonicalization

• “Canonical to the parent configurable product.” — Dan Taylor, Moteur de recherche Journal, The Technical Guide to Courant Magento (Adobe Commerce) SEO Issues. Jump to quote
• “The canonical tag used on each of the simple products points back to the primary configurable version — to prevent duplicate variants of the product from being indexed by Google.” — Paul Rogers (Vervaunt). Jump to quote
• “…potentially generates 144,000 product combinations.” — Vervaunt, on a hypothetical fashion-store exemple (3 000 parent products × 8 sizes × 6 colors), illustrating pourquoi an explicit canonical policy matters at scale, pas a universal catalog size. Jump to quote

Magento SEO checklist

Prioritized roughly by impact — top items are où Magento stores win or lose.

Version & foundation

• Confirmer you’re on Magento 2, pas end-of-life Magento 1 (migrate si so).
• Know votre edition (Adobe Commerce, Magento Ouvrir Source, or ACCS) pour fonctionnalité scope — ACCS drops the Luma theme entirely.

Layered navigation (the big un)

• Confirmer si the store runs standard layered navigation or the paid Live Search facets — Adobe documents les as distinct implementations.
• Audit how nombreux parameter URLs filters generate (explorer le site; vérifier site: count and GSC indexed-vs-discovered).
• Canonical filtered category URLs to the clean category URL.
• noindex low-value filter combinations (and garder les crawlable so the tag is lire — jamais noindex + robots.txt Disallow ensemble).
• Identifier filters with réel search demand and construire les as indexable, clean-URL landing pages with unique copy.

Configurable & simple products

• “Use Canonical Link Meta Tag for Products” enabled (Stores → Configuration → Catalog → Catalog → Moteur de recherche Optimization).
• Confirmer on the rendered page — pas simplement the setting — que simple product URLs carry a canonical back to leur parent configurable product.
• Don’t rely on “Not Visible Individually” alone; it doesn’t block direct URL, sitemap, or internal-link indexation.

URLs & redirections

• “Use Web Server Rewrites” enabled (aucun index.php in URLs).
• SEO-friendly URL keys définir on products and categories.
• “Create Permanent Redirect for old URL” enabled avant quelconque URL-key edits.
• Decide on category-path-in-product-URL (off avoids multi-URL duplication).

Données structurées

• Ajouter Product JSON-LD (Magento 2 ships none) via extension or dev.
• Confirmer aucun duplicate schema (theme microdata + extension JSON-LD).
• aggregateRating/review seulement from réel reviews.

On-page & indexation

• Unique titles + meta descriptions on products and categories.
• Category description copy filled in (blank by par défaut).
• Pagination: unique self-referencing canonicals; series pas noindexed.
• Out-of-stock / discontinued product policy decided (don’t strand 404s).

International & performances

• Store-view duplication controlled; hreflang complet & bidirectional si multi-locale.
• Full-page cache (Varnish), CDN, and WebP images pour Core Web Vitals.

Magento SEO cheat sheet

Version map

Layered navigation — Que faire per URL type

Clé Admin settings (Magento 2)

• Stores → Configuration → General → Web → Moteur de recherche Optimization: Use Web Server Rewrites = Yes.
• Stores → Configuration → Catalog → Catalog → Moteur de recherche Optimization: product/category URL suffix, Use Canonical Lien Meta Tag pour Categories/ Products = Yes.
• Marketing → SEO & Search → URL Rewrites: the url_rewrite manager.
• Product/Category edit → Moteur de recherche Optimization: URL clé, meta title, meta description; enable Create Redirection permanente pour old URL.

Hard facts

• Magento 2 emits aucun JSON-LD by par défaut (microdata in some themes seulement).
• Google recommends JSON-LD over microdata/RDFa.
• noindex nécessite a crawlable page — don’t combine with robots.txt Disallow.
• Friendly URLs live in the url_rewrite table.

The mental models

1. Version-first. Avant quelconque tactic, réponse: Magento 1 or 2? Si 1, the project is a migration, complet arrêter. Si 2, the edition (Adobe Commerce vs Ouvrir Source) changements fonctionnalités, pas SEO fundamentals.

2. Layered navigation = a binary, per-URL decision. Every filtered URL is soit an asset (réel search demand → faire it an indexable landing page) or a liability (aucun demand → canonical it away and/or noindex). Don’t treat tout facets the même; sort les by demand, alors appliquer the correct signal.

3. The three “don’t combine” rules.

• noindex + robots.txt Disallow on the même URL → tag jamais lire.
• noindex + canonical on the même URL → contradictory signals.
• canonical alone pour budget d’exploration → source pages encore obtenir crawled.

4. Contrôler l’URL space, alors the index. Magento’s url_rewrite system and web-server rewrites govern what URLs exist and où ils redirect. Canonical/noindex govern what’s dans l’index. Fix URL generation premier (don’t manufacture duplication), alors manage indexation.

5. Schema is opt-in ici. On la plupart platforms schema is a tweak; on Magento it’s a construire. Plan JSON-LD as a deliverable, alors guard contre shipping two Product blocks.

Outils pour Magento SEO

• Magento Admin — URL Rewrites (Marketing → SEO & Search) — the native manager pour the url_rewrite table; votre source of truth pour friendly URLs and redirections.
• Robots d’exploration / site audits — Screaming Frog SEO Spider or Ahrefs Site Audit to mesurer how nombreux parameter URLs layered navigation en réalité generates, surface duplicate titles/canonicals, and trouver chaîne de redirectionss. Ce is how vous size the faceted-navigation problem.
• Recherche Google Console — the Page indexing report (Découvert/Crawled — currently non indexée souvent balloons on parameter sprawl) and Statistiques d’exploration to voir budget burned on filter URLs.
• Résultats enrichis Tester / Balisage de données structurées Validator — confirmer votre ajouté JSON-LD is valid and que vous don’t have a competing microdata block.
• Magento SEO extensions — Mageworx, Mirasvit, Amasty, and similaire ajouter JSON-LD, finer canonical contrôler, and layered-navigation indexation rules que Magento core leaves to vous. (Evaluate pour duplicate-schema behavior.)
• Log fichier analysis — pour grand catalogs, server logs montrer exactly how beaucoup explorer is wasted on filter URLs.

How to mesurer Magento SEO health

Ces are the standing KPIs pour a Magento store, pas one-time checks — track les on a recurring cadence so layered navigation, indexation, and schema don’t quietly drift back into a mess.

Indexé vs. découvert URL ratio

Ce que it indique vous: How beaucoup layered navigation is bloating Google’s view of the site. A category with a few hundred products shouldn’t have tens of thousands of découvert URLs.

How to pull it: Search Console → Page indexation report, specifically the “Discovered — currently not indexed” and “Crawled — currently not indexed” buckets. Segment by URL pattern (filter requête strings) en utilisant the report’s Inspection d’URL sample or a explorer export.

Benchmark / realistic range: Aucun universal number — dépend on catalog size and filter count. The signal que matters is the trend: a ratio climbing month over month signifie the canonical/noindex strategy on layered navigation isn’t holding.

Cadence: Monthly, or après quelconque layered-navigation config modifier.

Budget d’exploration spent on filter URLs

Ce que it indique vous: Si Googlebot is wasting explorer capacity on near-duplicate parameter combinations au lieu de votre réel product and category pages.

How to pull it: Search Console → Statistiques d’exploration report (by réponse and by objectif), cross-referenced with server/CDN log fichiers filtered to ? parameter requêtes. My Faceted Navigation Auditor peut classify a supplied liste of parameter URLs to aider size qui combinations are en réalité being generated.

Benchmark / realistic range: Dépend on catalog size and explorer frequency — there’s aucun fixed “good” percentage. Treat a rising share of explorer hits on parameter URLs relative to canonical product/category URLs as the warning sign.

Cadence: Monthly pour established stores; weekly during and après a layered-nav config modifier.

Canonical signal consistency

Ce que it indique vous: Si filtered and paginated URLs are en réalité resolving to the canonical vous intended, pas silently reverting to self-referencing or manquant tags après a theme/extension mettre à jour.

How to pull it: Spot-check filter and pagination URLs with my Canonicalization Checker — it audits HTML and HTTP canonical signals and flags conflicts.

Benchmark / realistic range: Devrait be 100% — every filtered URL vous intend to suppress devrait carry a canonical pointing to the clean category page, every paginated page a self-referencing canonical. Quelconque exception is a bug, pas a range.

Cadence: Après every theme, extension, or layered-navigation setting modifier; spot-check quarterly sinon.

Product rich-result eligibility

Ce que it indique vous: Si the JSON-LD vous ajouté (Magento ships none by par défaut) is en réalité valid and complet suffisant to earn price/rating résultats enrichis, and si a leftover theme microdata block is conflicting with it.

How to pull it: Search Console → Enhancements report pour Product snippets, or spot-check individual URLs with Google’s Résultats enrichis Tester. Pour a raw-HTML audit of the schema itself — notamment duplicate-block detection — utiliser my PDP SEO Checker.

Benchmark / realistic range: Dépend on catalog size and examiner coverage — pas every SKU va have aggregateRating données. Track the trend in valid vs. error/ warning items, pas an absolute target.

Cadence: Monthly, and immédiatement après quelconque schema extension mettre à jour or theme modifier.

Validation tests: proving a Magento SEO fix took effect

Réussir/échouer checks pour the spécifique changements covered in ce article — run chaque un correct après vous faire the modifier, alors à nouveau on the monitoring cadence noted.

Canonical ajouté to a filtered category URL

Tester to run: Charger a filtered URL (e.g. /running-shoes?color=blue) in my Canonicalization Checker.

Attendu result: The outil reports a rel=canonical on the filtered URL pointing to the clean category URL (/running-shoes), with aucun conflicting HTTP header canonical.

Échec interpretation: Aucun canonical, a self-referencing canonical, or a canonical pointing somewhere sinon signifie the “Utiliser Canonical Lien Meta Tag pour Categories” setting or votre template/extension logic isn’t emitting it pour ce URL pattern.

Monitoring window: Immediate pour the tag itself; 2–4 weeks in Search Console’s Page indexation report to voir Google pick up the consolidated signal.

Rollback trigger: Si indexed-URL counts pour the filter pattern garder climbing après 4 weeks with the canonical confirmed présent, the signal isn’t being respected — vérifier pour a conflicting noindex or robots.txt block on the même URL.

noindex applied to a low-value filter combination

Tester to run: Récupérer the filtered URL’s rendered HTML <head> (view-source or curl) and vérifier pour <meta name="robots" content="noindex,follow">. Alors vérifier robots.txt pour que URL pattern with my Google Index Checker.

Attendu result: The noindex tag is présent AND l’URL is pas disallowed in robots.txt — Google peut seulement lire the tag on a crawlable page.

Échec interpretation: Si robots.txt aussi disallows the pattern, Googlebot jamais récupère lune page to voir the noindex tag, and l’URL peut stay indexé indefinitely from historical signals alone.

Monitoring window: Days pour the explorer to pick up the tag; 2–8 weeks pour l’URL to en réalité drop out of the index (plus long pour previously well-linked filter pages).

Rollback trigger: URL encore indexé après 8 weeks with noindex confirmed crawlable — vérifier pour a canonical fighting the noindex on the même URL (they’re contradictory signals; Google may ignore un).

Simple product canonical points to its configurable parent

Tester to run: Charger a simple-product variant URL (a spécifique size/color combination) in my Canonicalization Checker.

Attendu result: The outil reports a rel=canonical on the simple product URL pointing to the parent configurable product’s URL, with aucun conflicting HTTP header canonical.

Échec interpretation: A self-referencing or manquant canonical signifie “Utiliser Canonical Lien Meta Tag pour Products” isn’t enabled, or the variant is being treated as visible/indexable independent of the parent relationship.

Monitoring window: Immediate pour the tag itself; 2–4 weeks in Search Console’s Page indexation report to confirmer the variant URLs consolidate sous the parent plutôt que accumulating as separate indexé pages.

Rollback trigger: Si indexed-URL counts pour simple-product URLs garder climbing après 4 weeks with the canonical confirmed présent, vérifier si “Not Visible Individually” is being relied on au lieu de the balise canonical — catalog visibility doesn’t block direct-URL, sitemap, or internal-link exploration.

Redirect-on-URL-change is protecting old URLs

Tester to run: Après modification a product or category URL clé, requête the old URL directement: curl -I https://yourstore.com/old-url-key.

Attendu result: A unique 301 to the nouveau URL (aucun chaîne de redirectionss).

Échec interpretation: A 404 signifie “Create Permanent Redirect for old URL” was off quand the clé modifié, or the url_rewrite entry didn’t generate — the old URL and quelconque inbound liens/rankings it held are now stranded.

Monitoring window: Immediate — ce is a status-code vérifier, aucun waiting nécessaire.

Rollback trigger: Quelconque 404/chain on une URL que previously ranked — restore the url_rewrite entry or ajouter a manual redirection avant it drops from the index.

JSON-LD Product schema is valid and pas duplicated

Tester to run: Run the product page via my PDP SEO Checker to audit the raw JSON-LD pour requis fields and duplicate blocks, alors confirmer rich-result eligibility with Google’s Résultats enrichis Tester.

Attendu result: Un valid Product block with name, image, description, offers (price, priceCurrency, availability), and — si you’re claiming star ratings — aggregateRating/review sourced from réel reviews. Aucun second, conflicting block from leftover theme microdata.

Échec interpretation: Two Product blocks (theme microdata + extension JSON-LD) usually signifie Google picks un arbitrarily or discards les deux as inconsistent; manquant offers fields mean lune page won’t qualify pour price snippets at tout.

Monitoring window: Immediate pour validity; 2–4 weeks in the Search Console Enhancements report to confirmer résultats enrichis en réalité commencer appearing.

Rollback trigger: Enhancements report montre rising “Invalid items” après a theme or extension mettre à jour — disable the newer source jusqu’à the duplicate is resolved.

Ressources utiles

On the topics que dominate Magento SEO (on ce site)

• Faceted navigation — the canonical home pour the layered-navigation problem and the index-or-suppress decision framework.
• Canonicalization and the balise canonical — the principal fix pour Magento’s parameter duplication.
• Contenu dupliqué — pourquoi filter and store-view URLs split signals.
• URL parameters and budget d’exploration — the crawl-side mechanics of parameter sprawl.

My connexe writing (Ahrefs)

• The Beginner’s Guide to SEO technique — où ces contrôle fit in the bigger picture.
• Faceted Navigation: Definition, Exemples & SEO Meilleur Practices — the complet decision framework (I’m a reviewer on ce un).
• URL Parameters: A Complet Guide pour le SEOs.

Official

• Adobe Commerce SEO meilleur practices — the platform’s propre guidance.
• Google’s Managing exploration of faceted navigation URLs.

From others

• r/TechSEO and the Magento Stack Exchange — où Magento-specific explorer/index quirks obtenir debugged.
• The Technical Guide to Courant Magento SEO Problèmes (Moteur de recherche Journal, Dan Taylor) — comprehensive practitioner guide covering URL rewrites, configurable/simple product canonicalization, and faceted navigation contrôle.
• The Ultimate Guide to Contenu dupliqué in Magento (Vervaunt, Paul Rogers) — the most-cited source pour the complet duplicate-content source map and the configurable/simple product canonical strategy.
• SEO Considerations pour Configurable and Simple Products in Magento (Paul Rogers) — deep dive on canonicalizing simple SKUs to leur configurable parent at scale.
• Layered Navigation Causing Problems? Deal With It (Scandiweb) — current Google-aligned guidance on robots.txt disallow as principal faceted-navigation explorer contrôler.
• Magento 2 Layered Navigation SEO: The Ultimate Guide (Mageworx) — detailed walkthrough of parameter URL proliferation with concrete URL exemples.
• Product Schema pour Adobe Commerce (Lumio) — explique pourquoi Luma ships almost aucun JSON-LD and walks via building a custom JSON-LD module contre the EAV model.

Journal des modifications