Magento SEO Services for Magento Open Source and Adobe Commerce Stores

Updated October 2026 · Written and maintained by the Progression Agency strategy team

Magento SEO services are search engine optimization work carried out inside a Magento Open Source or Adobe Commerce store: the catalog settings, URL keys and rewrites, layered navigation, canonical tags, sitemaps, structured data, speed and migrations that decide which category and product pages search engines crawl, index and rank. We do this work for ecommerce managers and store owners who need organic search to produce orders, not just sessions. Progression Agency is based in New York City and works with clients across the United States and worldwide.

What do Magento SEO services cover?

Everything between the Admin and the search result. Magento gives a store more SEO controls than most platforms, which means more settings that can be wrong, and most of the work is finding the few that matter on your catalog and changing them safely.

General store SEO, from category page strategy to product copy and out-of-stock handling, is covered on our ecommerce SEO page, and crawling, rendering and audits on any platform on our technical SEO agency page. This page stays with what is particular to Magento: where each setting lives, what its default does, and how it interacts with the rest of the catalog. Adobe’s own SEO overview for Commerce lists the built-in tools we start from: metadata, the sitemap, URL rewrites and search engine robots.

Configuration

Settings in the Admin that change URLs, canonical tags, robots directives and sitemaps for a whole store view at once. Small edits, large consequences.

Catalog architecture

Categories, anchor settings, filterable attributes and product types. This is where duplicate URLs and crawl waste are born.

Templates and content

Title masks, category descriptions, product copy and the markup the theme prints. The visible part of the work, and the part shoppers read.

Platform changes

Upgrades, theme replacements and replatforms. Each one can undo years of search equity in a weekend if URLs and redirects are not planned first.

Who hires a Magento SEO agency?

Mostly teams that already run a Magento store and have more catalog than search traffic. The common thread is a capable platform that nobody has configured with search engines in mind.

The Open Source store with a developer and no SEO owner

A developer keeps the store running and a marketer runs paid campaigns, but nobody owns organic search. The settings are whatever the original build left behind, and the first audit usually finds more than anyone expected.

The Adobe Commerce team

Larger merchants on Adobe Commerce often have merchandising, development and marketing in separate teams. The SEO job is partly technical and partly coordination: agreeing who may change URL keys, filters and templates, and how changes are checked before release.

B2B distributors and manufacturers

Catalogs of thousands of parts, buyers who search by part number or specification, and pages that must rank for very specific queries. Our B2B marketing team works with these stores on the demand side as well.

Stores in the middle of a move

A Magento 1 store that never upgraded, a Magento 2 store moving to another platform, or a store coming onto Magento. The search work starts months before launch, with the URL inventory.

How do store owners search for a Magento SEO expert?

By the platform name. In Ubersuggest data for September 2026, magento seo is the largest phrase at about 390 US searches a month, followed by magento seo services at about 260, then magento seo agency and magento seo expert at about 140 each and magento seo company at about 110.

The bids say more than the volumes. Magento seo services carries a cost per click of $33.58, more than twice the $13.52 on the broader magento seo, which suggests the longer phrase is typed by people ready to hire. Difficulty is modest across the set, from 14 for the company phrase to 33 for the head term, so specialist pages can compete with large agencies here.

Layered navigation and faceted URLs: the largest Magento SEO risk

Layered navigation is the filter panel on category and search pages, and on most stores it creates far more URLs than there are products. Deciding which of those URLs search engines may crawl is usually the highest-value change on a Magento catalog.

Adobe’s guide to layered navigation explains the mechanics. Filters appear only on anchor categories and, optionally, on search results. An attribute becomes a filter when its input type is Yes/No, Dropdown, Multiple Select or Price and its Use in Layered Navigation property is set to Filterable (with results) or Filterable (no results). The second option lists every attribute value, including values with no matching products. Price filters can be split automatically, by equal price ranges or equal product counts, or manually by a step you choose.

Google’s guidance on managing crawling of faceted navigation describes what happens next. Parameter-based filters can produce an effectively infinite URL space, crawlers spend time on those URLs before they can tell they are useless, and new pages are discovered more slowly. Google’s preferred fix, when filtered pages do not need to appear in search, is to disallow the filter parameters in robots.txt and keep the individual product pages and an unfiltered listing crawlable. It describes rel=”canonical” and nofollow links as generally less effective in the long term.

