eCommerce SEO Checklist 2026: 150+ Optimization Items

Product Detail Pages are where transactional intent converts. The PDP template affects every SKU in your catalog, so template-level fixes scale instantly. Audit the template first, then sample 20 live PDPs across different categories to confirm the rules hold.

1. Check: Every PDP has a unique, keyword-targeted <title> tag under 60 characters.
2. Check: Meta descriptions are unique per SKU, mention price or shipping, and stay under 155 characters.
3. Check: H1 is unique, contains the product name, and is not duplicated elsewhere on the page.
4. Check: Product images use descriptive filenames and alt text referencing brand, model, and color.
5. Check: Primary product image is defined for Product schema and OpenGraph.
6. Check: Price, currency, and availability are rendered server-side (not lazy-loaded via JS).
7. Check: Breadcrumb navigation is present and marked up with BreadcrumbList schema.
8. Check: Variant selection (size, color) does not create duplicate URLs without canonicals.
9. Check: Out-of-stock products remain indexable with accurate availability schema.
10. Check: Review snippets render above the fold and are included in schema if genuine.
11. Check:Cross-sells and upsells use descriptive anchor text, not generic "see also".
12. Check: Sticky add-to-cart or buy box works on mobile without layout shift.
13. Check: Canonical tag points to the definitive product URL (no trailing parameters).
14. Check: PDPs return 200 OK, not 302 or soft 404, when the product is live.
15. Check: Structured data validates in both Rich Results Test and Schema Markup Validator.

When you find template issues, fix once and redeploy — a corrected canonical rule or schema field will repair thousands of URLs simultaneously. Pair these fixes with the 2026 eCommerce statistics to model the revenue impact of even incremental CTR gains on high-volume PDPs.

Category pages (also called collections, departments, or listing pages) are the highest commercial-intent landing pages on most eCommerce sites. They target shorter, broader queries with more volume than any individual product. Treat them as content assets, not just product grids.

1. Check: Every category has a unique H1 that matches user search intent, not internal taxonomy.
2. Check: 150-300 words of unique intro copy appear above or below the product grid.
3. Check: The URL structure is shallow: /category/ or /shop/category/, not /store/dept/sub/sub/.
4. Check: Pagination uses clean URLs (?page=2) — not infinite scroll without history API support.
5. Check: Page 1 of paginated results is canonical to itself, not to a view-all.
6. Check: Each paginated page has a self-referencing canonical (deprecated rel=next/prev is gone).
7. Check: Category images have alt text and are served in modern formats (AVIF/WebP).
8. Check: Sort-order parameters (?sort=price) are canonicalized to the default sort URL.
9. Check: Empty or near-empty categories are noindexed until they have sufficient products.
10. Check: Seasonal categories (holiday, sale) keep stable URLs year-over-year.
11. Check: Category internal-link hubs (related categories) use descriptive anchors.
12. Check: No category page relies on JavaScript to render its first screen of products.
13. Check: Breadcrumbs are present and schema-marked on every category depth.
14. Check: Duplicate categories (different URLs, same products) are consolidated with 301s.

Faceted navigation is the single largest source of crawl waste on most eCommerce sites. A category with 6 filter dimensions and 4 values each can generate tens of thousands of URL combinations — 99% of which should never reach Google's index.

1. Check: A documented facet policy exists specifying which combinations are indexable.
2. Check:Non-indexable facets use rel="canonical" pointing to the parent category.
3. Check:Facet URL parameters appear in a consistent order (avoid ?color=red&size=m vs ?size=m&color=red).
4. Check: Selected facets use POST or fragment URLs when they should not be indexed.
5. Check: Robots.txt blocks crawling of parameters known to generate infinite combinations.
6. Check:Meta robots "noindex, follow" is set on non-indexable facet pages.
7. Check: Indexed facet combinations (brand + category) have unique titles and H1s.
8. Check:Facet links use rel="nofollow" only where truly needed — not blanket-applied.
9. Check:URL parameters are documented in Search Console's legacy URL Parameters tool archive for reference.
10. Check: Multi-select facets do not create combinations that exceed 3 simultaneous filters indexed.
11. Check: Price-range facets (?price=100-200) are never indexed.
12. Check: Out-of-stock facet combinations return useful content or redirect to the parent.
13. Check: JavaScript-only facets are tested with rendering tools (Inspect URL) to confirm Googlebot sees content.

Core Web Vitals affect both rankings and conversion. Retailers that improve LCP from 4s to 2.5s routinely see measurable revenue lift per session, independent of ranking changes. Use CrUX field data for real user measurement — lab scores alone are insufficient.

