Magento (Adobe Commerce) SEO guide: the settings that matter

Why Magento SEO needs its own playbook

Magento, now sold as Adobe Commerce for the paid edition and Magento Open Source for the free one, is built for large and complex catalogs. It gives merchants deep control over URLs, store views, attributes, price rules and layered navigation. That control is exactly why Magento stores can rank very well, and also why they can become some of the hardest sites to keep healthy. A single setting can change the canonical behavior of ten thousand categories. A single extension can add a second set of meta tags. A slow server can undo years of content work.

This guide explains the Magento settings and structures that matter most for search: URL rewrites, canonical configuration, layered navigation, multi-store setups, sitemaps and robots rules, structured data, speed and routine audits. It supports our Magento SEO service and assumes you can read a crawl report. For the general theory of how large stores should structure categories and filters, see enterprise ecommerce SEO and faceted navigation SEO.

A word on versions. Magento has changed a great deal across releases, and the admin paths, defaults and extension ecosystem differ between them. Use this guide to know what to look for, then verify the exact settings in your own version and test on a staging environment before touching production.

URL rewrites and URL structure

Magento stores human-readable URLs in a rewrite table that maps the address people see to the internal route. This system is powerful and, at scale, it can become a source of trouble.

Choose the URL pattern deliberately

Typical Magento addresses include the category path and a suffix, for example /mens/shoes/trail-runner.html. You can usually decide whether product URLs include the category path, and whether the .html suffix is used. The cleaner option for most stores is a product URL that does not depend on a category, so each product has a single address that stays put if you rearrange the category tree. If product URLs do include the category, a product in several categories can exist at several addresses, which makes canonical settings essential.

Let Magento create redirects, and check them

When you change a product or category URL key, Magento can create a permanent redirect from the old address to the new one automatically. This is helpful but it builds up. Years of renamed products produce redirect chains where A goes to B goes to C. Audit the rewrite table periodically, collapse chains so each old URL points directly at the final address, and remove redirects that point to pages that no longer exist.

Watch for duplicate URL keys

Two products or categories with the same URL key in the same store can cause conflicts, often resolved by appending numbers such as -1. These numbered URLs are a sign of duplicate or poorly named catalog entries. Fix the cause by giving items distinct, meaningful URL keys.

Canonical tags and duplicate content

Magento includes settings that tell it whether to print canonical link tags for categories and products. Check that both are on. Without them, filtered, sorted and parameterized versions of a page compete with the main version.

• Category canonicals. The canonical on a category page should point at the clean category URL, not at a filtered or sorted variation.
• Product canonicals. If products can be reached through category paths, the canonical should consolidate on one address. Decide which, then confirm the rendered tag.
• Pagination. Paginated pages should not all canonicalize to page one if that would hide products from crawlers. Each page of a series should canonicalize to itself and link clearly to its neighbors. Our category page guide explains why.
• Extension interference. SEO extensions and themes sometimes print their own canonical tags. Count the tags on a rendered page. There should be exactly one.

Test settings on staging. A switch that is changed for all store views at once can alter thousands of pages.

Layered navigation and crawl control

Magento's layered navigation lets shoppers filter by price, brand, size and any attribute set to be filterable. Each combination can create a unique URL with parameters. On a catalog with hundreds of attributes, the number of crawlable combinations can reach millions, which wastes crawl capacity and creates endless thin pages.

A sound approach separates filters into three groups.

Make filters on the third group non-crawlable by using JavaScript that does not expose links, or add noindex directives, depending on how the theme renders them. If you also use robots.txt rules, remember that a URL blocked from crawling cannot have its noindex read. Our guide to noindex versus disallow explains the trade-off, and identifying crawl traps shows how to find the combinations that waste the most crawl activity. For choosing which filtered pages to open up, see strategic indexing of filtered attributes.

Store views, websites and multi-store setups

Magento's hierarchy of websites, stores and store views is a strength for international and multi-brand businesses, and a hazard for SEO if not handled carefully.

