On July 7, 2026, Google's documentation update log recorded two additions for merchant listings. One covers the category property on Product. The other covers how to state when a sale price starts and ends.
If your Product markup shows a temporary price, start with the sale dates. Add validFrom and validThrough, or priceValidUntil on the Offer, and keep the product page, the checkout and your Merchant Center feed on the same price for the same days.
Stores without sales can leave the timing fields alone for now and still add the category. Google describes category as recommended for this feature, while the active price and the currency remain the required fields.
What Google documented on July 7, 2026
Google's Search Central documentation updates list the change in two parts. The first part says the merchant listing documentation now explains how Product.category can carry plain text, a CategoryCode, or both, and that this lines up with the product_type and google_product_category attributes in a Merchant Center feed.
The second part says the merchant listing guide gained a section on sale duration. It explains how validFrom, validThrough and priceValidUntil set the effective range of a sale price, with examples for placing them on an Offer or on a PriceSpecification.
Both entries describe documentation and supported markup, and valid markup is not a promise of a merchant listing. Make the page, the JSON-LD and the feed describe one product, one price and one set of dates.

Google's merchant listing documentation is the place to confirm the current property rules before you change a template, because the page is edited over time.
Add a category as text, a CategoryCode, or both
Product.category can hold a plain text value such as "Jackets". Google documents that form as the counterpart of the product_type attribute in Merchant Center, which is your own category structure. If your shop already organizes products as Jackets, Candles or Dresses, the text value is where that structure goes.
The second form is a CategoryCode object. It stands for a Google Product Category, the counterpart of google_product_category. It needs an inCodeSet with Google's taxonomy URL and a codeValue holding either the category path or its numeric ID. A numeric ID without the taxonomy URL in inCodeSet leaves the value without its code set, so keep the two together.
You can also use an array that mixes both forms, which is how the example below is written. Schema.org defines category as accepting text, a CategoryCode and other value types, so the array is valid vocabulary as well as supported by Google's merchant listing page.
Keep the two meanings apart when you fill them in. The text value should match what you send as product_type, and the CategoryCode should match what you send as google_product_category. Putting a Google taxonomy path in the text slot, or your own shop category in a CategoryCode, mixes the two systems.
State when the sale starts and ends
A sale price is only true for a stretch of time, so the markup can now say when. On an Offer, use validFrom for the start together with either validThrough or priceValidUntil for the end. On a PriceSpecification, use validFrom and validThrough; Google says priceValidUntil does not apply there.
Use ISO 8601 date-time values with a time zone, for example 2026-07-07T23:59:59-05:00. The time zone matters for a promotion that ends at a set local time, such as midnight at your shop. The start must be earlier than or equal to the end.
The active sale price stays in the Offer as its current price, with priceCurrency. If you also want to show the regular price crossed out, Google documents a PriceSpecification whose priceType is https://schema.org/StrikethroughPrice. That part is optional for this Google feature, and the strikethrough price is never a replacement for the active price.
Product markup before and after
The first block is a sale offer written the way many templates still print it. It carries the sale price and a text category, with no statement of when the sale ends. The product, URLs and prices are fictional and use example.com.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Trail Jacket",
"image": [
"https://example.com/images/example-trail-jacket.jpg"
],
"description": "A fictional lightweight trail jacket.",
"sku": "ETJ-100",
"category": "Jackets",
"offers": {
"@type": "Offer",
"url": "https://example.com/products/example-trail-jacket",
"price": "79.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}Replace the name, sku, URLs, image and price with your own product. Nothing here says when the price stops applying, and the only category is your own.
The second block adds a CategoryCode beside the text category and a sale window on the Offer. Change the two dates to your real sale, keep the offset that matches your time zone, and replace the category path with the Google Product Category that fits the product.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Trail Jacket",
"image": [
"https://example.com/images/example-trail-jacket.jpg"
],
"description": "A fictional lightweight trail jacket.",
"sku": "ETJ-100",
"category": [
"Jackets",
{
"@type": "CategoryCode",
"inCodeSet": "https://www.google.com/basepages/producttype/taxonomy-with-ids.en-US.txt",
"codeValue": "Apparel & Accessories > Clothing > Outerwear > Coats & Jackets"
}
],
"offers": {
"@type": "Offer",
"url": "https://example.com/products/example-trail-jacket",
"price": "79.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"validFrom": "2026-06-29T00:00:00-05:00",
"validThrough": "2026-07-07T23:59:59-05:00"
}
}If you want the regular price shown as a strikethrough, add a priceSpecification inside the Offer, as in the third block. Set its price to the regular price, and keep the Offer price as the sale price.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Trail Jacket",
"image": [
"https://example.com/images/example-trail-jacket.jpg"
],
"description": "A fictional lightweight trail jacket.",
"sku": "ETJ-100",
"category": [
"Jackets",
{
"@type": "CategoryCode",
"inCodeSet": "https://www.google.com/basepages/producttype/taxonomy-with-ids.en-US.txt",
"codeValue": "Apparel & Accessories > Clothing > Outerwear > Coats & Jackets"
}
],
"offers": {
"@type": "Offer",
"url": "https://example.com/products/example-trail-jacket",
"price": "79.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"validFrom": "2026-06-29T00:00:00-05:00",
"validThrough": "2026-07-07T23:59:59-05:00",
"priceSpecification": {
"@type": "PriceSpecification",
"price": "99.00",
"priceCurrency": "USD",
"priceType": "https://schema.org/StrikethroughPrice"
}
}
}For the full set of Product fields beyond these, the JSON-LD schema examples guide shows other types written the same way. The Product schema generator builds a starting block you can then extend with the category and the dates.
Keep the Merchant Center feed in step
Merchant Center describes the same facts with feed attributes. price holds the regular price, sale_price holds the temporary lower price, and sale_price_effective_date holds the sale window as an ISO 8601 start and end separated by a slash. product_type and google_product_category hold the two category forms.

