Magento SEO Checklist: 10 Critical Issues Adobe Commerce Stores Miss

Magento and Adobe Commerce are powerful platforms — but that power comes with complexity. Layered navigation, product combinations, and a deep module ecosystem create SEO problems that Shopify stores simply don't have. Here are the ten issues we see most often when scanning Magento stores.

1. Canonicals on layered navigation pages

Magento's layered navigation generates URLs like /women/tops?color=59&size=91. Without canonical tags pointing to the base collection URL, every filter combination becomes a separate indexable page competing for the same keyword. On a store with 500 products and 10 filter attributes, this can generate thousands of near-duplicate pages.

How to fix: Enable the "Use Canonical Link Meta Tag" option in Magento's Catalog > Search Engine Optimization settings for both categories and products. For custom filter combinations, add canonical tags programmatically.

2. Missing security headers

Magento is a frequent target for Magecart attacks — skimmers that steal payment data from checkout pages. The attack surface expands significantly when critical security headers are missing. HSTS prevents protocol downgrade attacks. CSP can block unauthorized script execution. X-Frame-Options prevents clickjacking.

In our scans of Magento stores, security headers are the single most common category of failure — over 80% of stores miss at least one critical header.

How to fix: Add security headers via your web server configuration (nginx or Apache) or through a security extension. At minimum, implement HSTS, X-Content-Type-Options, and X-Frame-Options.

3. Duplicate product pages from URL keys

Magento allows products to exist in multiple categories, generating URLs like /women/tops/blue-shirt.html and /sale/blue-shirt.html simultaneously. Without proper canonical configuration, both URLs index and split your SEO equity.

How to fix: Set a single preferred URL key per product and ensure canonical tags point to the non-category URL path (/blue-shirt.html) rather than the category path.

4. Render-blocking scripts from conflicting extensions

Most Magento stores run 15-40 third-party extensions. Each injects CSS and JavaScript into the page, often without defer or async attributes. The result: customers wait 4-8 seconds while the browser processes scripts before rendering anything visible. Google measures this — and so do your bounce rates.

How to fix: Run a performance audit to identify which scripts block rendering. Move non-critical scripts to defer or async loading. Consider a Magento performance extension that bundles and minifies JavaScript.

5. Missing structured data on product pages

Structured data (JSON-LD Product schema) enables rich results in Google — star ratings, price, availability, and review counts directly in search results. These dramatically increase click-through rates. Magento 2 includes basic Product schema, but it often lacks review data, availability status, or multiple images.

How to fix: Audit your Product schema output using Google's Rich Results Test. Ensure offers includes price, priceCurrency, availability, and url. Add aggregateRating if you have product reviews.

6. Slow admin-side config changes breaking cache

Magento's full-page cache (FPC) is one of its biggest performance advantages — but configuration changes frequently invalidate it and cause unintentionally slow responses. Stores experiencing a cache miss serve 4-10 second response times. When this happens at scale, it destroys conversion rates and Core Web Vitals scores.

How to fix: Monitor your Time to First Byte (TTFB). A healthy TTFB from FPC should be under 200ms. If you're consistently seeing 1-2+ seconds, warm your cache after changes and investigate FPC configuration.

7. Missing Open Graph tags on non-product pages

Magento includes Open Graph support for product pages, but category pages, CMS blocks, and blog posts often generate broken social previews — no image, no description, generic title. When customers share these pages on social media, the lack of proper OG tags means the preview looks unprofessional.

How to fix: Add OG meta tags to all page types. At minimum: og:title, og:description, og:image (1200×630px), and og:url.

8. Large uncompressed images from bulk import

Product image bulk imports frequently bypass Magento's resizing logic, resulting in 3-5MB images that Magento serves at full resolution instead of generating optimized thumbnails. A product page with 6 gallery images can easily total 20MB of image data.

How to fix: Run Magento's image resize command (bin/magento catalog:images:resize) and audit your media storage for unoptimized originals. Set maximum upload size limits and consider serving images through a CDN with on-the-fly resizing.

9. XML sitemap not updated after catalog changes

Magento's sitemap generation is often set to weekly or monthly. When you launch new categories, add products, or restructure your catalog, the sitemap lags behind by days. This delays Google indexing your new pages.

How to fix: Configure sitemap generation to run daily (or hourly for active stores) and ping Google/Bing after each update. Set your sitemap priority values to give product and category pages higher priority than CMS pages.

10. Missing alt text on CMS block images

Magento's WYSIWYG editor makes it easy to add images to homepage banners, CMS pages, and category descriptions — and equally easy to skip the alt text field. These images are invisible to search engines and screen readers, and they show up as failures on both SEO and accessibility audits.

How to fix: Audit all CMS blocks and pages for images missing alt text. Establish a policy that every image added via the admin panel requires alt text before it's saved.

Run a free audit on your Magento store

StoreVitals runs a free health audit on any Magento or Adobe Commerce store — checking all 20 categories including security headers, structured data, canonical tags, and performance. Paste your URL and get results in under 60 seconds.