Which filter pages deserve to be indexed

A small number of filtered views match real searches: a category plus a brand, a material or a use. Those are better built as categories or landing pages with their own copy and a clean URL, chosen from search data, than left as parameter combinations.

Blocking the rest

Everything else, including sort orders, page sizes, price ranges and multi-select combinations, is kept out of the crawl with robots.txt rules on the filter parameters, added in the custom instructions box in the Admin or in a physical robots.txt file.

Empty and nonsensical combinations

Google asks for a 404 status when a filter combination returns no products, contains duplicate filters or makes no sense, served at the URL itself rather than through a redirect to a shared not-found page. Setting attributes to Filterable (with results) removes many empty options from the panel in the first place.

Price filters and configurable products

Adobe notes that price filtering uses the lowest price among a configurable product’s child items, so the parent appears only in the lowest price range of its children. Price filter pages are rarely worth indexing for that reason alone.

URL keys, rewrites and the category path setting

Magento decides product and category URLs from URL keys plus a handful of store-view settings. Most duplicate URL problems on Magento start with one of them.

The Search Engine Optimization section of the Catalog configuration reference holds the settings: a Product URL Suffix and a Category URL Suffix such as html, Use Categories Path for Product URLs, Create Permanent Redirect for URLs if URL Key Changed, Generate category/product URL Rewrites, transliteration of product URLs and the two canonical switches. Adobe warns that including category paths in product URLs can cause multiple URLs to point to the same page.

Category paths in product URLs

With the path setting on, a product assigned to two categories is reachable at two or more addresses, plus the short URL built from its key. We generally prefer short product URLs and breadcrumbs for context, and where a store already ranks on path URLs we weigh the cost of changing them against the canonical fix.

When a URL key changes

Adobe’s URL rewrites guide says the rewrite tool creates a permanent 301 redirect by default, and the Create Permanent Redirect for old URL box under each product’s URL key is selected unless someone turns it off. Leave it on. The same page notes that GET parameters are dropped during redirection for security reasons, which matters for campaign tracking links.

Rewrites at scale

Saving a category with many products can regenerate product and category rewrites in real time and slow the store, so Adobe offers a global setting to skip that generation. Changing it does not stop product URLs from resolving, but the rewrite table should be checked before and after so redirects are not lost.

Suffixes and transliteration

Switching a store from .html URLs to bare URLs, or the reverse, changes every product and category address at once and needs a full redirect plan. Transliteration is on by default; Adobe gives a Chinese-language store as a case where native characters in product URLs can be the better choice.

Canonical tags in Magento: the two settings and what they do

Magento can print a canonical tag on category pages, on product pages, or both, controlled by two Yes or No settings per store view. Adobe recommends enabling both.

Adobe’s metadata and canonical tag guide gives the logic. With canonical tags on for products, the canonical points to the domain plus the product URL key, because URL keys are unique across the catalog, even when the product can also be reached through a category path. With canonical tags on for categories, the tag points to the full category URL.

Google treats a canonical tag as a strong signal rather than a command. Its page on consolidating duplicate URLs ranks redirects and rel=”canonical” as strong signals and sitemap inclusion as a weak one, says the methods stack, and lists the mistakes to avoid: using robots.txt for canonicalization, pointing different methods at different URLs, and using noindex to pick a canonical within one site. It also asks for a self-referencing canonical on the canonical page and internal links that point at the canonical version.

Pagination is not a canonical problem

Google’s pagination guidance asks for a unique URL for each page of a category and says not to point every page’s canonical at page one. It also says Google no longer uses rel=”next” and rel=”prev”. Themes that canonicalize every page to the first page hide the products further down.

Configurable, simple and child products: duplicate content by design

A configurable product is a parent with a separate simple product behind every variation, each with its own SKU. Unless child products are kept out of search, a store can end up with dozens of near-identical pages per item.

