# Product page: what it is and what it should include

> What a product page is, what data it carries, how Google and AI assistants read it, and how to check that the text and the markup say the same thing.

URL: https://clione.ai/glossary/product-page/
Lang: en

A product page is the page of a store where one product lives: the one with its photo, its price and the add-to-cart button. It is not the spec sheet PDF the manufacturer sends, nor the product record in the Shopify or BigCommerce admin, although the three look alike: **the record is the stored data, the page is the published data**, and they do not always match. It is the most important page in a store for two reasons that now go together. It is where the buyer decides, and it is the page a search engine or an AI assistant reads when someone asks about that product.

## What it includes

[Schema.org](/glossary/schema-org/) defines a product, the [Product](/glossary/product-schema/) type, as **any product or service that is offered**: a pair of sneakers, a concert ticket, a car rental.[^schemaorg-product] A product page is the page that presents one of them to sell it, and Google makes it clear from the other side: its product results only support pages focused on a single product, or on several variants of the same one, and it recommends marking up product pages rather than pages that list products or a category.[^google-merchant-listing]

What a complete page carries, and what Google's markup for [merchant listings](/glossary/merchant-listings/) calls it:

| Element                                                     | What it is on the page                                | In Google's markup                                                                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Name                                                        | The product's name, the way it is searched            | `name`, required[^google-merchant-listing]                                                                               |
| Images                                                      | Photos where the product can be seen clearly          | `image`, required; the URLs have to be crawlable and indexable[^google-merchant-listing]                                 |
| [Price and availability](/glossary/price-and-availability/) | What it costs and whether it is in stock              | `offers`, with a required [Offer](/glossary/offer-schema/): the store has to be the seller[^google-merchant-listing]     |
| Brand and category                                          | Who makes it and where it fits in the catalog         | `brand.name` and `category`, recommended[^google-merchant-listing]                                                       |
| Ratings                                                     | The average of the store's reviews                    | `aggregateRating`, recommended[^google-merchant-listing]                                                                 |
| Variants                                                    | Sizes, colors or capacities of the same product       | Variant markup, which helps Google understand which products are variations of one parent product[^google-product-intro] |
| Shipping and returns                                        | Costs, timeframes and conditions                      | Shipping details and [return policy](/glossary/return-policy/)[^google-product-intro]                                    |
| Description and features                                    | The text that explains who it is for and what it does | No field replaces it: it is page text                                                                                    |

[Product variants](/glossary/product-variants/) and [product attributes](/glossary/product-attributes/) have their own entries; here it is enough to know they are part of the page, not an add-on.

## How Google and assistants read it

When a page carries product [structured data](/glossary/structured-data/), its information can show up in Google in a richer form, as [rich results](/glossary/rich-results/), also in Google Images and in Lens: **price, availability, ratings or shipping, right in the results**.[^google-product-intro] Google distinguishes two kinds of markup: product snippets, for pages where you cannot buy (a review, for example), and merchant listings, for pages where the customer buys.[^google-product-intro] Only pages where the product can be bought qualify for merchant listings, and Google may try to verify their data before showing it.[^google-merchant-listing]

Google also asks for the data to come by two routes: structured data on the page and a feed in [Google Merchant Center](/glossary/google-merchant-center/). Having both **widens the experiences you qualify for and helps it understand and verify your data**, and some combine them: a product snippet can take the price from the feed if it is not in the markup.[^google-product-intro] The same goes for AI: Google's generative answers can include product listings and information, and Merchant Center feeds help your products show up in them.[^google-ai-guide]

AI assistants read the page as text, and Microsoft gives three warnings that affect many stores: do not hide important answers in tabs or expandable menus, because AI systems may not render hidden content; do not leave key information only in a PDF; and do not put it only in an image, because reading text in images adds complexity and often reduces accuracy. It also asks for context: a page should say "42 dB dishwasher designed for open-concept kitchens", not just "quiet dishwasher".[^microsoft-ai-search]

## In a store

A **fictional example** of before and after, with the provenance of each fact. A camera backpack whose page said little more than its trade name:

| Attribute     | Before            | After                                                         | Where the data comes from                  |
| ------------- | ----------------- | ------------------------------------------------------------- | ------------------------------------------ |
| Name          | "Trek 25"         | "Trek 25 camera backpack, 25 liters"                          | The manufacturer's trade name and capacity |
| Capacity      | Not shown         | 25 liters                                                     | Manufacturer spec sheet                    |
| Rain          | "Water-resistant" | Water-repellent fabric and waterproof cover included          | Manufacturer spec sheet                    |
| Carry-on size | Not shown         | Outer dimensions, so the buyer can compare with their airline | Measured by the store                      |
| Who it is for | Not shown         | One camera with two lenses and a 14-inch laptop               | The store's own test with the product      |
| Rating        | Not shown         | The average of the store's reviews                            | The store's own reviews                    |

The last column is what separates a trustworthy page from one that only sounds good: **every fact has a source someone can check**. A fact with no source is the first one a buyer, or an assistant, doubts.


That a [category page](/glossary/category-page/) can be marked up as if it were a product page. Google rules it out with an example: "shoes in our shop" is not a specific product, and its product results only support pages focused on one product or its variants.[^google-merchant-listing] A category lists products and links to their pages; the product page is the one that sells one.


## How to check it

1. **Open a product page and note what the buyer sees**: name, images, price, availability, variants, shipping and returns.
2. **Find the Product block in the code** and compare it field by field. Google asks for the markup to describe the same thing as the body of the page and not to mark up content the visitor cannot see.[^google-sd-policies]
3. **Validate the markup with the [Rich Results Test](/glossary/rich-results-test/)** and then check with the URL Inspection tool in [Search Console](/glossary/google-search-console/) how Google sees the page, with no `robots.txt` blocks or `noindex`.[^google-merchant-listing]
4. **Compare the page with your Merchant Center feed**: price and availability have to match, because Google combines the two sources.[^google-product-intro]
5. **Look for hidden data**: answers in tabs, measurements in an image or specifications only in a PDF.[^microsoft-ai-search]

## Related concept: product description

The [product description](/glossary/product-description/) is a part of the page: the text that explains what the product is, who it is for and why. The product page is the whole page, with that text, the images, the price, the variants and the buy button. In the industry it is also called a [PDP](/glossary/pdp/), for product detail page. Improving the description does not fix a page that lacks the price in the markup or the measurements; completing the page often does mean rewriting the description.

To keep going, [the catalog and entities reading path](/learn/catalog-and-entities/) puts the other terms in order, the study [from stored data to published data](/studies/stored-vs-published-data/) measures what gets lost along the way, and the guide to [auditing the structured data of a product page](/guides/audit-product-page-structured-data/) breaks it down into steps.