Magento SEO: Every Magento 2 Setting to Change, With Admin Paths and a Checklist

Magento SEO is the work of configuring a Magento 2 store (Magento Open Source or Adobe Commerce) so Google crawls one clean URL per product and category, then adding the content and links the platform doesn't create for you. Magento ships the right tools: URL rewrites, canonical tags, an XML sitemap generator, a robots.txt editor and SEO fields on every product. Several of them are switched off by default, and its layered navigation can generate thousands of duplicate URLs.

This guide lists the settings to change with their exact admin paths, explains the duplicate-URL traps specific to Magento, and ends with a checklist you can tick off. Everything below applies to the 2.4 release line, including 2.4.9 (May 2026).

#Is Magento good for SEO?

Yes, if someone technical looks after it. Magento gives you control over almost everything that matters for SEO: URL keys, rewrites, canonical tags, meta fields per store view, robots directives, sitemaps and full access to templates. That flexibility is why it suits large catalogs and multi-store setups.

The catch is that few things are set up for you. Compared with Shopify or Wix, Magento expects you (or a developer) to configure canonicals, tame layered navigation, keep the frontend fast and add structured data beyond the basics. W3Techs counts Adobe Commerce on 0.3% of all websites in October 2026, so it's a smaller ecosystem with fewer SEO plugins than WordPress, and more of the work happens in code. Our best CMS for SEO comparison covers how it stacks up against the alternatives.

#The Magento 2 SEO settings to change first

These are the settings that cause most Magento SEO problems. Defaults come from Magento's own configuration files in the 2.4 code base.

Sources: Adobe's catalog URL documentation, metadata documentation and the Magento 2.4 config.xml defaults.

Two notes. Before changing any field, untick Use system value next to it, then click Save Config. And the canonical settings matter more than they look: with product canonicals on, every product page points to yourstore.com/url-key.html, even if a visitor reaches it through a category path.

#The duplicate URL traps specific to Magento

Most Magento stores that struggle in Google have the same problem: Google finds many URLs for the same content, crawls the wrong ones and indexes fewer real pages. If your Search Console Page indexing report shows lots of "Duplicate without user-selected canonical" or "Crawled - currently not indexed" URLs, start here. Our guide on fixing crawled but not indexed pages covers the diagnosis in general.

#Layered navigation filters

Magento's layered navigation adds a parameter for every filter, using attribute option IDs: /women/tops.html?color=49&size=167&price=20-30. Combine five filters with a few values each and one category becomes thousands of URLs. Google's faceted navigation guidance says this kind of setup can create infinite URL spaces and slow the discovery of useful pages.

Multi-vendor stores built on Magento face the same problem at a larger scale, as our marketplace SEO guide explains. Your options: block filter parameters in robots.txt (simplest), rely on category canonicals (helps, but Google treats them as hints and keeps crawling), or use an extension that turns a few valuable filter combinations into clean, indexable landing pages ("red dresses") and leaves the rest blocked.

#Sort, limit and view parameters

Every category also exists as ?product_list_order=price, ?product_list_limit=36 and ?product_list_mode=list. These pages add nothing new. Block them along with the filters.

#Category paths in product URLs

If Use Categories Path for Product URLs is set to Yes, a product in three categories gets three URLs (/men/shoes/runner-x.html, /sale/runner-x.html...). Leave it on No. If a previous agency switched it on, turn product canonicals on before you switch it off, and expect a reindex period.

#Internal search results

/catalogsearch/result/?q=... pages are thin and infinite. They should never be indexed.

#Robots.txt for Magento

Magento builds robots.txt from the field at Content → Design → Configuration → (Global or store view) → Search Engine Robots → Edit custom instruction of robots.txt file. Click Reset to Default and Magento fills in a starting set of rules that Adobe documents:

