Magento SEO Services

Layered navigation and faceted URLs

Every filterable attribute in Magento’s layered navigation creates URLs like ?color=23&size=145&price=50-100. Multiply by sorting, pagination and display mode and a 10,000-product catalogue exposes millions of crawlable combinations. We decide which attribute filters deserve indexable, keyword-rich URLs (often brand, material, a key spec) and canonicalise or block the rest, in the core settings or with an extension such as Amasty Improved Layered Navigation, Mirasvit or Mageworx configured correctly.

Canonicals, URL rewrites and category paths

‘Use Canonical Link Meta Tag for Categories/Products’ is off by default in many installs. ‘Use Categories Path for Product URLs’ creates one product under five category paths. Imports regenerate URL rewrites and leave thousands of 404s. We set the right canonical strategy, flatten product URLs where it makes sense, clean the url_rewrite table and build redirect maps that survive the next catalogue import.

Configurable vs simple products

Simple products assigned to a configurable are often visible individually, competing with the parent and showing out-of-stock variants in Google. We set visibility rules, canonicalise children to the parent, make sure the parent exposes price range, availability and GTINs in Product and Offer schema, and keep Merchant Center feeds consistent with the page.

Multi-website, multi-store, multi-language

One Magento instance can serve ten countries through websites, stores and store views. Wrong setup means hreflang pointing to the wrong store view, default store duplicating every URL, or ___store= parameters indexed everywhere. We design the URL structure (ccTLD, subfolder or subdomain), hreflang output and currency handling so each market ranks on its own, as we do for brands across the US, UK and EU.

Performance: FPC, Varnish and JavaScript

Magento 2 without properly configured full page cache, Varnish or Fastly and production mode is slow; with heavy RequireJS bundles and third-party JS it stays slow even cached. We tune the cache layer, image optimisation (WebP via Fastly IO or an extension), critical CSS, deferred JS and Hyvä or optimised Luma themes to pass Core Web Vitals on category and product pages.

Indexers, cron and crawl budget

Stale indexers, broken cron and flat catalogue settings cause empty categories, wrong prices and slow category pages that Googlebot abandons. We monitor indexer and cron health as part of SEO, because for a large catalogue crawl efficiency is the difference between new products ranking in days or months.

Millions of duplicate URLs from filters, sorting and pagination

Layered navigation parameters, ?product_list_order=, ?product_list_limit=, ?product_list_mode= and ?p= pagination combine into an almost infinite URL space. We keep pagination indexable and self-canonical so deep products get crawled, canonicalise sorting and limit parameters to the clean category URL, block pure noise in robots.txt and let only the filter combinations with proven demand become indexable pages with their own title, H1 and copy.

Category path in product URLs and multiple canonical candidates

With ‘Use Categories Path for Product URLs’ enabled, a product in four categories exists on four URLs plus the root one. We usually disable the category path, set a single canonical, 301 legacy paths and rebuild internal links so authority consolidates on one URL per product. Where business rules require category paths, canonicals and breadcrumbs are configured so Google still sees one version.

Thin and duplicate product content from supplier feeds

Large catalogues often import manufacturer descriptions shared with every competitor. We prioritise by revenue: unique content for the top products and all category pages, templated but differentiated content built from attributes for the long tail, and FAQ and specification blocks that also serve AI assistants answering buying questions.

Slow category and product pages

Typical causes: developer mode left on, FPC disabled or constantly invalidated, no Varnish, uncompressed images, dozens of third-party scripts, and heavy Luma themes. We measure with CrUX and PageSpeed Insights and fix in order of impact. Many stores we work with move to Hyvä or a tuned Luma theme and reach green Core Web Vitals on category templates within the first quarter.

Magento 1 to Magento 2 and platform migrations

Migrations are where stores lose 30 to 60 percent of organic traffic. Magento 2 changes URL keys, category structures and media paths, and a default import leaves thousands of 404s. We prepare URL maps and redirect rules, check template parity (titles, schema, internal links), verify hreflang per store view and monitor indexation daily after launch. The same applies for moves to Shopify Plus, BigCommerce or commercetools when Magento no longer fits; see our ecommerce SEO services.

B2B catalogues and shared catalogs

Adobe Commerce B2B features such as shared catalogs, company accounts and customer-specific pricing often hide products behind login or show ‘price on request’. We design which parts of the catalogue stay public and indexable, how to expose availability and price ranges in schema, and how to build content for RFQ-driven buyers who research in Google and ChatGPT before contacting sales.

Visibility in ChatGPT, Gemini and AI Overviews

Buyers increasingly ask AI assistants which product or supplier to choose. Those systems rely on clean product data, consistent entity information, structured specification and FAQ content and third-party mentions. Our Magento work includes structured data, comparison content and brand citations so your store is the one being recommended. Read more about AI SEO.

Is Magento good for SEO?

Magento 2 and Adobe Commerce are among the most SEO-capable platforms when configured properly: full control over URLs, canonicals, robots, templates, schema and server stack. The risk is that default settings and careless extensions create massive duplication and slow pages. A Magento SEO specialist turns that control into rankings instead of index bloat.

How much do Magento SEO services cost?

We quote after the free audit, because the price depends on catalogue size, number of store views and how much technical work the store needs. Starter engagements for single-store shops are smaller in scope than Enterprise programmes for multi-website Adobe Commerce installations. There is no 12-month contract.

Do you work with Adobe Commerce as well as open source Magento?

Yes. We work with Magento Open Source, Adobe Commerce (on-premise and Cloud) and Adobe Commerce B2B. The SEO logic is the same; Cloud projects add Fastly configuration and deployment workflows that we take into account.

Do you implement changes or only send recommendations?

Both, depending on your setup. For stores with an in-house or agency development team we write precise tickets with configuration paths, code references and acceptance criteria, then verify every deployment. Where there is no developer, we implement on staging with our own Magento developers and deploy with you.

How long does Magento SEO take to show results?

Configuration fixes (canonicals, navigation, speed) usually show within 4 to 10 weeks as Google recrawls a large catalogue. Category and filter rankings and revenue growth typically build over 3 to 6 months; competitive national terms can take 6 to 12. Monthly reports show progress in clicks and revenue, not just positions.

Can you help with a Magento 1 to Magento 2 migration?

Yes. We prepare the URL map and redirect rules, review the new theme for template parity, validate hreflang and schema per store view, and monitor indexation daily after go-live. Migration support is included in the Enterprise package and available as a standalone project.