Ecommerce Technical SEO Audit Checklist

Technical SEO is what determines whether the content and keywords you have worked on can actually be found, understood, and ranked by Google. For ecommerce stores, technical issues carry a disproportionate cost compared to smaller sites because they scale with catalogue size. A canonical tag problem that affects one page on a blog affects one page. The same problem on an ecommerce store with ten thousand product pages affects ten thousand pages simultaneously.

This checklist covers the technical SEO audit process for ecommerce stores at the layer that matters most: crawlability, indexing, duplicate content, page speed, structured data, URL health, and internal linking. Work through each section in sequence, as issues in earlier sections often explain problems you find in later ones. This is designed to be used as a recurring audit, not a one-time exercise.

This checklist builds on the strategic foundation covered in our guide on what is ecommerce SEO. If you are new to the discipline, start there before working through the technical detail in this audit.

Before You Start: Tools You Need for This Audit

A thorough ecommerce technical SEO audit requires a small set of tools. Google Search Console is essential and free: it provides crawl data, indexing reports, Core Web Vitals, and structured data errors specific to your domain. Google PageSpeed Insights gives you Lighthouse-based performance diagnostics at the page level. Google’s Rich Results Test validates your structured data output. A site crawler such as Screaming Frog SEO Spider or Semrush Site Audit enables bulk analysis of your URL set, which is critical for stores with large catalogues where manual checking of individual pages is not practical.

Set up Google Search Console before anything else if it is not already configured. All meaningful technical audit data flows from it, and without it you are auditing blindly. Verify all versions of your domain, both HTTP and HTTPS, and confirm the primary domain version is set correctly.

Section 1: Crawlability

Robots.txt Review

Access your robots.txt file at yourdomain.com/robots.txt and review every disallow directive. Confirm that your homepage, product pages, category pages, and blog content are not inadvertently blocked. Common ecommerce robots.txt errors include disallowing the entire /products/ or /collections/ directory, blocking CSS and JavaScript files that Google needs to render pages correctly, and allowing app-generated or internal search result URLs that should be blocked.

Confirm that your XML sitemap URL is referenced in the robots.txt file. This is not required but is a clean signal that assists crawlers in finding your sitemap without relying solely on Search Console submission.

Crawl Error Review in Google Search Console

Navigate to Indexing in Search Console and open the Pages report. Filter by Not Indexed to see all URLs Google has encountered but chosen not to include in the index. Review each category of issue separately: Crawled but not currently indexed, Discovered but not currently indexed, Blocked by robots.txt, and Page with redirect. Each category has a distinct cause and a distinct fix. Prioritise resolving issues affecting your product and category pages before addressing lower-priority template pages.

Crawl Depth Analysis

Use your site crawler to map the depth of your key commercial pages from the homepage. Product pages should be reachable within three clicks maximum. Pages buried at four or five clicks deep receive significantly less crawl attention and link authority than pages closer to the surface. If important product pages are only reachable through deep sub-category trees, improve their accessibility through homepage featured sections, improved navigation, or blog content that links directly to them.

Section 2: Indexing Health

Confirm Key Pages Are Indexed

Use the URL Inspection tool in Search Console to check your homepage, top five category pages, and ten best-selling product pages individually. Confirm each is indexed, the last crawl date is recent, and there are no issues flagged with the canonical, mobile usability, or structured data for those specific URLs. Pages that appear in the search results are indexed. Pages that should appear but do not, or that show as crawled but not indexed, need investigation.

Check for Unintended Noindex Tags

Run your site crawler across your live domain and filter for pages returning a noindex directive in either the meta robots tag or the X-Robots-Tag HTTP header. A theme update, plugin change, or staging environment setting copied to production can apply noindex to commercial pages at scale without any visible indication on the front end. This is one of the most common and most damaging silent errors in ecommerce technical SEO.

Sitemap Accuracy and Submission

Open your XML sitemap and review its contents. Confirm it includes your product pages, category pages, and key static pages. Confirm it does not include low-value URLs such as filtered collection variants, internal search results, app-generated pages, or URLs blocked by robots.txt. A sitemap containing URLs that return errors or redirects is a signal of poor site hygiene. Submit a clean, accurate sitemap to Search Console and monitor it for errors in the Sitemaps report.

Section 3: Duplicate Content

Canonical Tag Audit

