Inventory and price freshness

What the scanner requests

• /products
• /shop

It also reads documents it has already fetched: $home.

What is measured

Profile-scoped: reported as not scored and excluded from the denominator unless the e-commerce or marketplace profile has been positively identified, and this check never creates that identification itself. In scope, the scanner flattens the Product/Offer JSON-LD it already holds from the homepage and, when reachable, /products and /shop, and passes every Offer that carries an availability from the schema.org ItemAvailability set (InStock, OutOfStock, PreOrder, BackOrder, SoldOut, LimitedAvailability) together with an ISO-date priceValidUntil; an Offer with availability but no price validity is a partial (0.7), and an Offer with neither is a fail.

Reproduce it yourself

You do not have to take our word for any of this. Run the same measurement against your own domain:

              DOMAIN=shop.example.com
curl -sL "https://$DOMAIN/" | perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' | jq -r '.. | objects | select((."@type"? | if type == "array" then .[] else . end) == "Offer") | [(.url // "NO url"), (.availability // "NO availability"), (.priceValidUntil // "NO priceValidUntil")] | @tsv'
            

The fix

This is the artifact to ship. It is the complete change, not a description of one.

              {
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Aurora Desk Lamp",
  "sku": "ADL-100-BLK",
  "offers": {
    "@type": "Offer",
    "url": "https://shop.example.com/products/aurora-desk-lamp",
    "price": "1299.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2026-12-31"
  }
}
            

Standards referenced

• schema.org/Offer

Related checks