Ecommerce SEO Audit

Ecommerce SEO Audit for Stores Whose Organic Traffic Has Stalled

A fixed-scope review of your catalogue, templates, crawl and tracking. Every finding comes back as a developer ticket, ranked, with a 90-day plan on top.

From $1,100Fixed-scope audit, scope and fee agreed in writing before we start
20+ yearsIn search for two decades, across 50+ brands
200M+Monthly visits across 11 countries as OLX Group’s Global Head of SEO
6 platformsShopify, custom JavaScript, WordPress, custom CMS, Webflow, Squarespace
Book an Audit Call

Quick answer

An ecommerce SEO audit checks the parts of an online store that search engines handle badly: catalogue and URL structure, collection and product templates, variants, filters, JavaScript rendering, structured data, and whether Search Console and GA4 can be trusted. Mine is fixed scope and starts at $1,100. You get every finding as a ranked, template-level developer ticket, a 90-day plan and a call to walk through it. If traffic is flat, it tells you whether the cause is technical, tracking, content or demand before you pay for the wrong fix.

Most stores that come to me aren’t broken. They’re stuck. Impressions creep up, clicks don’t, and every agency report says things are improving. The catalogue grew and the apps piled up. Then someone changed the theme, and nobody went back to check what Google actually indexes now.

I’m Ram Kr Shukla. I’ve worked in search for over 20 years, with 50+ brands, and I ran SEO across 11 countries as OLX Group’s Global Head of SEO. Think of this as the store version of my general SEO audit. It has the same fixed scope and fee model, but every check here is about your catalogue: collections, products, variants, filters, plus the tracking that’s supposed to prove any of it worked. Don’t sell online? Then that general page is the one you want.

Who This Audit Is For

You’ll probably recognise at least two of these.

1
Traffic has been flat for two or three quarters

Search Console impressions keep rising but clicks sit still, or both lines went sideways right after a theme change, an app install or a replatform.

2
Collection pages stuck on page two

Your category pages sit somewhere between positions 11 and 30 for the searches that matter, while a product page (or worse, a blog post) ranks for the head term instead.

3
Search Console lists URLs you never made

You open the Pages report and find parameter URLs, ?variant= links, old handles and filter combinations. That’s index bloat, and it quietly dilutes the pages you actually want ranked.

4
GA4 numbers that can’t be right

More purchases than cart adds, say, or organic revenue that jumps right after a tag change. Maybe two measurement IDs nobody can explain. If the data’s wrong, so is every SEO decision you’ve built on it.

5
A rebuild, replatform or new theme is coming

Do the audit first and your developer gets a list of what has to survive the change. Afterwards? It’s a recovery job.

6
You inherited the store and the agency

You’re new in the role, there’s no history, and the monthly report is one you can’t verify. An outside read gives you something to hold your suppliers to.

One honest exception. If your store launched a few months ago, it isn’t a fit yet: there’s not enough Search Console history to audit, and the free 40-point checklist will cover you for now.

What the Ecommerce SEO Audit Checks

Thirteen areas. These are where stores lose rankings without anything on the page looking broken, which is exactly why a generic site audit tends to skim them.

1Catalogue and URL architecture

How collections, sub-collections, products and guides map to real buying searches, how deep products sit, and whether URL patterns are stable. Related: crawl depth.

2Collection and category pages

H1, title and meta templates, intro copy, FAQs, pagination and links into and out of each collection. The method is in my collection page guide.

3Product templates

Title tag formulas, truncation, unique descriptions, and whether your specs and reviews are crawlable. I check each template against the 12 product page elements.

4Variants and duplicate URLs

Shades or sizes built as separate products, ?variant= URLs, collection-path product URLs, handle sprawl and case duplicates. See variants vs separate products.

5Faceted navigation and index bloat

Which filter combinations deserve to rank, which should be canonicalised or blocked, and how many of your indexed URLs earn nothing at all. See which filters to index.

6Crawlability, with throttled crawls

A crawl sized from your sitemaps and slowed down so the platform doesn’t rate-limit it. On Shopify that means a crawler access signature. Here’s why that matters.

7JavaScript rendering

Raw HTML against rendered HTML on every template, product grids that only load on scroll, and links that aren’t real hrefs. See client-side rendering and product pages.

