Ecommerce Technical SEO Audit Checklist

Technical SEO is the part of ecommerce SEO that search engines notice first. Before Google can rank your product pages, it has to find them, render them, and decide they are worth indexing. A flawed technical foundation means every piece of content you write and every link you earn punches below its weight.

This checklist organises the areas you need to review. Work through each group in order; issues at the top tend to compound problems further down. If you want a fuller picture of what a professional review covers, see our ecommerce SEO audit service.

---

Crawlability and Crawl Budget

Faceted navigation is the single biggest crawl-budget threat in ecommerce. A catalog of 5,000 products with a handful of filters can generate hundreds of thousands of unique URLs.

• Audit your robots.txt file. Confirm it blocks parameter combinations that produce no unique value: sort orders, session IDs, tracking parameters.
• Use Google Search Console (GSC) crawl stats to check how many pages Googlebot is requesting per day and whether that number is growing without a corresponding growth in real pages.
• Identify infinite filter combinations. If your faceted navigation lets users combine color, size, price range, and material with no limit, you likely have crawl-budget leakage. Confirm these URLs are either blocked or canonicalized.
• Check internal links. Every internal link you add to a low-value URL invites crawlers to follow it. Remove or nofollow links that point to parameter URLs you do not want indexed.
• Review JavaScript rendering. If products or navigation elements load via JavaScript, verify they appear in cached versions and that crawlers are not waiting on render.

---

Indexation and Index Bloat

More indexed pages is not better. Thin, duplicated, or near-duplicate pages dilute crawl attention and can suppress rankings across your whole site.

• Pull a full index count from GSC and compare it to your intended page count. A large gap in either direction signals a problem.
• Check for duplicate product pages created by URL variations: uppercase vs lowercase, trailing slash vs none, color or size variants surfaced as separate URLs.
• Audit canonical tags. Every paginated page, filtered URL, and variant page should carry a canonical pointing to the preferred version. Confirm canonicals are self-referencing on the pages you want indexed, and point away from the pages you do not.
• Review noindex usage. Thin search-results pages, empty filtered views, and tag or label pages that duplicate category content are good noindex candidates. Avoid noindexing pages that earn backlinks.
• For category pages producing near-duplicate content at scale, read our guide on how to fix thin category pages for concrete copy and template fixes.

---

Site Architecture and Link Depth

Shallow, logical architecture distributes authority well and helps crawlers reach every page on fewer hops.

• Verify your most important category and product pages sit within three clicks of the homepage. Pages buried deeper receive less crawl frequency and less internal authority.
• Check breadcrumb logic. Every product and subcategory page should have a breadcrumb that reflects its true position in your hierarchy.
• Audit your internal linking from high-authority pages. Homepage, top-level category pages, and popular blog posts should link to pages you want to perform well.
• Look for orphaned pages: pages with no internal links pointing to them. Run your crawler output against your sitemap to find them.

---

XML Sitemaps

• Confirm your sitemap contains only indexable, canonical URLs. No noindexed pages, no redirected URLs, no canonicals pointing elsewhere.
• Keep sitemap file sizes below 50 MB uncompressed and below 50,000 URLs per file. Use a sitemap index file if you need multiple files.
• Verify the sitemap is submitted in GSC and that GSC reports no errors.
• For large stores, consider separate sitemaps by content type: products, categories, blog posts. It makes monitoring easier.

---

Redirects and Status Codes

• Crawl for broken links returning 404 responses. Prioritise fixing those that have inbound links or internal links pointing to them.
• Check for redirect chains longer than one hop. Every extra hop adds latency and loses a small amount of link equity.
• Confirm that HTTP URLs 301-redirect to HTTPS, and that www and non-www variants redirect to your canonical root.
• Verify deleted products return 404 or 410, not 200 with a blank or error page.

---

Out-of-Stock and Discontinued Products

This area is often neglected and causes real ranking problems over time.

• Temporarily out-of-stock products: keep the page live, return a 200 status, show expected restock information or alternatives. Do not redirect or noindex.
• Permanently discontinued products with backlinks or ranking history: 301-redirect to the closest relevant category or replacement product, not to the homepage.
• Seasonally unavailable products that return each year: keep the URL live year-round and update copy to reflect availability.

---

HTTPS and Core Web Vitals

• Confirm your SSL certificate is valid, covers all subdomains you use, and is not within 30 days of expiry.
• Check Core Web Vitals in GSC. Pay particular attention to Largest Contentful Paint (LCP) on product pages, where large hero images are a common culprit. Cumulative Layout Shift (CLS) is a recurring issue on pages where late-loading ads or reviews push content around.
• Audit image formats. Serve WebP or AVIF where supported, with correct width and height attributes set to prevent layout shift.
• Check server response times (Time to First Byte). For stores with large databases, uncached category and search pages are common bottlenecks.
• Verify mobile usability in GSC. Tap targets, font sizes, and viewport configuration are the most common failures.

---

Structured Data

• Implement Product schema on every product page. At minimum include name, image, description, sku, offers (with price, currency, and availability), and aggregateRating where reviews exist.
• Add BreadcrumbList schema on product and category pages. This reinforces your architecture in search results.
• Add Organization schema to your homepage with logo, contact details, and sameAs links to your social profiles.
• Validate all structured data in the Rich Results Test. GSC will surface errors over time, but proactive validation catches issues before they reach Googlebot.

---

Hreflang for US and UK

If you run separate storefronts for the US and UK (different domains, subdomains, or subdirectories), hreflang is required.

• Confirm every US page links to its UK counterpart and vice versa using the correct en-us and en-gb locale codes.
• Hreflang tags must be reciprocal: if page A references page B, page B must reference page A.
• Verify hreflang in your sitemap as well as in the page source. For large stores the sitemap method is easier to maintain.

---

Pagination

• Verify paginated pages use self-referencing canonicals, not canonicals pointing to page one. Canonicalising all paginated pages to page one hides the content on those pages from Google.
• Confirm paginated URLs follow a consistent pattern and are crawlable.
• Consider whether paginated content belongs in the index at all. For very deep pagination with little unique content, noindexing pages beyond a threshold is reasonable.

---

Log File Analysis

Log-file data tells you what crawlers actually did, not just what your CMS says it should do.

• Pull at least 30 days of server logs and segment by user agent (Googlebot, Bingbot, others).
• Identify which URLs crawlers visit most frequently and compare to your priority pages.
• Look for crawlers repeatedly hitting 404 or redirect URLs, which suggests stale internal or external links.

---

Technical SEO as the Foundation for GEO

Getting AI engines such as ChatGPT, Perplexity, and Google’s AI Overviews to read and cite your store builds on this exact same technical foundation. Crawlable pages, correct canonical signals, fast load times, and clean structured data all make it easier for large language models to retrieve and surface your content. Our GEO service covers the additional steps needed once your technical base is solid.

---

Next Steps

Work through each group above and document what you find before you fix anything. Prioritising a full site migration over a broken redirect chain is the kind of mistake that comes from not having a complete picture first.

If you want an expert to do this for you, our SEO and GEO audit covers every item on this list and returns a prioritised fix plan within five business days.