MAGENTO SEO AUDIT · LAYERED NAVIGATION · PRODUCT SCHEMA · ADOBE COMMERCE
Free Magento SEO Audit
Magento's layered navigation generates thousands of filterable URLs that consume crawl budget and create duplicate content. DeepSEOAnalysis audits Magento and Adobe Commerce stores — detecting canonical gaps on filtered pages, missing Product schema, sitemap configuration issues, and AI visibility signals.
WHAT WE CHECK
6 Magento-specific SEO checks
Beyond the 80+ general checks, the engine applies Magento-aware analysis — detecting layered navigation canonical gaps, cross-category product duplicate content, missing Product JSON-LD schema, sitemap issues, and Core Web Vitals — with specific Magento admin paths and extension recommendations for each fix.
Layered navigation canonical and duplicate URL control
Magento\'s layered navigation generates filterable URLs for every attribute combination on a category page: `/shoes/womens?color=blue`, `/shoes/womens?color=blue&size=8`, `/shoes/womens?price=50-100`. A category with 5 colours, 10 sizes, and 5 price ranges can generate 50,000+ unique URLs — all crawlable, all thin or duplicate relative to the parent category page. Without canonical tags or parameter disallows, Googlebot crawls these pages instead of the high-value category and product pages, consuming crawl budget on low-value filter combinations. The critical fix: Stores > Configuration > Catalog > Search Engine Optimization > "Use Canonical Link Meta Tag For Categories" = Yes and "For Products" = Yes. This adds `link rel="canonical"` pointing all layered navigation URLs back to the parent category. Additional fix: a robots.txt rule disallowing common parameter combinations (`?price=`, `?color=`, `?size=`) for stores where Googlebot is crawling parameter URLs despite canonicals. The audit crawls the live site, detects parameter-based URL patterns, checks canonical tag targets on filtered pages, and flags missing or self-referential canonicals on parameter URLs.
Product and category duplicate content
Beyond layered navigation, Magento generates several other sources of duplicate content. Product URL paths: in Magento 2, a product accessible at both `/shoes/womens/blue-running-shoe.html` and `/blue-running-shoe.html` (when the product is available from multiple categories) creates duplicate product pages. Fix: Stores > Configuration > Catalog > Search Engine Optimization > "Use Categories Path for Product URLs" = No (enforces the canonical product URL without category prefix) and ensure the canonical tag on the variant URL points to the primary product URL. Pagination: category pages paginated with `?p=2`, `?p=3` generate paginated duplicate pages. Google has deprecated `rel="next"` / `rel="prev"` pagination markup — the recommended approach is canonical tags pointing paginated category pages to the main category page (page 1), or a "view all" page if practical. The audit checks canonical coverage across crawled product and category pages, detects cross-category duplicate product URLs, and flags pagination handling issues.
Product schema and BreadcrumbList
Magento 2 core does not emit Product JSON-LD schema. Product structured data — `Product` type with `name`, `description`, `image`, `brand`, `sku`, `offers` (with `price`, `priceCurrency`, `availability`), and `aggregateRating` (with `ratingValue` and `reviewCount`) — requires a third-party Magento 2 extension or custom theme implementation. Extensions: Mirasvit Advanced SEO Suite, Aheadworks SEO, or Yoast for Magento include Product schema generation. Without Product schema, product pages miss eligibility for Google Shopping-style rich results and price display in search snippets. BreadcrumbList JSON-LD: Magento themes typically render breadcrumb navigation in HTML, but the JSON-LD version (required for the Google breadcrumb rich result) needs to be added. Some SEO extensions include this; others require a theme customisation. The audit validates Product schema presence and completeness — `offers.price`, `offers.priceCurrency`, `offers.availability`, `aggregateRating.ratingValue`, `aggregateRating.reviewCount` — and checks for BreadcrumbList JSON-LD on product and category pages.
XML sitemap configuration
Magento 2 includes a built-in XML sitemap generator at Stores > Configuration > Catalog > XML Sitemap. Configuration checklist: enable sitemap generation, set the frequency and priority per entity type (product, category, CMS pages), schedule daily generation via cron, and add a `Sitemap:` directive to `robots.txt` pointing to the generated file (typically `sitemap.xml` in the Magento root). Common gaps: the sitemap includes out-of-stock or disabled products that are noindex (wasting the sitemap\'s crawl budget signalling); it includes thin filtered URLs (layered navigation paths in the sitemap amplifies the crawl budget problem); the sitemap path is not in `robots.txt`; large Magento stores generate sitemaps exceeding 50MB or 50,000 URLs (Magento splits these into a sitemap index automatically, but the index URL must be correct). For stores with hundreds of thousands of products, verify that the sitemap covers all products within reasonable size limits. The audit checks sitemap presence, URL count vs crawled page count, `lastmod` recency, and the `Sitemap:` directive.
Page speed and Core Web Vitals
Magento stores frequently have poor Core Web Vitals — LCP of 5–8 seconds on mobile is common for unoptimised stores. The primary causes: large unoptimised product images (JPEG at full size with no lazy loading or srcset), render-blocking third-party scripts (analytics, live chat, review widgets, payment provider scripts all loading synchronously in `head`), Magento\'s default JavaScript bundling (which can produce large bundles that block rendering), and unoptimised first-server-response time (Magento without a full-page cache like Varnish responds slowly). Key fixes: enable Magento\'s full-page cache (FPC) in Stores > Configuration > Advanced > System > Full Page Cache (Varnish recommended over Magento built-in), enable JavaScript bundling and minification in Deploy > Static Content, ensure product images are served in WebP with responsive srcset, add `fetchpriority="high"` to the above-the-fold product image, and defer third-party scripts. The audit uses real CrUX field data (LCP, INP, CLS from actual Chrome users) for your Magento store, segmented by mobile and desktop.
AI visibility for Magento stores
Serve `llms.txt` by placing it in Magento\'s root directory (the `pub/` directory if using the standard Magento web root, or the project root for some deployment configurations) — nginx or Apache will serve it at `/llms.txt`. FAQPage JSON-LD for product FAQ sections and category page questions can be added via a custom Magento module that injects JSON-LD into the page layout, or via a third-party SEO extension that supports FAQ schema. AI crawlers (GPTBot, ClaudeBot, PerplexityBot) should be explicitly allowed in `robots.txt` — Magento\'s default `robots.txt` allows all crawlers via `User-agent: *` with selective Disallow rules, but some security extensions add broad disallow rules that inadvertently block AI bots. The audit checks all five AI visibility signals — llms.txt presence, AI crawler access, FAQPage/HowTo schema, question-heading ratio (≥20% on content pages), and content chunkability — with Magento-specific configuration guidance.
HOW IT WORKS
Audit your Magento store in 60 seconds
- Enter your Magento store URL. Works with Magento 2.x, Adobe Commerce (Magento Enterprise), and Magento Open Source on any host: Nexcess, SiteGround, Cloudways, Hypernode, or self-hosted. No admin access, database credentials, or SSH needed — the audit crawls the live site.
- We crawl and analyse. The engine crawls up to 50 pages (free) or 1,000 pages (paid), detects layered navigation URL patterns and canonical tag coverage, validates Product and BreadcrumbList JSON-LD schema, checks sitemap configuration, measures CrUX Core Web Vitals for mobile and desktop, and evaluates all five AI visibility signals.
- You get a prioritised report. Magento-specific issues first — layered navigation canonicals, Product schema gaps, sitemap configuration, Core Web Vitals on mobile — then general SEO, each with the specific Magento admin path (Stores > Configuration > ...) or extension recommendation for the fix.
FAQ
Questions about the Magento SEO audit
What are the most common Magento SEO problems?
Magento\'s layered navigation (faceted filtering) is the largest SEO risk: each filter combination (colour, size, price range) generates a new filterable URL like `/shoes?color=blue&size=10`, creating hundreds or thousands of duplicate or near-duplicate URLs that dilute crawl budget and cannabilise each other\'s rankings. The fix: canonical tags pointing filterable URLs to the parent category page, and/or disallowing filter parameter combinations in robots.txt. Other common issues: duplicate content from pagination (`?p=2`), products appearing under multiple categories generating duplicate product pages, and missing or incomplete Product JSON-LD schema on product pages.
Does Magento 2 have good SEO out of the box?
Better than Magento 1, but significant configuration is required. Magento 2 includes URL rewrites (clean URLs for products and categories), configurable meta title/description per product and category, and a built-in sitemap generator. The gaps that need configuration: layered navigation canonical tags require setting "Use Canonical Link Meta Tag For Categories" and "For Products" to Yes in Stores > Configuration > Catalog > Search Engine Optimization; the XML sitemap needs to be enabled and scheduled in the admin; Product JSON-LD requires a third-party extension or custom code (Magento 2 core does not emit Product schema). The DeepSEOAnalysis audit checks all of these.
How do I fix Magento layered navigation SEO?
Three-part fix: (1) Enable canonical tags in Magento admin: Stores > Configuration > Catalog > Search Engine Optimization > "Use Canonical Link Meta Tag For Categories" = Yes and "For Products" = Yes. This adds canonical tags pointing filtered pages to the main category page. (2) Disallow crawling of common filter parameters in robots.txt: `Disallow: /*?` disallows all query parameters — effective but also blocks legitimate search parameters; a more targeted approach uses specific parameter names. (3) Optionally, set filtered URLs to noindex via a third-party SEO extension (Mirasvit, Aheadworks, or Yoast for Magento). The audit detects parameter-based duplicate URLs and missing canonical tags on filtered pages.
Is the Magento SEO audit free?
Yes. The complete audit is free with no signup and no email gate. Paid plans add saved history, scheduled monitoring, larger crawls (up to 1,000 pages), and agency workflows.