Magento SEO

Fix SEO Issues for Magento: A Practical Guide

Magento gives you more SEO control than any platform — and demands more discipline to use it. The same flexibility that lets you build any URL structure, schema configuration, or multi-store setup also lets you ship duplicate content, indexation traps, and broken canonicals. RankCart audits Magento and Adobe Commerce stores at scale and surfaces every issue ranked by revenue impact.

Who this is for: Mid-market and enterprise B2C and B2B brands, multi-store and multi-language operators, and stores running Magento Open Source 2.x or Adobe Commerce.

Easy Magento SEO fixes — the issues we see in 80% of audits

These are the high-impact, low-effort Magento fixes RankCart finds on most stores. Ship the easy ones first — they typically take an afternoon and recover 10-30% of lost organic traffic.

  1. 1. Layered navigation creating thousands of duplicate URLs

    Why it matters: Magento's faceted navigation generates URLs for every filter combination by default. On a catalog of 1,000 products with 5 filters, you can generate 100,000+ crawlable URL combinations — almost all near-duplicates.

    Fix: Stores → Configuration → Catalog → Layered Navigation → SEO settings. Add canonical tags pointing filtered URLs back to the parent category. For some filters (color, size), a robots.txt parameter block or a meta noindex follow may be more appropriate. Decision depends on whether filtered URLs should rank — RankCart helps you decide.

  2. 2. Multiple URLs per product (canonical issue)

    Why it matters: Magento allows products in multiple categories. By default, each category creates a unique URL: /men/shoes/leather-jacket, /sale/leather-jacket, /leather-jacket. All three resolve, none are obviously canonical.

    Fix: Stores → Configuration → Catalog → Catalog → Search Engine Optimization. Set "Use Categories Path for Product URLs" to No, and set canonical tags for products to point to /<product-url>. RankCart's audit flags every multi-URL product.

  3. 3. Default robots.txt allowing /catalogsearch and /customer paths

    Why it matters: Magento's default robots.txt is too permissive. Search-result pages, customer account pages, and checkout pages get indexed by accident.

    Fix: Stores → Configuration → Design → Search Engine Robots. Customize the robots.txt to Disallow /catalogsearch/, /customer/, /checkout/, /cart/, /sales/, /wishlist/, /tag/, and /catalog/product_compare/.

  4. 4. Empty or duplicate meta descriptions on category pages

    Why it matters: Magento doesn't auto-generate meta descriptions for category pages. If you don't set them, you get the global default repeated across every category.

    Fix: Catalog → Categories → click each category → Search Engine Optimization. Write 145-155 unique chars per category. For 100+ categories, use a third-party module or run a SQL update via the catalog_category_entity tables (with a backup first).

  5. 5. Multi-store setup leaking content across views

    Why it matters: Magento's multi-store / multi-website feature shares product data across stores by default. Without unique store-view content, you have identical copy ranking for the same keyword across stores.

    Fix: For each store view, override product names, descriptions, and meta tags at the store-view scope. Configure hreflang for international stores via theme XML or a module. RankCart audits each store view separately.

  6. 6. Slow PHP execution and Time-to-First-Byte > 1.5s

    Why it matters: Magento's database-heavy architecture is slow without proper infrastructure. TTFB on shared hosting regularly exceeds 2 seconds — past Google's threshold for poor.

    Fix: Move to Adobe Commerce on cloud, MageMojo, Sonassi, or another Magento-specialized host. Enable Varnish for full-page caching. Configure Redis for session and cache backends. Run Magento in production mode (not developer or default).

  7. 7. Schema partial or missing on PDP and category

    Why it matters: Magento's default schema emission is minimal. Product schema with offers and aggregateRating, BreadcrumbList, and FAQPage are not consistent across themes.

    Fix: Use a SEO extension (Mageworx, Mirasvit, Amasty) or add JSON-LD blocks via theme XML. Validate with Google's Rich Results Test on a sample of every page type. RankCart audits rendered schema on each page.

Step-by-step Magento SEO checklist

