Magento SEO Services

Layered navigation generates URLs faster than anything else

Magento's filtering is powerful and, left at defaults, close to unbounded. Ten filter attributes across a category produce more crawlable combinations than the catalogue has products — frequently by orders of magnitude.

The consequence is a crawler that never reaches your actual products because it is working through colour-and-size permutations of one category. On a large store this is the single largest SEO problem, and it is invisible until you look at logs or a full crawl.

The fix is a decision per attribute rather than a global switch. Some filters match real demand and deserve indexable pages; most do not and should be canonicalised or blocked. Getting that wrong in either direction is costly — block too much and you lose pages that were ranking.

Crawl budget is a real constraint here

On a 200-page site crawl budget is a theoretical concern. On a 200,000-URL Magento store it is the thing deciding whether new products get indexed this month.

Log file analysis is not optional at this scale. It shows where crawlers actually spend their time, which is routinely somewhere nobody expected — internal search URLs, sorted variations, or a filter combination generating infinite pagination.

Category pages carry the commercial traffic

As with any large retailer, category-level queries hold most of the volume. Magento gives you more control than Shopify over category content and structure, which is an advantage largely left unused.

What works: genuine buying guidance, sensible category hierarchy that matches how customers think rather than how the ERP is organised, and internal linking between related categories. Magento's ability to have a product in several categories is useful and needs canonical decisions to avoid competing with itself.

Performance, which Magento does not give away free

Magento is heavy. Full page cache, Varnish, correctly configured indexers and a sensible extension load are the difference between a fast store and one where Core Web Vitals never pass.

Extensions are the usual culprit. Stores accumulate them, several inject JavaScript on every page, and few are removed when abandoned. An extension audit is often the fastest performance work available.

Magento 1, and the migration question

Magento 1 has been unsupported since 2020. If you are still on it the security case for moving is stronger than the SEO case — but the migration is where rankings get lost, so the two arrive together.

Same rule as any replatform: every URL that earned traffic or links needs a mapped 301 to its specific equivalent, redirects tested on staging, and a crawl comparison before DNS changes. Magento migrations are higher risk simply because there are more URLs to map.

Multi-store and international

Magento's multi-store capability is a genuine advantage and a common source of self-inflicted duplication. One catalogue served across several store views — per country, per brand, per language — produces near-identical pages unless hreflang and canonicals are set deliberately.

The decisions worth making explicitly: whether store views get separate domains, subdomains or subfolders; whether currency and language vary independently; and what happens when a shopper lands on the wrong store view from search. Subfolders are usually the lowest-risk choice for a UK retailer adding a second market, because they inherit the authority the main domain has already built.

B2B catalogues

Adobe Commerce B2B adds customer-specific pricing and catalogues, which interacts badly with SEO if unmanaged. Pages that require login return nothing useful to a crawler, and pages showing different prices to different customers cannot carry honest Offer schema.

The workable pattern is a public layer that ranks — product information, specifications, availability — with pricing and ordering behind authentication. That way the page earns the traffic and the commercial terms stay private.

What we do

• Layered navigation strategy, decided per attribute
• Log file analysis and crawl budget allocation
• Category hierarchy and content
• Canonical strategy for multi-category products
• Multi-store and hreflang configuration
• Extension audit and performance work
• Product and Offer schema at catalogue scale
• Migration planning and URL mapping

What we need from you

Search Console and analytics access, server log access if it can be arranged, and a staging environment. Magento changes are not something to test on a live store, and most serious Magento setups already have staging — if yours does not, that is the first recommendation regardless of SEO.