• One catalog, many store views. Different languages or currencies often share a catalog. Without hreflang and clear separation, near-identical pages in different views compete.
• Hreflang. Core Magento does not add hreflang tags in every setup. Extensions or custom code usually do. Each language or region version must reference itself and its alternates, with correct codes and working URLs. See international ecommerce SEO for the structure choices.
• URL structure per view. Subfolders, subdomains or separate domains all work, but each has implications for authority and maintenance. Choose one pattern and apply it consistently.
• Default store view in the URL. Some setups add a store code such as /en/ to every URL. Decide whether you want it, and make sure the version without it redirects to the version with it, or the reverse, and not both.
• Per-view settings. Titles, descriptions, URL keys and canonical settings can be overridden at the store view level. Audit each view, not just the default.

XML sitemaps and robots.txt

Magento can generate XML sitemaps for categories, products and CMS pages, with options for update frequency and priority. Treat those two fields as low value: search engines largely ignore them. What matters is that the sitemap lists canonical, indexable, 200-status URLs and nothing else.

• Exclude disabled or out-of-stock products only if you have decided those pages should not be indexed.
• Confirm the sitemap does not contain redirected URLs, noindexed pages or parameterized filter URLs.
• For very large catalogs, split the sitemap into several files, within the size limits search engines document.
• Submit the sitemap in Search Console and check the coverage numbers against the number of URLs you expect to be indexed.

For robots.txt, block areas that offer no search value, such as the admin, checkout, customer account pages, search results and technical paths. Do not block the folders that hold CSS and JavaScript files that pages need to render. Remember that robots.txt controls crawling, not indexing.

Structured data

Product pages should carry accurate Product markup with name, image, description, SKU, price, currency, availability and, where genuine, ratings. Category pages benefit from breadcrumb markup, and the home page from organization and site information. Magento themes and extensions can print this in JSON-LD, microdata or both. The risk is duplication: a theme prints one block, an extension another, and the page ends up describing the product twice. Pick one source, remove the rest and validate with Google's Rich Results Test. Keep the data consistent with the visible page, including when a price changes or a product sells out.

Performance and hosting

Magento is resource intensive. Out of the box a poorly hosted installation can be slow enough to harm both conversions and rankings, so performance is part of SEO here, not a separate project.

• Hosting and architecture. Use hosting designed for Magento, with enough memory, a recent PHP version, a fast database and a search engine service configured as the version requires.
• Full-page caching. Enable the built-in cache and consider a reverse proxy cache. Confirm that personalized areas, such as the cart, do not break.
• Front-end weight. Many themes and extensions load large bundles of JavaScript and CSS. Reduce what loads on each template, defer non-critical scripts and consider a modern lightweight front end if your budget allows.
• Images. Serve properly sized, compressed images in modern formats, and reserve their dimensions to avoid layout shifts.
• Extensions. Each extension can add queries, scripts or both. Review them regularly and remove any you do not need.
• Database and indexers. Keep indexers running correctly and the database tidy so category and product listings stay quick.

Our Core Web Vitals guide explains the metrics, and the same fixes apply to Magento templates: product page, category page and home page.

Category, product and CMS content

Magento's flexibility lets you build thousands of pages; it does not make any of them good. The pages that rank are the ones with useful, original content.

• Category pages. Add a concise introduction above the product grid, and fuller buying advice below it where useful. Use the category description and the CMS block features to keep content unique and structured.
• Product pages. Replace supplier copy with original descriptions. For large catalogs, prioritize top sellers and high-margin products first, and use templates for the long tail that still include unique attributes.
• Attributes. Product attributes should be accurate and consistent, because they feed filters, structured data and sometimes page copy.
• CMS pages and blog. Use these for buying guides, comparisons and support content that links into categories and products. Our keyword research guide shows how to choose topics.

Governing a large catalog

As catalogs grow, process matters more than any one setting.

• Naming rules. Agree how products, categories and URL keys are named and who can create them.
• Lifecycle rules. Decide what happens to discontinued products: redirect to a close replacement, redirect to the category, or return an error if they have no value. Do not redirect them all to the home page.
• Import controls. Bulk imports can overwrite URL keys or titles. Preview changes and keep backups.
• Change log. Record every change to canonical, robots and URL settings with date and reason, so you can connect traffic changes to causes.
• Staging. Test upgrades, extensions and theme changes outside production, and crawl staging before release.

