Google Merchant Markup: Implementing category and saleDuration for AI SearchArticle · digest for October 18
Isometric sneaker product card with JSON-LD code blocks and a discount countdown timer
Article2 sections≈ 3 min

Google Merchant Markup: Implementing category and saleDuration for AI Search

If your online store still hopes search bots will figure out what category a product belongs to just by reading the H1 heading and breadcrumbs, I have unsettling news. In the era of generative search results (Google AI Overviews), algorithmic guesswork costs far too much.

A crawler can easily confuse sportswear with industrial workwear or toss premium running shoes into everyday slippers. The outcome is predictable: your product card drops out of relevant shopping carousels, and both paid and organic traffic sink by tens of percent.

To clean this up, Google updated its Schema.org structured data requirements for Merchant listings. Two key additions plug this leak for good: explicitly declaring the product taxonomy (category) and locking down promo timeframes through discount duration properties (saleDuration / validFrom and validThrough).

Exact Categorization Without Ambiguity

In the past, the category field in microdata was often ignored or filled with freeform text. Today, Google strongly recommends tying the category property to the official Google Product Taxonomy.

When your JSON-LD snippet spells out an exact path like Apparel & Accessories > Clothing > Activewear, Google's AI recognizes the product entity instantly. Your listing lands cleanly in thematic recommendation blocks and filtered search clusters without competing against mismatched items.

Urgency Timers and Protection Against Price Mismatches

E-commerce's second perpetual headache is stale discounts. On Friday you launch a 20% weekend sale, on Monday you restore the regular price, and Google's crawler keeps showing the old markdown in search results for another two days. Shoppers click through, see the higher price, get annoyed, and bounce—while Google Merchant Center threatens account penalties for price mismatches.

The updated protocol solves this right inside the markup:

  • Add validFrom (discount start date and time) and validThrough (end date and time) to the Offer node.
  • Pass timestamps strictly in ISO 8601 format with a timezone offset (for example, +03:00 for Moscow time).
  • The search algorithm knows in advance the exact second your promo expires. Once less than 24 hours remain, Google displays a dynamic countdown badge in search results: "Sale ends in 6 hours."

In practice, that interactive element triggers powerful FOMO and delivers a 15–30% lift in click-through rate (CTR).

Offer Markup Template With Exact Promo Dates

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Беговые кроссовки Pro Runner 2",
  "category": "Apparel & Accessories > Shoes > Running Shoes",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "RUB",
    "price": "8990",
    "validFrom": "2026-10-18T00:00:00+03:00",
    "validThrough": "2026-10-25T23:59:59+03:00",
    "availability": "https://schema.org/InStock"
  }
}

Notice one crucial detail: the dates on your page must match the sale_price_effective_date attribute in your Merchant Center product feed character for character.

Make sure to run your store pages through the official Google Rich Results Test. Once the validator shows zero errors and your timezones line up, your product cards will start earning priority placement in AI-powered search results.

Earlier, in our article on optimizing product listings and dynamic pricing on marketplaces, we covered how automated feed syncing prevents store suspensions during major sales events.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 2