Technical SEO Checklist for Ecommerce Websites

Most ecommerce stores lose organic traffic to technical problems they never see. Broken crawl paths, duplicate product URLs, and slow page loads quietly erode rankings while the team focuses on content and paid media. Interconnections resolved 1,442 crawl issues for one ecommerce client and improved site health from 67% to 92% over eight months. This checklist covers every technical SEO item specific to online stores, prioritized by the issues that cost the most traffic.

If you run a store with hundreds or thousands of SKUs, generic SEO checklists miss the problems that matter most to you: faceted navigation bloat, product variant duplication, and crawl budget waste from pages Google should never index. This is the ecommerce technical SEO checklist built for those exact challenges.

Site Speed and Core Web Vitals Targets

Ecommerce sites that pass all three Core Web Vitals thresholds see 15 to 30 percent higher conversion rates compared to those that fail. The three metrics that matter in 2026 are Largest Contentful Paint (LCP) under 2.5 seconds, Interaction to Next Paint (INP) under 200 milliseconds, and Cumulative Layout Shift (CLS) under 0.1. Google evaluates the 75th percentile of all page loads, meaning 75% of your real user visits must hit the "good" threshold.

For product pages specifically, LCP failures usually come from unoptimized hero images. Serve product images in WebP or AVIF format, set explicit width and height attributes to prevent layout shift, and lazy load images below the fold. Third-party scripts are the second biggest offender. Every review widget, chat plugin, and analytics tag adds render-blocking JavaScript. Audit your third-party scripts quarterly and defer anything that does not need to fire before the page is interactive.

INP replaced First Input Delay in March 2024 and is now the responsiveness metric Google uses for ranking. Ecommerce sites with heavy filtering interfaces and add-to-cart interactions need INP under 200ms. Test your product listing and product detail pages separately because they behave differently under load.

Run your audit in Google PageSpeed Insights using the field data tab, not lab data. Lab data shows what could happen. Field data shows what actually happens for your real users.

Crawl Budget: Why Google Ignores Most of Your Product Pages

Crawl budget is the number of pages Google will crawl on your site within a given timeframe. For stores with fewer than 10,000 URLs, this rarely matters. For stores with large catalogs, faceted navigation, and multiple product variants, crawl budget waste is one of the biggest invisible problems in ecommerce SEO.

Here is how it happens. A store with 1,000 products and filters for color, size, brand, and price can generate over 1,000,000 filterable URL combinations. Every combination is technically a unique URL. Googlebot does not know which ones matter and which ones are junk, so it crawls them all until it runs out of budget. The result: your actual product pages and category pages get crawled less frequently, and new products take weeks or months to appear in search results.

According to Google's crawl budget documentation, the two ways to increase crawl budget are adding more server resources and improving content quality and uniqueness. But for ecommerce, the faster fix is to stop wasting the budget you already have.

Three specific fixes:

1. Block faceted navigation URLs in robots.txt (see the robots.txt section below)
2. Add noindex tags to filtered and sorted variations of product listing pages
3. Use canonical tags to point variant URLs back to the primary product URL

Interconnections used this exact approach for an arts and crafts ecommerce brand. After fixing crawl waste from faceted navigation and resolving 1,442 crawl issues, the site's organic traffic grew from 891 to 4,544 monthly visitors, a 410% increase over eight months.

Duplicate Content: Product Variants, Filtered URLs, and Pagination

Duplicate content on ecommerce sites is not a penalty. It is a ranking dilution problem. When Google finds three URLs with nearly identical content, it has to choose which one to index. If it picks the wrong one, your preferred page loses ranking signals.

The three most common sources of ecommerce duplicate content are product variants (the same product in red, blue, and green each getting its own URL), filtered and sorted URLs (the same category page sorted by price, popularity, or rating), and paginated series (page 1, page 2, page 3 of a product listing that share the same title and description).

Canonical tags are the primary fix. A canonical tag tells Google which URL is the original version. For product variants, every color and size variation should include a canonical tag pointing to the main product URL unless the variant has genuinely unique content (different descriptions, different images, different use cases).

For filtered URLs, add a self-referencing canonical on the primary category page and canonical tags on all filtered versions pointing back to that primary URL. For pagination, each paginated page should have a self-referencing canonical so Google indexes the full series rather than collapsing it.

A Semrush study of 50,000+ domains found that 41% had internal duplicate content issues. On ecommerce sites with product variants, the number is almost certainly higher.

XML Sitemaps for Ecommerce Stores

Your XML sitemap tells Google which pages exist and which ones matter most. For ecommerce stores, the sitemap is not optional. It is the fastest way to get new products indexed and to signal priority across a large catalog.

Include every indexable product page, category page, and key content page in your sitemap. Exclude any URL you have set to noindex, any filtered or faceted URL, and any utility page (cart, checkout, account). Use the lastmod tag accurately. Google uses lastmod to decide which pages to recrawl first, so update it only when the page content actually changes.

For stores with more than 50,000 URLs, split your sitemap into multiple files organized by product category. Reference all sub-sitemaps in a sitemap index file. Google's limit is 50,000 URLs per sitemap file and 50MB uncompressed.

Generate your sitemap dynamically. Static sitemaps go stale within days on active ecommerce sites. Most ecommerce platforms (Shopify, WooCommerce, Magento, BigCommerce) generate sitemaps automatically, but you need to verify the output. Check that discontinued products are removed, that filtered URLs are not included, and that the lastmod dates are accurate.

Robots.txt: What to Block on an Ecommerce Site

Your robots.txt file controls which URLs search engine crawlers can access. For ecommerce sites, getting this right directly protects your crawl budget and prevents duplicate content from entering Google's index.

