If you run a Magento store and feel like Google doesn't rank you the way it should, you're probably right. 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.
This guide walks through every issue we see in the typical Magento audit — what it is, why it costs you traffic, and exactly how to fix it. Most of these are afternoon-sized tasks; a few need a developer. None of them require an SEO agency.
The fast version: Magento (Adobe Commerce) SEO — control the URL chaos, fix the schema gaps, ship the fundamentals.
What's actually wrong with most Magento stores
Every ecommerce platform has its own SEO blind spots. Magento is no exception. The patterns below show up on the majority of stores we audit — and the platform itself doesn't surface them in any admin dashboard, so they sit there leaking traffic until someone audits the live site.
1. Layered navigation creating thousands of duplicate URLs
Why this 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.
How to fix it: 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. Multiple URLs per product (canonical issue)
Why this 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.
How to fix it: 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 /
3. Default robots.txt allowing /catalogsearch and /customer paths
Why this matters: Magento's default robots.txt is too permissive. Search-result pages, customer account pages, and checkout pages get indexed by accident.
How to fix it: Stores → Configuration → Design → Search Engine Robots. Customize the robots.txt to Disallow /catalogsearch/, /customer/, /checkout/, /cart/, /sales/, /wishlist/, /tag/, and /catalog/product_compare/.
4. Empty or duplicate meta descriptions on category pages
Why this 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.
How to fix it: 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. Multi-store setup leaking content across views
Why this 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.
How to fix it: 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. Slow PHP execution and Time-to-First-Byte > 1.5s
Why this 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.
How to fix it: 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. Schema partial or missing on PDP and category
Why this matters: Magento's default schema emission is minimal. Product schema with offers and aggregateRating, BreadcrumbList, and FAQPage are not consistent across themes.
How to fix it: 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.
What to do next
The fastest way to know which of these issues exist on your store is to run an audit. RankCart's free audit crawls your live Magento store, finds every issue from this guide (plus a hundred more), and ranks each fix by estimated revenue impact so you know where to start.
If you'd rather follow a checklist by hand, we have a step-by-step Magento SEO checklist with the full sequence, or a shortlist of easy Magento SEO fixes for the highest-impact, lowest-effort wins first.
Either way, treat Magento SEO as a recurring discipline rather than a one-time project. The platform changes, your catalog changes, the SERP changes. Re-audit monthly and the regressions become small daily edits instead of quarterly rescue missions.
Frequently asked questions
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.