0412 086 912

Free AI Visibility Report
WLG Logo_icon

West Legacy

Group

Visibility + Authority + Growth
Powered by the Legacy Framework™

90 Day Roadmap to Fix Templates: Ecommerce SEO Audit for Small Stores

30 Aug 2026 | SEO

Hands using mouse for ecommerce site audit
Schedule a call

Start every ecommerce SEO audit with Google Search Console’s coverage report and a full site crawl. Together, they expose the three blockers that stall search performance: pages Google can’t or won’t index, template-level speed problems dragging down Core Web Vitals, and canonical or parameter chaos duplicating your catalogue. Fix those first, then build a 90-day roadmap around what’s left.

TL;DR:

  • Ensure your sitemap only contains canonical, indexable URLs and remove outdated or redirected links to optimize crawl budget.
  • Fix indexation issues by comparing search console reports with your crawl data to identify soft 404s and orphan pages that silently drain traffic.
  • Address duplicated content by implementing correct canonicals, managing URL parameters, and fixing pagination for better indexation and ranking stability.
  • Prioritize template-level speed and Core Web Vitals improvements, especially compressing images and deferring scripts, to boost overall site performance and conversions.
  • Focus on internal linking from high-traffic content and monitor review and schema implementation to enhance search appearance and click-through rates.

Table of Contents

What is an ecommerce SEO audit and where do you start?

An ecommerce SEO audit is a structured review of your online store’s technical health, content quality, and site structure, run to find exactly what’s blocking organic visibility and revenue. It’s not a vague “check everything” exercise. It’s a sequence: crawl the site, pull Search Console data, cross-reference the two, then work through templates rather than individual pages because template fixes lift hundreds of URLs at once.

That’s the part most store owners get wrong. They start by rewriting product descriptions or chasing a Google Analytics dip, when the real problem is often that Google can’t crawl half the catalogue in the first place. Backlinko’s ecommerce audit process makes the same point: reconcile your crawl with Search Console and your sitemap before you touch content, because indexation gaps hide everything else.

Two tools do most of the heavy lifting here. Google Search Console tells you what Google has actually seen and how it’s treating those pages. Screaming Frog (or a comparable crawler) tells you what’s really on the site, including the broken links, redirect chains, and duplicate templates Search Console won’t flag directly. Run both, compare the outputs, and you’ve got your starting baseline within a few hours.

How do you check crawlability and indexation first?

Pull the Page Indexing report in Search Console before anything else. It splits your URLs into indexed and excluded buckets, and the excluded reasons (crawled, not indexed; duplicate without user-selected canonical; excluded by “noindex” tag) tell you exactly where to dig.

Then run a full crawl and compare it against your XML sitemap. A healthy ecommerce sitemap should contain only canonical, indexable, 200-status URLs. In practice, most stores’ sitemaps are riddled with discontinued products, redirected URLs, or thin filtered pages that shouldn’t be there at all.

Common sitemap problems worth checking for:

  • Dead products still listed: discontinued SKUs left in the sitemap send Google to 404s or soft 404s, wasting crawl budget.
  • Redirected URLs in the sitemap: if a URL 301s somewhere else, it shouldn’t be in the sitemap pointing search engines at the old address.
  • Missing new categories or collections: seasonal collections launched outside the normal build process often never make it into the sitemap feed.
  • Multiple sitemaps with overlapping URLs: common on Shopify and WooCommerce when apps generate their own sitemap files alongside the platform’s default one.
  • Sitemap not referenced in robots.txt: a small miss, but it slows discovery on larger catalogues.

Robots.txt and the noindex tag do different jobs, and mixing them up causes real damage. Robots.txt tells crawlers not to request a URL at all, which is useful for internal search results pages, cart URLs, or filtered combinations with no search value. The noindex tag lets Googlebot crawl the page but tells it not to index the content, which is the right call for thin variant pages you still want linked internally. Blocking a page in robots.txt while also noindexing it is redundant. Blocking a page in robots.txt that you actually want deindexed is a mistake, because Google can’t see the noindex tag if it never crawls the page.

