Most e-commerce SEO problems aren’t content problems. They’re structural.

Duplicate product pages, broken canonical tags, bloated JavaScript, misconfigured faceted navigation — these issues silently drain crawl budget, dilute authority, and prevent pages from ranking. You can write the best product descriptions in your category and still lose to a competitor with cleaner architecture.

This checklist covers the technical SEO foundations that matter most for e-commerce — ordered by impact, not by how impressive they sound in an audit report.


Crawlability & Indexation

Search engines can’t rank what they can’t find. The first step in any technical audit is confirming that the right pages are crawlable and the wrong ones aren’t.

What to check

  • Robots.txt: Is it blocking critical pages? Common mistake: blocking /cart, /checkout is fine, but blocking /collections/ or /products/ kills visibility
  • XML Sitemap: Does it exist, is it submitted in Search Console, and does it only contain pages you actually want indexed? Many e-commerce sitemaps include thousands of filtered URLs, out-of-stock products, or paginated pages
  • Canonical tags: Every product page, collection page, and variant URL should have a self-referencing canonical or point to the correct canonical. Shopify generates variant URLs like ?variant=12345 — these need proper canonical handling
  • Noindex tags: Check for accidental noindex on important pages. Filter pages, search results, and utility pages should usually be noindexed. Product and collection pages should not
  • Crawl budget: For sites with 10,000+ URLs, check crawl stats in Search Console. If Googlebot is spending cycles on low-value pages, you’re wasting budget

Common e-commerce issues

ProblemImpactFix
Faceted navigation creating thousands of indexable URLsSevere — dilutes authority across near-duplicate pagesNoindex filter combinations, use canonical to parent collection
Out-of-stock products returning 404Moderate — loses accumulated authorityKeep page live with “notify me” or redirect to parent collection
Session IDs in URLsSevere — creates infinite duplicate contentParameter handling in robots.txt + canonical tags
Paginated collections without rel=prev/nextModerate — poor crawl discoveryImplement pagination signals or load-more patterns

Page Speed & Core Web Vitals

Google uses Core Web Vitals as a ranking signal. For e-commerce, slow pages also directly reduce conversion rates — every 100ms of load time costs roughly 1% in sales.

Key metrics

  • Largest Contentful Paint (LCP): Should be under 2.5 seconds. For product pages, this is usually the hero image
  • Interaction to Next Paint (INP): Should be under 200ms. Heavy JavaScript bundles and unoptimised third-party scripts are the usual culprits
  • Cumulative Layout Shift (CLS): Should be under 0.1. Product image galleries and lazy-loaded content are common offenders

Audit steps

  1. Run PageSpeed Insights on your homepage, a collection page, and a product page — these are your three critical templates
  2. Check field data (real user metrics) vs lab data. Field data is what Google actually uses
  3. Identify the largest render-blocking resources. Third-party scripts (analytics, chat widgets, review platforms) frequently add 1-2 seconds
  4. Check image formats. All product images should be WebP or AVIF with proper width and height attributes to prevent layout shift
  5. Evaluate JavaScript bundle size. Many Shopify themes ship 500KB+ of JS — much of it unused on any given page

Quick wins for e-commerce

  • Preload hero images on product and collection pages
  • Defer non-critical JS — chat widgets, review carousels, and analytics don’t need to load before the page is visible
  • Use native lazy loading (loading="lazy") on all images below the fold
  • Serve images at the correct dimensions — don’t load a 2000px image for a 400px thumbnail grid
  • Minimise redirect chains — each redirect adds 100-300ms

Structured Data & Schema Markup

Structured data helps search engines understand your products, prices, availability, and reviews. It’s also the foundation for rich results (star ratings, price ranges, availability badges in search).

Essential schema for e-commerce

  • Product schema: Every product page should have Product schema with name, description, image, sku, brand, offers (price, availability, currency)
  • BreadcrumbList: Helps search engines understand your site hierarchy and displays breadcrumb trails in SERPs
  • Organization: Your homepage should have Organization schema with name, logo, and contact information
  • FAQ schema: If your product pages have FAQ sections, mark them up. These can generate expandable results in SERPs
  • Review/AggregateRating: If you have legitimate reviews, mark them up — but only with genuine review data

