Costs
Part of Ecommerce SEO: Fix a Stale Shipping Promise
Ecommerce SEO checklist: what to check before release
A practical ecommerce SEO checklist for release day: title tags, canonicals, structured data, Core Web Vitals, status codes, robots.txt and sitemap rules.
What to take away
- Apply the checklist to representative templates and states beyond the home page.
- Record evidence, owner, version, and exceptions for every check.
- Block releases that break critical customer tasks or product truth.
An ecommerce SEO checklist is useful when it creates release evidence. Run it against available, unavailable, variant, discounted, paginated, filtered, retired, and error states on mobile and desktop. Save the URLs, time, environment, result, owner, and issue.
Prepublication checklist
Prepublication Gate Areas
- Purposecustomer task and index intent
- Responsestatus, redirect, headers, rendered content
- Productname, price, stock, variant, identifier
- Discoverynavigation, crawlable links, sitemap
- Signalscanonical, robots, language, structured data
- Experiencekeyboard, zoom, labels, errors, performance
- Evidenceclaims, reviews, images, policies
| Area | Verify |
|---|---|
| Purpose | Customer task and index intent |
| Response | Status, redirect, headers, rendered content |
| Product | Name, price, stock, variant, identifier |
| Discovery | Navigation, crawlable links, sitemap |
| Signals | Canonical, robots, language, structured data |
| Experience | Keyboard, zoom, labels, errors, performance |
| Evidence | Claims, reviews, images, policies |
| Reporting | Annotation, monitoring, owner, rollback |
The checks to run
Work through these items on a representative URL for every template and state, then sample the rest.
- Titles and snippets:one title tag and one meta description per indexable URL, unique across the store and written around the customer's task.
- Headings and copy:a logical H1, H2, H3 order, and unique category, filter, and product copy instead of manufacturer text.
- Canonicals and robots meta:a self-referencing canonical tag on every indexable URL, a
robotsmeta tag that matches the page's intent, and reciprocalhreflangannotations on locale and currency versions. - Images and internal links:descriptive
alttext on product images, plus crawlable text links to variants, categories, and related products. - Structured data:
Productmarkup withOffer(price, priceCurrency, availability),BreadcrumbList, andaggregateRatingonly where genuine reviews exist, validated with the Rich Results Test. - Core Web Vitals:LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1, read from mobile field data at the 75th percentile.
- Status and redirects:301 for permanent moves, 302 only for temporary ones, 404 for URLs that never existed, 410 for products that are gone for good, no soft 404s, and redirects that resolve in a single hop.
- robots.txt and sitemaps:
DisallowandAllowrules for paths that should not be crawled, plus aSitemap:line pointing to the sitemap index. - Deindexing:use a
noindexrobots meta tag for pages that must not be indexed, and do not pair it with aDisallowrule, because a blocked URL is never crawled and thenoindextag is never seen. - Pagination and filters:crawlable links between paginated pages, a self-canonical on each page, and a written rule for faceted and filtered URLs so they do not compete with the category page.
- Product states:a policy for out-of-stock, variant, and retired URLs, keeping and labeling the URL when the product will return and otherwise redirecting it to the closest category or successor product.
- Tools:Google Search Console (Sitemaps, Page Indexing, Core Web Vitals), Bing Webmaster Tools, a crawling tool such as Screaming Frog, and a keyword and backlink tool such as Ahrefs or Semrush.
Build a clean sitemap
Google's guide to building and submitting a sitemap describes supported formats, location, absolute URLs, canonical choices, and file limits. A sitemap supplies discovery information and hints; it does not force indexing or correct broken pages.
- Include intended canonical indexable URLs
- Use exact absolute production URLs
- Remove redirecting, blocked, error, and noncanonical entries
- Update last-modified values only for meaningful page changes
- Split large sets by a stable operational rule
- Keep each sitemap file at or under 50,000 URLs and 50 MB uncompressed
- List the sitemap in robots.txt with a
Sitemap:line and submit it in Google Search Console and Bing Webmaster Tools - Monitor generation failures and stale product states
Test access across the customer journey
W3C's overview of mobile accessibility explains that mobile accessibility is covered by existing W3C accessibility standards and highlights small screens, touch input, device use, and varied environments. Evaluate the complete store against the applicable requirements.
Use keyboard, touch, zoom, orientation changes, screen-reader output, and error recovery on navigation, filters, variants, cart, checkout, account, contact, and return tasks. Search visibility is not useful if the landing experience prevents a customer from completing the intended task.
The release owner blocks publication for inaccurate price or stock, broken purchase paths, inaccessible critical controls, conflicting index signals, exposed test URLs, unsupported claims, or missing ownership. Retest after the repair and after production caching settles.
After publication, verify a small production sample through the customer journey and the search-facing signals. Scheduled checks should confirm that later catalog and platform updates did not reverse the approved behavior.
Record the gate result
For every checklist item, record pass, fail, not applicable, or accepted exception. Add the evidence location, reviewer, decision date, and next review. A checked box without proof cannot protect a release. Stop the work when a mandatory privacy, security, data-quality, accessibility, or correction condition fails, even if the remaining score looks favorable.
Store the evidence record with the gate decision so a reviewer can rebuild reasoning without asking anyone, and give the ecommerce SEO checklist a next review date and name the change to bring it forward.
Log rejected options alongside the chosen path; the constraint that ruled them out may later lift. Interface, export, meeting note, and correction log share one set of definitions. When the decision cycle closes, retire unused reports and permissions.
Common questions
How often should the checklist run?
Run the core checks for every relevant release and a broader template audit on a defined schedule.
Can automation replace manual testing?
No. Automation finds repeatable defects, while people verify rendered meaning, task usability, evidence, and business effects.
How many URLs should be sampled?
Cover every template and important state, then add risk-based samples for large categories, variants, locales, and recent changes.
