Which Site Audit Findings Are Costing Your Store Sales

You have a report open with three hundred rows and a health score at the top, and no idea which row explains why your traffic stopped growing.

That is the normal outcome of an ecommerce SEO site audit, and it is why so many of them change nothing.

I'm John Butterworth. I run the organic search work on Shopify stores, and eleven years of that has mostly been spent reading reports like the one you are holding.

Here is the short answer, before anything else. Work your findings in the order of what stands between a page and a sale.

That order runs in three steps. Pages a buyer cannot reach come first, then pages that can be reached but answer a phrase nobody types, and last the pages that are both and are slow or awkward to use.

Everything below is that order in detail, with the pass condition I use for each check and the rows I skip.

The Order To Work Through Your Findings In

Three buckets, worked in sequence, because nothing in bucket two pays until bucket one is clear.

The three buckets, worked in order. Each one is a precondition of the next.

Bucket one is reachability and indexing. A product page that returns an error or has never been indexed is worth zero at any quality.

Those rows are usually few. They are also usually the cheapest to fix, which is the second reason they come first.

Once those rows are fixed, the question changes. Bucket two is whether the page answers a real query. Money hides here, and it is the bucket automated reports are worst at, so it gets its own section below.

Bucket three is the experience of the page: speed, layout, and how quickly a buyer reaches the thing they came for.

It matters, and it matters last, because it only affects people who already arrived.

Each bucket is a precondition of the next, so work done out of order is work done at a discount.

Experienced practitioners land on the same sequencing. An r/SEO thread on what justifies a five-figure audit runs through all the deep technical scope you would expect, then finishes on the judgement call underneath it all: "prioritizing fixes based on business impact".

Scanning is the commodity. Ordering is the work, and it is what we build every engagement around, because revenue from organic search is the outcome our clients buy.

Matching A Commercial Page To What People Search For

Following on from bucket two, the most valuable finding on most stores never appears in the report at all. It is a commercial page pointed at a phrase nobody searches.

No scanner flags that page, because nothing about it breaks a rule. A collection page can carry a clean title tag, valid structured data and a green score while being built around words your buyers never use.

Before touching a single tag, I take the pages that already convert and check them against what people type. That job is manual, and it is the one that moves revenue.

We did this for BedShelfie, a Shopify bedside-shelf brand, building a seasonal campaign around the phrases its buyers type in the run-up to term time. Google Search sales rose by 256% year on year across that quarter.

Everything further down the order still gets done. It gets done after the work that pays for it.

A page can pass every technical check on your list and still be invisible, because passing a rule and answering a question are not the same test.

There is a second reason to look here first, which is that what a shopping result even looks like is moving underneath you.

Reporting in March 2026, Search Engine Land covered an analysis of 20,900,323 shopping keywords. Of those, 2,919,229 returned an AI Overview, or roughly one shopping search in seven.

Four months earlier the same measure sat at roughly a seventh of that. Pages built to answer a question are what get pulled into a surface moving that quickly.

For the decision about which collection pages should exist at all, see our guide to category page SEO.

The Pass Condition For Every Checklist Item

With the order settled, here is what an ecommerce SEO site audit should check on each page. A checklist without a pass condition is the report you are already holding, so every item below states what done means.

Can A Buyer Reach The Page At All

Reachable means a crawler can follow links to it. A page discovered only through a sitemap sits on weaker footing than one linked from a page that already gets crawled.

Google's crawl budget guidance names the pattern to watch on bigger catalogues: "infinite scrolling pages that duplicate information on linked pages, or differently sorted versions of the same page".

Is The Page In Google's Index

Use URL Inspection inside Search Console for this check. It and the aggregate coverage report are built from different pipelines, and the aggregate one is a batch that falls behind.

How far behind is not theoretical. In June 2026 the page indexing report stopped updating for a fortnight, and Barry Schwartz recorded it at Search Engine Roundtable on 25th June: "It is stuck at June 11, 2026, for me, and has not been updated in 14 days." It stayed stuck for over three weeks before Google fixed it on 3rd July.

A diagnosis built on that report during those weeks would therefore have described a store that no longer existed.

Does The Page Match A Phrase People Search

This passes when the main heading names a phrase with genuine demand and the page is the best answer on your store to it. Judge the phrase family, counting near variants together.

Matching decides whether a page is eligible for a query at all. The technical items only decide whether an eligible page can be served.