Block these URL patterns:

• Faceted navigation and filter parameters (/collections/*?filter=, /products?sort=, /catalog?color=)
• Internal site search results (/search?, /search/*)
• Cart and checkout pages (/cart, /checkout)
• Account and login pages (/account, /login, /register)
• Wishlist and comparison pages (/wishlist, /compare)

Do not block CSS, JavaScript, or image files. Google needs these to render your pages correctly for mobile-first indexing.

Test your robots.txt in Google Search Console's robots.txt tester to confirm it blocks the right URLs and allows the right ones.

Structured Data: Product, BreadcrumbList, and FAQPage Schema

Structured data tells Google what your page content means, not just what it says. For ecommerce sites, three schema types are essential: Product, BreadcrumbList, and FAQPage.

Product schema should appear on every product detail page. Include name, description, image, price, currency, availability, brand, and review data (aggregateRating). Google recommends JSON-LD format because it is easier to maintain and does not require changes to your HTML structure. In 2026, Product schema is also required for Google Merchant Center integration. Sites with valid Product markup are eligible for rich results, free product listings, and automatic feed updates.

BreadcrumbList schema reinforces your site hierarchy for Google. Implement it on every page to show the path from homepage to category to product. This improves how your pages appear in search results and helps Google understand your site structure.

FAQPage schema should appear on category pages and product pages where you have FAQ content. Google's rich results for FAQ generate additional SERP real estate and increase click-through rates. Use Google's Rich Results Test to validate your structured data before deploying. Structured data must match the visible content on the page. If your schema says a product costs $19.99 but the rendered page shows $24.99, Google will flag the discrepancy and may remove your rich results.

Understanding how AI search is reshaping ecommerce traffic and CAC is critical here. Structured data is how AI crawlers from ChatGPT, Perplexity, and Google AI Overviews parse and cite your product information. Sites without schema are invisible to these systems.

Mobile Usability for Ecommerce Product Pages

Google uses mobile-first indexing, which means the mobile version of your site is the primary version Google crawls and ranks. Product pages that work on desktop but break on mobile lose rankings regardless of their content quality.

Check three things on every product page. First, ensure touch targets (buttons, links, form fields) are at least 48x48 CSS pixels with adequate spacing. Product variant selectors and add-to-cart buttons are frequent offenders. Second, confirm the viewport meta tag is set correctly. Third, verify that all content visible on desktop is also visible on mobile. Hidden tabs, collapsed accordions, and truncated descriptions that require a click to expand are indexed, but Google may give that content less weight.

Test your product pages using Chrome DevTools device emulation across multiple screen sizes. Pay specific attention to product image galleries, size and color selectors, and review sections on screens smaller than 375px wide.

HTTPS, Security, and Redirect Management

Every page on your ecommerce site must serve over HTTPS with a valid SSL certificate. This is not negotiable for stores processing payment information, but it also applies to every category page, blog post, and informational page. Google confirmed HTTPS as a ranking signal years ago, and any mixed content (HTTP resources loaded on HTTPS pages) degrades both security and performance.

Redirect management is where most ecommerce stores accumulate technical debt. When you discontinue a product, the product page still has backlinks, bookmarks, and indexed URLs pointing to it. A 404 error wastes all of that ranking equity. Instead, redirect discontinued products to the most relevant category page or a similar product using a 301 redirect. A Semrush study found that 12% of sites had redirect chains or loops, which pass less ranking equity with each hop and slow down page load times. Keep redirect chains to a maximum of one hop.

If you are evaluating help with these issues, understanding how to evaluate an ecommerce marketing agency before signing will save you from agencies that skip the technical audit entirely.

International SEO: Hreflang Tags for Multi-Region Stores

If your store serves multiple countries or languages, hreflang tags tell Google which version of a page to show to which audience. Without hreflang, Google may show your US English product page to French Canadian shoppers or your Canadian pricing page to US visitors.

Implement hreflang using link elements in the HTML head of every page that has a regional equivalent. Each page must reference itself and all of its alternates. The most common error is the missing return tag: if Page A references Page B as an alternate, Page B must also reference Page A. Google ignores hreflang when return tags are missing.

For ecommerce stores with separate domains or subfolders per region (store.com/us/, store.com/ca/, store.com/uk/), implement hreflang in an XML sitemap rather than in page headers. This is easier to maintain for large catalogs and avoids bloating your HTML head with dozens of link elements.

Use ISO 639-1 language codes and ISO 3166-1 Alpha 2 country codes. Examples: en-US, en-CA, fr-CA, de-DE. Test your implementation with a tool like Ahrefs' hreflang checker to catch missing return tags before they cause indexing problems.

This is the same process Interconnections used with an arts and crafts ecommerce brand. Over eight months, organic traffic grew 410%, daily clicks increased from 82 to 597 (a 628% increase), and the site earned 17 Page 1 rankings from zero. The domain rating improved from 19 to 28, and referring domains grew from 34 to 79. For context on the Shopify SEO limitations and workarounds most guides skip, the same crawl and canonical principles apply but Shopify's rigid URL structure adds additional constraints.

Fix the Foundation Before Scaling Traffic

Technical SEO is not a one-time project. It is the infrastructure that determines whether your content and product pages can compete in search at all. If your ecommerce store has hundreds of products and you have never run a structured technical audit, there are almost certainly crawl issues, duplicate content problems, and schema gaps costing you traffic right now. Interconnections runs a Growth Diagnostic Sprint that starts with exactly this kind of technical foundation work before touching content strategy or paid media budgets. That diagnostic is usually the fastest path to finding out what your store is actually leaving on the table.