1. Check: LCP is under 2.5s at p75 on both mobile and desktop (CrUX field data).
2. Check: INP is under 200ms at p75 across PDP, category, and cart templates.
3. Check: CLS is under 0.1 at p75 — especially on PDPs where images load late.
4. Check: Hero product image is preloaded on PDPs (link rel=preload, fetchpriority=high).
5. Check:Below-the-fold images use native lazy-loading (loading="lazy").
6. Check: All images have explicit width and height attributes to reserve layout space.
7. Check: Third-party scripts (reviews, chat, personalization) load async or deferred.
8. Check: Critical CSS is inlined; non-critical CSS is deferred.
9. Check: Fonts use font-display: swap and are preloaded for the first paint.
10. Check: JavaScript bundles are code-split per route; no single bundle exceeds 300KB gzipped.
11. Check: CDN is configured with proper cache headers and HTTP/2 or HTTP/3.
12. Check: Server response time (TTFB) is under 600ms at p75.
13. Check: Add-to-cart interactions do not trigger layout shift or long tasks.

For the full technical depth, cross-reference our technical SEO audit checklist which covers CWV diagnostics and remediation in broader detail.

Product schema unlocks rich results, price and availability in SERPs, and Merchant Center feed validation. It is the single highest-leverage structured data investment for eCommerce. Validate with Google's Rich Results Test and monitor Search Console's Shopping enhancement reports.

1. Check: Every PDP has Product schema with name, image, description, and brand.
2. Check: Offers block includes price, priceCurrency, availability, and priceValidUntil.
3. Check: Availability values use the correct schema.org URLs (InStock, OutOfStock, PreOrder).
4. Check: GTIN, MPN, or ISBN is provided when available — required for some Merchant Center features.
5. Check: AggregateRating is only used when genuine user reviews exist on the page.
6. Check: Shipping details (shippingDetails) are specified per offer when shipping varies.
7. Check: Return policy (hasMerchantReturnPolicy) is included for products with return policies.
8. Check: Product variants use ProductGroup and hasVariant for parent-child relationships.
9. Check: BreadcrumbList schema is present and matches visible breadcrumb navigation.
10. Check: Organization schema on the homepage includes logo, sameAs, and contactPoint.
11. Check: WebSite schema with SearchAction enables sitelinks search box eligibility.
12. Check: JSON-LD is preferred over Microdata or RDFa for maintainability.
13. Check:Search Console's Merchant listings and Product snippets reports show zero critical errors.

Internal links pass authority and signal relevance. In eCommerce, the main levers are category hub pages, cross-sells, breadcrumbs, and editorial content linking into commercial pages. Thin internal linking is why many PDPs never rank despite being crawled.

1. Check: Homepage links to top-level categories with descriptive anchor text.
2. Check: Every indexable page is reachable within 3 clicks from the homepage.
3. Check:Related product widgets use SKU-specific anchor text, not "buy now".
4. Check: Breadcrumb trails pass link equity back up the taxonomy.
5. Check: Blog and guide content links into relevant category and product pages.
6. Check: No single page contains more than 100 internal links without clear purpose.
7. Check: Orphan pages (indexable URLs with zero internal links) are flagged and linked.
8. Check: Footer links are focused — a 200-link footer is a red flag for link equity distribution.
9. Check: Anchor text for categories is varied: brand, model, use case, material.
10. Check: Deep internal linking from high-authority content to revenue pages is deliberate.
11. Check: JavaScript-only navigation is tested — crawlers must see links without executing full app JS.
12. Check: Brand pages link to all products from that brand using clean URLs.
13. Check: Editorial buying guides are linked from related category pages with contextual anchors.

For platform-specific internal-linking patterns, review the 2026 Shopify platform data — different platforms default to different navigation architectures.

If you ship to multiple countries or speak multiple languages, hreflang is how you tell Google which URL to serve to which user. Misconfigured hreflang is common and consequential — German users landing on US pricing is a direct revenue leak.

1. Check: Every localized page has a full hreflang cluster listing all language/region pairs.
2. Check: Hreflang tags are bidirectional — page A references B and B references A.
3. Check: A self-referencing hreflang is present on each URL.
4. Check: x-default is set to the most appropriate fallback (often the US or global English version).
5. Check: Hreflang values use correct ISO format (en-US, en-GB, de-DE, fr-CA).
6. Check: Currency and payment methods match the target market on each localized version.
7. Check: Prices are not auto-converted via JS only — server-rendered currency matches hreflang.
8. Check: Shipping and returns information is localized, not just translated.
9. Check: Geo-redirects (IP-based) do not block Googlebot from crawling alternate locales.
10. Check: Separate XML sitemaps exist per language/region, or a single sitemap uses xhtml:link.
11. Check: Search Console International Targeting report shows zero hreflang errors.
12. Check: Local domain or subfolder structure is consistent (/en-gb/ vs /en/gb/ confusion).
13. Check: Duplicate content across locales is expected and correctly signaled by hreflang, not canonical.

