Ecommerce Web Design · Our Approach

SEO Built In From the Start

Most stores get designed, launched, and then handed to SEO to rescue. We build in the other order: research before structure, structure before design, so search performance is a property of the store rather than a repair to it.

Updated: July 2026
Written by: Andrew Odgers, Managing Director
Reading time: 8 minutes
The short answer

Building with SEO in means changing the sequence: keyword research before the sitemap, category structure drawn from real search demand, URL patterns and template markup specified in the build, internal linking designed as a system, speed as a budget the build must meet, content planned with the catalogue, and, for replacements, a redirect map protecting every ranking the old site earned. It wins on arithmetic, template decisions multiply across every product, and architecture, skeletons are expensive to change after launch. Built-in never creates the debt that retrofits spend years paying.

The method

Research first, structure from evidence, templates that multiply

The whole method is a change of sequence, and it starts before anything is designed. Research first: we map what customers actually search for, the product-type terms carrying real volume, the comparisons people weigh, the questions they ask on the way to buying, and how that demand clusters, alongside an honest look at who already ranks and with what structures. Most projects skip this phase entirely, which is why most category structures describe the warehouse instead of the customer, the core failure named in how web design affects ecommerce SEO. Structure from evidence: the research becomes the information architecture, which categories exist, how they nest, which keyword each page targets, what content the store needs beyond products, and only then does design begin, expressing the structure rather than improvising one, with each category built to do its dual job per category pages that rank and sell. Templates that multiply correctly: during the build we specify the layer where one decision repeats across the whole catalogue, semantic markup, title and heading patterns, product structured data for the rich results covered in product pages that convert, breadcrumbs, canonical rules keeping filter combinations out of the index, sitemaps, and internal linking modules that construct themselves for every new product. Get this layer right once and a thousand pages inherit it; get it wrong and a thousand pages need correcting.

PHASE 01

Before design

Keyword research, competitor structures, demand clusters: the evidence the architecture is drawn from, not decorated with.

PHASE 02

In the build

Template markup, structured data, linking systems, canonical rules and a speed budget the launch must meet.

PHASE 03

At launch & after

Redirect maps protecting earned rankings, measurement wired from day one, and the ongoing work that compounds it.

The protections

Speed as a budget, redirects as insurance, and the honest promise

Two disciplines complete the method, and both are insurance against the industry's most expensive habits. Speed is a budget, not an aspiration: image handling, script discipline, theme weight and hosting are specified so the store launches fast on real phones, rather than launching heavy and hoping optimisation catches up, because the causes of slowness are all build decisions and the bill lands on both sales and rankings, per why speed affects sales and rankings. Redirects are mapped before launch, not after the traffic drops: when a build replaces an existing store, we inventory every old URL, note what it ranks for and earns, and map it to its successor, so search engines transfer years of accumulated authority to the new structure. Skipping this remains the single most expensive mistake in ecommerce redesigns, rankings burned in a weekend that took years to earn, and it is entirely preventable: routine work when planned, an emergency when remembered late.

What built-in honestly buys, and what it doesn't

The honest promise matters, because this page is our pitch and pitches earn scepticism. Built-in SEO does not mean the store ranks the week it launches, rankings take months to build as engines crawl, index and evaluate, and competitive terms still need the ongoing work, content, authority, refinement, that follows launch, which is exactly the work our monthly programme exists to do. What built-in buys is the start line: a store with structure aligned to demand, templates multiplying correctly, speed on budget and history protected starts the race where retrofitted stores spend their first year trying to arrive. That difference compounds every month afterwards, and it is why the question to ask any designer quoting for your store is simple: what SEO work happens before the design, and can you show it in the plan? A blank look answers the question, and the rest of the vetting kit lives in how to choose an ecommerce web design agency.

SEO done properly, from £350 a month

Built to be found.
From the first sketch.

Research before structure, structure before design, templates that multiply correctly, redirects that protect history, and the ongoing programme that compounds it, that is how we build stores.

Everything included in your plan:

Google Maps optimisation Full website management Local SEO campaign AI optimisation (GEO) Facebook, Instagram and LinkedIn Quarterly audits Monthly reporting
£350 per month

One clear retainer. No setup fee.

Frequently asked

SEO-first builds

What does building an ecommerce website with SEO built in actually mean?
It means the sequence changes: keyword research happens before the sitemap, not after the launch. The category structure is drawn from what customers actually search; URL patterns, template markup and structured data are specified in the build; internal linking is designed as a template system; speed is a budget the build must meet rather than a problem to diagnose later; content is planned alongside the catalogue; and, for replacements, redirect mapping protects every ranking the old site earned. SEO stops being a service applied to the website and becomes a property of it.
Why is building SEO in better than adding it later?
Arithmetic and architecture. Arithmetic: template-level decisions repeat across every product page, so getting them right once at design time costs a fraction of correcting them across a live catalogue. Architecture: the highest-value SEO assets, category structure, URL scheme, site hierarchy, are the skeleton of the store, and changing a skeleton after launch means redirect projects with real risk to existing rankings, per how web design affects ecommerce SEO. Retrofits recover stores partially and expensively; built-in simply never creates the debt.
What happens before design in an SEO-first ecommerce build?
Research that most projects skip. Keyword research maps what customers search for, the product-type terms with real volume, the comparisons, the questions, and how demand clusters. Competitor analysis shows who ranks and with what structures. From that evidence comes the information architecture: which categories exist, how they nest, what each page targets, and what content the store needs beyond products. The design then expresses the research, which is precisely backwards from the usual workflow, and precisely why it works.
What SEO work happens during the build itself?
The template layer, where one decision multiplies across the catalogue: clean semantic markup, title and heading patterns, product structured data for rich results, breadcrumbs, canonical rules that keep filter combinations out of the index, XML sitemaps, and internal linking modules, related products, subcategory links, editorial cross-links, that construct themselves for every new page. Plus the speed budget: image handling, script discipline and hosting specified so the store launches fast, per why speed affects sales and rankings.
How are rankings protected when replacing an existing store?
With a redirect map, built before launch, not after the traffic drops. Every URL on the old site is inventoried, its ranking and traffic value noted, and mapped to its equivalent on the new structure, so search engines transfer the old pages' earned authority to their successors. Launch without this and years of rankings burn in a weekend, which remains the single most expensive mistake in ecommerce redesigns, and the most preventable: the map is routine work when planned, and an emergency when remembered late.
Does SEO built in mean the store ranks immediately at launch?
No, and anyone promising that deserves suspicion. Built-in SEO means the store launches without handicaps: structure aligned to demand, templates that multiply correctly, speed on budget, redirects protecting history. Rankings still take months to build as search engines crawl, index and evaluate, and competitive terms still require the ongoing work, content, authority, refinement, that follows launch. The honest claim is different and better: a store built this way starts the race at the start line, while a retrofit project spends its first year getting there.