On a homeware client's store I lean on its own Search Console queries for this, since the queries it already half-ranks for are the honest test of what it is eligible for.

Does One Page Own That Phrase On Your Store

One URL should be built to win a phrase and the others should link to it.

When several near-identical pages chase one term, the choice of which to serve moves from you to Google. In the audits I run, the version it picks is often not the one the store would sell from.

That is worth catching precisely because nothing is broken. Two decent pages competing looks perfectly healthy in a report.

Can Google Read The Product Data

Price and availability need to sit in the structured data and to agree with the visible page. Stale product data is worse than none, because it contradicts what the buyer is looking at.

Stakes here differ from the other rows. Product data is what a shopping result gets assembled from, so a missing field removes a page from the surfaces carrying buying intent altogether.

Does The Page Load Before A Buyer Gives Up

Last on the list, deliberately. Speed decides whether someone who arrived stays, so its return scales with the traffic a page already has.

Where it does pay, it pays properly. Rakuten 24 ran a live A/B test against its own storefront and Google's web.dev published the result: a 53.37% increase in revenue per visitor and a 33.13% increase in conversion rate.

Note what that was measured against: a working store with traffic already on it.

For the deeper sequence behind this bucket, see our guide to the order we fix engineering problems in.

The Findings That Are Usually Noise On A Small Catalogue

Some of the loudest rows in an ecommerce SEO site audit are describing a problem your store does not have.

Such rows are easiest to spot when their status has changed underneath them. Take the instruction to block your internal search pages, which has been in circulation since the 2007 webmaster guidelines.

Google has since dropped it from its documented policy requirements while still suggesting it on technical grounds today, as John Mueller explained in reporting on the change at the end of July 2026.

"it's still something that I think just purely for technical reasons makes sense"

That is a row worth doing once and never worrying about again.

Canonical warnings are the second case, and they behave much the same way. On a catalogue of a few hundred products I have almost never traced a ranking problem to a missing canonical tag on its own.

Health scores are the third case, and the one that does most damage in an ecommerce SEO site audit, because a rising number feels like progress.

A furniture store owner posted on r/SEO after six months of textbook work. Among the things they had got right: "No crawl or index issues. Our technical health score of 98". Clicks were flat.

A moderator's reply in that thread is the line I would put above any dashboard: "People think its checklist driven".

Compliance and demand are different things, and only one of them sells. None of these checks are wrong in themselves. They are wrong to do first.

How Shopify Already Handles Your Filter And Search URLs

Almost every report on a Shopify store raises the same alarm. Your filter and sort URLs are crawlable, there are thousands of them, and they duplicate your collection pages.

Part of that is real, and most of it is handled before you touch anything. To find out how much, I ran a check.

On 6th August 2026 I requested `/robots.txt` once from each of fifteen live Shopify storefronts, chosen as well-run stores where neglect would not explain the result, among them Allbirds, Gymshark, Spanx, Mejuri and Ruggable. For each file I recorded whether it blocked sorted collection URLs, two-filter combinations and single-filter URLs. The chart shows how those three checks landed.

The three checks across fifteen live Shopify robots files, requested 6th August 2026.

The split was clean. All fifteen blocked sorted collection URLs, fourteen blocked two-filter combinations, and not one blocked a single-filter URL.

Behind that split sits the directive itself, which ships as `Disallow: */collections/*filter*&*filter*`. It only matches where two filter parameters are combined, so a URL carrying one filter gets crawled normally.

The part of this finding that is really yours is narrow: the single-filter collection URL. That is one decision about one pattern.

Shopify says as much in its merchant documentation: "you don't need to make any changes to your robots.txt.liquid file unless you have a specific reason to do so". The single-filter URL is that specific reason.

On 6th August 2026 I also checked two of those storefronts live. A filtered collection URL on Spanx returned HTTP 200 with index,follow and a canonical pointing back to the unfiltered collection, and a filtered URL on Mejuri behaved the same way with no robots meta tag at all.

That is consolidation by canonical, which works, though a disallow is the stronger instrument once you have decided you would rather the pages were not crawled.

One store in my fifteen shipped an older file with no two-filter line, so open yours and read it. Our full breakdown sits in every filter needs one of four answers.

What To Change When The Findings Are Cleared And Traffic Is Flat

This is the position most people are in when they call me. The report is clean, the work got done, and nothing moved.

