Every product page gets a silent list of questions from the person looking at it. How big is it. What is it made of. What does it cost to get here. What happens if it is wrong. The page either answers those or sends the shopper off to ask somebody, and most shoppers do not ask.
This post follows what Google’s own documentation says a product page should contain and adds the questions that sit behind each item.
What the buyer is asking

Start with the buyer’s side, because the markup is only a way of writing the same answers in a form a machine can read.
Two situations are worth planning for with made-to-order goods. Offering too many customizations makes every piece different, which makes the pieces hard to track and hard to remake. And a customer who sees work on social media may ask for an exact remake of a piece seen there. Both of those are questions a product page can answer before a message ever arrives: what can be changed on this piece, what cannot, and whether the piece in the photo is the piece being sold or a one-off that is gone.
A short list of the standing questions covers most products:
- What exactly is this, and what is it called?
- What does it look like from more than one angle?
- What is it made of, and what size is it?
- What does it cost, and is it available now?
- What does shipping cost and how long does it take?
- What happens if it is wrong?
- Is this the exact item, or a variation?
That list is not Google’s. It is the list a counter person answers all day. The reason to start there is that the next section, Google’s list, turns out to be the same list with different labels.
The fields Google asks for
Google’s product structured data overview describes two kinds of markup. Product snippets are for pages where people cannot buy the product directly, such as an editorial review. Merchant listings are for pages where customers can buy from you, and they support more detail, including apparel sizing, shipping details and return policies. The two overlap, and the page adds that providing more properties can make a page eligible for more enhancements.
The merchant listing guidelines name three required properties:
- name, the product’s name
- image, with multiple high-resolution photos recommended in 16×9, 4×3 and 1×1 aspect ratios, at URLs Google can crawl and index
- offers, which has to be a single Offer and not an AggregateOffer, because the merchant must be the seller
Recommended properties include a description, which the page strongly recommends, along with brand, color, category, aggregate rating and the product identifiers called GTINs. For product snippets, the product snippet page requires a name plus one of review, aggregate rating or offers, and a price if offers is used.
Set that next to the buyer’s list and the correspondence is plain. What is it: name. What does it look like: image. What is it made of and how big: description, color, and the product-specific properties. What does it cost: the price inside offers. The questions are the same. The difference is only whether a shopper or a crawler is asking them.
Price, availability, shipping and returns

Google’s description of what merchant listings can show includes ratings, shipping costs, availability and return information. The page says the more product information is provided, the more a search experience has to work with, and that each experience decides how and whether to display any enhancement. It also says Google calculates price drops itself from observed price changes and does not guarantee they appear.
That last point is the honest limit of the whole subject. Markup makes a page eligible. It does not buy a placement.
Returns get a slightly different home. In Google’s ecommerce structured data page, return policies are covered through Organization markup and through Merchant Center guidance, which recommends sharing return policies on your site. The product overview adds that merchant return policy markup is nested under Organization markup. In plainer words, the return policy lives at the business level and the product page points to it, so a page that says “see our returns” with no actual return terms is answering nothing.
Shipping is where small makers tend to feel the strain, because a handmade piece ships on its own timeline. The ecommerce page says nothing about shipping policies, while the merchant listing page’s examples include shippingDetails on the Offer. The practical answer is to put the shipping cost and the made-to-order timing in the visible text. That wording does not come from Google. It follows from the buyer’s question, and a visible sentence helps the person even if no markup is attached.
The post on returns and refund policies covers the policy itself.
Variants and addresses

Most products come in more than one size or color. Google’s guidance on ecommerce URLs says each variant should get its own URL, either as a path segment or a query parameter. If you use optional query parameters for variants, the canonical URL should be the version without them. Variant pages that have their own URLs should point the canonical tag to the main product URL.
The same page tells sellers to prefer descriptive words in URL paths over bare numeric IDs, to use persistent URLs rather than ones carrying session IDs or tracking codes, and to use ordinary links that name the product rather than generic phrases like “click here.” The merchant listing page adds that each page should focus on a single product or variants of one product, and that product markup belongs in the initial HTML when possible, because markup generated by JavaScript can make crawls less frequent and less reliable.
None of that is glamorous. It is the bench work under the page, comparable to labeling bins before the shelves go up. A page whose address changes on every visit gives the buyer a worse experience and gives Google two copies of the same thing.
The earlier post on naming a product for search goes into the title side of this.
The page for the person
Markup answers the machine. The words answer the shopper, and Google’s guidance on helpful content says the two are judged differently. Its self-assessment questions ask whether the content shows first-hand experience, such as having used a product, whether it offers original information instead of rewriting other sources, and whether a reader will finish feeling they learned enough to reach their goal. Google states that of the E-E-A-T qualities, “Of these aspects, trust is most important.” Warning signs it lists include content made mainly to attract search visits, and targeting a word count.
The separate page on writing high-quality reviews is aimed at reviewers, not sellers, but the habits transfer. It tells reviewers to support claims with their own photos or other evidence, to concentrate on the few factors that most affect a purchase, to explain how design choices affect everyday users, and to say what distinguishes a product from alternatives. A maker is in a better position to do all four than a stranger with a free sample.
In practice, that means measurements in the description instead of a word like “spacious,” the actual thickness and type of the material, and a plain sentence on what the piece is not suited for. The post on writing product descriptions for handmade goods takes that further.
There is a tension here. A page that answers everything runs long, and a long page can bury the price and the buy button. The usual remedy is order: the facts a shopper needs to decide go near the top, and the detail goes below for the shopper who wants it. Google’s documents do not say how long a product page should be, and the helpful content page specifically warns against writing to a word count.
What the markup cannot fix
A few boundaries in the same documents are worth knowing before spending an afternoon on structured data. Merchant listing eligibility applies only to pages where a shopper can buy the product, not pages that link to other sellers. Products promoting widely prohibited or regulated goods, such as firearms, tobacco, vaping or gambling, are not allowed. And the product overview notes that Merchant Center feeds and page markup can work together, with product snippets sometimes taking pricing data from a merchant feed when the page markup lacks it.
Beyond that, the order of work matters more than the vocabulary. Get the visible page right first: clear photos, true measurements, shipping and returns written out. Then add the markup that describes what is already there. Markup that describes a page which does not contain the answers is a label on an empty box.
For informational purposes only. Google’s documentation changes, and this post reflects the pages as read on the day it was written; check the current versions before editing a live store.
Sources
- Google Search Central, Product structured data: https://developers.google.com/search/docs/appearance/structured-data/product
- Google Search Central, Merchant listing structured data: https://developers.google.com/search/docs/appearance/structured-data/merchant-listing
- Google Search Central, Product snippet structured data: https://developers.google.com/search/docs/appearance/structured-data/product-snippet
- Google Search Central, Structured data for ecommerce sites: https://developers.google.com/search/docs/specialty/ecommerce/include-structured-data-relevant-to-ecommerce
- Google Search Central, URL structure for ecommerce sites: https://developers.google.com/search/docs/specialty/ecommerce/designing-a-url-structure-for-ecommerce-sites
- Google Search Central, Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search Central, Write high quality reviews: https://developers.google.com/search/docs/specialty/ecommerce/write-high-quality-reviews
- Video: https://www.youtube.com/watch?v=Gw8ZADoEqbU
