The Design Decisions That Decide What Your Store Ranks For

Your ecommerce web design gets briefed as a look. You approve a homepage, a palette and a set of product photography. Then the build happens, and your traffic does whatever it was going to do anyway.

Yet the decisions that change what you rank for are made somewhere else entirely. They sit inside templates nobody puts in a pitch deck.

To find out how far apart those two things sit, I looked at what real Shopify collection pages serve to a crawler in their raw HTML, before any JavaScript runs. Most of the readable ones shipped no crawlable link to page two at all. The sample and the method are below.

Their products on page one were all present in the HTML. Only the route to the rest of the catalogue was missing.

I am John Butterworth. Over eleven years in SEO, including a talk at SEO Mastery Summit, I still find that pattern in ecommerce web design three months after a five-figure rebuild.

Nobody chooses it. It arrives with the theme.

Here are the decisions that carry a search consequence, in the order I would make them. Later sections cover how to change them on a live store without losing traffic you have already paid for once.

The Templates Are Where Your Rankings Live

Your store has perhaps six templates and several thousand pages. A category template, a product template, search results and the cart do nearly all of the work.

Each renders hundreds or thousands of URLs. One decision inside a template therefore lands on every page it produces.

In contrast, your homepage is one page. It absorbs most of the design attention in most projects, and it is where your customers are least likely to arrive.

Template quality is measurable, too. Reporting on Online Store 2.0 shows LCP improvements of 18% and CLS halved on modern themes against legacy ones, which is a whole-store gain from one template layer.

What The Grid Cannot Tell A Crawler

Two things read your store. A shopper looks at the rendered page, while a crawler reads the markup.

Those are different artefacts, and the space between them is where damage sits.

My August sample was 30 stores and 21 usable results. Nine could not be read at all. Four returned a 404 on the universal collection route, three rate-limited me, one blocked the request and one failed to resolve.

Those nine sit outside every figure below.

Here is how the 21 readable stores scored, and the shape matters because it splits cleanly into what modern themes have fixed and what they have left alone.

What 21 live Shopify collection pages ship in their raw HTML. Our own crawl, 2nd August 2026.

Two results in that chart matter more than the rest. Every readable store rendered its product links server-side, so the old worry about JavaScript-only grids has largely been fixed by modern themes.

Browse paths had not been fixed. Infinite scroll and Load more buttons fetch products when a person interacts with them, and a crawler never interacts, so the catalogue beyond page one has nothing pointing at it.

This distance between what looks finished and what is readable runs through everything below. Jono Alderson, an independent consultant working on site performance and structured data, puts the general condition bluntly in Majestic's SEO in 2026 series, saying "we have accepted that it's normal for websites to be rubbish."

Alderson is describing a baseline, and a low baseline is an opportunity. It means fixing ordinary build quality is itself a competitive move.

The Order To Work In

Given that, work the templates that repeat before the pages that do not.

Ridge is useful here, because nobody would call it an unpolished store. Its collection page carries a real heading, category copy above the grid and a crawlable route to page two.

Ridge's collection page with our annotations, captured 2nd August 2026.

Nothing on that page reads as a compromise made for search, which is why it is worth copying. Polish and readability are not competing for the same budget.

Theme age also matters more than most owners expect. Stores on themes that have not shipped an update since 2022 are watching rankings slide while peers on modern themes pull ahead, because the newer templates keep absorbing platform improvements the older ones never receive.

That decay happens even when nobody touches the site, which is why an ageing theme is worth auditing before anything visibly breaks. Our guide to choosing a theme that holds up covers what to look for.

Practitioners see it from the other direction too. On r/SEO, u/0_2_Hero argued in a thread that drew 263 comments: "a lot of people still separate SEO and design too much, when in reality the best ranking pages are usually easier to scan, trust, and use."

That same poster describes a ranking gain which came from redesigning a page with three backlinks behind it. One person's account is not evidence on its own, though it matches what we see when a template gets clearer.

That order runs templates first and homepage last.

How To Rebuild Without Losing The Traffic You Already Have

What Breaks On Launch Day

This is the part that keeps store owners awake, and it is what a design brief almost never covers.

The margin for error has narrowed too, which makes an unplanned relaunch dearer than it used to be. Alderson sums up where search now sits:

"You get one shot to prove that your content is relevant, meaningful, good, and performant."

A relaunch loses traffic through its URL, template and link decisions.

Redesigns run without SEO planning can cost between 30% and 70% of organic traffic, because the loss is never one mistake. It is the compound of unmapped URLs, dropped copy and severed internal links, all landing in the same week.

That is the worst case, and it is not what a planned move looks like. Where the work is mapped in advance, redesigns typically cause a 10-25% traffic dip in the first 30 days.

Recovery then takes anywhere from two to eight months, depending on how much of the site moved and how cleanly the old URLs were carried across.

The mechanics are unglamorous. URLs change without being mapped. Headings and body copy get dropped because a new design had no slot for them.

Alongside those, internal links collapse when navigation is simplified. Each of those removes a signal your old pages had earned, and a design review is the wrong place to catch any of them.

Beyond the markup itself, rendering adds a sharper edge that most design reviews never think to check. For ecommerce projects the safest route is to render content in the initial HTML through server-side rendering or prerendering.

Anything left to the browser gets read later, and read less reliably.

Store owners describe the consequences vividly. Posting to r/SEO as u/Comfortable_Cake_443, one documented the view from inside after a handover and a replatform: "within 12 days the organic search traffic went from 7,260 on July 31 to 2,668 on August 12".

His description of the change is the giveaway. "They took down a headless WooCommerce site and put everything on an Ecwid Instant Site."

Preparation is what prevents that. Pre-migration planning is responsible for nearly 60% of migration success, so map every existing URL and template element before the build starts. We set out how to inventory a live store before anything moves.

Reading The Numbers Afterwards

Once it is live, rule out what else moved before you blame your redesign.

Google's broad core update began rolling out on 21st May 2026 and was declared complete on 2nd June, eleven days later. A core update re-weights how the index scores everything, so it promotes and demotes pages whose owners changed nothing. A store that shipped no code that month can still read as a casualty.

A spam update followed on 24th June, which Google described as applying "globally and to all languages". Two named updates therefore landed inside five weeks of each other, and neither had anything to do with your build.

On top of those, search results kept changing shape around the same period. One June 2026 analysis put organic click-through at 0.61% with AI Overviews present against 1.62% without them, which is a fall of roughly two thirds on the same ranking position.

None of that means your relaunch went well. It means a before-and-after read across that period has several candidate causes, and separating them takes more than one chart.

Reversing design decisions on weak evidence is how good work gets thrown away. Line your traffic up against that update timeline first, and against the metrics worth watching.

Your Category Pages Are Doing The Ranking

Give The Page Something To Read

A category search lands on your collection page, so it answers buyer intent before any product template does. Yet no ecommerce web design brief I have been sent carries a line for what that page should say.

This is also where the remaining clicks land, and there are fewer of them to go round. Organic SERP click share fell 11-23 percentage points across verticals in the twelve months to January 2026, which makes the pages that still earn a visit worth more attention than they used to be.

In the same crawl we ran, 13 of the 21 stores carried no collection-level intro copy above their product grid.

It happens because collection templates render products from the catalogue and nothing else. Unless somebody deliberately adds category-level text, your page ships with no words of its own.

Three of the 21 went further and served no h1 at all in raw HTML. Rothy's, Death Wish Coffee and Loop Earplugs each show a category name on screen as styled text, with no heading markup behind it.

Finisterre is the case that stuck with me. Here is a brand built on story and provenance, whose collection page has a heading and server-rendered products but no category copy.

Everything that brand has to say is absent from a page its category searches would land on. It is a design decision nobody made deliberately.

A collection page structured so a shopper and a crawler can both use it.

None of that structure is hard to build, and no technical obstacle explains the omission. Metafields and metaobjects now let merchants build content systems that repeat across a catalogue, directly inside Shopify.

Shopify has been moving quickly here. Its developer changelog logged a new Collection model and APIs on 17th July 2026, then Liquid templates composing pages with blocks and partials on 21st July, and a shopify-account component becoming a Theme Store requirement on 30th July.

Three platform changes inside a fortnight is a fair signal that the collection template is being taken seriously. Yours should be too.

We have run this work ourselves. When we worked with BedShelfie, under-ranking product and collection pages sat on a store leaning hard on paid traffic through its seasonal peak. Our 12-week programme covered product and collection on-page optimisation, technical fixes and buyer-intent content, and delivered 256% more sales from Google Search.

