Ecommerce SEO
Ecommerce SEO Checklist: 30 Checks for UK Online Shops
An ecommerce SEO checklist tests whether shoppers can find, understand and buy from your category and product pages. Start with crawl and indexing access, then check category intent, product information, structured data and stock handling. These 30 checks give each issue an owner and pass test, so fixes can be prioritised rather than counted.
Before ticking a box, choose a sample: your homepage, two high-value categories, two products in stock, one out-of-stock product and a filtered category URL. Add more templates if your shop has them. Run the checks against real rendered pages on desktop and mobile. A checklist of green tool scores is of little use if customers cannot locate the right item or understand delivery and returns.
How do you use this ecommerce SEO checklist?
Work from site-wide access to the pages with commercial value. This site architecture review shows whether categories lead to products without forcing shoppers through search. Record the affected URL, evidence, owner and fix date for every failed check. A developer usually owns crawling, templates and structured data; a merchandiser owns taxonomy, stock and product facts; an editor owns explanatory copy and internal links. One person may hold several roles in a small shop.
Use Google Search Console to inspect index status and query performance, a browser to test navigation, and your platform's product feed or Merchant Center diagnostics where applicable. Google provides a dedicated ecommerce search documentation hub. Its advice helps you check site structure and product information, but passing a check does not guarantee a ranking or rich result.
- Select representative URLs. Include a category, an in-stock product, an unavailable product and a filtered view, then add every distinct shop template.
- Run the 30 checks in order. Verify access first, then category and product information, shopping data and purchase tracking.
- Record each failure. Save the affected URL, observed evidence, responsible owner and a test that will prove the fix worked.
- Fix and retest by impact. Start with issues affecting important pages or whole templates, then repeat the failed check on several URLs.
Which crawl and index checks matter first?
The first eight checks establish whether important URLs can be discovered and considered for search. A product cannot earn organic clicks from a page that is unintentionally blocked or excluded, while an endless combination of filters can distract crawlers from the pages you actually want surfaced.
| # | Check and pass test | Evidence | Owner |
|---|---|---|---|
| 1 | Important categories return a working page and are linked from navigation. | Browser crawl from the homepage | Developer |
| 2 | Priority products are linked from categories or relevant guides. | Click path to sampled products | Merchandiser |
| 3 | Intended search pages are indexable and have no accidental noindex. | Search Console URL Inspection | Developer |
| 4 | robots.txt allows crawling of important pages and assets. | Robots file and URL test | Developer |
| 5 | XML sitemap lists canonical, useful URLs rather than blocked or redirected ones. | Sitemap sample and index report | Developer |
| 6 | Each intended index page has a suitable canonical URL. | Rendered canonical tag and URL Inspection | Developer |
| 7 | Filter and sort URLs have a deliberate crawl/index strategy. | Sample parameter URLs | Developer |
| 8 | Broken, redirected and soft-404 product links are resolved or intentionally handled. | Crawl report and browser test | Developer |
Do not use robots.txt as a substitute for removing an indexed URL: Google documents separate crawling and indexing controls. For faceted navigation, decide which filtered combinations have real search demand and unique value. Keep the others from multiplying into thousands of thin, near-duplicate URLs. Google explains ecommerce URL structure and site hierarchy in its own documentation.
How should category pages be checked?
Category pages usually answer broader shopping needs than individual products. Compare their search intent with the product pages they link to. The page should help a customer compare a range, narrow it and reach suitable items. A title that says only “Shop” or a category description that repeats the same line across 40 pages gives neither the shopper nor the search engine much context.
| # | Check and pass test | Evidence | Owner |
|---|---|---|---|
| 9 | The category name matches the product range and likely shopper language. | Search result review and on-page sample | Merchandiser |
| 10 | Title tag and H1 describe the distinct category without conflicting promises. | Rendered page and source | Editor |
| 11 | Intro copy explains how to choose, where explanation helps the shopper. | Customer task test | Editor |
| 12 | Filters use useful attributes such as size, material or compatibility. | Product selection test | Merchandiser |
| 13 | Sorting and pagination leave products reachable by normal links. | Crawl and click-through | Developer |
| 14 | Related subcategories and buying guides use descriptive internal links. | Link path sample | Editor |
| 15 | Category images and text are usable on a mobile screen. | Mobile browser test | Developer |
Do not fill the top of every category with a long SEO essay. Put concise choice guidance where shoppers need it, then offer deeper help lower on the page or in a linked buying guide. If your shop has different uses for similar products, use subcategories only when they help customers navigate and contain enough distinct products to justify the division.
What makes a product page search-ready?
A product page should identify the exact item and answer purchase questions accurately. Manufacturer text can supply specifications, but your page also needs the details your customers rely on: dimensions, compatibility, delivery, returns, variations and current availability. Never invent test results or customer experiences to make a page appear unique.
| # | Check and pass test | Evidence | Owner |
|---|---|---|---|
| 16 | Product title names the item and distinguishing model or variant. | Page and feed comparison | Merchandiser |
| 17 | Description explains use, fit and limitations in the shop's own accurate language. | Product-page review | Editor |
| 18 | Price, availability and selectable variants agree with checkout. | Live purchase test | Merchandiser |
| 19 | Images show the actual product, have descriptive alternative text where needed and load well. | Media and mobile test | Editor |
| 20 | Specifications answer common compatibility or sizing questions. | Support-ticket sample | Merchandiser |
| 21 | Delivery and returns information is visible and current. | Policy and checkout comparison | Merchandiser |
| 22 | Product reviews, if shown, are genuine and attached to the correct item. | Review source audit | Merchandiser |
| 23 | Product variants have deliberate URLs, canonicals and inventory behaviour. | Variant URL sample | Developer |
The proof for checks 18 and 21 is operational, not just technical. A crawler may see valid markup while the checkout tells a different story. Ask the shop team to test an actual purchase path, including a postcode and delivery option, before calling the page complete.
Which shopping data and technical checks remain?
Structured data and feeds describe products to search systems, but they should reflect what a shopper sees on the page. Google documents product data sharing through markup and Merchant Center. Keep identifiers, prices and stock synchronised at the source rather than fixing mismatches in three places by hand.
| # | Check and pass test | Evidence | Owner |
|---|---|---|---|
| 24 | Product structured data is valid and matches visible product details. | Rich Results Test and page | Developer |
| 25 | Feed data, if used, matches landing pages and inventory. | Merchant Center diagnostics | Merchandiser |
| 26 | Shipping and returns data is accurate in the feed or markup where supplied. | Feed and policy comparison | Merchandiser |
| 27 | Core Web Vitals are checked on real category and product templates. | Search Console and field data | Developer |
| 28 | Mobile menus, filters and add-to-basket controls work with touch and keyboard. | Device and keyboard test | Developer |
| 29 | Search Console tracks product/category clicks separately enough to spot changes. | Performance page filter | Analyst |
| 30 | Organic visits can be connected to add-to-basket and purchase outcomes. | Analytics test transaction | Analyst |
If check 24 fails, do not simply add more schema properties. Compare the generated JSON-LD with the rendered product and Google's structured data guidance for ecommerce. If check 27 fails, identify the affected template and users before paying for a site-wide rebuild. Our technical SEO checklist covers broader site diagnostics.
How should UK shops handle out-of-stock products?
Keep a temporary out-of-stock product page available when customers may still search for it, especially if restock is expected. State availability clearly, remove any misleading purchase action and offer a relevant alternative or notification. Update product markup and feeds from the same stock source. If the item is permanently discontinued, decide whether the page still helps customers with specifications, compatible accessories or a genuine replacement.
| Stock situation | Page decision | Shopper next step |
|---|---|---|
| Short temporary shortage | Keep useful page live; show out-of-stock status | Notify or show real alternatives |
| Seasonal item likely to return | Preserve page and explain expected season only if known | Offer notification or related category |
| Discontinued with close successor | Keep comparison if useful, or redirect only to a genuinely relevant successor | Explain the replacement |
| Discontinued with no useful content or replacement | Remove or return an appropriate status after checking links and demand | Navigate to the nearest honest category |
Do not redirect every discontinued product to the homepage. That breaks the customer's search journey and can create a soft 404. Test any redirect against intent: the replacement should solve substantially the same need. Also keep customer-service and inventory teams informed, because a technically correct page with wrong stock information still fails.
How do you prioritise the 30 checks?
First fix issues that prevent important pages from being found or bought from. Then improve pages with demand but weak click-through or conversion. Use a simple three-part score: affected commercial value, number of URLs affected and confidence in the diagnosis. A broken canonical on an entire product template is usually more urgent than a missing adjective on one low-demand description.
Create one ticket for each root cause, with an example URL and acceptance test. Recheck the template after deployment and inspect a few other URLs to ensure the change did not introduce a new problem. If the catalogue is large or the platform has complex filters, our ecommerce SEO service can help turn this checklist into a prioritised implementation plan.
01What is the first ecommerce SEO check?+
Check that your valuable category and product pages are accessible and intended for indexing. A page hidden from navigation or accidentally marked noindex cannot contribute as expected, however polished its copy is.
02Should every product have a unique description?+
Each important product should give shoppers accurate details that distinguish it. Rewriting shared specifications into awkward synonyms adds little; focus on use, fit, limitations and evidence you can verify.
03Do filtered pages need to be indexed?+
Only selected filtered pages need indexing when they meet real search demand and provide a useful distinct result. Most sorting and parameter combinations need deliberate crawl and canonical handling so they do not multiply low-value URLs.
04Does product schema guarantee rich results?+
No, valid structured data makes product details machine-readable but does not guarantee display. The details must match the visible page, and Google decides which features to show.
05Should I remove out-of-stock products?+
Not automatically; temporary shortages can leave a useful product page in place with honest availability and alternatives. Permanent removal needs a decision based on demand, replacement relevance and the page's remaining usefulness.
06How should variants be handled?+
Variants need consistent URLs, canonical signals and stock details that fit how shoppers choose them. Test real colour or size selections because platform defaults can create duplicate pages or mismatched offers.
07Is a category page more important than a blog post?+
A category page is usually closer to a purchase for a broad product query. A buying guide earns its place when it helps customers choose and links to appropriate categories or products.
08How often should this be re-run?+
Run it after major platform, catalogue or template changes and review the highest-value pages regularly. The right frequency depends on how quickly products and inventory change, so record failures and trends rather than setting a universal interval.
09Do I need paid tools?+
No, a small shop can work through the main checks with its storefront, Search Console, browser and analytics. A paid crawler can save time on a large catalogue, but it cannot decide which problems matter to your customers.
10What if I fail most of the checks?+
Group failed checks by root cause and fix the ones affecting whole templates or valuable pages first. Keep the evidence and retest after each change so a long list becomes a short, ordered implementation plan.
11What should a small shop do without a developer?+
Start with accurate product facts, category names, internal links and clear policies in the platform controls you already have. Escalate crawl, canonical, speed and schema problems to someone who can test template code safely.
12Are Core Web Vitals enough to judge mobile SEO?+
No, field speed metrics do not show whether filters, menus or checkout controls are usable. Test the buying journey on a phone as well as the measured template performance.
13Can an ecommerce SEO audit cover the same checks?+
Yes, an audit should diagnose these areas and rank fixes by impact and effort. This checklist gives the shop team pass tests and owners so the audit can become actionable work.
Free SEO audit
Get a straight answer on what to fix first.
Request a free SEO audit and we will come back with the largest constraint on your organic growth and the first practical fix. No sales sequence.
Prefer to hire through Upwork? Hire me on Upwork