eCommerce SEO · Technical catalogues

eCommerce SEO for products buyers have to find, understand and trust.

Not backlinks and blog posts. The architecture, content and technical decisions that let a large technical catalogue rank for the searches that end in orders.

Start with the Multi-Channel Audit Talk about SEO
  • Category and product architecture
  • Make, model and application demand
  • Variants and discontinued lines handled

Where technical catalogues lose

The site is organised for the warehouse. The buyer searches by machine.

A parts site lists a filter under Filters, Engine, Brand. The buyer searches for the model number of the tractor it fits. No page on the site is about that tractor, so a competitor with a compatibility page wins the click. Multiply that by every model, every application and every part number and the gap is enormous.

Then the technical problems. Faceted navigation generating thousands of unnecessary crawlable URLs that duplicate and dilute the pages that matter. Product variants each on their own page, or all collapsed onto one that ranks for none of them. Discontinued products returning 404s, taking their rankings and their replacement sales with them. Out of stock pages removed and re-added every season. Category pages that say nothing where a buyer needed a sentence.

None of this is fixed by link building. It is fixed by understanding how buyers search for what you sell and building the site so that each distinct buyer intent has a genuinely useful page, that Google can crawl efficiently, and that the buyer can trust when they land. That is eCommerce SEO consultancy for a technical catalogue, most often on Shopify or WooCommerce.

What the work covers

The parts of SEO that matter for a technical catalogue.

  1. 01

    Architecture

    Category and product structure

    Categories built from demand, not from the ERP. Compatibility and application pages where buyers search by machine rather than by part.

  2. 02

    Demand

    Make, model and application

    The long tail of fitment and application searches mapped, prioritised by value, and given pages that answer them.

  3. 03

    Technical

    Facets, variants and indexing

    Faceted navigation controlled so it stops producing unnecessary URLs, variants consolidated correctly, indexable URLs limited to pages that serve a search, structured data for products and offers.

  4. 04

    Lifecycle

    Discontinued and out of stock

    Superseded products handled case by case: redirected where there is a real replacement, kept where the page still serves demand, retired where it does not. Out of stock and seasonal lines handled without losing rankings.

  5. 05

    Content

    Category and product content

    Content where it helps the buyer and clarifies the intent: specifications, compatibility, application, selection. Not a block of prose on every category for its own sake.

  6. 06

    Measurement

    Organic revenue

    Rankings are a leading indicator. The measure is organic revenue by category, including the phone orders it produces.

    →

Generic versus technical

Generic eCommerce SEO versus SEO for a technical catalogue.

Generic eCommerce SEOArlieo
Keyword focus Category head terms Make, model, part number, application and specification
Content Blog posts Compatibility pages, application pages, category copy that answers real questions
Facets Left to the platform Controlled with rules, canonicals and indexing decisions
Discontinued products Deleted Assessed: redirected, kept or retired depending on replacement, demand and links
Links Bought or begged Earned from supplier, dealer and trade relationships, when they are genuinely useful
Measure Traffic Organic revenue by category

How it runs

Demand first. Then the site. Then the content.

  1. 01

    Map the demand.

    How buyers search for your products, by make, model, application and part, prioritised by value.

  2. 02

    Audit the architecture.

    Categories, facets, variants, lifecycle handling and crawl, against what the demand needs.

  3. 03

    Fix the technical layer.

    Indexing, canonicals, redirects, structured data, speed. Unglamorous, decisive.

  4. 04

    Build the pages.

    Compatibility, application and category pages that do not exist yet, and copy for the ones that do.

  5. 05

    Measure revenue.

    Organic revenue by category, including phone orders, reported monthly.

Questions about eCommerce SEO.

Do we need blog content?

Rarely as a priority. For a technical catalogue the demand is in product, category, compatibility and application pages. Articles help when they answer a genuine buyer question and link to the products that solve it.

What do we do with discontinued products?

It depends on the product. Where there is a genuine replacement, redirect to it. Where the old page still has demand, links or usefulness, it may be better kept with a clear message. Where none of that applies, retiring it is fine. Deleting everything by default throws away rankings and the sale of the replacement part.

Our platform generates thousands of filter URLs. Is that bad?

Often. It creates duplicate and near duplicate pages that compete with the ones that should rank, and makes crawling less efficient. Facets need rules: which combinations serve a real search and should be indexable, which are canonicalised to a parent, which are kept out altogether.

How long before it works?

Technical fixes and architecture changes can move within a few months. New compatibility and application pages build over six to twelve. The audit sets the order so the fastest returns come first.

Related.

Find out which searches your catalogue is missing.

Architecture, demand, technical health and content reviewed together, with a written report on what to fix first.

Start with the Multi-Channel Audit Talk about SEO