Keep Page Two Reachable

Where paging is JavaScript-only, most of your catalogue has no crawl path into it.

Represent ships a real anchor to page two alongside 67 product links in its raw HTML, on a large fashion catalogue where that decision matters most.

Snag does the same and adds collection copy above its grid. Neither store looks like it traded anything away to get there.

Allbirds sits on the other side. Its products are server-rendered and its heading is in place, with no crawlable link to page two.

Finisterre is in that same position, which tells you budget is not what decides this. Neither of those is a small store, and both made the same call by accepting a theme default.

That means keeping a real link to your next page in the markup, whatever the visible control does. An infinite scroll and a crawlable anchor sit happily together, and on four of my 21 stores they already do.

What A Product Page Has To Answer

A product page has to settle the questions that stop a purchase. Assets that do that now carry published specifications with dates against them.

Google added an optional video link attribute for product data, with serving and quality validation beginning on 30th June 2026. The same specification raised the minimum product image resolution:

"500×500 pixels across all product categories and marketing methods"

Warnings against that threshold started on 14th April 2026, and enforcement begins on 31st January 2027. That leaves a working window to re-export product imagery at a higher resolution before the feed starts rejecting items, which is a photography and asset-management job as much as a technical one.

Two familiar design choices have therefore become scheduled requirements. Image dimensions and whether you shoot product video now have dates attached, which moves them out of the taste column and into the build plan.

There is room to move here. Average product pages convert at 1.5% to 3%, which is the band most stores sit in without ever testing what the template is doing to them.

Top performers reach 4% to 8%. The difference between an ordinary product template and a good one is a multiple of the traffic you already have, which is why the template repays attention before the traffic does.

Design your product template around questions a buyer still has at that moment: sizing and materials, delivery and returns, plus whatever angle your hero shot does not show. Our notes on ecommerce UX go deeper on ordering that information.

Filters Decide What Google Can Afford To Crawl

Every filter you add to a category page multiplies the URLs a crawler has to spend its budget on.

On that point Google's faceted navigation documentation is direct:

"Use robots.txt to disallow crawling of faceted navigation URLs. Oftentimes there's no good reason to allow crawling of filtered items, as it consumes server resources"

That same guidance explains the cost: "crawling faceted URLs tends to cost sites large amounts of computing resources due to the sheer amount of URLs and operations needed to render those pages."

Left alone, faceted navigation can eat over 40% of crawl budget. It is capacity which never reaches your products.

Filters still earn their place, and stripping them out would cost more than it saved. Baymard's Homepage and Category Navigation benchmark reports that 76% of sites perform at a level of "mediocre" or worse, measured across 335 top-grossing US and European sites.

Both things are true at once, which is why this is a design decision. Your call is per filter, and each one is index-worthy, canonicalised or blocked.

Make that call at design time and write it into the build.

Speed Is A Design Output

Speed is decided by what your design ships, rather than by what you install afterwards.

Alderson describes the pattern precisely in that Majestic piece:

"slow, client-side rendered, JavaScript-powered sites that ship 20MB of JavaScript before they put an image on the page"

Carousels, personalisation scripts and chat widgets all get chosen in a design review. They then load on every page for the rest of that theme's life.

Interaction to Next Paint is where this surfaces most clearly. Filtering, sticky headers and personalisation scripts show up far more sharply in INP than they did in FID.

So the features added to help shoppers are the ones making a page feel slow.

Field data backs that up. As of May 2026 Chrome UX Report data, 68.6% of origins had good LCP and 86.6% good INP, while only 55.9% passed all three Core Web Vitals at once. For ecommerce that figure drops to roughly 35%.

Read together, those numbers say passing one metric is common. Passing all three is the hard part, and it is the part a heavy template makes impossible.

Harry Roberts, a consultant web performance engineer who has spent years on site-speed work, published a warning on 1st June 2026 about reading these numbers too fast. Writing at CSS Wizardry, he sets out what the metric really covers:

"TBT is not an unbounded sum of all blocking work in the trace: it is a sum of all the blocking time between First Contentful Paint and Time to Interactive."

His diagnostic follows from that. If blocking time rises while the window stays flat, your extra work is real. If both move together, check whether the window itself shifted before assuming anything got worse.