price: 99.00 USD
sale_price: 79.00 USD
sale_price_effective_date: 2026-06-29T00:00-0500/2026-07-07T23:59-0500
product_type: Jackets
google_product_category: Apparel & Accessories > Clothing > Outerwear > Coats & JacketsCompare this block with the second JSON-LD example. The sale window, the sale price and both categories describe the same jacket in two places. Google's Merchant Center help says the sale price is submitted in addition to the regular price and should match the landing page and the checkout. The help pages for sale price effective date and the product data specification cover the feed side in full.
A feed is not schema.org markup, and sale_price_effective_date is not a schema.org property. The two are separate channels that Google's documentation now describes in matching terms, so a change to the dates in one place needs the same change in the other.
Make the product markup readable for Bing and AI search
Bing's structured data help says Bing supports schema.org markup for products and offers. Valid Product and Offer JSON-LD, a visible price and a crawlable product page are the baseline for Bing, and for Copilot Search, which Microsoft describes as using information available on the web. Treat CategoryCode and the sale-date fields as Google's merchant listing guidance.
Yandex documents its own product information markup: a product name, a description, a price and a currency. Check that page before reusing Google's fields there. For the full comparison across systems, see whether AI systems use schema markup.
Mistakes to check before a sale goes live
Most problems with timed prices come from markup that no longer matches the page. Go through these before each sale and again after it ends:
- An expired
validThroughorpriceValidUntildate left in the markup. - A sale price in the JSON-LD while the page or the checkout still shows the regular price.
- A future sale price published before the page visibly shows that price.
- A start and end written in the wrong order.
- No time zone on a promotion that ends at a set local time.
- A Google Product Category ID in
codeValuewithout the taxonomy URL ininCodeSet. - A category page marked up as if it were a single product.
Product variants add one more check. Each Offer should describe the variant a shopper is actually buying, with the price and dates for that variant.
Check the markup and clean up when the sale ends
Paste the page into Google's Rich Results Test to see whether the markup parses and whether the product qualifies for the feature. Google says that test checks syntax and eligibility, and it does not guarantee display. Run the Schema Markup Validator as well if you want to confirm the vocabulary, such as the category array and the PriceSpecification fields.
Then inspect the live URL in Search Console, so you are looking at the page Google fetches rather than the template you edited. After Merchant Center processes the feed, compare its price, sale window and categories with the page. The guide on fixing missing field warnings walks through reading a warning once a test flags one.
Plan the end of each sale as a task. When a promotion closes, remove the sale dates or replace them with the next window, restore the regular price in the Offer, and update the feed on the same day. An expired date left in place is the most common way a store's markup drifts from its checkout.
Questions people ask
Is Product.category required for Google merchant listings?
No. Google documents category as recommended for this feature, while the active price and currency are required on the Offer. Add it when you can state a category you also use in your feed.
Should sale dates go on the Offer or on a PriceSpecification?
On the Offer, use validFrom with validThrough or priceValidUntil. On a PriceSpecification, use validFrom and validThrough, because Google says priceValidUntil does not apply there. For most stores the Offer is the simpler place.
Does this change apply to Bing or Copilot?
Bing's documentation describes support for schema.org Product and Offer markup. Keep your markup valid and the visible price clear, and treat the new fields as Google's documented guidance.
Do I need both a regular price and a sale price?
Merchant Center asks for the sale price in addition to the regular price in the feed. In JSON-LD the Offer carries the active sale price, and the regular price appears only if you add the optional strikethrough PriceSpecification.
Does valid markup guarantee a merchant listing?
No. Google says its tests check syntax and eligibility, and display is never guaranteed. Valid markup that matches your page and feed is the part you control.
