Service 02
Ecommerce SEO
Search optimisation built for online stores: category and product page architecture, technical performance, content strategy and conversion-focused visibility. Grounded in 14 years of hands-on work growing ecommerce projects in the UK and European markets.
Experience
14 years, hands-on
Markets
UK and Europe
Format and investment
Scoped on the first call
When this is the right move
A big catalogue is not the same as a visible one
Stores rarely lose to better products. They lose to better architecture: the way categories, filters and product pages are built decides what search engines can even see.
- Thousands of products, a handful of rankings — and nobody can say which pages carry the revenue.
- Category pages that never rank while blog posts quietly outperform the shop.
- Filters and variants multiply URLs until the crawler gives up before it reaches what matters.
- Traffic grows, revenue does not — visibility landing on pages that cannot convert.
Scope
What the work actually covers
The four areas from the service itself: architecture, technical performance, content, conversion. Each one read against your catalogue, not a checklist.
Category & product architecture
- How categories map to real demand
- Which filters deserve to be pages
- Product page templates that rank and sell
- Internal linking that moves authority to money pages
Technical performance
- Crawl behaviour across the catalogue
- Speed on the templates that convert
- Structured data for products and offers
- Index bloat from variants and parameters
Content & conversion
- Content strategy tied to buying intent
- Category copy that helps rather than pads
- Conversion-focused visibility — not traffic for its own sake
Fit
Who this is for
A good fit
- Online stores in the UK and European markets
- Catalogues large enough that architecture decides visibility
- Teams that can implement, with direction
Not a good fit
- Single-product landing pages — that is SEO Audit & Strategy territory
- Anyone expecting traffic without touching the site
- Stores unwilling to change how categories are built
Questions
Before you get in touch
Which platforms do you work with?
The work is architectural, so it applies across platforms — the constraints differ, the logic does not. Platform specifics are assessed in the first conversation.
We already publish content. Why does the shop not rank?
Because content and catalogue are different systems. A store ranks through its category and product architecture; articles can support it but cannot replace it. If your blog outranks your shop, that is usually the diagnosis, not the achievement.
Is this a one-off project or ongoing?
It depends on the size of the catalogue and how much of the problem is architectural. Both the fee and the timeline are agreed before the work starts — no open-ended retainers, no surprise invoices.
How much does it cost?
It depends on the size of the catalogue and how much of the problem is architectural. Both the fee and the timeline are agreed before the work starts — no open-ended retainers, no surprise invoices.
Where this leads
Start with the catalogue
A conversation first, to check the fit. If this is not what you need, I will say so.
The vocabulary behind this work: PDP, PLP, faceted navigation, product feeds, organic revenue.
When it is not yet clear whether architecture is the constraint.
Category authority decides whether new products ever rank.
Migrations and structured data behind the store.