E-commerce SEO begins with a map of customer tasks
E-commerce SEO is not publishing hundreds of paragraphs for every product. Separate the search tasks first: buying a category, choosing by a property, comparing models, finding a compatible accessory or understanding delivery. Each group needs its own page type and an obvious route to purchase.
Query wording can be collected in an authorised Wordstat account with region, period and operators defined, then checked against search suggestions, buyer questions and the store’s own data. Numbers with no date or region do not identify the important category. For a new page, the link between a query, actual stock, margin and purchase intent matters more.
A category helps choose; a product page proves the product
A category should explain what is available, how to choose and how to narrow the range. A product page confirms a specific model: specifications, package contents, dimensions, compatibility, price, stock, delivery and real images. Copying category text into every product page removes the difference between products.
When a product is temporarily unavailable, the treatment depends on demand and available replacements. Do not silently delete a page that has visits and viable alternatives: explain the status and offer a close option. If a model is permanently gone with no replacement, use an agreed 404 or redirect rather than a blank 200 page.
| Page | Main task | What to prove |
|---|---|---|
| Category | Help choose a product type | Range, filters and selection criteria |
| Product page | Prove a specific model | Specification, price, stock and package |
| Guide | Answer a pre-purchase question | Useful evidence and route to products |
Filters help until they create endless versions of the same catalogue
Filter combinations can serve customers, but search needs only stable landing pages with stock and a clear intent. Random sort orders, empty combinations and thousands of near-identical URLs consume crawl resources and dilute the main pages. Before opening a combination to search, define who needs it and how it differs from the parent category.
The technical implementation must align internal links, canonicals, sitemaps, parameters and empty-result responses. A single meta tag does not solve a navigation system that exposes thousands of links. Fix URL generation and navigation first, then confirm that the sitemap contains only chosen pages.
- Index only landings with stock and distinct demand.
- Keep sorts, empty results and technical parameters out of the sitemap.
- Check canonicals for filters and pagination.
- Give a visitor a clear route when a filter has no products.
Check the store as a buyer and as a crawler
Choose control URLs for each page group: main category, filter, in-stock product, unavailable product and pagination. Check status code, main content without an account, canonical, links, product structured data and route to the basket. Confirm that price and specifications do not disappear after JavaScript runs.
Do not promise ranking growth from one template change. Confirm publication quality and availability first, then watch impressions, clicks, queries, basket additions and orders. This separates a technical fault from weak demand or limited inventory.
Release changes in small groups and retain an unchanged control group when the catalogue allows it. That makes it easier to separate the effect of structure from seasonality, price or stock. Record the publish date, URL set and decision for each group: extend, revise or stop the hypothesis. Avoid bundling navigation, pricing, advertising and catalogue changes in one release; then the observed result still has a useful cause. This discipline also lets a team catch a publication error quickly and return to a working catalogue state.
Questions
Key questions
Does every category need unique copy?
Only when it helps choose a product or answers a real question. Template copy for keywords alone has little value.
Should every filter be indexable?
No. Open only stable combinations with stock and a distinct customer intent.
Can every product use one page template?
A shared template is useful, but the data and images must prove the specific model.