Canonical tags tell Google which version of a URL is the definitive one when multiple URLs serve the same or very similar content. Run your site crawler and export all canonical tag data across your full URL set. Check for: self-referencing canonicals on pages that should have them, canonical tags pointing to the wrong URL, missing canonical tags on paginated pages, and pages where the canonical tag has been stripped by a theme or plugin update.

Canonical tag management is particularly important on stores with faceted navigation, where filter combinations generate thousands of near-duplicate URLs. Our dedicated guide on faceted navigation SEO: how to handle filtering without destroying crawl budget covers the full decision framework for managing filter URLs across different ecommerce platforms.

Duplicate Meta Titles and Descriptions

Export meta title and meta description data from your site crawler and identify any duplicates. In ecommerce, duplicate meta titles commonly arise from product variants sharing a parent title, category pages sharing a generic template title, and paginated pages using the same title as page one. Each commercial page needs a unique meta title and meta description written specifically for its target keyword and buyer intent.

Thin Content Pages

Thin content pages are pages with insufficient unique text content for Google to establish their relevance to any search query. In ecommerce, the most common sources are product pages using manufacturer descriptions copied identically from other sources, category pages with no description at all, and tag or attribute archive pages generated automatically with no original content. Audit your pages by word count and flag any commercial page with fewer than 150 words of original content for description improvement.

Improving product page content quality, including writing original descriptions that satisfy both SEO and conversion requirements, is covered in full in our guide on how to write product descriptions that rank and convert.

Section 4: Page Speed and Core Web Vitals

Core Web Vitals Report in Search Console

Open the Core Web Vitals report in Google Search Console. This report uses real-world data from Chrome users visiting your store and separates performance by URL group: product pages, category pages, and other page types. Review the Poor and Needs Improvement URL counts for each group. Note that this report lags by approximately 28 days, so recent changes will not be reflected immediately.

PageSpeed Insights Across Page Types

Test your homepage, one representative category page, and one representative product page separately in Google PageSpeed Insights. Record your LCP, INP, and CLS scores for each. These three page types typically have distinct performance profiles: homepages often struggle with large hero images and multiple script tags; category pages with filter systems add JavaScript overhead; product pages with image galleries and review widgets accumulate significant combined weight.

Render-Blocking Resource Audit

In the PageSpeed Insights diagnostics, identify any Eliminate Render-Blocking Resources flags. These point to CSS or JavaScript files loaded synchronously in the page head that delay the browser from painting visible content. For ecommerce stores, the most common sources are third-party app and plugin scripts, non-critical font loading, and tracking pixels loaded in a way that blocks the main thread. Address by deferring non-critical scripts, loading fonts with font-display: swap, and moving non-essential tracking to load after the main content.

Image Optimisation Check

Run your product and category pages through PageSpeed Insights and check for Properly Size Images and Serve Images in Next-Gen Formats flags. Uncompressed product images are one of the most common performance issues on ecommerce stores. Compress images before upload to under 200KB where possible, use WebP format where your platform supports it, and ensure all images have explicitly declared width and height attributes to prevent cumulative layout shift during page load.

Section 5: Structured Data and Schema Markup

Product Schema Validation

Use Google’s Rich Results Test to check your top product pages. A valid Product schema block must include at minimum: name, image, description, price with currency, and availability status. Missing any of these required properties disqualifies the page from rich result eligibility. The data in the schema must also match what is visibly displayed on the page. A schema claiming ‘In Stock’ when the product is out of stock will trigger a manual action.

Review Schema Audit

If your store displays customer reviews on product pages, confirm that the review schema output matches the reviews actually visible to users. Applying review schema to pages with no visible reviews, or with star ratings that differ from the on-page aggregate, is a policy violation that results in rich result removal across the entire store. Validate your review schema output separately from product schema since the two are often generated by different systems.

For a complete breakdown of product, review, and breadcrumb schema implementation across ecommerce stores, including how to diagnose and fix the most common structured data errors, our guide on ecommerce schema markup: product, review, and breadcrumb implementation covers the full technical picture.

Breadcrumb Schema

Breadcrumb schema reinforces your site’s navigational hierarchy in Google’s understanding and enables the breadcrumb trail to replace the URL in search result listings, which improves click-through rate. Confirm that breadcrumb schema is present on product and category pages, that the trail accurately reflects the page’s position in the site hierarchy, and that the schema is validated without errors in the Rich Results Test.

Section 6: URL Health and Redirect Management

Redirect Chain Audit

