Service 02 · E-commerce
Ecommerce Technical SEO for Large Catalogues
Faceted navigation, crawl budget and product templates engineered so Googlebot finds, renders and indexes the pages that sell.
On a catalogue of thousands of SKUs, rankings are rarely won with keywords alone. They are won or lost in URL generation, facet rules and template logic. As ecommerce SEO consultants with engineering roots, we fix the systems that create millions of crawlable URLs — so search engines spend their time on categories and products, not filter permutations.
catalogue-scope.yml
FACETS
indexable vs crawlable rules per attribute
CRAWL
Googlebot hits on products vs parameters
TEMPLATES
category, product, variant, out-of-stock
LINKS
click depth to every money page
SCHEMA
Product, Offer & merchant listing data
Sound familiar?
Signs your catalogue is fighting Google.
Search Console lists hundreds of thousands of URLs as “Crawled – currently not indexed”, most of them filter combinations.
New products take weeks to appear in search, while sorted and filtered URLs are crawled every day.
Category pages compete with their own filtered versions for the same queries.
Discontinued products return soft 404s, or every one of them redirects to the homepage.
Each size and colour variant has its own thin, near-duplicate URL.
Merchant listings show the wrong price or availability — or don’t appear at all.
The difference
Why ecommerce SEO is an engineering problem.
Ecommerce technical SEO is the discipline of controlling how a catalogue generates, exposes and describes its URLs — so search engines index the pages that make money and ignore the rest.
A store with 20,000 products and eight filterable attributes can generate tens of millions of unique URLs. No content strategy survives that. Googlebot’s crawl capacity for your site is finite: if it is spent on ?color=red&size=m&sort=price_asc, it is not spent discovering this week’s new arrivals or recrawling price changes. The fix lives in routing rules, template conditionals and platform configuration — not in a spreadsheet of meta descriptions.
We work at that level: deciding which facets deserve an indexable landing page, which should be crawlable but not indexed, and which should never be requested at all — then specifying the exact implementation for your platform. Not sure where the biggest leaks are? Start with a technical SEO audit. If product templates are slow on mobile, pair this with Core Web Vitals optimization, and to make products eligible for merchant listings, see schema markup.
What’s included
Eight systems that decide what your catalogue ranks for.
Scoped to your platform, your attribute model and the categories that drive revenue.
Faceted navigation SEO
An index / crawl / block ruleset for every facet and combination, enforced with canonicals, noindex, robots.txt and link markup.
Parameter & URL hygiene
Sort, view, session and tracking parameters normalised — one consistent, ordered, lower-case URL per page state.
Crawl budget optimization
Log analysis by template showing where Googlebot’s requests go, then reclaiming the waste for products and categories.
Inventory discovery
XML sitemaps split by type with honest lastmod dates, so new and updated products are found in hours, not weeks.
Category templates
Pagination that stays crawlable, slots for unique intro copy, and rules that keep thin or empty categories out of the index.
Product & variant templates
Variant consolidation, canonical rules and out-of-stock and discontinued handling that preserves link equity.
Architecture & internal linking
Money pages within three clicks of the homepage, supported by breadcrumbs, related categories and facet landing links.
Product schema & merchant data
Product, Offer, shipping and returns markup generated from the same data as the visible page and your product feed.
How it works
From crawl waste to a controlled catalogue.
Deliverables
Facet & parameter ruleset (YAML or sheet)
Category, product & variant template specs
Out-of-stock & discontinuation policy
Sitemap & internal-linking architecture
Dev tickets with acceptance criteria
Post-release crawl & index monitoring
Map the catalogue
We model your attribute taxonomy, URL patterns and platform constraints — Shopify, WooCommerce, Magento / Adobe Commerce or headless — and pull 30–90 days of server logs and Search Console data.
Measure crawl & index
Every URL is classified by template and facet depth, so we can see exactly how much of Googlebot’s activity goes to products versus parameters — and what ends up indexed as a result.
Design the rules
Facet by facet, we decide what earns an indexable landing page based on search demand and inventory depth, and specify canonical, robots and linking behaviour for everything else.
Ship & verify
Tickets go to your developers or platform agency. We review the implementation on staging, then monitor crawl distribution and indexation after release.
What changes
Googlebot’s attention moves to the categories and products you actually sell, new inventory is indexed faster, and your team has a written ruleset that stops the problem returning with the next filter.
Sample output
A facet ruleset, not a guess per URL.
Every attribute gets an explicit rule and a reason. This file becomes the spec your developers and merchandisers work from.
facet-rules.yml · illustrative
FACET
EXAMPLE URL
RULE
REASON
color
/dresses/red/
Index
Proven search demand; static path, self-canonical on top combinations.
size
/dresses/?size=12
Crawl · noindex
Useful to shoppers, no search demand; links still followed.
price range
/dresses/?price=50-100
Block
Infinite ranges; disallowed in robots.txt, no crawlable links.
sort
/dresses/?sort=price_asc
Canonical → base
Same products, different order; canonical to /dresses/.
brand + category
/dresses/brand-x/
Index · landing
High-intent combination; own template, copy and breadcrumb.
8 facets · 5 shown
→ enforced in routing layer
Platforms
Shopify, WooCommerce, Magento & headless.
Every platform constrains what can be changed. Our recommendations are specified for your stack, theme and extensions — not copied from a generic checklist.
SHOPIFY
Shopify technical SEO
Working within Liquid and fixed URL structures: /collections/…/products/ duplication, tag-based filtering, variant parameters, app-injected scripts and robots.txt.liquid.
WOOCOMMERCE
WooCommerce technical SEO
Taming attribute archives, filter-plugin parameters, pagination and variation URLs — plus hosting and caching that hold up under crawl load.
MAGENTO
Magento / Adobe Commerce
Layered navigation, store views and hreflang, URL rewrites, category-path product URLs and full-page cache behaviour on multi-store catalogues.
HEADLESS
Headless commerce
Next.js, Nuxt or Hydrogen on a commerce API: server rendering, routing-level facet rules and links that exist in the HTML. See JavaScript SEO.
Who it’s for
Built for catalogues at scale.
LARGE CATALOGUES
Thousands of SKUs, deep filters
Retailers whose faceted navigation has grown faster than anyone’s ability to control what Google crawls.
REPLATFORMING
Moving between platforms
Shopify to headless, Magento to Adobe Commerce, WooCommerce to anything — get URL and facet rules right before launch. See website migration SEO.
IN-HOUSE TEAMS
Dev and SEO need one spec
Teams of engineers and marketers who need a single written ruleset both sides can build, test and maintain.
Investment
Fixed scope, quoted upfront.
Pricing depends on catalogue size, platform, number of facets and log access. After a 30-minute scoping call you’ll receive a fixed quote — no hourly billing, no surprises.
Related services
Often paired with ecommerce SEO.
Schema Markup
Product, Offer and merchant listing markup generated from your catalogue data.
Explore schema markup →
Technical SEO Audit
A full-stack diagnosis when catalogue issues are only part of the picture.
Explore the audit →
Website Migration SEO
When you’re replatforming and need URL, facet and redirect rules locked down.
Explore migrations →
FAQ
Ecommerce technical SEO questions.
Anything else? Ask us directly — we reply within two working days.
Should faceted navigation pages be indexed?
Some should. A facet value earns an indexable URL when there is real search demand for it (for example “red midi dresses”) and enough products to make a useful page. Those get a clean static path, a self-referencing canonical and internal links. Everything else stays crawlable but noindexed, is canonicalised to its parent, or is blocked entirely — decided per facet, not per URL.
What is crawl budget, and does it matter for my store?
Crawl budget is the number of URLs Googlebot is willing and able to fetch from your site in a given period. For a site with a few hundred pages it rarely matters. For catalogues with tens of thousands of products and filterable attributes, it often decides how quickly new products, price changes and stock updates are reflected in search.
How should we handle out-of-stock and discontinued products?
Temporarily out-of-stock products should stay live with a 200 status, accurate availability in Product schema and links to alternatives. Permanently discontinued products should 301 to the closest equivalent product or category when one exists, or return 404/410 when none does. Mass-redirecting them to the homepage is treated by Google as a soft 404.
Should product variants have their own URLs?
Only when a variant has distinct search demand — a colour people search for by name, for example. Otherwise variants are best consolidated on one product URL with selectable options. Where separate variant URLs exist, they need clear canonical rules and ProductGroup markup that describes how the variants relate.
Do you work with Shopify, WooCommerce and Magento?
Yes — plus Adobe Commerce, BigCommerce and headless builds on Next.js, Nuxt or Hydrogen. Each platform limits what can be changed (Shopify’s fixed URL structure, for instance), so every recommendation is specified for your platform, theme and app or extension stack.
How long until we see results?
Crawl distribution usually shifts within weeks of new rules going live, visible in server logs and Search Console crawl stats. Indexation and ranking changes follow over one to three months, depending on catalogue size and how often Googlebot revisits. We set up before-and-after measurement so the impact is visible, not assumed.
Next step
Put your catalogue back in control.
Send your store URL and platform. You’ll get a scoped proposal with a fixed price within a few days.