Adobe’s configurable product guide gives the arithmetic: a shirt in three colors and three sizes becomes nine simple products. The parent has no price of its own; the price shown comes from its in-stock children. Child products are assigned to the parent globally across every website, store and store view. Adobe’s SEO notes for its newer storefront make the search point directly: the canonical URL for a configurable product should be the parent product URL, or Google may index child URLs instead.

Child products with their own URLs

If children are visible individually, they get URLs, appear in the sitemap and compete with the parent. We check visibility, sitemap output and internal links for children before anything else on apparel, footwear and parts catalogs.

Variant markup

Google’s product variant structured data uses ProductGroup with variesBy, hasVariant and productGroupID. For a single page holding all variants, Google wants one canonical URL for the whole set of variants, a unique identifier such as a SKU or GTIN for every variant, and a distinct URL that preselects each variant with the right image, price and availability.

When a variant earns its own page

Sometimes a color or size is searched for in its own right. Google also supports a multi-page approach where each variant has a full, self-contained page. That is a deliberate catalog decision, made from search data, not the side effect of child visibility.

Category and product templates: titles, descriptions and copy at scale

Magento fills meta fields from masks unless someone writes them, and the default masks are thin. Templates are where a large catalog’s titles get fixed in one change instead of ten thousand.

In the Product Fields Auto-Generation section of the catalog configuration, the default Meta Title mask is the product name alone, and the default Meta Description mask is the product name followed by the description. Adobe’s metadata guidance asks for a meta title unique to the page and under 70 characters, and a meta description of about 150 to 160 characters, although the field accepts 255.

Masks are a floor

A mask guarantees every product has a title; it does not make the title useful. We build masks from the attributes that carry search demand on your catalog and then hand-write titles for the categories and products that bring the most revenue.

Category copy that helps the shopper

A paragraph that explains how to choose within the category, written once and kept short, does more than a long block of text pushed below the products. Content production for large catalogs runs through our SEO content writing team.

Store views change the template

Most of these fields can be set per store view. A second language or region needs its own titles and descriptions, not the first store’s copy run through a translation tool.

XML sitemaps and robots.txt for each store view

Magento generates sitemaps and robots instructions itself, per store view. Both are easy to set once and forget, and both drift out of date as the catalog changes.

Adobe’s XML sitemap guide covers the settings. Sitemaps are created under Marketing > SEO & Search > Site Map, one per store view, with frequency and priority per content type and a choice of no images, base images only or all images. The default limit is 50,000 URLs per file and 10,485,760 bytes per file. From release 2.4.9 a batch generation method uses memory-optimized processing for large catalogs, and a setting adds the sitemap location to robots.txt.

Two details change how we configure it. Google’s sitemap documentation says Google ignores priority and changefreq values and uses lastmod only when it is consistently accurate, so time spent tuning priorities is wasted. And Google’s own limit is 50,000 URLs or 50MB uncompressed per file, so Magento’s 10MB default is the tighter ceiling on stores with long URLs or many images.

Robots instructions and staging leftovers

Robots settings live under Content > Design > Configuration, where the Default Robots value and a box for custom instructions sit in the Search Engine Robots section. Adobe suggests disallowing everything while a site is in development. The risk is the reverse: a store launched with that instruction still in place, or a production robots file copied back from staging.

robots.txt does not remove pages

Google is explicit that robots.txt is not a way to keep a page out of its results; a blocked URL can still be indexed without its content. Pages that must not appear need noindex or password protection, and they must stay crawlable for the noindex to be seen.

Several websites, one Admin

For installations with more than one website, Adobe describes a sitemaps folder at the root with a subfolder per domain, each store’s sitemap saved to its own path, and one Sitemap line per domain added to robots.txt. Every site must be verified in Search Console.

Structured data for Magento product pages

Magento’s product template prints schema.org markup by default, which is a start. Whether it is complete, accurate and present in the first HTML response depends on the theme and the extensions installed since.

Google’s product structured data overview separates product snippets, for pages where people cannot buy, from merchant listings, for pages where they can. Merchant listing markup supports detail such as shipping and return policy, and Google recommends describing return policies and loyalty programs once under Organization markup. It also warns that markup generated with JavaScript can make shopping crawls less frequent and less reliable, and recommends Product markup in the initial HTML.

What we check on the template