Reconciling your crawl against Search Console usually surfaces two problems generic checklists skip entirely: soft 404s (pages that return a 200 status but show “no results” or empty content) and orphan pages (URLs that exist and might even rank, but have zero internal links pointing to them). Both quietly bleed traffic. Soft 404s confuse Google about what your site actually offers, and orphan pages rely entirely on external links or sitemap inclusion to get found, which is a fragile way to run a catalogue. Google’s own ecommerce guidance covers URL design and indexation signals in more detail, and it’s worth reading before you finalise your sitemap strategy.

Technical SEO checklist: status codes, canonicals, parameters and pagination

Once indexation is sorted, move to the technical layer that causes most ecommerce ranking problems: duplication and inconsistent signals across near-identical URLs. Work through this in order, because each step depends on the one before it.

  1. Audit status codes sitewide. Export every 4xx and 5xx error from your crawl, then sort by internal link count, so you fix the pages costing you the most crawl equity first. Redirect chains (A to B to C) waste crawl budget and dilute link value at every hop, so collapse chains to a single 301 wherever you find them.
  2. Check canonical tags against actual rendered HTML. Shopify auto-generates canonicals for most templates, but collection pages with sort or filter parameters sometimes canonicalise incorrectly if a theme or app overrides the default. WooCommerce sites built on generic themes often have no canonical logic at all until you add one, which leaves every parameter variation competing against the clean URL.
  3. Decide your parameter policy before problems compound. Faceted navigation on colour, size, or price range can generate thousands of crawlable URL combinations from a catalogue of a few hundred products. Blocking low-value facet combinations in robots.txt while creating genuine indexable landing pages for search-driven combinations, like “waterproof hiking boots size 10,” is a pattern worth following deliberately rather than letting crawlers loose on every permutation.
  4. Fix pagination so category pages beyond page one still get crawled. Infinite scroll looks slick, but if there’s no crawlable “load more” fallback with real URLs, Googlebot may never see products past the first screen. A simple paginated URL structure, with rel next/prev signals no longer required but still useful for user navigation, solves this cleanly.
  5. Confirm HTTPS is applied consistently across every URL variant, including old HTTP links buried in old sitemaps or third-party backlinks. Let’s Encrypt issues free TLS certificates if your platform doesn’t handle this automatically, and mixed HTTP/HTTPS content still trips up trust signals on some setups.

Faceted navigation deserves its own deep dive if your platform relies on filters heavily. West Legacy Group’s guide to faceted navigation SEO walks through platform-specific patterns for both Shopify and WooCommerce stores. JetOctopus’s enterprise checklist makes a similar case: crawl budget, canonicalisation, and parameter handling should sit at the top of your priority list precisely because they block indexation for so many pages at once, not because they’re inherently more “technical” than other fixes.

On-page and product page optimisation at scale

Titles and meta descriptions are usually the fastest wins in an ecommerce audit, and also the most neglected because “we’ll get to it” turns into eighteen months of duplicate title tags across four hundred product variants.

Export every title tag and meta description from your crawl and sort for duplicates. Most stores find one of two patterns: every product title follows the exact same template with no differentiation (“Buy [Product] Online | [Brand]”), or variant pages (different sizes or colours of the same product) share an identical title with zero distinction. Neither helps you rank, and the second actively confuses Google about which variant to show.

Where to template and where to write unique copy:

  • Templated titles work fine for category pages when the template includes real differentiators like material, use case, or audience, not just the category name repeated.
  • Product descriptions need genuine uniqueness at least at the parent-product level, even if you template variant-level differences like size or colour.
  • Category intro copy above the fold helps both ranking and click-through, but keep it to two or three genuinely useful paragraphs. A wall of keyword-stuffed text at the bottom of a category page fools nobody, least of all Google.
  • Image alt text should describe the product specifically, not just repeat the page title. “Red merino wool jumper, front view” beats “Product Image 47.”
  • Use responsive images with srcset so mobile visitors aren’t downloading desktop-sized files, and apply lazy-loading everywhere except the above-the-fold hero image, which should load immediately to protect your Largest Contentful Paint score.