Validation

  1. Test every template type with Google’s Rich Results Test
  2. Check Search Console’s “Enhancements” section for schema errors
  3. Ensure prices and availability in schema match what’s actually on the page — mismatches can trigger manual actions

What not to do

  • Don’t add review schema if you don’t actually display reviews on the page
  • Don’t markup product pages for items you don’t sell directly (affiliate-only products)
  • Don’t use SameAs links to social profiles that don’t exist or aren’t maintained

Internal Linking & Site Architecture

Internal links distribute authority and help search engines discover content. For e-commerce, the architecture directly determines which pages rank.

Architecture audit

  • Click depth: Critical product and collection pages should be reachable within 3 clicks from the homepage. Run a crawl with Screaming Frog to map click depth
  • Orphan pages: Pages with no internal links pointing to them. These get discovered slowly (if at all) and accumulate minimal authority
  • Collection/category structure: Your navigation should mirror how customers think about your products, not how your warehouse organises inventory
  • Cross-linking: Product pages should link to related products, parent collections, and relevant content. Collection pages should link to subcollections and key products

Common fixes

  • Add breadcrumb navigation to every product and collection page
  • Link from blog/content pages to relevant products naturally
  • Ensure your footer includes links to key collections (not just utility pages)
  • Review anchor text — don’t make every internal link “click here” or “learn more”

URL Structure

Clean URLs are easier to crawl, easier to understand, and earn more clicks from search results.

Best practices for e-commerce URLs

  • /collections/engagement-rings not /collections/cat-47839
  • /products/lab-grown-diamond-ring-1ct not /products/item-SKU-29481
  • Avoid unnecessary URL parameters where possible
  • Keep URLs lowercase and use hyphens, not underscores
  • Don’t include dates in product URLs (they become outdated)

Migration checklist

If you’re changing URL structures:

  1. Map every old URL to its new equivalent
  2. Implement 301 redirects for all changed URLs
  3. Update internal links to point to new URLs (don’t rely on redirect chains)
  4. Update XML sitemap
  5. Monitor Search Console for crawl errors for 90 days post-migration

Mobile & Responsive Audit

Mobile-first indexing means Google primarily uses the mobile version of your site for ranking. If your mobile experience is degraded, your rankings suffer.

Check these on mobile

  • Content parity: Same product information, descriptions, and structured data on mobile and desktop
  • Tap targets: Buttons and links need at least 48px × 48px touch areas with adequate spacing
  • Font size: Body text at minimum 16px to avoid “text too small” flags
  • Viewport configuration: <meta name="viewport" content="width=device-width, initial-scale=1">
  • No horizontal scroll: Test on actual devices, not just Chrome DevTools
  • Image galleries: Swipeable, properly sized, with fast load times on 4G connections

Implementation Priority

Not everything needs fixing at once. Here’s a practical sequencing:

Week 1-2: Foundations

  • Fix canonical tags and noindex issues
  • Submit updated sitemap
  • Resolve crawl errors in Search Console

Week 3-4: Performance

  • Optimise images (format, dimensions, lazy loading)
  • Defer non-critical JavaScript
  • Address Core Web Vitals failures

Month 2: Structure

  • Implement missing structured data
  • Fix internal linking gaps
  • Address orphan pages

Month 3: Ongoing

  • Monitor Search Console weekly for new issues
  • Run monthly crawls to catch regressions
  • Track Core Web Vitals field data trends

Tools Worth Using

ToolWhat it doesCost
Screaming FrogFull site crawl — finds technical issues at scaleFree up to 500 URLs
Google Search ConsoleReal indexation data, crawl errors, Core Web Vitals field dataFree
PageSpeed InsightsCore Web Vitals testing with field and lab dataFree
Ahrefs Site AuditAutomated technical SEO monitoring with issue trackingPaid
Schema Markup ValidatorTests structured data for errorsFree

The goal isn’t to score 100 on every tool. It’s to fix the issues that actually prevent your pages from ranking — then move on to content and authority building.