Merchant Center powers Shopping ads and free product listings. A healthy feed extends your SERP real estate far beyond blue links. The feed must match what's on your site — any divergence between feed and landing page can suspend your account.

1. Check: Primary product feed is configured with daily fetch or supplemental feed updates.
2. Check: Product IDs are stable and consistent between feed and Product schema.
3. Check: Prices in the feed match displayed prices on the landing page exactly.
4. Check: Product titles use the pattern: Brand + Product + Key Attribute + Size/Color.
5. Check: Descriptions are 500-1000 characters, benefit-led, and not duplicated from other retailers.
6. Check: Product images are high-resolution (800x800 minimum), on white or neutral backgrounds.
7. Check: GTINs are submitted for every product that has one — required for branded goods.
8. Check:Availability status in the feed matches the live site's inventory state.
9. Check: Shipping rates and tax settings are configured per ship-to region.
10. Check: Return policy is defined in Merchant Center and matches on-site policy.
11. Check: Disapproved products are reviewed weekly and resubmitted after fixes.
12. Check: Automated Item Updates are enabled so Google can sync price/availability from schema.
13. Check: Free Listings opt-in is active to surface products in unpaid Shopping results.

Manufacturer copy is duplicated across every retailer carrying that product. Unique PDP content — your own descriptions, specs presentation, reviews, and buying guidance — is how you differentiate in SERPs. UGC (reviews, Q&A) adds scale that editorial teams cannot match.

1. Check: Top-selling PDPs have rewritten, unique product descriptions (not manufacturer boilerplate).
2. Check: Key specs are presented in a structured table, not buried in paragraph text.
3. Check: Genuine customer reviews are collected and displayed with reviewer name and date.
4. Check:A Q&A section allows customers to ask and answer product-specific questions.
5. Check: Review snippets include both pros and cons — overwhelmingly positive reviews reduce trust.
6. Check: User-uploaded photos are surfaced (with moderation) for social proof.
7. Check: Size guides, fit notes, and comparison tables answer purchase-blocking questions.
8. Check: Videos (product demos, unboxings) are embedded with VideoObject schema.
9. Check: FAQs on PDPs are presented as visible content, not folded into FAQPage schema (which is not eligible here).
10. Check: Related buying guides or comparison articles link into the PDP with contextual anchors.
11. Check: Trust signals (warranty, guarantee, shipping, returns) appear near the add-to-cart.
12. Check: Product descriptions include natural language around how, when, and why to use.
13. Check: No PDP relies solely on bullet points — longer narrative content ranks better for informational queries.

High-quality PDP content is a force multiplier for ongoing SEO optimization — it compounds with every link earned and every ranking improvement across the catalog.

The final section covers technical issues specific to eCommerce platforms: internal search, checkout URLs, login-gated content, and deprecated product handling. These rarely get attention in generic SEO audits but cause real index bloat and crawl waste.

1. Check: Internal search pages (/search?q=) are disallowed in robots.txt and noindexed.
2. Check: Cart and checkout URLs are disallowed in robots.txt.
3. Check: Account, wishlist, and login-gated pages are noindexed.
4. Check: Discontinued products either 301 to a replacement, 410 if permanent, or stay live if restocking.
5. Check: URL slugs are lowercase, hyphen-separated, and stable across catalog updates.
6. Check: Tracking parameters (utm_, gclid, fbclid) are canonicalized to clean URLs.
7. Check: XML sitemap excludes noindexed URLs, redirected URLs, and canonicalized duplicates.
8. Check: Sitemap is split when catalogs exceed 50,000 URLs or 50MB per file.
9. Check: Log files are analyzed monthly to confirm Googlebot spends time on revenue-generating URLs.
10. Check: No infinite spaces (calendar widgets, session IDs in URLs, nested filters) exist.
11. Check: HTTPS is enforced sitewide with HSTS and proper certificate chain.
12. Check: Mobile experience passes mobile-friendly checks — no tap targets too close, no horizontal scroll.
13. Check: A process exists to flag platform updates (theme, app installs) that alter rendering or structured data.

Putting it all together

One hundred and fifty checkpoints sounds like a lot, but most eCommerce teams discover that 80% of their issues cluster in three sections: faceted navigation, PDP schema, and Core Web Vitals. Fix those first. The remaining sections then become steady, compounding improvements that extend your organic reach over quarters and years.

The checklist is designed to be rerun. Quarterly audits catch regressions from platform updates, app installs, and theme changes. Monthly spot-checks on schema validity and Merchant Center errors catch problems before they hit revenue. Treat this as an operating rhythm, not a one-time exercise.

Frequently asked questions