If you’re rewriting product copy at scale, the partner guide on writing product descriptions that sell covers the copywriting side well, and West Legacy Group’s own product page SEO guide covers the technical pairing of structured data and image handling.

Pro Tip: Audit your top 50 revenue-generating products first, not your top 50 by traffic. A product ranking on page two of Google with strong margins is worth more attention than a page-one product nobody buys.

Site architecture and internal linking: getting crawl equity to priority pages

Click depth determines how quickly and how often Googlebot revisits a page. As a rule of thumb, your highest-priority category and product pages should sit within two to three clicks of the homepage. Anything buried deeper than that gets crawled less frequently and passes through weaker link signals.

Map your revenue-driving pages against actual click depth using your crawl data. It’s common to find that a store’s best-margin category sits four or five clicks deep behind a generic “Shop All” navigation structure, while a low-value clearance category sits prominently in the main menu simply because nobody’s updated it since launch.

Orphan pages show up clearly once you cross-reference your crawl’s internal-link report against your full URL list. Any page with zero inbound internal links, but which still exists and is indexable, is relying entirely on the sitemap or external links to get found. That’s a fragile position for anything you actually want to rank.

A few fixes tend to move the needle fast:

  • Add contextual links from blog content and buying guides straight to relevant category and product pages, using descriptive anchor text rather than “click here” or “shop now.”
  • Fix navigation and merchandising to surface seasonal or high-margin SKUs in main menus and homepage modules, not just the newest arrivals.
  • Build a “related products” or “you may also like” module driven by category or tag relationships, which distributes link equity automatically as your catalogue grows.
  • Review footer links quarterly, since footers accumulate legacy links to discontinued collections that quietly dilute the equity flowing to current priority pages.

West Legacy Group’s internal linking guide for ecommerce goes deeper into anchor text strategy and how to structure hub pages that funnel authority down to product level.

Performance and Core Web Vitals: fixing templates, not pages

Testing a single homepage in PageSpeed Insights tells you almost nothing useful about an ecommerce store, because your homepage and your product template are built completely differently and will score differently too.

Work through performance in this order:

  1. Pull the Core Web Vitals report in Search Console and look at how it groups URLs. Google clusters pages by template automatically, which means a slow product page template shows up as one grouped issue affecting potentially thousands of URLs, not thousands of individual problems.
  2. Sample three to five real product and category pages in PageSpeed Insights, choosing pages with different layouts (a page with a video, a page with a large image gallery, a standard page) so you catch template-specific issues rather than testing the same layout five times.
  3. Fix the highest-impact template issues first. Compress and resize hero images before anything else, since oversized product images are the single most common Largest Contentful Paint problem on ecommerce sites. Cut or defer third-party scripts (review widgets, chat tools, marketing pixels) that load before the main content renders. Check server response times if you’re on shared hosting, since Time to First Byte problems affect every single page on the site simultaneously.
  4. Always test with mobile in mind first. Google indexes with mobile-first crawling, so a fast desktop score paired with a slow mobile score is the more urgent problem, not the reverse.

EcomHint’s audit guidance makes the template-first case directly: fixing one slow template can lift Core Web Vitals scores across an entire product category in a single deployment, rather than requiring page-by-page intervention.

The conversion stakes are real. Even a single-second improvement in mobile load time can meaningfully lift conversion rates on mobile-first ecommerce sites, which is exactly why template-level speed fixes deserve priority over cosmetic changes that touch only a handful of pages.

Structured data and product schema: what actually moves the needle

Not every schema type affects visibility the same way. Getting this distinction right saves you from spending a sprint on markup that only changes how a result looks, when your real problem is whether the page appears at all.

Implement Product, Offer, AggregateRating, BreadcrumbList, and ItemList schema where they genuinely apply, generating the values directly from your governed product data (price, availability, SKU) rather than hand-coding them. Hand-coded schema drifts out of sync with real inventory within weeks, and a mismatch between schema price and displayed price is a common cause of manual actions or rich result removal.

