Product Schema: Choose Snippets or Merchant Listings
Start with the page's purchase relationship. A merchant selling one product needs different markup from a page comparing offers from other sellers. This complete fictional product example pairs visible facts with Product and Offer JSON-LD. Four Schema.org tests show why a clean vocabulary result alone cannot establish that the page meets Google's merchant-listing requirements.
Copy the complete Product HTML example
Save as product-example.html, inspect the visible facts and paste the complete file into Schema.org's Code snippet test. The product and all URLs are fictional. The image and purchase link do not lead to a working shop.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Harbor Desk Stand — fictional product example</title>
<link rel="canonical" href="https://shop.example/harbor-desk-stand">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://shop.example/harbor-desk-stand#product",
"name": "Harbor Desk Stand",
"description": "A fictional folding aluminum laptop stand, sold as one stand.",
"image": "https://shop.example/images/harbor-desk-stand.jpg",
"sku": "HDS-01",
"brand": {
"@type": "Brand",
"name": "Harbor Example"
},
"offers": {
"@type": "Offer",
"url": "https://shop.example/harbor-desk-stand",
"price": "39.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}
</script>
</head>
<body>
<main>
<p>Teaching example: the product, brand, stock, price and URLs are fictional.</p>
<h1>Harbor Desk Stand</h1>
<p>A fictional folding aluminum laptop stand, sold as one stand.</p>
<img src="https://shop.example/images/harbor-desk-stand.jpg" alt="Harbor Desk Stand" width="800" height="800">
<dl><dt>Brand</dt><dd>Harbor Example</dd><dt>SKU</dt><dd>HDS-01</dd></dl>
<p>Price: <strong>39.00 USD</strong> for one stand, paid once.</p>
<p>Condition: new. Availability: in stock.</p>
<a href="https://shop.example/checkout/harbor-desk-stand">Buy from this merchant</a>
<p>No customer reviews have been supplied.</p>
<p>Replace all example facts, URLs, images and purchase details before real use.</p>
</main>
</body>
</html>
Which Product feature fits the page?
Write down what the page lets the buyer do. Google describes product snippets for product pages where the visitor cannot directly purchase, such as reviews and comparisons. Merchant listings concern products customers can buy from you. Merchant markup can also support product snippets, so these are overlapping opportunities with different requirements, not mutually exclusive labels to add to JSON-LD.
Keep this implementation focused on one product. A list of unrelated products is a different page task; do not relabel a category as the single product in this example. Variants need their own documented treatment. The example intentionally has one stand, one currency and one current offer so that the purchase relationship stays clear.
A Merchant Center feed is another way of supplying product information. Having page markup does not mean a feed, account or product approval exists. This guide implements the page only. Decide separately whether a feed belongs in your operating workflow and who will keep it aligned with the website.
| Page relationship | Route to review | Implementation decision |
|---|---|---|
| Customer buys this product from the merchant | Merchant listings and potentially product snippets | Describe the product and the merchant's Offer; include the product image. |
| Visitor compares sellers and leaves to buy elsewhere | Product snippets | Describe the same product and supported offer information; do not claim merchant-listing support. |
| Page describes a SaaS application | Existing software implementation guide | Choose the truthful application type and check the applicable software requirements. |
What should the single-merchant example contain?
Harbor Desk Stand is an invented folding laptop stand sold for 39.00 USD, paid once. The HTML repeats the name, description, brand, SKU, price, stock and condition shown in JSON-LD. The Product identifier points to this one product; the Offer URL points to its detail page. The visible purchase link represents buying from that merchant.
The copied node uses Product with name, image and offers. Its Offer has a positive price and currency, plus truthful availability and condition for the fictional scenario. Those fields are a deliberately small starting point. Check the current documentation for additional applicable recommendations, including shipping and returns, rather than filling optional properties with guessed policy text.
The image element and JSON-LD reference the same reserved image URL. Its width and height attributes do not establish that a real image exists. Replace the placeholder, fetch the actual file and check that it represents the product and is accessible for crawling and indexing. The external pasted-code tests did not perform that production asset review.
Use one authoritative source for the live offer. Record its commerce field, template or plugin and update owner. Review existing output before inserting another script. If the rendered page and markup already disagree, use the mismatch guide to find the emitter; duplicating the product block can preserve the original conflict.
Can Product schema work without reviews?
For product snippets, Google requires name and at least one of review, aggregateRating or offers. The copied example supplies an offer and contains no reviews. Google's documentation says an offers-only implementation can produce a warning about missing review information. A warning is a prompt to inspect the named recommendation, not permission to invent customer evidence.
If the business has no qualifying reviews, leave them absent. An internal assessment, an AI visibility score or a marketing claim is not a customer rating. Keep genuine future review data consistent with what users can see and with the applicable feature rules. This example does not demonstrate review stars or a price-drop enhancement.
When should Offer become AggregateOffer?
Keep Offer for the merchant's single sale in this example. Use AggregateOffer only when the facts actually describe an aggregation of offers for the same product. Our second page scenario compares two fictional external sellers: the visible range and markup both say 39.00–45.00 USD from two offers. It is not a way to describe two unrelated products or make a merchant appear to offer a broader range.
Product snippets support both types, while merchant listings do not support AggregateOffer. Changing the node's type therefore changes the documented feature fit even when the vocabulary validator remains clean. It also does not turn a comparison page that links out to sellers into a merchant page. Preserve the real purchase relationship when selecting the type.
What did the four validator tests show?
We pasted four complete HTML inputs into Schema.org's public Code snippet test on September 12, 2026. Each produced one top-level Product result with its nested offer. The first was the exact copied HTML. The second removed only the Product image property; its visible image element remained. The third used the two-seller scenario. The fourth added the invented aiVisibilityScore property with value 99.
The counts below are observed Schema.org output. The final column is a separate manual comparison with Google's documentation. No Google Rich Results Test result is claimed. To reproduce the negative vocabulary case, add aiVisibilityScore: 99 as a valid JSON member of Product; do not break JSON punctuation. Remove that invented member before adapting the example.
The missing-image case is particularly useful: an image element in HTML did not fill the missing Product image property, yet Schema.org returned no error. The clean AggregateOffer result likewise did not establish merchant-listing support. Keep the exact input with the tool, date and result so a later change can be reviewed against the same evidence.
| Submitted input | Schema.org errors / warnings | Manual Google requirement comparison |
|---|---|---|
| Single merchant Offer; no reviews | 0 / 0 | Contains the named starting fields. Real facts, page access and feature requirements still need review. |
| Same Product without image markup | 0 / 0 | Missing a required merchant Product property; restore a truthful image value. |
| Two-seller AggregateOffer | 0 / 0 | Supported offer type for snippets; unsupported for merchant listings. |
| Merchant Product plus aiVisibilityScore | 1 / 0 | Remove the unrecognized property. No Google verdict was collected. |
What changes for SaaS and service pages?
Schema.org defines Product broadly enough to include offered services. That vocabulary scope does not establish support by every Google feature. For a SaaS application, use the existing SoftwareApplication implementation guide to decide the truthful type and offer. Switching to Product solely to avoid an unmet software feature requirement does not establish a valid alternative.
Merchant listings also require compliance with Google's free-listings policies. Those policies exclude services and many recurring-billing products, but state an exception for software subscriptions that are prepaid and renew automatically on an annual basis only. Review the exact plan and current policy; neither an unconditional SaaS exclusion nor blanket subscription eligibility is justified. These are free-listing boundaries, not a ban on organic search visibility.
An agency service description can still answer buyers clearly without borrowing the physical-product example. Preserve the true deliverable, charge and purchase terms. The implementation decision should follow those facts. Do not change labels or omit recurring charges to make the page resemble a different kind of product.
What belongs in the production handoff?
Completed fictional decision: retain Product with one Offer for the stand. The exact pasted graph passed Schema.org. The missing-image case needs an image property for the merchant route; the aggregator case belongs in a separate snippet-focused scenario; the invented score must be removed. The reserved shop, product photo, checkout and factual claims remain unverified, so the teaching example is not a completed production release.
For the real page, attach approved product facts, the intended feature, the exact HTML, emitter diff and rollback version. Capture separate vocabulary and Google feature tests. After deployment, inspect the served page, image and purchase path, reconcile visible and structured prices, and record any remaining access or policy checks. Retain the output and date instead of reducing the handoff to a green badge.
RankEcho's Fix Engine supports reviewing a bounded page change and its acceptance record. Preview the sample fix for that handoff. This guide does not describe a native merchant approval service, feed manager or automatic schema deployment. Later search appearances, referrals and buyer actions belong in a separate measurement record; valid markup alone does not establish a gain.
Frequently asked questions
The snippet requirements allow offers as an alternative to review or aggregateRating. This example has an offer and no reviews. Do not invent reviews to fill a recommendation; check the complete requirements for the intended feature.
Google's merchant documentation does not support AggregateOffer. It is supported for product snippets when it describes the actual offers for the same product. Our clean Schema.org result did not change that distinction.
No. Missing merchant image markup and AggregateOffer both returned zero errors in our pasted tests. Review feature requirements, visible facts, access and policies separately; no Google display is guaranteed.
No. Start with the software implementation guide and the real application and billing facts. Free-listing rules have specific exclusions and an annual software-subscription exception; the tangible-product fixture is not a universal SaaS template.
Sources reviewed
Material technical claims below were checked against primary provider documentation. The sources support the documented control or signal, not a guarantee of indexing, ranking, an AI impression, or a citation.
7 claim-level source records
| Claim reviewed | Official source | Review record |
|---|---|---|
| Google distinguishes product snippets from merchant listings by page purpose and purchase relationship. | Google: Product overview | Checked 2026-09-12 · Primary source checked September 12, 2026 · Documentation review; no Google search feature was observed for the fictional shop. · Confidence: High |
| Product snippets accept Offer or AggregateOffer; offers can supply the required alternative to review or aggregateRating. | Google: product snippets | Checked 2026-09-12 · Primary source checked September 12, 2026 · Manual requirements comparison. The three vocabulary-clean fixtures do not establish Google eligibility or a Rich Results Test verdict. · Confidence: High |
| Merchant listing markup requires a product image and an Offer; AggregateOffer is not supported for that feature. | Google: merchant listings | Checked 2026-09-12 · Primary source checked September 12, 2026 · The missing-image and AggregateOffer inputs passed Schema.org despite these documented merchant requirements. No fictional image or checkout was fetched. · Confidence: High |
| Schema.org's Product vocabulary broadly covers offered products and services. | Schema.org: Product | Checked 2026-09-12 · Primary source checked September 12, 2026 · Vocabulary scope does not establish acceptance by a particular Google feature. · Confidence: High |
| Google free listings have exclusions for services and recurring billing, with a stated annually renewed software-subscription exception. | Google Merchant Center: unsupported free listings content | Checked 2026-09-12 · Primary source checked September 12, 2026 · Policy review specific to free listings. Do not generalize it to all organic search or assume every software subscription is excluded. · Confidence: High |
| Structured data should represent current visible content and does not guarantee search display. | Google: general structured data guidelines | Checked 2026-09-12 · Primary source checked September 12, 2026 · The copied HTML repeats its invented product facts visibly; it is not a production facts, access or indexing check. · Confidence: High |
| Schema.org's validator accepts pasted markup and extracts its graph. | Schema.org: validator documentation | Checked 2026-09-12 · Primary source checked September 12, 2026 · Four complete HTML inputs were submitted through Code snippet mode. Three returned zero errors and warnings; the invented aiVisibilityScore property returned one error and zero warnings. · Confidence: High |