Magento SEO in 2026: the stock settings, the layered-nav fix, and when to migrate off

Most Magento SEO guides on the first page of Google are written by extension vendors. They have a paid SEO suite to sell you, so the post conveniently ends with a feature comparison and a buy button. Plumrocket, Amasty, Mageworx, Mirasvit, all the same shape. Moz and Conductor cover the basics well but stop short of the Magento-specific traps that actually move rankings.

We build and migrate Magento and Adobe Commerce stores, and we also run plenty of WooCommerce sites, so we have no module to push you toward and no reason to oversell the platform. This is the practical setup that gets a Magento 2.4.x store ranking, in the order we configure it, with the parts most vendors skip because they sell a fix for them.

Magento SEO in 2026: what is actually different

Magento is more SEO-capable out of the box than people give it credit for. Stock Magento 2.4.x ships with canonical tags, XML sitemaps, robots controls, meta-data fields per product and category, friendly URLs, and structured-data hooks. About 80 percent of what extension vendors sell you for 200 to 500 dollars a year is already in the core admin, badly labelled and three menus deep but there.

The remaining 20 percent is where Magento eats agencies for breakfast: layered navigation creating thousands of duplicate URLs, Page Builder content rendering with the wrong canonical, Adobe Commerce B2B and category-permissions setups that hide pages from Google by accident, and Hyvä frontends shipping without the schema that the Luma frontend used to render automatically. Those are the SEO issues that drag a store down, and you fix them with configuration, not a paid module.

Step 1: turn on the SEO settings the docs hide

Before anything else, walk through these four settings. New Magento builds we audit fail at least one of them, and on older 2.3 stores it is usually all four.

Stores > Configuration > General > Web > URL Options. Set “Use Web Server Rewrites” to Yes. Without this, every URL on your store carries an index.php segment. Google does not enjoy that, and neither will any human pasting links.

Stores > Configuration > Catalog > Catalog > Search Engine Optimization. “Use Canonical Link Meta Tag For Categories” and “Use Canonical Link Meta Tag For Products” should both be Yes. This is the single most important Magento SEO control and it ships set to No. The layered-nav duplicate-URL problem starts here.

Stores > Configuration > Catalog > XML Sitemap. Enable it, set the cron schedule to daily, and check that the generated sitemap is at /sitemap.xml not /pub/sitemap.xml. The default sitemap path differs between installations depending on whether the document root points at the project root or the pub directory. We see this misconfigured on roughly half the stores we audit.

Stores > Configuration > Design > Search Engine Robots. Set Default Robots to INDEX, FOLLOW on production and NOINDEX, NOFOLLOW on staging. Adobe Commerce Cloud stages do not always inherit this from your config files, so verify on every environment.

Step 2: kill the layered-navigation duplicate URLs

This is the SEO problem unique to Magento that almost every “guide” glosses over. Layered navigation (the price, colour, size filters on category pages) generates a separate URL for every combination of filters. A category with five filterable attributes and four options each produces a few hundred indexable URL variations, all serving near-identical content. Google sees duplicate content and dilutes the category’s rank.

Canonical tags help but do not solve it on their own. The stock canonical points the filtered URL back at the base category, but Google still crawls every variation and your crawl budget burns. What you actually want:

• Canonical to the base category URL (enabled in step 1).
• A robots.txt rule blocking filter-parameter URL patterns. The exact pattern depends on your theme: typically Disallow: /*?* with allow-exceptions, or a targeted Disallow: /*?cat= set.
• For attribute filters you genuinely want indexed (colour pages that get search volume, for example), build a dedicated landing category and link to it instead of relying on the filter URL.

This is the configuration step where a paid extension like Mageworx or Mirasvit earns its money, because they automate the per-attribute rules. We still configure most of it by hand on smaller stores, because the recurring fee outweighs the one-time setup time below a few thousand SKUs.

Step 3: fix the product and category metadata at the data layer, not the page

Magento stores tend to have 90 percent of products inherit a default meta title and description, because nobody filled them in. The fix is not to write 4,000 unique meta titles by hand. It is to set a sensible templated default at the catalog level and override only the products that earn the editorial attention.

In Stores > Configuration > Catalog > Catalog > Product Fields Auto-Generation, configure the URL-key, meta-title and meta-description templates with attribute placeholders: {{name}} | {{brand}} | YourStore for the meta title, a short description template for the meta description. Then build a small report of products with traffic potential and write the manual overrides on those. Most stores with 2,000 SKUs only need 50 to 100 hand-written meta descriptions to cover the products that account for 80 percent of search demand.

Step 4: Core Web Vitals, where Magento wins or loses today

In 2026, page speed is the single biggest ranking lever for a Magento store. The platform has a reputation for being slow, and stock Luma on a default LAMP stack deserves it. A modern Magento install does not.

The two-line summary of how to make Magento fast: Varnish in front of PHP-FPM, indexers on Update on Schedule, and Hyvä replacing Luma on the frontend. Hyvä alone takes a typical store from a Largest Contentful Paint around 3.5 seconds to under 1.5, which Google has been weighting heavily since the 2024 Core Web Vitals update. The Hyvä licence is 1,000 euros one-off per store, which sounds steep until you compare it to the cumulative cost of fighting Luma performance with paid optimization modules.

If you are still on Luma, the highest-leverage fixes are Redis for session and cache, Elasticsearch for the catalog (mandatory since 2.4 anyway), critical CSS inlined in the head, and JS-bundling left off because Magento’s bundling is worse than no bundling. We have measured a 1.2-second LCP improvement on a 500-SKU Luma store from just those four changes, with no extensions added.

Step 5: schema for product, category, and FAQ pages

Magento ships Product schema by default on product pages, which is the table-stakes ecommerce structured data. What it does not ship:

• BreadcrumbList on category pages (most themes drop this).
• FAQPage schema on product or content pages with FAQ blocks.
• Organization markup with sameAs links to your social profiles.
• Review aggregateRating in the right shape (Magento’s stock review rendering passes the validator but does not surface in rich results for many themes).

We add these through a small custom module on every Magento build, which is the kind of work an open-source platform actually rewards you for: a 200-line PHP module that ships with the project and does not need a vendor relationship to maintain. Hyvä makes this even simpler because the schema templates are first-class blocks rather than scattered through layout XML.

What about Adobe Commerce vs Magento Open Source for SEO

Adobe Commerce adds Page Builder, which is a problem for SEO until you configure it. Page Builder content blocks render in iframe-like wrappers that some crawlers handle badly, and the canonical URL on Page Builder content pages defaults to the wrong path on Adobe Commerce Cloud installs. We have seen entire Page Builder landing pages drop out of the index because of this. The fix is configuring the canonical override per page and confirming the rendered HTML matches the Magento Open Source equivalent.

Adobe Commerce B2B is the bigger SEO gotcha. Category permissions, shared catalogs, and customer-group pricing all interact with what Googlebot sees as an anonymous crawler. A common pattern: the staging password gets removed, B2B locks the category to logged-in users, and Google sees a login redirect for every product. Audit this carefully before launch.

For pure SEO, Magento Open Source and Adobe Commerce are equivalent. The licence cost of Adobe Commerce does not buy you better rankings, only the B2B features and the Adobe support contract.

When SEO is telling you to migrate off Magento

The honest part. If you are running a Magento Open Source store with under 500 SKUs and your SEO problem is “we cannot get the meta descriptions filled in, the hosting bill is 300 dollars a month, and the developer who set up our extensions left”, the SEO answer is probably not to optimize Magento. It is to move to WooCommerce on a Cloudways or Kinsta plan and run Rank Math or Yoast. We have done this migration enough times to know the SEO numbers usually improve, because the per-product editorial workflow becomes light enough that the meta data finally gets written.

Magento earns its place on stores with complex catalogs (10K+ SKUs), multi-store, B2B pricing, or a roadmap that needs the customization Adobe Commerce supports. If that does not describe your business and your SEO is suffering, the platform itself may be the bottleneck. Our WooCommerce build and migration team handles the move when that is the right call.

The minimum-viable Magento SEO setup, in order

To put it all together, this is the sequence we work through on every Magento SEO engagement:

1. Turn on the four configuration settings from step 1.
2. Audit and fix the layered-navigation duplicate URLs.
3. Set templated meta and write manual overrides for the top 50 to 100 products by traffic potential.
4. Move to Varnish + Redis + Hyvä (or fix Luma to within shouting distance of those numbers).
5. Add schema for breadcrumbs, FAQ, and Organization through a small custom module.
6. Double-check Adobe Commerce canonical and B2B permissions if you are on Adobe Commerce.
7. Review monthly in Google Search Console and Bing Webmaster Tools, because Bing still sends meaningful B2B traffic.

If you want the same work done on your store, our Magento development services page covers SEO audits, performance work, and migrations. For more context on the platform itself, the Magento blog covers comparisons and migration playbooks, and the Magento vs Shopify post walks through when the right answer is “neither, run on WooCommerce instead”.

Need a build, not just SEO? Our Magento development services cover Adobe Commerce and Open Source stores end to end.

Selling to businesses rather than consumers? See how we set up Magento for B2B and wholesale, including company accounts, negotiable quotes, and the Adobe Commerce versus Open Source cost decision.

Slow store dragging down your rankings and conversions? Our Magento speed optimization service fixes TTFB, sets up Varnish and Hyva, and proves the gain in Core Web Vitals.

Trying to choose an edition? See our breakdown of Adobe Commerce vs Magento Open Source and when the paid license actually pays for itself.

Page speed is also a ranking factor, so once the on-page work is done, walk through our guide to Magento speed optimization to make sure Core Web Vitals are not holding the store back.