Product Schema for Google Shopping: Complete Guide (2026)

Product schema is JSON-LD structured data, defined by schema.org, that you embed on product pages so Google can read prices, availability, brand, ratings, and other attributes without parsing visible HTML. For Google Shopping, valid Product schema is effectively required: it's one of the most common failure patterns we see, and missing or invalid schema triggers "landing page requirements" disapprovals plus reduced impression share for products that do serve.

Why Product schema matters for Shopping

Three reasons:

1. Cross-validation with the feed. Google compares your feed's price, availability, and brand against what the page schema says. Mismatches disapprove.
2. Rich Results in Search. Product schema unlocks rich snippets in organic Search (price, rating, availability shown directly in SERP).
3. Performance Max ranking signal. PMax weights well-structured landing pages higher than poorly-structured ones, even when both pass standard Shopping requirements.

Required fields

For Google Shopping eligibility, Google requires these fields [1]:

Field	Type	Notes
name	string	Product title, ideally matching feed title
image	URL or array	Primary image, must be reachable, no auth
offers.price	number/string	Match the feed price exactly
offers.priceCurrency	ISO 4217 code	"USD", "EUR", "GBP", etc.
offers.availability	URL enum	https://schema.org/InStock, OutOfStock, PreOrder, etc.

Recommended fields

Add these to maximize Shopping ranking and rich-result eligibility:

• brand (string or Brand node) — strongly affects Shopping ranking
• sku (string) — useful for variant-level tracking
• gtin or gtin8/12/13/14 (string) — Google's preferred identifier
• mpn (string) — for branded items without GTIN
• description (string) — improves rich-result coverage
• aggregateRating (AggregateRating node) — unlocks rating stars in Search
• review (Review array) — for individual review display
• offers.priceValidUntil (date) — required for sale prices
• offers.itemCondition (URL enum) — schema.org/NewCondition by default
• hasMerchantReturnPolicy (MerchantReturnPolicy node) — required for return badge eligibility

Full reference example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Wireless Headphones, Black",
  "image": [
    "https://example.com/products/acme-headphones-1.jpg",
    "https://example.com/products/acme-headphones-2.jpg"
  ],
  "description": "Acme noise-cancelling wireless headphones with 40-hour battery life.",
  "sku": "ACME-WH-001-BLK",
  "gtin13": "0840000123456",
  "brand": { "@type": "Brand", "name": "Acme" },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/acme-wireless-headphones",
    "price": "199.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "priceValidUntil": "2026-12-31",
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": 247
  }
}
</script>

Common schema bugs that disapprove products

1. priceCurrency missing

The price is "29.99" but no currency is declared. Google does not know if USD, EUR, or CAD. Fix: always populate priceCurrency with an ISO 4217 code.

2. availability as plain text

The value is "In Stock" or "true" instead of the URL https://schema.org/InStock. Google's parser is strict here. Fix: use the full schema.org URL.

3. Image URL not reachable or requires auth

The image link redirects, returns 404, or requires authentication. Fix: serve images at stable public URLs.

4. Multiple Product schemas on the same page

Theme emits one Product node, an SEO plugin emits another, a review app emits a third. Google picks one and may pick the wrong values. Fix: audit page source, disable all but one source.

5. priceValidUntil missing on sale prices

You have a sale price with no end date in the schema. Google strips the rich result. Fix: include priceValidUntil for any product where the price is time-limited.

6. Brand as a string when Google expects a node

Some Shopify themes emit "brand": "Acme". Google now requires Brand to be a node: "brand": { "@type": "Brand", "name": "Acme" }. The string form still works but emits a warning.

Validation workflow

1. Pick 5 random products (a high-price item, a variant-heavy item, a sale item, a low-stock item, a free-shipping item).
2. Run each through Google's Rich Results Test [4]. Confirm Product schema passes with no errors and only minor warnings.
3. Cross-check with Schema.org's Markup Validator [5] for strict spec compliance.
4. Use Search Console's URL Inspection to fetch the page as Googlebot and confirm the rendered HTML includes the JSON-LD block.
5. Compare schema values against feed values for each product. Mismatches must be resolved before going live.

Bottom line

Product schema is the contract between your landing page and Google's Shopping infrastructure. Get the five required fields right, add the recommended ones for ranking and rich results, audit for common bugs, and validate on a sample. Most schema disapprovals come from one of six recurring bugs covered above; fixing those resolves nearly all "landing page requirements" flags we see.