Schema type What it affects Data source
Product Rich result eligibility, product snippets Canonical product feed (title, description, image)
Offer Price and availability display in search Live inventory and pricing system
AggregateRating Star ratings in search results Review platform (see below) or native review system
BreadcrumbList Breadcrumb trail in search results Site navigation hierarchy
ItemList Carousel and list-based rich results Curated or dynamic category listings

Validate everything with Google’s Rich Results test before deployment, then monitor the Enhancements reports in Search Console afterward, since schema errors often only surface after Google has actually attempted to parse the live pages. Schema remains the canonical reference for the full vocabulary if you need field-level detail beyond what a generator tool provides.

If you’re pulling review data into AggregateRating markup, review platforms like Trustpilot document supported integration approaches, which is worth checking before you build a custom solution.

  • Product and Offer schema affect whether you’re eligible for rich results at all.
  • BreadcrumbList and ItemList mostly affect presentation, not eligibility.
  • AggregateRating sits in between: it changes appearance and can lift click-through, but a missing or broken instance won’t stop indexation.

Turning findings into a 30/60/90-day roadmap

An audit that ends in a spreadsheet nobody actions is worse than no audit at all, because it burns the goodwill for doing the next one properly. Score every finding on impact against effort, then sequence the work.

  1. P0, weeks 1 to 4: indexation and sitewide speed. Fix crawl blockers, sitemap errors, and any template-level Core Web Vitals issue affecting the majority of the catalogue. These changes lift the ceiling for everything that follows.
  2. P1, weeks 4 to 8: category templates and schema. Roll out corrected canonicals, parameter handling, and Product/Offer schema across category and product templates. Because these are template fixes, one deployment covers hundreds of pages.
  3. P2, weeks 8 to 12: content and internal linking at scale. Rewrite priority product copy, build out category intro content, and repair internal link flows to orphaned or deep pages.
  4. Ongoing: assign owners and a review cadence. Track indexed page count, Core Web Vitals pass rate, and organic revenue by category as your core KPIs, and re-audit quarterly or immediately after any major platform migration or theme change.

Because ecommerce inventory changes constantly, treat the audit as a recurring loop rather than a one-off project. Backlinko’s guidance on iterative auditing applies directly here: a store that added forty new SKUs and discontinued twenty since your last crawl has already accumulated new technical debt, whether you’ve noticed it yet or not.

West Legacy Group’s approach: what 20 years of small business audits teaches you

West Legacy Group has spent more than 20 years working inside small business ecommerce, and the pattern repeats constantly: stores with volatile, seasonal, or fast-changing inventories accumulate technical debt faster than a single annual audit can catch. A cross-functional review, pairing technical crawl work with content and merchandising input, tends to surface problems a purely technical checklist misses, like a high-margin category buried in navigation or review schema silently breaking after a platform update.

The stores that recover fastest aren’t the ones with the fewest problems. They’re the ones that treat the audit as the start of a 90-day sprint, not a report to file away.

A few things worth applying beyond the checklist itself:

  • Run the audit again after any major theme, app, or platform migration, not just on a calendar schedule.
  • Treat the common ecommerce SEO mistakes you find as a pattern to prevent in your build process, not just a one-time fix list.
  • Keep the category page optimisation checklist handy for anyone on the team adding new collections.

How does your store compare to competitors in the same search results?

Running your own audit in isolation tells you what’s broken. Running a competitor comparison alongside it tells you what’s actually achievable in your specific search results, which matters more than any generic best-practice benchmark.

Pick three or four competitors who actually rank for your priority category and product terms, not just the biggest brand names in your space. Crawl their category pages and note structural patterns: how deep is their click depth, do they publish buying guides that outrank product pages directly, what schema types show up in their rich results.

The gap analysis that matters most is usually content depth. If competitors are ranking category pages with genuine buying guide content above the product grid, and your category pages are a bare product listing with no supporting copy, that’s a specific, fixable gap rather than a vague “we need better content” observation.

Check their review volume and schema implementation too. A competitor showing star ratings in search results while you don’t is a direct, visible click-through disadvantage, and it’s usually a fast fix once you know it’s the gap. Pricing signals matter as well. If competitors show “in stock” or promotional pricing directly in search snippets via Offer schema and you don’t, that’s lost click-through on every single query where you’re both ranking.

