Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Where Store SEO Differs From Site SEO
Stores fail in places service sites never see: hundreds of near-identical product variants competing with each other, filter pages generating endless thin URLs, category pages with no copy at all, and product descriptions pasted from the manufacturer and duplicated across every store selling the same item. This checklist covers only that store layer.
The site-wide fundamentals, Search Console, unique titles, internal links, page speed, are the same for a store as for any other site, and they are already ranked by impact in the site-wide half of the checklist. Do that half first. What follows assumes it is done and deals only with the problems a catalog creates: duplication at scale, template pages that must each earn a ranking, and inventory that changes under your feet. The audience here is a small store, tens to hundreds of products, on Shopify or WooCommerce, run by the owner rather than a team.
The 16-Point Store Checklist
| # | Check | Layer | Time |
|---|---|---|---|
| 1 | Unique product titles written as buyers search: brand, product, key attribute | Product | 5 min each |
| 2 | Descriptions rewritten from manufacturer copy, with your own use guidance | Product | 20 min each |
| 3 | Product schema with price and availability on every product | Technical | 2 h |
| 4 | Review markup only where real reviews exist | Technical | 1 h |
| 5 | One canonical URL per product, variants canonicalized to it | Technical | 2 h |
| 6 | Filter and sort URLs blocked from indexing or canonicalized | Technical | 2 h |
| 7 | Category pages given 100 to 200 words of genuinely useful buying copy | Category | 30 min each |
| 8 | Category-to-product internal links in both directions | Category | 2 h |
| 9 | Image filenames and alt text describing the product plainly | Product | 1 h |
| 10 | Out-of-stock pages kept live with alternatives, not deleted | Inventory | 1 h |
| 11 | Discontinued products 301-redirected to the closest category | Inventory | 1 h |
| 12 | Site search results pages noindexed | Technical | 30 min |
| 13 | A buying-guide page per major category answering pre-purchase questions | Content | Half a day each |
| 14 | Product URLs kept short and stable | Technical | 1 h |
| 15 | XML sitemap limited to canonical, in-stock-or-returning URLs | Technical | 1 h |
| 16 | Search Console checked monthly for which product queries earn impressions | Measurement | 1 h per month |
The ordering is deliberate. Rows 1 and 2 fix the duplication you share with every other store carrying the same catalog: a manufacturer description is, by definition, identical everywhere it is published, so a rewritten description with your own guidance on who the product suits is the cheapest differentiation available. Rows 3 and 4 are the eligibility layer: Product structured data with offers, price, and availability makes products eligible for rich results per Google's documentation, and review markup belongs only on pages showing real reviews. Rows 5 and 6 stop your own store from competing with itself, and everything after that compounds on a catalog that is finally clean.
On a small store the schedule is manageable. The technical rows, 3 through 6 and 12 through 15, are one-time setup that a weekend covers on either platform. The per-product rows, 1, 2, and 9, scale with catalog size, so work through them in order of what sells: your twenty best sellers first, then the rest as time allows, because a rewritten description on a product nobody buys returns nothing. Row 16 is the habit that makes the rest measurable; the monthly look at which product queries earn impressions tells you which category deserves the next buying guide and which titles to rewrite next.
The Variant and Filter Trap, Explained Plainly
Every size, color, and filter combination can mint its own URL, and a 200-product store can quietly serve 20,000 near-duplicate pages. Those pages split ranking signals across copies of the same content and burn crawl attention on URLs no shopper will ever search for. The fix is one canonical URL per product, with variants and filters kept out of the index.
The mechanism is worth understanding, because platforms create the problem silently. A blue version, a large version, and a "sort by price" view of a category are each useful to a shopper on the page, but as separate indexable URLs they are near-copies of a page that already exists. Canonical tags are the standard fix for this variant and filter duplication: variants stay selectable on-page while their URLs point at the one canonical product page, and filter or sort URLs are either noindexed or canonicalized to the unfiltered category.
Spotting the trap takes two minutes. Search site:yourstore.com on Google and compare the result count to your real page count: products, categories, and a handful of static pages. If Google reports several times that number, variants or filters are leaking. If it reports far fewer, you have the opposite problem, and the indexing diagnostic walks through the causes in order of likelihood.
Category Pages: The Money Pages Stores Neglect
Category pages match the commercial queries with real volume. Shoppers search "mens trail running shoes" far more often than any specific SKU, and the page built to rank for that query is the category, not a product. Yet most stores leave categories as bare product grids with a heading and nothing else.
Three changes turn a grid into a ranker. First, 100 to 200 words of genuinely useful copy above or below the grid: what distinguishes the options, who each type suits, what actually matters when choosing. Not keyword filler, buying help. Second, category names that match how buyers search, which is a research question rather than a taste question; the free workflow in our keyword research guide answers it in an afternoon. Third, a buying guide linked from the category and linking back, so the informational query and the commercial query reinforce each other.
Stores with many similar categories face a template problem: the same copy pattern repeated across forty categories drifts into thin duplication. The rules for making template pages each earn their existence are the same as for any page set at scale, covered in the programmatic SEO playbook.
Platform Notes: Shopify and WooCommerce in Practice
Both platforms can execute every row of the checklist. Shopify handles more of the technical layer by default and hides some controls; WooCommerce exposes every control and therefore every way to misconfigure one. The checks below are where each platform typically needs attention.
Shopify. Canonicals are mostly handled by default: variant URLs point at the main product URL without any work from you, which covers row 5 out of the box. Blogs live under shop.example/blogs/ paths, so buying guides will sit at URLs like shop.example/blogs/guides/choosing-trail-shoes, which is fine as long as the category links to them. The common Shopify failure is apps: review and SEO apps can each inject their own Product markup, so check a product page for doubled schema and keep one source of truth.
WooCommerce. More control, more ways to break it. Verify the category archive settings so categories are indexable pages with editable copy, watch for plugin-generated filter URLs that multiply crawlable parameters, and run exactly one SEO plugin, because two will emit conflicting canonicals and duplicate markup. Publishing buying guides and other product-adjacent content on a schedule is the same automation problem as any blog, covered in our guide to automating publishing and handled by the platform integrations directly.
Questions Store Owners Ask About Store SEO
- How is ecommerce SEO different from normal SEO?
The site-wide fundamentals are identical: indexability, titles, internal links, measurement. What changes is scale and duplication. A store multiplies URLs through variants, filters, and sorting, and it inherits manufacturer descriptions that hundreds of other stores also publish. Ecommerce SEO is mostly the discipline of controlling that multiplication and making template pages individually worth ranking.
- Do product pages or category pages matter more for SEO?
Category pages usually match the commercial queries with real volume, because shoppers search for the type of thing before the exact SKU. Product pages close the long tail: specific model numbers, brand-plus-attribute searches, and comparison queries. You need both, but category copy is the commoner gap, since most stores leave categories as bare product grids with nothing for a search engine to rank.
- What schema markup does an online store need?
Product markup with offers, price, and availability on every product page is the core, and per Google's documentation it makes products eligible for rich results. Add review markup only where real customer reviews exist on the page; marking up reviews you do not display invites trouble. Beyond that, standard Organization and Breadcrumb markup is enough for most small stores.
- How do I stop product variants from hurting SEO?
Pick one canonical URL per product and point every size and color variation at it with a canonical tag, which is the standard fix for variant duplication. Let shoppers select variants on the page rather than through separate indexable URLs. Then check the result: search site:yourstore.com on Google and compare the indexed count to your real product count. A large gap means variants or filters are still leaking into the index.