Upgrades and platform migrations

Magento stores often face major upgrades, theme replacements or moves to another platform. Each is a risk to rankings. Before a change, crawl the live site and export titles, descriptions, canonicals, redirects and top-ranking URLs. After the change, compare the same data and fix gaps quickly. If you are moving away from Magento, or to it, follow the process in our ecommerce platform migration SEO approach and consider our SEO migration service.

A worked example: a category with thousands of crawlable URLs

Take a fictional Magento store selling outdoor equipment. Search Console shows 18,000 indexed URLs, though the catalog has 2,500 products and 120 categories. A crawl reveals the cause: the "Tents" category produces URLs with price ranges, sort orders, brand and size filters in every combination. Googlebot is spending much of its time on these, while new products take weeks to be discovered.

The team works through it in order.

1. Classify the parameters. Brand is valuable, size and color are useful to shoppers but not search targets, and price ranges, sort order and items per page have no search value.
2. Fix canonicals. Filtered and sorted pages canonicalize to the clean "Tents" URL. The team confirms the rendered tag on staging.
3. Open the valuable pages. "Tents by brand" combinations that match real searches get static URLs with their own introduction, and links from the category page.
4. Close the rest. Links to price and sort variants are removed from the crawlable HTML, and noindex directives are added where the theme still outputs them.
5. Clean the sitemap. Only canonical category and product URLs remain.
6. Watch the numbers. Over several weeks, the indexed count falls toward the real number of useful pages, new products are discovered faster and the main category begins to hold its position more reliably.

The lesson is general: on a large catalog, the biggest SEO gain often comes from subtraction. Fewer, better pages mean search engines spend their attention where it pays.

A Magento SEO audit in eight steps

1. Crawl the site on staging and production, and group URLs by type: category, product, CMS, filter, search and other.
2. Check canonical settings in the admin and in the rendered HTML for each type.
3. Review layered navigation output and decide which combinations should be indexable.
4. Inspect the rewrite table for chains, loops and numbered duplicate URL keys.
5. Verify sitemaps and robots.txt against the URLs you actually want indexed.
6. Test hreflang and store view setup if you run more than one language or region.
7. Validate structured data on products, categories and the home page, and remove duplicates.
8. Measure speed by template, using real-user data where possible, and tie fixes to specific components.

The technical SEO audit checklist covers the general checks, and our ecommerce SEO audit applies them to stores like yours.

Common Magento SEO mistakes

1. Leaving canonical tags off. Filtered and sorted pages compete with the main category.
2. Allowing every filter combination to be crawled. Crawl capacity is spent on pages with no value.
3. Letting redirect chains grow. Old renames pile up into slow, weak paths.
4. Running two sources of meta tags or schema. A theme and an extension both print them.
5. Ignoring other store views. The default view is fine, the others are not.
6. Treating hosting as an afterthought. Slow servers cap everything else you do.
7. Sending discontinued products to the home page. Relevance and equity are lost.
8. Publishing supplier descriptions. Pages are indistinguishable from competitors'.
9. Changing settings on production without testing. One switch can affect thousands of pages.
10. Not tracking changes. Nobody can explain a traffic drop.

How we help

We begin with the rendered output and the rewrite table, because those show what search engines actually receive. We then map your filters, store views and templates, hand your developers a prioritized change list and measure the effect in Search Console. See our Magento SEO service, read about ecommerce SEO or request a free SEO audit of your store.

Summary

• Magento gives deep control, and the settings you choose for URLs, canonicals and filters decide how clean your index is.
• Turn on and verify canonical tags, and keep redirects short and direct.
• Decide which filtered pages should rank, and keep the rest out of crawl paths and internal links.
• Audit every store view, with hreflang, sitemaps and robots rules that match your intent.
• Treat performance and hosting as part of SEO, and keep one source of structured data.
• Govern the catalog with naming, lifecycle and change-log rules, and test everything on staging.