Document the comparison the same way you documented your own audit findings: specific, prioritised, and tied to a page type rather than a vague impression of “they seem to be doing better.”

Backlink audits for ecommerce sites differ from standard link audits in one important way: product URLs change constantly, which means links pointing at discontinued or restructured pages are far more common than on a static content site.

Start by exporting your backlink profile from your link tracking tool of choice and cross-referencing every linked URL against your current live site. Any backlink pointing at a 404 or a redirect chain is losing value it doesn’t need to lose. A single 301 redirect from the dead URL to its current equivalent (or the nearest relevant category if the exact product is gone) usually recovers most of that value.

Look specifically for links pointing at old seasonal collections, discontinued product lines, or old URL structures from a previous platform migration. Ecommerce stores that have switched platforms (from a custom build to Shopify, for instance) often carry years of accumulated backlinks pointing at URL patterns that no longer exist anywhere on the current site.

Toxic link risk matters less for most small and mid-sized stores than link waste, meaning legitimate links losing their value because nobody redirected the target URL after a catalogue change. Before spending time on disavow files, spend time confirming every meaningful backlink actually resolves to a live, relevant page. Prioritise recovering links to your highest-margin categories first, since a handful of recovered links to a priority category page often outweighs dozens of scattered links to low-value pages.

Auditing site search and how it affects your SEO performance

Internal site search shapes SEO in a way many audits skip entirely: it’s a direct signal of what customers actually want, and it’s also a common source of crawlable junk if it’s not configured carefully.

Check your internal search results pages first. If they’re crawlable and indexable by default, you likely have thousands of thin, near-duplicate pages generated from every search query customers have ever typed. Block internal search result pages in robots.txt unless you’ve deliberately built curated landing pages for high-volume queries.

Then flip the analysis around. Pull your internal search query data (available in most platform admin panels or via analytics) and compare it against your actual category and product structure. Queries that return zero results, or return an awkward mismatch, point directly at either missing products or a category structure that doesn’t match how customers actually think about your catalogue.

This is one of the more underused datasets in an ecommerce audit. If forty customers a month search “waterproof phone case” and land on an empty results page because your product is tagged “water resistant” instead, that’s a taxonomy fix with a direct revenue impact, and it’s sitting right there in your search logs waiting to be found.

Site search speed matters too, particularly on mobile, where a laggy search experience pushes customers to abandon before they even see your products.

Do you need hreflang and international SEO for your store?

International SEO factors only matter if you’re actually serving distinct markets with different content, pricing, or language, and applying them when you don’t need them creates more problems than it solves.

If your store ships to multiple countries but serves identical content and currency everywhere, you likely don’t need hreflang at all. Hreflang exists to tell Google which version of a page to show a searcher based on language or region, and it only earns its complexity when you have genuinely different versions to differentiate between.

If you do run country-specific subdirectories or subdomains (different currency, different shipping messaging, translated content), check that every regional version canonicals to itself, not back to a single master version, and that hreflang tags reference every regional variant reciprocally. A common failure pattern is a store with a “/us/” and “/au/” structure where the Australian pages accidentally carry a canonical tag pointing back to the US version, effectively telling Google to ignore the entire regional store.

Geo-targeting settings in Search Console (where still relevant) and consistent currency and shipping signals on each regional page reinforce the same message. If you’re running a single-market store, this entire section is safely something to skip. Don’t build hreflang infrastructure “just in case” you expand internationally later. Build it when you actually launch a distinct regional version, not before.

Content quality beyond product pages: does your blog actually earn rankings?

Product pages alone rarely rank for the broader, higher-volume search terms that bring new customers into a category. That’s the job of blog content, buying guides, and comparison content, and it’s the area most ecommerce audits treat as an afterthought.

Audit your existing blog or guide content the same way you’d audit product pages: pull organic traffic and rankings for each piece, and be honest about which posts are doing genuine work versus which were published once and forgotten. It’s common to find a store with forty blog posts, thirty-five of which get effectively zero organic traffic, because they were written to a keyword list rather than a genuine customer question.