8Structured data

Product, Offer and BreadcrumbList generated by the template, with price and stock that match the page and nothing marked up that a shopper can’t see. More on schema at scale.

9Site speed

Core Web Vitals field data per template (collection, product, cart) and the app scripts behind the slow ones. Fixed at template level where possible.

10Internal linking

Orphaned products, collections buried behind menus, and pages sitting one step from page one that just need more links. See internal linking at scale.

11Search Console and GA4 tracking integrity

Funnel order from view_item to purchase, which measurement ID gets which event, bot traffic and comparison windows after a fix. The checks are in my Shopify GA4 audit.

12Brand vs non-brand split

How much of your organic traffic comes from people who already know you. The growth is usually in the non-brand half. Here’s how I split it.

13Content and AI search visibility

Cannibalisation between blog and collections, guides that feed the pages that sell, AI crawler access, and ChatGPT and Perplexity referrals segmented in GA4.

I check each area on your templates first, then on the URLs that carry revenue. Why templates? A store with 4,000 products usually has five or six of them, and that’s where the faults live.

From crawl to ticketFour data sources are grouped by template, turned into ranked tickets placed in a 90-day plan, and walked through on a call. From crawl to ticket How the audit turns store data into work a developer can ship 1. WHAT I COLLECT Throttled crawl Raw vs rendered HTML Search Console GA4 ecommerce events 2. GROUPED BY TEMPLATE Collection, product, variant, filter, blog One fault on a template is one ticket, however many URLs it hits 3. RANKED TICKETS GA4: fire add_to_cart on quick-add buttonsDays 1 to 30 Collection template: output one H1Days 1 to 30 Filter URLs: canonical to parent collectionDays 31 to 60 Then a 90-day plan and a walkthrough call Illustrative ticketsRamKrShukla.com
Four data sources, grouped by the template that causes each fault, then ranked and placed in a 90-day plan. Illustrative.

Shopify SEO Audits, and the Other Platforms I Cover

Shopify is the platform I audit most, and its defaults create the same faults on almost every store. You’ll usually find product URLs reachable through collection paths, ?variant= links and old handles that never got redirected. Then there’s the theme that cuts every title tag at a fixed length, the collection template that skips the H1, and app scripts nobody remembers installing. The full list is in Shopify’s built-in SEO traps, and the ongoing work sits on my Shopify SEO page.

Shopify also rate-limits crawlers. Run Screaming Frog at its default speed and a big share of your collection and product pages come back as 429 errors, which look exactly like broken pages in an export. I’ve seen almost every collection on one store reported as dead for that reason alone. So every Shopify audit I do starts with a crawler access signature and a throttled crawl. If a crawl has a 429 in it, nothing from it goes into the report.

Here are the other platforms I’ve done real projects on, and what changes in the audit for each:

Platforms covered

  • Shopify: Liquid templates, variants, handles, Markets parameters, app scripts
  • Custom JavaScript builds (React or Next-style front ends): rendering, hydration, crawlable links, client-side product grids
  • WordPress: template and plugin output, archives and tag pages, parameter handling
  • Custom-built CMS: URL rules, canonical logic and sitemap generation written by your own developers
  • Webflow: CMS and product templates, collection list pages, what the platform lets you change
  • Squarespace: fewer controls, so the audit says which fixes the platform allows and which need a workaround

Here’s why the platform matters. On a Squarespace to WordPress move for a US fitness studio, all 16 URLs were mirrored one to one. Fine, you’d think. But staging QA still turned up no meta descriptions, no analytics, no LocalBusiness schema and a staging site Google could index. You don’t see any of that unless someone checks before launch. Planning a move? My rebuild and migration work covers it.

What You Get

Three things, all written so your team can act on them.

01
A ranked fix list, written as tickets

Each finding comes with the template it lives on, example URLs, the exact change, and a test your developer can run to prove it shipped. Then I rank them by what each one costs you now against what it takes to fix.

02
A 90-day plan

What ships in days 1 to 30, 31 to 60 and 61 to 90, in dependency order. Tracking fixes go first, so you can measure everything after them. And it tells you what to ignore this quarter.

03
A walkthrough call

We go through the findings together, ideally with your developer on the call. By the end you should be able to defend the plan without me in the room. The documents are yours to keep.

