What does SEO look like on a Magento store?

Magento, now sold as Adobe Commerce, is built for catalogues too big for simpler platforms: thousands of products, several store views, complex pricing and a development team behind it. That scale is why SEO on Magento looks different. The biggest wins are rarely a better title tag. They're about controlling which of your store's many thousands of possible URLs a search engine ever sees, and making a heavy frontend fast enough for a phone.

Here's how Magento creates those URLs, which settings decide what gets indexed, and the order we work through a Magento store, usually alongside the developers who own the code.

Where Magento SEO problems come from

Most Magento SEO problems trace back to three features that exist for good reasons: layered navigation, flexible product URLs and a JavaScript-heavy default frontend. The HTTP Archive's 2024 Web Almanac shows the third one in its numbers. While most ecommerce platforms now have a pass rate above 75% for Interaction to Next Paint, Google's responsiveness measure, Magento sat at 49% on mobile, behind BigCommerce on 67%.

How Magento layered navigation creates crawlable URLs

Layered navigation is the filter panel on a category page, and Adobe's documentation on layered navigation describes it as the way shoppers find products by attribute. Each filter a shopper can click is also a link a crawler can follow, and the filters combine.

We counted them on a live Australian Magento store while writing this. A single clothing category page carried 48 distinct filter links before any two filters were combined: 18 for colour, 10 for size, 10 for sub-category, 7 for brand and 3 for pagination. The store handled it well, because each filtered page returns noindex with a canonical back to the category.

Why noindex alone is not enough

A noindex tag keeps a page out of the results, but Google still has to crawl the page to read it. On a large catalogue that's a lot of crawling spent on pages that'll never rank. Google's guidance on managing faceted navigation is explicit that crawlers visit a very large number of filter URLs before working out they are useless, leaving less time for new products.

What to do with layered navigation

1. Find the filters people search for. A brand name plus a category, or a material such as linen, may deserve a page; most colour and size combinations don't.
2. Build those as proper landing pages with their own content, rather than relying on a filtered URL to rank.
3. Keep the rest out of the index with noindex or a canonical to the category.
4. Reduce the crawling on the worst combinations, with robots.txt rules for parameter patterns or by not rendering combined filters as plain links.
5. Check your server logs to see where Googlebot actually spends its time, which is the only way you'll know it worked.

How to set up product URLs and canonicals on Magento

Magento can put the category path into a product's URL, so the same shirt might live at /mens/shirts/linen-shirt.html and /sale/linen-shirt.html. Adobe's catalogue URL documentation explains the setting and the alternatives plainly: you can exclude the category path from the URL, or use a canonical meta tag to tell search engines which version to index. It also notes that by default, Commerce does not include the category path in product URLs.

• Leave category paths out of product URLs unless you've got a strong reason, so each product has one address.
• Turn on canonical tags for products and categories, so any duplicate you do have points to the right version.
• Link products at their canonical URL everywhere your theme builds a product link, not just in the canonical tag.

How to keep Magento URL rewrites and redirects clean

Magento records a rewrite every time a product or category URL changes, which is how your old URLs keep working. Adobe's URL rewrites documentation covers how these are created, including automatic redirects when a URL key changes. Over years of renamed categories and retired products, that table fills with chains, loops and rewrites pointing at pages that don't exist any more.

A redirect audit, step by step

1. Crawl your site and list every redirect with more than one hop.
2. Point each old URL straight at its final destination.
3. Find redirects that land on a 404 or on your homepage, and send them somewhere relevant.
4. Check Search Console for URLs Google still tries that now return errors.

Internal search, pagination and the other URLs to keep out

• Internal search results at /catalogsearch/result/ are thin and endless. Keep them out of the index and out of your navigation.
• Sort and limit parameters on your category pages create more copies of the same list. Canonicalise them to the category.
• Pagination should stay crawlable so your deep products are reachable, with each page self-canonical rather than pointing every page at page one.
• Customer, checkout and wishlist URLs should never be indexed; check your robots.txt still covers them after any upgrade.

Why Magento stores are slow on mobile, and what to do about it

The default Luma frontend builds pages with RequireJS and Knockout, and every extension adds to the JavaScript it loads. That's the likeliest reason Magento trails other platforms on interaction speed. You've got two realistic paths.

Optimise the frontend you have

Remove the extensions you don't use, tune your JavaScript bundling, make sure full page caching is working with a high hit rate, and serve correctly sized images. This helps, and it's where most stores should start.

Move to a lighter frontend

Hyvä is a third-party frontend for Magento that replaces the Luma stack with a much lighter one. It's usually faster, but it means rebuilding every template, and some extensions need compatibility modules. Treat it like any migration: map your URLs, keep your content and structured data, and crawl the new frontend against the old before you launch.

Store views, currencies and hreflang on Magento

Magento lets you run several stores from one install, such as an Australian and a New Zealand store, but it doesn't output hreflang tags by itself. Without them, Google can show your New Zealand store to Australians. Google's documentation on localised versions of a page sets out how hreflang should work; on Magento you add it through an extension or custom code.

Each of your store views also needs genuinely local content where it matters, its own currency and pricing, and internal links that stay inside the store. The wider version of this work is covered by our international SEO for multi-country stores.

Keep the platform itself supported

An out-of-support version is an SEO risk as well as a security one, because a hacked store can have spam pages injected into it. Adobe's software lifecycle policy states that extended support for Adobe Commerce 2.4.4 and 2.4.5 ends in April and August 2026. If your store is still on either version, it's due an upgrade, and you should plan that upgrade with the same URL and redirect checks as any other release.

Content and the XML sitemap on a large Magento catalogue

With a catalogue of thousands of products you can't write every title and description by hand, and you don't need to. The trick is deciding where hand-written content pays and where a good template is enough.

Templates for the long tail, writing for the categories that sell

• Meta title and description templates built from product attributes, such as brand, product type and a key feature, give every product a sensible default. Magento can generate these from attribute masks rather than leaving them blank.
• Hand-written category content for your categories with the most search demand and revenue: an introduction, buying guidance and FAQs, written once and maintained.
• Unique product copy for your best sellers, where it earns its keep, instead of the manufacturer's text that dozens of other retailers publish word for word.

A sitemap that only lists what should rank

Adobe's SEO overview describes the site map as a way to help search engines find pages they might otherwise miss, and Magento can generate it on a schedule. Make sure yours lists canonical category and product URLs only, excludes disabled and out-of-stock products you've chosen not to index, and has a separate file per store view where you have several. A sitemap full of URLs that redirect or carry noindex tells Google the sitemap can't be trusted.

How to measure Magento SEO

On a large store your measures are organic revenue and transactions, non-branded clicks by category, and crawl health: how much of Googlebot's time goes to categories and products rather than filters. Server logs are worth the effort on Magento because they show you that last one directly.

The result that matters is revenue. The Lowes case study, an SEO-only engagement for a menswear retailer, records a 167% increase in Google organic revenue and an 80% increase in organic transactions, with a number one ranking for "big mens".

A Magento SEO checklist

Most of that list is shared between SEO and development, which is how Magento SEO works in practice: someone has to find the problems, prove which matter, and brief your developers precisely enough that the fix ships once. That's the job of our Magento SEO service, and for very large sites it overlaps with our enterprise SEO for large catalogues. If you're weighing Magento against a simpler platform, how SEO works on WooCommerce and the Shopify version of this guide show what changes, and where a store owner trades control for maintenance. We handle all three as a digital marketing agency for large retailers, and the first step on any of them is the same: a crawl that shows what your store is really publishing. If you want that crawl done for you, a Magento SEO specialist can start there.