Magento SEO Guide: Enterprise Ecommerce Optimisation

Magento is powerful. It's also an SEO disaster out of the box.

I've worked on Magento sites that had 10x more indexed URLs than actual products because of layered navigation, store views, and URL rewrites gone wrong. The platform gives you enterprise-level flexibility, but that flexibility means there are more ways to break things.

Here's how to get Magento's SEO right, whether you're on Magento 2 (Adobe Commerce) or Magento Open Source.

Magento's Default SEO Settings You Need to Change

Fresh Magento installs come with SEO settings that actively hurt your site. Fix these first.

URL Rewrites and Suffixes

Magento adds .html to category and product URLs by default. While this isn't inherently bad, it creates issues when:

• You change it after pages are already indexed (mass redirects needed)
• You're migrating from a platform that didn't use suffixes

Go to Stores > Configuration > Catalog > Search Engine Optimization and decide on your URL suffix strategy before launching. Stick with it.

Category URL Path in Product URLs

By default, Magento includes the category path in product URLs: /clothing/shirts/blue-cotton-shirt.html. The same product in multiple categories creates multiple URLs for the same page.

Set "Use Categories Path for Product URLs" to No. This gives you clean product URLs like /blue-cotton-shirt.html regardless of which category the customer navigated from.

Canonical Tags

Enable canonical tags for both categories and products in Stores > Configuration > Catalog > Search Engine Optimization:

• Use Canonical Link Meta Tag For Categories: Yes
• Use Canonical Link Meta Tag For Products: Yes

This is non-negotiable. Without these, every product assigned to multiple categories generates duplicate content signals.

Layered Navigation: Magento's Biggest SEO Problem

Layered navigation (Magento's faceted filtering) is the number one cause of index bloat on Magento sites.

Every filter combination creates a crawlable, indexable URL by default. A category with 8 filterable attributes and 10 options each can generate millions of URL combinations.

Fixing Layered Navigation

1. Use AJAX-based filtering. Prevent filter selections from changing the URL. Amasty Improved Layered Navigation and similar extensions support this.
2. Add noindex to filter pages. If URLs must change, add <meta name="robots" content="noindex, follow"> to any page with active filters.
3. Block filter parameters in robots.txt. Add Disallow: /*? patterns for known filter parameters.
4. Canonical all filter pages to the parent category. Every filtered URL should canonical back to the clean category page.

This is the same approach I cover in detail for all platforms. The principles of technical SEO apply regardless of your CMS.

Magento 2 vs Magento Open Source: SEO Differences

Adobe Commerce (Magento 2 Commerce) and Magento Open Source share the same core, but there are SEO-relevant differences.

For pure SEO purposes, both platforms can achieve the same results. Adobe Commerce just makes some tasks easier with built-in tooling.

Indexing Configuration

Magento's indexer system affects how quickly changes appear on the frontend, and how quickly Google sees updated content.

Set Indexers to "Update on Schedule"

Go to System > Index Management and set all indexers to "Update on Schedule". This runs reindexing via cron jobs instead of on every save, which:

• Prevents admin timeouts when saving products
• Ensures product and category changes propagate consistently
• Reduces server load during peak traffic

Flat Catalog Settings

Magento's flat catalog feature was designed to improve frontend query performance. In Magento 2.3+, it's largely unnecessary due to improved EAV (Entity-Attribute-Value) performance. Disable flat catalog unless you have a specific performance need. It adds complexity without meaningful SEO benefit.

Performance Optimisation

Magento sites are notoriously slow. Core Web Vitals failures are common, and Google's page experience signals directly affect rankings.

Must-Have Performance Settings

• Enable full page cache. Varnish is the recommended caching layer for Magento 2. Built-in full page cache is a fallback option but significantly slower.
• Merge and minify CSS/JS. Enable in Stores > Configuration > Advanced > Developer. This reduces the number of HTTP requests and file sizes.
• Enable image lazy loading. Defer offscreen images to improve Largest Contentful Paint (LCP).
• Use a CDN. Serve static assets (images, CSS, JS) from a CDN. Adobe Commerce Cloud includes Fastly. Open Source users need to configure their own.
• Optimise images. Magento doesn't compress images by default. Use extensions or CLI tools to convert to WebP and compress on upload.

Hosting Considerations

Magento is resource-hungry. Shared hosting won't cut it. Minimum viable setup:

• Dedicated or cloud server with at least 4GB RAM
• PHP 8.1+ (Magento 2.4.6+ requires it)
• Elasticsearch or OpenSearch for catalog search
• Redis for session and cache storage
• Varnish for full page caching

Magento SEO Extensions Worth Using

The Magento extension ecosystem is mature. These are the ones I've seen deliver consistent SEO value:

• Amasty SEO Toolkit. Canonical management, rich snippets, meta templates for bulk optimisation
• Amasty Improved Layered Navigation. AJAX filtering, SEO-friendly filter URLs, noindex controls
• Mageplaza SEO Extension. Hreflang tags, structured data, HTML/XML sitemaps, meta tag templates
• Hyva Themes. Not an SEO extension, but a frontend framework that dramatically improves Core Web Vitals by replacing Magento's heavy default frontend

Before installing any extension, check compatibility with your Magento version and existing extensions. Extension conflicts are a leading cause of Magento site issues.

Magento-Specific XML Sitemap Configuration

Magento generates XML sitemaps automatically, but the default settings need adjustment.

• Exclude noindexed pages. Filtered URLs, out-of-stock products you've noindexed, and CMS pages that shouldn't be in search results.
• Set appropriate change frequencies. Product pages that update daily should have <changefreq>daily</changefreq>. Category pages weekly. Static pages monthly.
• Split large sitemaps. Magento supports sitemap splitting above 50,000 URLs. Configure the maximum URL count per sitemap file in Stores > Configuration > Catalog > XML Sitemap.
• Schedule automatic generation. Set a cron job to regenerate sitemaps daily so new products are included promptly.

Need help implementing this on your Magento site? I cover the full technical audit process on my ecommerce SEO consulting page.

Frequently Asked Questions

Is Magento good for SEO?

Magento is capable of excellent SEO, but it requires significant configuration. Out of the box, it creates duplicate content, index bloat, and performance issues. With proper setup. Canonical tags, layered navigation controls, performance tuning, and clean URL structure. It can outperform any ecommerce platform at scale.

Should I use Magento or Shopify for SEO?

Shopify is easier to optimise and faster to launch. Magento gives you more control and scales better for complex catalogues (10,000+ products, multiple store views, custom attribute sets). Choose Magento if you need enterprise flexibility and have the development resources to maintain it.

How do I fix duplicate content in Magento?

Three steps: (1) Disable category paths in product URLs, (2) enable canonical tags for both categories and products, (3) implement noindex or AJAX filtering for layered navigation pages. This eliminates the three most common sources of Magento duplicate content.

What's the best Magento SEO extension?

Amasty SEO Toolkit is the most comprehensive single extension. It handles canonical management, meta templates, rich snippets, and redirect management. For layered navigation specifically, Amasty Improved Layered Navigation is the industry standard.