Template-level tickets matter more on a store than anywhere else, in my experience. On one of my Shopify audits, a tool had listed missing H1s as dozens of separate page tasks, and the developer was about to quote a week. The actual fix? One edit to one Liquid file. I’ve written that one up on my Shopify SEO page, along with the other faults I keep finding.

What one ticket looks like (illustrative)

Collection template doesn’t output an H1

Where: the collection template, so every collection page at once.

Change: render the collection title in one H1 above the product grid. Keep the current visual style.

Done when: view source on five sample collections shows exactly one H1, matching the collection title.

Priority: high impact, low effort. Days 1 to 30.

How the Audit Runs, Step by Step

1
Scoping call

We go through your URL count, platform, markets and anything that changed in the last year. You get the scope and fee in writing before anything starts.

2
Access

Search Console, GA4, read-only access to your store admin, and on Shopify a crawler access signature. I also ask who your developer is, because the tickets are written for them.

3
Throttled crawl and render check

A crawl sized from your sitemaps and slowed so the platform doesn’t block it, then raw against rendered HTML on every template type.

4
Catalogue and data review

Templates, variants, filters and the index, then Search Console and GA4 integrity, the brand vs non-brand split, and content and AI search visibility.

5
Tickets and the 90-day plan

Findings grouped by template, ranked by impact against effort, and sequenced into three 30-day blocks, with a short list of what to leave alone.

6
Walkthrough call

We go through it together, with your developer if possible. After that it’s yours to run in-house, hand to an agency, or bring me back for.

Turnaround is agreed at kickoff. It depends on catalogue size, how many templates and markets you run, and how quickly access comes through. A store waiting a week for GA4 access waits a week for the audit.

Are Ecommerce SEO Audits Worth It When Traffic Is Flat?

Sometimes. Flat traffic has four usual causes, and an audit is built for two of them.

1
A technical ceiling

Index bloat, variant duplicates, a rendering problem, or collections Google simply can’t reach. This is the case an audit is built for, because one template fix lifts hundreds of URLs at once.

2
Tracking that’s lying

Sometimes traffic isn’t flat at all. Maybe tags broke, or a second measurement ID split the data, or bots padded the earlier months. Run the free GA4 Ecommerce Tracking Checker before you pay anyone. Me included.

3
The wrong audience

In my medical apparel case study, the blog drew 14.6M monthly impressions at a 0.3% click-through rate, from students and patients who were never going to buy. So the fix was content direction. Impressions went down, and site-wide CTR went up 20%.

4
Not enough demand

If very few people search for what you sell, no audit changes that. Your Search Console impressions for category terms will show it fast. And I’d rather say so on the first call.

My honest answer? If you’ve got a catalogue of a few dozen products on a clean theme, Search Console shows no indexing trouble and the free checks pass, you probably don’t need a paid audit yet. Hundreds of products, filters, more than one market, or a GA4 setup nobody trusts is a different story, because then flat traffic is usually structural. Finding the cause costs far less than six months spent fixing the wrong thing.

One more condition. If nobody on your side can ship template changes in the next quarter, wait. The audit will still be right in three months, and sitting in a folder it’s wasted.

Free Tools That Do Parts of the Audit

Rather check some of this yourself first? These run in your browser on your own exports, and nothing gets uploaded. They’re the same checks I use, minus the joining up. The full set is on the free SEO tools page.

Start with these

Why Me for an Ecommerce Audit

I’ve spent 20+ years in search, mostly on sites where templates generate the pages. That’s the part that carries over to a store.

1
OLX Group, Global Head of SEO

11 countries across Asia, Europe and LATAM, 200M+ monthly visits, in classifieds and autos. Listings behave a lot like a product catalogue, if you think about it. Filters, category pages, items that sell and then disappear.

2
BOLD and OYO Rooms

5 global and 15 multilingual, multi-regional portals at BOLD across Europe, the UK and New Zealand. At OYO, India organic plus the US, UK, Indonesia, China and Japan, on a multilingual setup. That’s useful if your store sells in more than one market.

3
A Shopify fashion store, from zero

It started with more than 200,000 URLs in the index and almost no organic traffic. It reached 120,000 monthly organic visitors in 14 months, and collection pages ended up driving over 70% of organic revenue. The Shopify case study has the full account.

