Category pages
A category page is the landing page for a range query and the hub for everything beneath it. The engine needs enough on it to understand the range and to find the products and subcategories; the shopper needs enough to choose a direction. The elements:
- A title and heading that name the range the way shoppers do (the title tag guide covers templates), with the count and the main refinements visible.
- Introductory content at the top: a short paragraph on what the range is and how to choose, written for the person who typed the query. Longer buying guidance can sit below the grid, visible and useful, not hidden.
- Links to subcategories and indexable refinements, in HTML, so the hierarchy is crawlable — the faceted navigation guide decides which refinements qualify.
- The product grid with crawlable links to each product, product names as anchors, prices and availability in text.
- Links to related guides and content: the buying guide, the comparison, the care instructions.
- Breadcrumbs with
BreadcrumbListmarkup. - Pagination handled as below.
A category page with only a grid can rank on product names and authority alone; one with content ranks for the range and its questions, and converts the shopper who is not yet sure. The breadcrumb trailA trail of links showing a page's position in the site hierarchy, from the home page down to the current page. also gives every product page a link back up to its category.
The shopper's side of the same template, from product cards and filters to the default order and empty results, is covered in the guide to category and listing pages.
Product pages
Google's e-commerce guidance describes the product page as the place where product details are shared with search, and lists the kinds of information it uses. A complete product page has:
- A unique title and description. The manufacturer's text appears on every retailer's site; a page that repeats it offers the engine nothing to prefer. Writing for every product is expensive; the compromise is a template that assembles unique content from structured attributes (material, dimensions, use, compatibility, what is in the box) plus a written paragraph for the products that matter most.
- Specifications in a table, in HTML text, not an image or a PDF.
- Price, availability and shipping in text and in markup, consistent with each other and with the feed.
- Images that follow the image SEO guide: descriptive alt text, responsive sizes, the first image eager-loaded.
- Reviews, with the review markup only where the reviews are real and on the page.
- Questions and answers, for the questions buyers ask before purchasing.
- Identifiers: brand, model, GTIN or MPN where they exist, in the markup, which Google documents help match the product across its surfaces.
- Links out: the category, related products, accessories, the buying guide.
A template that assembles unique product content
A kitchenware retailer with thousands of products cannot write each one. Its product template builds an opening paragraph from attributes — "A three-litre cast-iron casserole with an enamel interior, oven-safe to the stated temperature, suitable for induction, dishwasher-safe lid" — followed by a specifications table, a "best for" line derived from category rules, and the manufacturer's description clearly labelled as such below. For the hundred products that drive most revenue, a writer adds a paragraph of genuine guidance. The result is a catalogue where no two pages read the same, the facts are in text, and the effort went where the revenue is.
When the attribute-built copy is drafted by a language model, the guide to generating product descriptions from catalogue data covers attribute hygiene, banned claims and sampling review across the catalogue.
Product structured data
Google's Product structured data documentation covers the properties that enable product rich results and merchant listings: name, image, description, brand, identifiers, offers with price, currency and availability, aggregate rating and reviews, and shipping and return details. The rules that matter:
- The markup must describe the product on the page and match what the page shows; Google's policies treat markup for content not visible on the page as a violation.
- Price and availability in the markup must match the Merchant Center feed where one exists, or listings are disapproved.
- Review markup is for reviews of that product on that page, not site-wide ratings and not self-serving reviews.
- Variants can be expressed with the product-group pattern, where a parent product group lists its variants with the attributes that distinguish them.
The structured data guide covers implementation and testing (Schema MarkupStructured data vocabulary.); the e-commerce expertise page includes a product schema generator. The product structured data tutorial implements the markup on a product template step by step, from catalogue fields to monitoring.
Variants: one page or many
The decision per attribute is whether people search for it.
| Attribute | People search for it? | Treatment |
|---|---|---|
| Colour of a fashion item | Often | Own URL per colour with its own images and title; parent lists all |
| Size | Rarely | Selector on the parent; no URL change, or parameter canonicalised to the parent |
| Capacity or model number of a device | Often | Own product page per model |
| Pack quantity | Sometimes | Judge by query data; usually selector |
| Material or finish | Sometimes | Judge by query data |
Platform defaults vary: some generate a URL per variant and canonicalise to the parent (Canonical TagTells search engines the preferred URL.); some keep one URL and switch by script. Either is fine as long as variants that deserve indexing have distinct, indexable pages, and the rest resolve to one. The keyword research section provides the query data for the decision.
Pagination and load-more
Google's documentation on pagination and incremental loading recommends: give each page of a list its own
URL (?page=2 or /page/2/), link pages sequentially with crawlable <a> links, do not canonicalise page
two onward to page one (that hides the products listed there), and if "load more" or infinite scroll is
used, also update the URL and expose the paginated URLs so the crawler can reach every product. The
rel="next"/rel="prev" attributes are no longer used by Google for indexing. Each paginated pageSplitting a long list of items, such as products or articles, across a series of numbered pages. may be
indexable or noindexed depending on the store's preference; what must not happen is for products to be
reachable only through script.
Availability, out of stock and discontinued
Product pages change state, and the wrong handling throws away rankings:
| State | Handling |
|---|---|
| Temporarily out of stock | Keep the page live and indexable; set availability in markup; show expected date, alternatives and a notify option; do not redirect or noindex |
| Seasonal | Keep the page live year-round with the content; update availability |
| Discontinued, direct successor exists | Permanent redirect to the successor; update internal links |
| Discontinued, close alternative exists | Keep briefly with a clear notice and the alternative; then redirect or 410 |
| Discontinued, nothing comparable | Keep briefly with alternatives from the category; then 410; remove from sitemap |
| Never coming back, no traffic, no links | 410 and remove links |
The reasoning: a page that has earned links and rankings is an asset, and the engine treats a redirect to an unrelated page as a soft error. Google's e-commerce guidance covers how to signal unavailable products, and the crawling and indexing guide covers status codes.
Pages that end by design rather than going out of stock, such as events, listings and time-limited offers, follow the lifecycle policy in expired listings, events and offers.
Reviews, questions and other user content
Customer reviews and answered questions are the only content on a product page that no competitor can copy, and they answer the questions buyers have in the buyers' own words. Google's e-commerce guidance covers review markup and its policies cover review integrity; beyond compliance, the practical points are: render reviews in the HTML, not only in a widget loaded by script the crawler may not execute; paginate long review sets with crawlable links; moderate for spam and policy without suppressing negative reviews, which raters and shoppers read as a trust signal; and ask for reviews after purchase in a way that does not condition the request on a positive experience. Question-and-answer sections work the same way and, because they are written by buyers, surface the long-tail queries the keyword research missed.
Launching new products
A new product page starts with no links, no history and no reviews, and in a large catalogue it may wait weeks to be crawled. To shorten that: link it from the category page's first page and from related products on launch, include it in the sitemap with an accurate modification date, make sure the template renders its content and markup server-side, submit it through the Merchant Center feed where one exists, and, for products that matter, link it from a launch piece or the homepage for the first weeks. The faceted navigation guide explains why a crawl consumed by filter noiseFilters on a listing page that narrow results by attributes such as brand, size or price, often creating a URL for each combination. is the usual reason new products are slow to appear.
Page experience on catalogue templates
Product and category templates are where Core Web VitalsGoogle's user experience metrics. are usually lost: image galleries, third-party review widgets, recommendation scripts, chat, tracking. The Core Web Vitals guide applies; the store-specific habits are to eager-load the first product image, reserve space for widgets, defer non-essential scripts, and measure the two templates in the field separately.
Measuring template performance
Because the pages are templates, the measurement is by template: impressions, clicks, click-through rate (CTRShare of impressions that result in a click.) and position for category pages as a group and product pages as a group in Search Console, revenue per organic landing page in analytics, and the index coverage of each group in the Page Indexing report. A change to a template moves a thousand pages at once, so the before-and-after is readable in weeks. The SEO KPIs guide covers the reporting.
Platform choice limits how far templates, URLs and structured data can be customised, which the Shopify versus WooCommerce comparison covers for teams planning a build or a move.
Empty categories and stripped-down unavailable products are a common source of soft errors in Search Console; the troubleshooting page on soft not-found errors decides per case whether to add content, redirect or retire the page.
Title patterns for category and product templates can be tested before rollout with the SEO title tag test, which splits the template's pages at random into changed and unchanged groups.
Common mistakes
- Manufacturer descriptions everywhere. Nothing to prefer over the other retailers.
- Grid-only category pages. No range content, no guidance.
- Markup that does not match the page or the feed. Disapprovals and policy violations.
- Page two canonicalised to page one. Half the products hidden.
- Products reachable only by script. Never crawled.
- Redirecting out-of-stock products to the category. Rankings and links thrown away.
- Site-wide ratings as product reviews. A documented markup violation.
- Lazy-loading the first product image. A self-inflicted LCP failure.
The faceted navigation guide is the companion: it decides which filtered views of these category pages become pages themselves.