All of it points the same way. Budget your page weight during design. Treat every added widget as a cost with a number against it.

Design For The Phone First

Mobile is where the field is measurably weakest, which makes a competent phone layout a genuine advantage.

Baymard's Mobile UX Trends 2026, updated on 14th July, reports that "the vast majority (75%) of mobile ecommerce sites are only 'Mediocre'". That study goes further, finding "nearly all (95%) of sites are either 'Mediocre' or 'Decent', and only 1 site is rated 'Good'", from 71,000+ mobile site elements its researchers reviewed by hand.

One good site in a benchmark of that size tells you how low the bar sits. Clearing it is not a stretch goal.

Much of that shortfall comes down to reach, which is a physical constraint. Your screen's bottom third is where the thumb naturally sits, so primary navigation and search belong in that lower half.

A hamburger menu is a design decision that buries your catalogue behind a tap, starting with the top-level categories you most want found.

Design your phone layout first and let the desktop version be the adaptation. Doing it the other way round is why so many mobile layouts read as a squeezed desktop.

Make The Trust Signals Visible

Reassurance only works where the doubt is, and it has to come from somebody other than you.

Search has drawn that line since 2019. Google stopped showing review stars for LocalBusiness structured data wherever the entity controls the reviews about itself.

Praise you write about yourself earns nothing in search results now. Your trust design has to rest on genuine product reviews, which makes review collection part of the build.

Placement is a template decision, which is why it belongs in the design brief rather than a later conversion sprint. In a 2026 trust-signal placement analysis, Digital Applied is specific about where reassurance has to sit:

"Trust signals work best when placed where doubt happens: right before the click, right before card entry, and right before final confirmation."

Build a slot into each of those three templates. The same analysis puts a number on one of them, finding that "A visible return policy reduces cart abandonment by 17% on product pages and checkout", which is a measurable return on a decision that costs nothing at wireframe stage.

That ordering matters because a footer link gets read after the decision has already been made. Our conversion framework covers where else that logic applies.

Where Mint SEO Fits In A Store Redesign

Eight sections in, a pattern should be clear. These are not two jobs.

Whoever chooses how a category template paginates is making a search decision, whether anyone at that table calls it one or not. That is why ecommerce web design and search work belong in the same brief.

That thinking sits behind our SEO-first website builds. We brief the design and the search work as one piece, starting from the templates that repeat.

Your crawl path, heading structure and page weight then get decided while they are still cheap to change. It is the same approach behind £1.23M in revenue from SEO.

Holding a redesign quote and wanting a second opinion on what it will do to your rankings is reason enough to talk. Book a free 30-minute consultation and I will go through it with you.

Common Questions About Ecommerce Web Design

How Much Does A Store Redesign Cost

Costs vary too widely for a headline number to be honest, because a theme customisation and a ground-up build are different projects.

This is where scope moves the figure. Faceted navigation left unchecked can eat 40%+ of crawl budget, and fixing that is a different job from restyling a homepage.

A more useful question is what your design is being asked to fix. Name the templates that need work and why, and you can price it.

Why Did My Traffic Drop After A Redesign

Check URLs, headings, internal links and status codes first. Then check whether a Google update landed in that same window.

May 2026 brought a broad core update, and a spam update followed in June. Both fell inside five weeks of each other.

Rankings also move without a named update at all. Google confirmed nothing for July 2026, yet trackers recorded volatility scores of 9 to 10 out of 10 around the 11th and 12th, so a quiet month on the dashboard is not the same as a quiet month in the results.

Does A Redesign Always Hurt Rankings

No, and the usual shape is a dip rather than a cliff. Website redesigns typically cause a 10-25% traffic dip in the first 30 days, and ecommerce web design work that maps its URLs first tends to sit at the shallow end of that range.

Larger losses come from unmapped URLs and stripped templates. Both are avoidable with a pre-launch inventory.

What Is The Most Common Mistake You See

Browse paths. In my August 2026 sample, 17 of the 21 readable stores had no crawlable link to page two of their main collection.

So if you have one budget line, spend it on the category template. It renders the most URLs and competes for your most valuable terms.

On most stores it also carries the least considered ecommerce web design work in the whole theme. Our wider strategy guide sets out what to do once the templates are right.