The content that tends to perform is the content that sits directly upstream of a purchase decision: buying guides that compare options within a category, sizing or fit guides, and genuine how-to content tied to product use. These pieces rank for broader terms your product pages can’t compete for, and they link naturally down into the category and product pages that convert.

Hand writing buying guide notes in workspace

Check internal linking from blog content into your commercial pages specifically. A guide ranking well for “how to choose a running shoe” that doesn’t link into your running shoe category is leaving crawl equity and referral traffic on the table. This is one of the fastest wins available in a content audit, because it doesn’t require new content at all, just better linking from what already exists and already ranks.

Do reviews and Q&A content actually help your SEO?

User-generated content does two jobs for ecommerce SEO simultaneously: it adds fresh, unique text to otherwise templated product pages, and it feeds the AggregateRating schema that improves click-through in search results.

Audit whether your review content is actually crawlable and indexable, not loaded entirely via a JavaScript widget that renders after the page loads without server-side rendering. Some third-party review platforms load content in a way that’s invisible to crawlers unless configured correctly, which means the unique text and rating signal you think you’re getting isn’t actually reaching Google at all.

Check review volume and freshness across your priority products specifically. A product with zero reviews looks identical to Google whether it’s brand new or simply never been asked for feedback, but a product with recent, substantive reviews adds genuinely unique content that a static product description never will.

Q&A sections work similarly, and often surface the exact long-tail questions customers search for before buying. If your product pages support a Q&A feature, check whether it’s indexed and whether it’s structured with any schema markup, since well-implemented Q&A content occasionally earns its own rich result treatment in search.

The audit question here is simple: is UGC actually reaching search engines, and is it substantive enough to matter? A five-word review adds almost nothing. A detailed, specific review or answer adds real differentiated content that a template never could.

Why most ecommerce audits fail before they start

The conventional advice treats an SEO audit like a one-time inspection: run the checklist, fix what’s broken, move on until next year. That model breaks down for ecommerce specifically, because your catalogue is never static. New SKUs, discontinued lines, and seasonal collections mean technical debt accumulates continuously, not annually.

What the evidence actually supports is prioritising template-level fixes over page-by-page cleanup, every time. A canonical error in your product template affects every product using that template, and fixing it once is worth more than a hundred hours spent hand-correcting individual pages. Most generic checklists bury this insight under a flat list of tasks with no sequencing logic.

If you take one thing from this audit process, take the sequencing: indexation and crawlability first, template-level speed and duplication second, content and internal linking third. Skipping ahead to content polish while your indexation is broken is effort spent on pages Google may never fully credit.

— Christopher

How West Legacy Group can help you fix what the audit finds

Running the audit is half the job. Fixing it at template scale, without breaking something else in the process, is where most small teams run out of time or in-house expertise. West Legacy Group works specifically with small business ecommerce operators on Shopify and WooCommerce, and the offer is built around exactly the gap this audit exposes: you get an experienced technical team without hiring one, and you keep control over pace and spend instead of signing a rigid annual contract.

West Legacy Group

West Legacy Group runs standalone ecommerce SEO audits for stores that want a clear, prioritised fix list without committing to ongoing work. For stores ready to act on the findings, a 90-day implementation sprint tackles the P0 and P1 fixes directly, template by template, with reporting on indexed pages and Core Web Vitals along the way. For stores wanting continuous coverage as inventory changes, an ongoing monitoring retainer keeps the audit loop running quarterly rather than annually. If you’d rather run parts of the process yourself with structured guidance, the self-serve SEO planning tool is built for exactly that. Start with a small business website design and ecommerce build consultation if your platform itself is due for a rebuild alongside the SEO work.

Primary sources for validating your own audit

Three references are worth bookmarking alongside this checklist. Google Search Central’s ecommerce documentation is the primary source for URL design, pagination, and structured data guidance direct from Google. PageSpeed Insights is the standard tool for testing individual product and category page performance against real Core Web Vitals thresholds. Schema.org remains the canonical reference for every Product, Offer, and AggregateRating field you’ll need when implementing or validating structured data, and Google’s Rich Results test confirms your markup renders correctly before it goes live.

Sources

Schedule a call