Missing field "priceValidUntil" (in "offers")

Yes, unless the product is on sale with an end date. The warning is non-critical. Watch for the opposite problem: a priceValidUntil date in the past can stop your product's rich result from showing.

Google describes priceValidUntil as the date after which the price is no longer available, "if applicable". Its docs warn that a listing may not display if that date has passed. So a missing date costs nothing, and a stale one can cost you the rich result.

Check for an old date first

Run a product page through the Rich Results Test and open the offer details, or search the page source for priceValidUntil.
If a date shows and it's in the past, fix that now. It can come from a sale that ended, or a date someone typed into a theme or app once and forgot.
If no date shows and the product isn't on sale, you're done. Leave the warning.

Add it for a sale

Google's sale example puts the sale price in price, the start in validFrom, and the end in priceValidUntil. The old price goes in a priceSpecification marked as a strikethrough price. Use priceValidUntil or validThrough for the end, not both.

Before: sale price, no dates

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Canvas Weekender Bag",
  "image": "https://example.com/photos/weekender-bag.jpg",
  "offers": {
    "@type": "Offer",
    "price": 69,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

After: sale runs November 20 to 30, was $89

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Canvas Weekender Bag",
  "image": "https://example.com/photos/weekender-bag.jpg",
  "offers": {
    "@type": "Offer",
    "price": 69,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "validFrom": "2026-11-20T08:00:00-05:00",
    "priceValidUntil": "2026-11-30T23:59:59-05:00",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "priceType": "https://schema.org/StrikethroughPrice",
      "price": 89,
      "priceCurrency": "USD"
    }
  }
}
</script>

Google asks for the date in ISO 8601 format, with the time and time zone for accuracy.

What your platform does

Shopify

The structured_data filter that Dawn and Horizon use leaves priceValidUntil out, so this warning is common on Shopify stores. It's safe to leave.

WooCommerce

WooCommerce's own markup fills priceValidUntil with December 31 of next year, or with the sale end date when a sale is scheduled. With Yoast WooCommerce SEO, Yoast's help says the date comes from a scheduled sale: Products > your product > Product data > General > Sale price > Schedule.

BigCommerce

Cornerstone sets priceValidUntil to one year from the day the page is built, so the date never falls in the past.

Questions

Is "Missing field priceValidUntil" an error?

No. It's a non-critical issue. The product can still show its price in Google without it.

What date should I use if the price has no end date?

Leave the field out. Google says to use it if applicable. Some platforms fill in a date a year ahead. That's fine as long as the date stays in the future.

My sale ended. Do I need to change anything?

Yes. Remove the sale dates or update them when the sale ends, so the markup shows the current price and no past priceValidUntil.

Sources

Checked on October 8, 2026. Vendors change their tools and docs, so check the source if something looks different.

Missing field "priceValidUntil" (in "offers"): safe to ignore?