That one Product entity appears per page, not two from the theme and an extension; that price, currency and availability match what the shopper sees; that review markup reflects reviews shown on the page; and that variants follow the ProductGroup pattern described above.

Breadcrumbs and organization data

Breadcrumb markup that follows the canonical category path, and organization markup with the store’s name, logo, contact details and policies, are small additions that help search engines understand the whole catalog.

Speed on Magento: full page cache, Varnish, images and the theme

Magento is heavy without caching, and slow responses limit both shoppers and crawlers. The biggest gains usually come from the cache layer and images before any theme work.

Adobe’s Varnish configuration guide strongly recommends Varnish in production and says the built-in full page cache, written to the file system or the database, is much slower. On Adobe Commerce on cloud infrastructure, Fastly image optimization can convert and compress product images in real time, including lossy conversion and adaptive pixel ratios with support for WebP, once the Fastly service and origin shielding are set up.

Google’s Core Web Vitals targets are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint under 200 milliseconds and a Cumulative Layout Shift under 0.1, and Google says good results align with what its core ranking systems seek to reward. Crawling is affected too: Google’s crawl budget guide says the crawl capacity limit rises when a site responds quickly and steadily and falls when responses slow down or return server errors.

Luma, Blank and Hyva

Adobe’s frontend guide describes Luma as a demonstration theme and Blank as the base for custom themes, and permits Luma on a live store. Hyva is a separate Magento frontend built on the same templating system but without UI components, Knockout, RequireJS or LESS, using Tailwind CSS and Alpine.js instead, and its makers say it was built with a focus on performance and reduced complexity. In November 2025 Hyva relicensed the Hyva Theme under OSL3 and AFL3 and made it free from November 10, 2025, while Hyva Checkout, Enterprise and Commerce stay commercial.

A theme change is a migration

Replacing the frontend changes templates, markup, internal links and often URLs for CMS pages. We treat it with the same URL inventory, structured data comparison and crawl before and after as a platform move.

Performance projects for stores are scoped on our website speed optimization page, where a Core Web Vitals audit is published at $1,000 to $3,000 and a store or application performance project at $10,000 to $40,000.

Does crawl budget matter for your Magento catalog?

Only for some stores. Google says its crawl budget guide is written for very large or fast-changing sites, but layered navigation can make a mid-sized Magento catalog behave like a much larger site.

Google’s crawl budget guide is aimed at sites with more than about a million pages that change weekly, sites with more than about 10,000 pages that change daily, and sites where much of the inventory sits in Search Console as Discovered, currently not indexed. It counts crawl budget per hostname and names duplicate URLs as a common waste of what Google calls perceived inventory. A catalog of a few thousand products with a dozen filterable attributes can expose many more filter URLs than products, which is why the filter decisions above come first.

• Search Console’s Page indexing report: how many URLs are Discovered, currently not indexed, and which patterns they follow.
• Crawl stats: requests by response code and file type, and whether average response time is rising.
• Server logs: which URL patterns Googlebot requests most, compared with the pages that earn revenue.
• A crawl of the store with filter parameters followed, to see how far the URL space really extends.
• The sitemap: whether it lists only canonical, indexable, in-stock or intentionally kept product and category URLs.

Multi-store, multi-language and hreflang on Magento

Magento’s website, store and store view structure can run several countries or languages from one Admin. Search engines need to be told which version is for whom, or the versions compete with each other.

Adobe’s page on site, store and view scope sets out the hierarchy: websites at the top, each with its own domain if needed; stores beneath them with their own root category; and store views for language and currency, each of which can have its own base URL. Settings cascade from global to website to store to store view.

Google’s hreflang documentation allows annotations in HTML, HTTP headers or the sitemap and treats the three as equivalent. Each language version must list itself and every other version with fully qualified URLs, annotations that are not returned by the other page are ignored, and an x-default value can catch unmatched languages. Google does not use language subdomains or folder names to decide the audience; the annotations do that.

Check what the store actually prints

Whether hreflang comes from the theme, an extension or the sitemap, we crawl every store view and confirm the sets are complete and reciprocal. Our hreflang guide covers the syntax and our international SEO agency page the market strategy.