4
A paid-only D2C brand

A brand running almost entirely on Meta ads, where the audit found crawl errors, faceted navigation duplicates and slow mobile pages before any content work began. Read the D2C e-commerce case study, or see my D2C SEO work.

The rest comes from Shopify audits on D2C stores, written up with the numbers and without the brand names. There’s a crawl that reported almost every collection as broken because Shopify was throttling it. A GA4 property recording more purchases than cart adds. Shades built as separate products, all fighting over one head term. And a theme cutting every product title tag mid-word. Start with the Shopify crawl guide and the GA4 funnel audit. For the wider strategy, see my ecommerce SEO service.

What an Ecommerce SEO Audit Costs

Audits start at $1,100. That’s a fixed fee for a fixed scope, confirmed in writing after the scoping call. You won’t get a surprise invoice for extra hours.

What moves your store above the starting point:

1
Catalogue size

URL count, products, variants and how many filter combinations the platform generates.

2
Templates and storefronts

A single Shopify theme is quicker to audit than a custom JavaScript front end with its own rendering setup.

3
Markets and languages

Each country, currency or language version adds URLs, hreflang and tracking to check.

4
Data and history

How much Search Console and GA4 history exists, and whether there’s a past migration to trace.

Implementation and ongoing retainers get quoted after the audit, once we both know how long the fix list is. Some clients hand the tickets to their own developer and never need me again. Honestly, that’s a fine outcome. Want to compare pricing models first? I’ve written about what SEO costs in general.

Ecommerce SEO Audit Questions

What does an ecommerce SEO audit include?

Mine covers 13 areas: catalogue and URL architecture, collection pages, product templates, variants and duplicate URLs, faceted navigation and index bloat, crawlability with throttled crawls, JavaScript rendering, structured data, site speed, internal linking, Search Console and GA4 tracking integrity, the brand vs non-brand split, and content and AI search visibility. You get a ranked list of developer tickets, a 90-day plan and a walkthrough call.

How much does an ecommerce SEO audit cost?

My audits start at $1,100 for a fixed scope. Catalogue size, the number of templates, extra markets or languages and the amount of data history can move it up, and the final fee is agreed in writing before work starts. Implementation and retainers are quoted separately, after the audit.

Are ecommerce SEO audits worth it for an online store with flat traffic?

Often, but not always. An audit pays off when flat traffic comes from a technical ceiling or broken tracking, which is common on stores with hundreds of products, filters or several markets. It won’t help if there’s little search demand for what you sell, or if nobody can ship template changes in the next quarter. Run the free checks first if your catalogue is small.

How long does an ecommerce SEO audit take?

Turnaround is agreed at kickoff. It depends on catalogue size, the number of templates and markets, and how quickly Search Console, GA4 and store access come through.

Do you do Shopify SEO audits?

Yes, Shopify is the platform I audit most. I also audit stores and catalogue sites on custom JavaScript builds, WordPress, custom-built CMS platforms, Webflow and Squarespace.

What access do you need for the audit?

Search Console and GA4 at a minimum, read-only access to your store admin, and on Shopify a crawler access signature so the crawl isn’t rate-limited. It also helps to know who your developer is, because the tickets are written for them.

Do you implement the fixes?

The audit is written so your own developer or agency can ship it without me. If you want me to run or oversee the work, implementation is quoted after the audit, once the size of the fix list is known.

How is this different from your general SEO audit?

The general SEO audit works for any kind of site. This one is built for online stores, so it spends its time on catalogues: collections, product templates, variants, filters, rendering and ecommerce tracking in GA4.

Want to know what’s capping your store?

Send me your store URL and book a call. I’ll look at what Google indexes and how your collections rank, then tell you whether an audit is worth it for you. If it isn’t, I’ll say so.

Book an Audit CallTry the Free Checklist
RS

Written by Ram Kr Shukla

SEO and growth consultant with 20+ years in SEO and growth and 50+ brands. Former Global Head of SEO at OLX Group. Google Analytics and Google Ads certified. Works with stores as a consultant or Fractional Chief Digital Officer, and audits Shopify and custom-built catalogues for the crawl, template and tracking faults that defaults hide.