Instinct after a clean report says audit again, harder. It is the wrong instinct, and Google's own team said so this July.

On 16th July 2026 John Mueller and Martin Splitt gave over an episode of Search Off the Record, How to read the Indexing Report, to the Search Console page indexing report.

Asked whether the crawled but not indexed status signals a quality problem, Mueller went straight at the assumption behind every re-audit:

"It's not that you need to fix this technical issue that Google is not indexing this page at the moment. But rather, you almost need to take a step back and think about the quality overall."

He described the mechanism too. When Google's systems are "seriously worried about the quality of a website", they index fewer pages and crawl less as well.

Those unindexed pages are therefore the symptom of a judgement about the site as a whole.

That reframes the exercise. Where the report is clean and the pages are still not being indexed, the thing to change is the pages.

Reports of pages vanishing usually turn out to be something narrower. Covering the mid-2026 wave in June, Search Engine Journal found many claimed deindexing cases "represent ranking losses, canonical consolidation, or technical blocking rather than true removal from the index".

What changes things from here is fewer, better pages, each one clearly the best answer to something a buyer types. Our note on the order to work in for more sales covers where that effort goes next.

What A Store Site Audit Is

Worth defining at the end, because a definition ahead of the answer buries the answer.

An ecommerce SEO site audit is a diagnosis of why pages are not earning, and its output should be a ranked order of work.

One that returns an inventory of everything improvable has answered a different question, because on any store that list is effectively unbounded.

Scope follows the store, which is why two documents carrying the same name can be very different pieces of work. As one practitioner put it in that same pricing thread: "Depends on the size of the site and complexity."

Here is the test I would apply to anything you are handed. Does it tell you what to do on Monday morning, and why that job ahead of the other two hundred?

If it does not, you have a scan, and the diagnosis is the missing half.

Where To Get Your Findings Ranked For You

Ranking the findings needs something a scanner does not have, which is knowledge of which of your pages earn. That is why our SEO audit and strategy service is built to end in an order.

It is a full teardown of where a store is leaking rankings and revenue, delivered as a clear strategy, not a 200-point PDF nobody reads.

If you would rather sanity-check the order you already have, book a free 30-minute call with me instead. We will look at your current rankings, the biggest quick wins and a rough 90-day direction.

Either way you finish with a shortlist you can act on. Get your SEO audit and we will start with the pages that already sell.

Common Questions

How Long The Work Takes

For a store of a few hundred to a few thousand products, the scanning is a day and the judgement is the rest.

Scanning keeps getting cheaper, too. Screaming Frog's version 24.0, released on 19th May 2026, added an option to "select 'Auto Compare Crawls' for scheduled (and CLI) crawls", so the crawl half of the job can now run itself on a timer.

It has moved quickly since, with point releases through 24.3, 29th June 2026. A method you wrote down a year ago is already describing an older tool.

That shifts the balance further: most of the elapsed time goes into checking commercial pages against real demand, which cannot be automated.

Which Findings Can I Safely Ignore

On a small catalogue: crawl budget rows, most canonical warnings and the overall health score.

Google's crawl budget guidance applies from a million pages, or ten thousand changing daily, so below that the resource being protected sits under no pressure.

When To Run The Next One

Once or twice a year for a stable catalogue, plus a check after any migration, replatform or theme change.

That cadence is what I run on client stores, because between those events the findings that matter change slowly. Reacting to every core update keeps you busy without moving anything.

Do I Need To Edit robots.txt.liquid On Shopify

Usually not, since the shipped file already blocks sorted collection URLs and two-filter combinations.

Those defaults held across the sample. Across the 15 storefronts I read on 6th August 2026, every robots file declared a sitemap, and the disallow counts ranged from 38 lines to 156. Where files differed, the extra lines were store-specific additions sitting on top of the same default.

The one case worth acting on is the single-filter URL, and only once you have decided you would rather those pages were not crawled.

Why Is My Health Score High But My Traffic Flat

Because the score measures rule compliance and not demand.

A page can pass every rule while being built around a phrase nobody searches. In the audits I run, that mismatch is the most common single reason a clean report sits beside flat clicks.

How Long Before A Fix Shows Up

Reachability fixes can move within days, while query-matching work is usually weeks to months.

In the audits I run, that second bucket moves in steps, because it depends on Google recrawling and reassessing the pages before anything shows.