User-agent: *
Disallow: /index.php/
Disallow: /*?
Disallow: /checkout/
Disallow: /app/
Disallow: /lib/
Disallow: /*.php$
Disallow: /pkginfo/
Disallow: /report/
Disallow: /var/
Disallow: /catalog/
Disallow: /customer/
Disallow: /sendfriend/
Disallow: /review/
Disallow: /*SID=

The Disallow: /*? line blocks every URL with a parameter. That handles filters, sorting and search results in one go, but it also blocks paginated category pages (?p=2). If products deep in your categories aren't in the XML sitemap, add Allow: /*?p= so Google can still crawl pagination. Then add your sitemap line: Sitemap: https://www.yourstore.com/sitemap.xml.

Remember that robots.txt stops crawling, not indexing. URLs already in Google's index stay there until they drop out, and Google can't see a canonical or noindex tag on a page it isn't allowed to fetch.

#XML sitemap setup

1. Go to Stores → Settings → Configuration → Catalog → XML Sitemap. Under Generation Settings, set Enabled to Yes and pick a daily frequency for stores that add products often.
2. Under Search Engine Submission Settings, set Enable Submission to Robots.txt to Yes.
3. Set Add Images into Sitemap to Base Only or All for product images.
4. Go to Marketing → SEO & Search → Site Map, click Add Sitemap, set the filename and path, and generate it.
5. Submit the sitemap URL in Google Search Console under Indexing → Sitemaps.

Magento splits files at 50,000 URLs by default, which matches Google's limit. Make sure Magento's cron is running, or the sitemap silently stops updating. Our sitemap guide explains what Google does with it.

#Product and category page SEO

Each product has a Search Engine Optimization section on its edit page with URL Key, Meta Title, Meta Keywords and Meta Description. Meta Keywords can stay empty: Google ignores that tag.

The defaults are weak. Magento's auto-generation masks set the meta title to the product name and the meta description to the name followed by the description, which usually gets cut mid-sentence. Rewrite the title and description by hand for your top sellers and highest-impression categories (Search Console's Performance report tells you which), and change the masks so new products get something better. Our guide to writing meta titles has formulas that work for product pages.

Category pages are where Magento stores rank for their most valuable searches. Give each important category a unique H1, a short description above the grid (two or three sentences on what's in the category and who it's for) and links to related categories. Keep longer copy below the products. Use the ecommerce keyword research process to decide which categories deserve that effort first.

For structured data, the Luma theme outputs basic schema.org Product microdata (name, SKU, price, description). That's a start, but most stores add JSON-LD with an extension or theme code to include offers with availability, aggregateRating from real reviews, brand and gtin. Test product pages with Google's Rich Results Test.

#Speed and Core Web Vitals on Magento

Magento's default Luma frontend is heavy, and slow stores lose both rankings and sales. Google's Core Web Vitals thresholds for a "good" experience are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 (web.dev).

What usually moves the numbers on Magento:

• Run the store in production mode with full-page cache on Varnish, which Adobe recommends for production.
• Consider Hyvä, a lightweight frontend theme that replaces Luma's RequireJS and Knockout front end with Alpine.js and Tailwind CSS, and has been free and open source since November 2025.
• Serve WebP images at the size they display and lazy-load images below the fold. See our guide to optimizing images for the web.
• Audit third-party extensions and tracking scripts: each one adds JavaScript to every page.

Check field data in Search Console under Experience → Core Web Vitals, and use PageSpeed Insights for page-level diagnosis. Google retired its separate Mobile-Friendly Test in 2023, so Lighthouse and PageSpeed Insights are now the tools for mobile checks.

#Multi-store and multilingual Magento SEO

Magento's store views make multi-language and multi-country stores easy to run, and easy to get wrong in search. Magento has no built-in hreflang setting, so stores add the tags with an extension or theme code. Every language version needs hreflang annotations pointing to all the others, translated URL keys and meta fields per store view, and its own sitemap. Our SEO localization guide covers hreflang and what to translate beyond the words.

#Content: the part Magento doesn't do for you

Product and category pages win commercial searches. They rarely win the research searches that come first: "how to choose a road bike size", "merino vs synthetic base layer". Those need articles, and Magento Open Source has no native blog. Stores either install a blog extension or run WordPress on a /blog subfolder of the same domain.

Content is also how Magento stores earn links, since few sites link to a category page. Our ecommerce link building guide covers the tactics that work for stores.

Outrank has no native Magento connector. Magento stores use it through its custom webhook (a developer maps incoming articles to your blog module) or through a WordPress blog on the same domain. It then researches low-competition keywords, writes the articles and publishes one a day. For stores of this kind the results are encouraging: in our study of 2,119 sites, 71% of e-commerce sites grew their Google clicks, and 78% of the 332 sites publishing through a custom webhook did.

#When to hire a Magento SEO developer

Some Magento SEO tasks are admin settings anyone can change. Others need a developer who knows Magento specifically:

• Writing robots.txt rules and testing them against real URLs
• Adding hreflang and JSON-LD structured data in the theme
• Redirect plans for a migration or a URL key change across thousands of products
• Varnish, Hyvä or Core Web Vitals work
• Cleaning up a bloated url_rewrite table after years of category changes

When you interview one, ask how they handle layered navigation, which canonical settings they'd use and why, and how they'd measure the result in Search Console. A good answer names specific settings and URL patterns, not "we optimize your on-page SEO". For broader help, our guide to technical SEO services explains what an engagement should include and cost.

#Magento SEO checklist

#FAQ

#Is Magento good for SEO?

Yes. Magento gives you control over URLs, canonical tags, meta fields, robots directives and sitemaps, which suits large catalogs and multi-store setups. The trade-off is that several important settings are off by default and its layered navigation creates duplicate URLs, so it needs more technical setup than Shopify or Wix.

#What are the most important Magento SEO settings?

Turn on canonical tags for categories and products, keep Use Categories Path for Product URLs on No, and keep Create Permanent Redirect for URLs if URL Key Changed on Yes. All three are in Stores → Settings → Configuration → Catalog → Catalog → Search Engine Optimization. Then set up robots.txt and the XML sitemap.

#How do I add meta titles and descriptions in Magento 2?

Open the product or category in the admin, expand the Search Engine Optimization section, and fill in Meta Title and Meta Description. For default patterns on new products, edit the masks in Stores → Settings → Configuration → Catalog → Catalog → Product Fields Auto-Generation.

#How do I stop layered navigation from hurting SEO in Magento?

Block filter, sort and limit parameters in robots.txt (Magento's default rules include Disallow: /*?), and turn on category canonical tags. If some filter combinations have real search demand, use an extension that gives them clean, indexable URLs and keep the rest blocked.

#Does Magento have a blog for SEO?

Magento Open Source has no built-in blog. Stores install a blog extension or run WordPress on a subfolder of the same domain so articles build authority for the store. Page Builder, included in both editions since 2.4.3, can build content pages, but it isn't a blog system.

#What does a Magento SEO developer do?

A Magento SEO developer handles the tasks that need code: robots.txt rules, hreflang and structured data in the theme, redirect plans for migrations, Varnish and Core Web Vitals work, and URL rewrite cleanups. Admin settings and content can usually be handled by the store team.