Every URL change without proper cleanup adds another hop to a redirect chain. A URL that passes through three redirects before reaching its destination loses link equity at each hop and increases load time for anyone following an old link. Use your site crawler to identify redirect chains of two or more hops and update the originating redirect to point directly to the final destination URL, collapsing the chain into a single redirect.

404 Error Review

Export all 404 errors from your Search Console Coverage report and your site crawler. For each 404, determine whether it was a previously valid URL with existing traffic or backlinks. URLs with historical traffic or inbound links should be redirected to the most topically relevant current page. Orphaned 404s with no external links and no historical traffic can be left to expire without a redirect.

URL Handle and Parameter Audit

Review your product and category URL handles for keyword relevance and cleanliness. Auto-generated handles often include stop words, repeated category names, or internal product codes that add no SEO value. For new pages, set keyword-focused handles before publishing. For established pages with existing rankings, the risk of changing the URL must be weighed against the SEO benefit of a cleaner handle.

Section 7: Internal Linking Structure

Navigation Depth Check

Confirm that every product page on your store is reachable within three clicks from the homepage through natural navigation. Use your site crawler to identify orphaned pages, which are pages with no internal links pointing to them and therefore invisible to Google’s crawler unless they appear in your sitemap. Orphaned product pages receive no link equity and are the least likely to be crawled and indexed regularly.

Internal Link Equity Distribution

Your highest-priority commercial pages, typically your best-selling products and highest-volume category pages, should receive the most internal link equity. Review whether your navigation, category descriptions, blog content, and homepage feature sections are directing link authority toward these pages proportionally to their importance. Pages buried deep in the site architecture with few internal links pointing to them will rank below their potential regardless of how well their on-page content is optimised.

Optimising category pages as internal linking hubs that concentrate authority and distribute it to product pages below them is a core structural SEO strategy. Our guide on category page SEO: how to win high-volume commercial keywords explains how to build category pages that perform this dual role effectively.

The Full Ecommerce Technical SEO Audit Checklist

• Robots.txt reviewed: no key page types blocked, sitemap URL referenced
• Crawl errors in Search Console identified and categorised by issue type
• Key product and category pages confirmed as indexed via URL Inspection
• Full site crawled for unintended noindex tags on commercial pages
• XML sitemap reviewed, cleaned, and confirmed as submitted to Search Console
• Canonical tags confirmed on all product and category pages
• Filter and pagination URL variants canonicalised or restricted
• Duplicate meta titles and descriptions identified and resolved
• Thin content pages flagged and queued for description improvement
• Core Web Vitals report reviewed across all page type groups
• PageSpeed Insights run on homepage, category page, and product page
• Render-blocking scripts identified and deferred or removed
• Product images compressed and served in next-gen format where supported
• Product schema validated with Google’s Rich Results Test on key pages
• Review schema confirmed to match on-page review data
• Breadcrumb schema present and validated on product and category pages
• Redirect chains identified and collapsed to single-hop redirects
• 404 errors triaged and redirects applied for URLs with traffic or backlinks
• URL handles reviewed for keyword relevance across product and category pages
• All product pages reachable within three clicks from the homepage
• Orphaned pages with no internal links identified and linked from relevant pages

How Often to Run This Audit

For most ecommerce stores, a full technical audit should be conducted every six months as a baseline. Additionally, a targeted audit should be run after any significant change to the store: a platform migration, a major theme or plugin update, a URL restructure, a new app installation that affects the front end, or a significant expansion of the product catalogue.

Between full audits, set up monthly monitoring habits that catch the most common issues before they compound. Check the Coverage report in Search Console for changes in indexed page counts. Run the Rich Results Test on your top product pages after any theme update. Monitor Core Web Vitals for regressions after installing new apps or plugins. These lightweight monthly checks make the full six-monthly audit faster and more targeted because emerging issues are caught early.

Understanding what a thorough agency-level SEO audit covers across both technical and on-page elements gives useful context for how this checklist fits into a broader optimisation programme. Our article on SEO audit: 15 things your agency should check provides that wider reference point.

A Sound Technical Foundation Multiplies Every Other SEO Effort

Every piece of original content you publish, every keyword you research, and every link you earn performs better when the technical foundation of your store is sound. Crawl issues prevent your best content from being discovered. Duplicate content dilutes the authority of your strongest pages. Slow load times lose buyers before they convert. Broken structured data removes rich results that would otherwise improve click-through rates. Work through this checklist systematically, fix what is broken, and commit to running it regularly. The compounding return on a technically healthy ecommerce store is one of the most reliable SEO advantages available to store owners in 2026.