Ecommerce SEO
The closing guide of the ecommerce silo is the whole discipline as a working checklist — the launch items, the template layer, the quarterly rhythm and the growth programme, each line linking its full guide. Print it, run it top to bottom on a new store, or use it as the gap-finder on an existing one; the ordering is the leverage ordering the case study validated.
Foundation (once, at launch or adoption)
- ☐ Structure: demand-driven taxonomy, shallow tree, one primary category per product, URL patterns decided forever.
- ☐ Research → map: the three demand pools assigned to landing types (category/product/guide) before pages exist.
- ☐ Facet policy: the three tiers (block/canonicalise/promote) implemented before parameters multiply.
- ☐ Pagination: self-canonicals, crawlable paths, done.
- ☐ Staging locked, deployment indexability assertions live.
- ☐ Instrumentation: Search Console (domain property, sitemap segments by type), analytics with revenue attribution, Merchant Center connected.
The template layer (once per template, multiplied by the catalogue)
- ☐ Categories as real pages: intro + grid + below-grid buying content on the money twelve.
- ☐ Product template: title pattern, variant handling, trust furniture, related-products logic.
- ☐ Product schema from live data, validated per state (in-stock/out/sale/variant).
- ☐ Review engine firing and rendering indexably; Q&A stream seeded from support archives.
- ☐ Description triage: rewrites on the revenue head, honest templates on the middle, structure on the tail.
- ☐ Speed: srcset thumbnails, app-stack audited, LCP images eager, field data green on money templates.
- ☐ Routing: breadcrumbs marked up, nav allocated to money, guide↔category↔product links flowing.
- ☐ Meta system: templates on the tail, written copy on the impression head.
- ☐ Feed: optimised titles, complete identifiers, free listings live, page↔markup↔feed consistent.
The standing rhythms
- ☐ Quarterly: the store technical audit (index shape, crawl diff, consistency triangle, speed) + the CTR mine.
- ☐ Continuously: the stock-URL policy automated; seasonal calendar on SEO lead times, permanent URLs reused.
- ☐ Annually: content verdicts on the guide layer, link profile review, catalogue-sync check on comparisons and guides.
The growth programme (permanent)
- ☐ Content-to-cash architecture: buying guides per money category, comparisons on shortlist demand, every piece routed.
- ☐ The link engine per the doctrine: the annual data asset, reference layer, seasonal pitch cycles — earned broad, routed narrow.
- ☐ Conversion floor maintained: the funnel audited, evidence-backed fixes shipped, revenue-per-visitor watched.
- ☐ Channel strategy deliberate: marketplace/store split owned, local layer where shops exist, Amazon/Etsy run on their own physics.
- ☐ The ledger: organic revenue by page type, category positions on the mapped set, referring domains, quarterly against last year.
Frequently asked questions
We can't do all this. What's the minimum that moves revenue?
The case-study core: facets contained, the twelve money categories made real, schema rendering stars, the review engine on, one data asset earning links yearly — items 3, 7, 9, 10 and 20. That subset built the +310% result; everything else compounds it.
In what order for an existing, messy store?
Audit first (item 16 run once, hard), then the leverage ordering: whatever's binary-broken (indexing blocks, facet floods), then templates by revenue, then the growth programme — the emergencies-cheap-wins-structural-programmes queue with a revenue column.
And when the checklist is green?
Then the contest is the permanent one this whole library keeps arriving at: coverage competitors can't match and authority they can't copy — content on cadence, links accumulating, the flywheel the checklist exists to serve (we push the second wheel).