Canonicals across store views

Google asks that a canonical point to a page in the same language. A store view that canonicalizes to the default store’s English pages tells Google to ignore the translation.

Currency-only store views

Two English store views that differ only in currency are near duplicates. They need region-specific hreflang values, and often a decision about whether both should be indexable at all.

Migrations: Magento 1 to 2, Magento to Shopify, and onto Magento

Replatforming is where stores lose the most organic revenue, almost always for avoidable reasons. The SEO work is an inventory, a redirect map and a long tail of monitoring.

Adobe’s Data Migration Tool documentation describes the Magento 1 to Magento 2 route: a command-line tool that runs in three modes, settings, data and then delta for changes made since the last run, with an integrity check, a transfer and a volume check inside each step. Adobe’s planning notes add that media files are copied across by hand, extensions need Magento 2 versions or replacements, themes and customizations have to be rebuilt, and the whole migration should be rehearsed on a copy of the store first. Product and category data moves with the tool; the theme, the templates and anything an extension printed do not.

Google’s site move guidance applies to every route. Prepare a mapping of old URLs to new ones, redirect each old URL directly to its new equivalent, and keep chains short, ideally no more than three hops and fewer than five. Do not send many old URLs to one irrelevant page such as the new home page, which Google may treat as a soft 404. Keep redirects for at least a year, expect rankings to fluctuate, and expect a small to medium site to take a few weeks for most pages to move.

Magento to Shopify, or Shopify to Magento

The URL patterns change on almost every page, so the redirect map is the whole project. Our Shopify SEO page covers the destination side, and the platform trade-offs are set out in our Shopify versus WooCommerce and BigCommerce versus Shopify comparisons.

Onto Adobe Commerce as a Cloud Service

Adobe’s storefront documentation says URL rewrites created on the PaaS version do not transfer automatically to Adobe Commerce as a Cloud Service; active rewrites have to be added to the storefront’s redirect sheet.

Upgrades inside Magento 2

Adobe’s lifecycle policy gives each Adobe Commerce release three years of standard support from general availability. Release 2.4.9 became available on May 12, 2026, and standard support for 2.4.6 ended on August 11, 2026. Upgrades rarely change URLs, but they often change themes and extensions, so we compare crawls before and after.

Migration projects are scoped on our website migration services page and store rebuilds on our ecommerce website redesign page.

What changes for SEO between Adobe Commerce and Magento Open Source?

Most SEO settings are the same in both editions. The differences that matter come from features only Adobe Commerce has, from the hosting model, and from Adobe’s newer storefront.

Category permissions and crawling

Adobe describes category permissions as an Adobe Commerce feature that can restrict browsing to selected customer types or redirect a category to a landing page. A category hidden from guests is hidden from crawlers too, which is right for trade-only catalogs and a costly mistake for public ones.

Live Search

Live Search is installed from the Adobe Marketplace, needs Adobe Commerce 2.4.4 or later on cloud infrastructure or on-premises, and moves catalog data to Adobe’s hosted service. Its facets replace the standard layered navigation settings, so filter URL rules are reviewed again after it is switched on.

The Edge Delivery Services storefront

Adobe’s storefront SEO indexing notes set a default product URL of /products/ followed by the URL key and the SKU, enforce lowercase SKUs in URLs, handle redirects through a spreadsheet, and generate a sitemap on publication. A move to this storefront is a URL change for every product.

How AI assistants find, read and describe Magento stores

Shoppers and trade buyers now ask ChatGPT, Claude, Perplexity, Gemini, Copilot and Google’s AI Overviews for products and suppliers. The answers draw on pages those systems can crawl and parse, so the same configuration that serves search engines decides whether a store can be named.

The questions buyers ask

A shopper describes a need, such as a waterproof hiking boot for wide feet under a set price, and asks for options. A trade buyer asks which distributors stock a part number or meet a specification. Both get answers assembled from product pages, category guides, comparison tables, reviews and merchant listings.

What the answers draw on

Plain-text product facts in the HTML, specifications in tables, clear category explanations, and structured data that matches the page. Google says there are no additional requirements to appear in AI Overviews or AI Mode beyond its normal guidance.

Crawler access on Magento