A complete sequence — run it top-to-bottom for a full Magento SEO overhaul, or pick the steps that match the gaps in your audit.

  1. 1

    Run a deep RankCart audit

    Magento sites need depth-3+ crawls. Enter your storefront URL, set a max depth of 3, and let RankCart map the full URL inventory. Compare against your XML sitemap and Search Console index count to spot duplication.

  2. 2

    Configure URL handling

    Stores → Configuration → Catalog → Catalog → Search Engine Optimization. Set Use Categories Path for Product URLs = No. Set Use Canonical Link Meta Tag for Products = Yes. Set Use Canonical Link Meta Tag for Categories = Yes. Save and reindex URL Rewrites.

  3. 3

    Lock down layered navigation

    Stores → Configuration → Catalog → Layered Navigation. Enable canonicals on filtered URLs. For sort and pagination parameters, add robots.txt rules: Disallow: /*?p= and Disallow: /*?product_list_order=. Decide which attribute filters (color, brand, size) should remain indexable as standalone category-style pages.

  4. 4

    Customize robots.txt

    Stores → Configuration → Design → Search Engine Robots → Edit custom instruction. Add Disallow rules for /catalogsearch/, /customer/, /checkout/, /cart/, /sales/, /wishlist/, /catalog/product_compare/, and /review/. Validate via Google's robots.txt tester.

  5. 5

    Write category-page meta and copy

    Catalog → Categories. For each top-revenue category: Search Engine Optimization → Meta Title, Meta Description (145-155 chars), Meta Keywords (skip), Description (150-300 words). Display the description above the product grid via theme template (often catalog_category_view.xml).

  6. 6

    Add complete schema via extension or theme XML

    Either install a SEO extension that emits Product, BreadcrumbList, Organization, and Review schema (Mageworx SEO Suite, Amasty SEO Toolkit), or add JSON-LD blocks in <referenceContainer name="head.additional"> via theme XML. Validate with Google's Rich Results Test on each template type.

  7. 7

    Tune infrastructure for speed

    Magento performance depends on PHP-FPM tuning, Varnish full-page cache, Redis for sessions and cache, MySQL/MariaDB optimization, and CDN for static assets. If you're on shared hosting, move. Adobe Commerce Cloud, MageMojo, and Sonassi are specialized Magento hosts. Aim for TTFB under 0.8s.

  8. 8

    Set up monthly audits and Search Console monitoring

    Magento sites accumulate technical debt fast. Schedule monthly RankCart audits and weekly Search Console Coverage report reviews. Alert on score drops > 5 points or new "Discovered, not indexed" spikes — they almost always reveal a layered navigation regression or a redirect break.

Magento SEO — frequently asked questions

Real questions from real Magento merchants. Answered without the fluff.

Is Magento good for SEO?

Magento gives you more SEO control than any other ecommerce platform — every URL, every meta tag, every schema field, every robots.txt rule is configurable. The flip side: that flexibility lets you ship terrible SEO if you don't configure it properly. Magento sites that rank well are configured well. Magento isn't plug-and-play.

What's the difference between Magento Open Source and Adobe Commerce?

Same core platform. Adobe Commerce (formerly Magento Commerce) adds enterprise features — B2B, content staging, advanced reporting, headless support, official cloud hosting — and dedicated support. SEO behavior is identical between the two. Most enterprise brands run Adobe Commerce; most mid-market brands run Open Source.

How do I fix duplicate content on Magento?

Three places to look: layered navigation filter URLs (set canonicals or noindex), products in multiple categories (use category-less canonical URLs), and multi-store overlap (override content per store view). RankCart's audit flags all three patterns and shows you which products and categories are affected.

Why is my Magento site so slow?

Almost always infrastructure. Magento's architecture demands proper PHP-FPM, Varnish, Redis, and MySQL tuning. Shared hosting (especially generic LAMP shared hosts) won't deliver acceptable TTFB. Either move to a Magento-specialized host or hire a DevOps consultant for a tuning pass — usually pays for itself in two months from organic traffic recovery.

Does Magento add Product schema automatically?

Partially. The default theme (Luma) emits basic Product schema. Custom themes often strip it during development. For complete schema (offers, aggregateRating, Review, BreadcrumbList, FAQPage), install a SEO extension or add JSON-LD via theme XML. Validate everything with Google's Rich Results Test.

Should I migrate from Magento to Shopify Plus?

It depends. Brands above $5M GMV with complex B2B, multi-store, or deeply custom catalogs often stay on Magento for the flexibility. Brands below $5M GMV that aren't using Magento's advanced features often save engineering hours by migrating to Shopify Plus or BigCommerce. Migrate based on operational fit, not SEO — both platforms can rank equally well.

How often should a Magento store audit SEO?

Monthly at minimum. Magento accumulates technical SEO issues faster than other platforms because every extension, theme update, or admin configuration change can affect URLs, schema, and crawlability. Layered navigation regressions are the most common silent killer. A monthly RankCart audit catches them in days instead of months.

Other ecommerce platforms we audit

Shopify SEO →Shopify Plus SEO →WooCommerce SEO →BigCommerce SEO →Wix SEO →Squarespace SEO →

Want this list for your store, ranked by revenue impact?

RankCart audits your live Magento store, finds every issue from this guide (plus a hundred we didn't list), and tells you which fix unlocks the most missed revenue first.