OpenAI says sites that allow OAI-SearchBot can appear in ChatGPT search results, Perplexity uses PerplexityBot to surface and link sites, and Anthropic says blocking Claude-SearchBot may reduce visibility in its search answers. On Magento those rules live in the custom robots instructions; our AI crawler access checker shows what a store currently allows, and our answer engine optimization agency team covers the rest, including AEO for ecommerce.

How to choose a Magento SEO company or Magento SEO expert

Choose on demonstrated knowledge of the platform and on how changes reach production. Ask how a provider would handle your filters, your URL settings and your next release before you ask about rankings.

Questions to ask before you sign

Use the same questions with every candidate so the answers can be compared.

1. Which three settings would you check first on our store, and why?
2. How would you decide which filter pages may be indexed?
3. What do you need from our developers, and in what format?
4. How do you test changes before they reach production?
5. What would you measure in the first ninety days?
6. How would you protect our rankings during the next upgrade or theme change?
7. Which extensions on our store affect SEO output, and how would you check them?

Red flags

Walk away from any of these.

• Guaranteed rankings or guaranteed positions for named phrases.
• An audit that is a tool export with no URLs, settings or priorities.
• Advice to noindex or block whole sections without checking what they earn.
• An SEO extension offered as the whole answer.
• No plan for working with your developers or release process.
• Link packages bought by volume.

Choosing between a Magento SEO agency and an individual Magento SEO expert is mostly about capacity. A consultant can diagnose and direct a capable in-house team; a store without developers or writers usually needs a team that can also ship the fixes.

What do Magento SEO services cost?

Ongoing SEO for a store is published at $2,000 to $15,000 a month as a planning range, with catalog size and faceted navigation the main drivers. One-off work such as a technical audit starts at $1,200.

These are published planning ranges from our SEO pricing guide, migration and AEO pricing pages, not quotes. A quote follows a written scope that lists the store views, the catalog size, the deliverables and any developer time or third-party costs on separate lines.

How long does Magento SEO take, and how is it measured?

Configuration fixes show in crawl and index data within weeks; category rankings and organic revenue build over months. The measures change as the work moves from fixing to growing.

Revenue attribution needs working analytics first. Our marketing analytics team fixes ecommerce tracking where it is broken, and conversion rate optimization picks up when traffic grows faster than orders.

How a Magento SEO engagement runs with us

In six steps, from access to a monthly cycle. Each step has an owner and a date, agreed in the written scope before work starts.

1. Access: Search Console, analytics, an Admin user with the right role, a staging environment and the deployment process.
2. Crawl and review: the store, every store view, the configuration sections above and the installed extensions.
3. Priorities: a ranked list of fixes with URLs, settings and the expected effect, written as developer tickets.
4. Release: fixes shipped through your process, checked on staging, then verified in production.
5. Growth: category copy, product templates, structured data, internal links and new pages for unserved demand.
6. Monthly cycle: a report on indexing, traffic and revenue by landing page, and a check of every release.

Search work often sits beside other channels on a Magento store: ecommerce advertising for paid search and shopping, ecommerce email marketing for repeat orders, and link building or digital PR when a store needs authority it has not yet earned.

Related services for Magento and ecommerce teams

• Ecommerce SEO: store SEO on any platform, from category strategy to product copy.
• Technical SEO agency: crawling, rendering, audits and fixes beyond the store.
• SEO audit service: a one-off diagnosis with a ranked list of fixes.
• SEO services: our full search program for any kind of business.
• Local SEO services: for stores with showrooms, counters or pickup locations.
• International SEO and multilingual website design: stores selling across borders.
• Ecommerce development and ecommerce web development: builds and integrations.
• Ecommerce website design and UI and UX design: templates shoppers can use.
• Website migration services: platform moves with the redirect map done first.
• Website speed optimization: Core Web Vitals and store performance.
• Shopify SEO and WordPress SEO: when the store runs on another platform.
• Amazon SEO: for brands selling on the marketplace as well as their own store.
• Ecommerce marketing agency: paid, organic, email and conversion together.
• Answer engine optimization: visibility in AI assistants and AI search.
• BigCommerce SEO services

Frequently asked questions