When markup meets money and maps
After this lesson you can write Product and LocalBusiness JSON-LD that is honest and maintainable. These types matter more than most because the facts change and customers act on them.
Google's structured data gallery, read 2026-11, lists Product and Local business among the supported features, alongside Review snippet. Google's generative AI guide also recommends Merchant Center feeds for products and a maintained Google Business Profile for local businesses. Both are documented. How any of this feeds AI answers beyond that is not.
Product
Use it on a page about one specific product the visitor can buy or enquire about.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Hand-bound notebook, A5",
"description": "A5 notebook with 96 pages of 100gsm paper and a linen cover.",
"sku": "NB-A5-LIN",
"image": "https://www.example.com/images/notebook-a5.jpg",
"brand": { "@type": "Brand", "name": "Example Bookshop" },
"offers": {
"@type": "Offer",
"price": "499.00",
"priceCurrency": "INR",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/shop/notebook-a5/"
}
}Everything above is fictional. The price must equal the visible price, and availability must reflect reality: when stock runs out, the markup has to change. Generate it from the same database as the page so they cannot drift apart.
Reviews and ratings
Only add aggregateRating or review when real customers have reviewed the product and those reviews are shown. Self-written reviews, copied reviews and ratings from another site are against Google's guidelines and consumer law in many places. If you have none, leave it out. This is a hard rule of the course.
LocalBusiness
For a business with a physical location or a service area. Use the most specific schema.org type that is accurate, for example Bakery rather than the general type.
{
"@context": "https://schema.org",
"@type": "Bakery",
"name": "Greenfield Bakery",
"url": "https://www.example.com/",
"telephone": "+91-00000-00000",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 Example Street",
"addressLocality": "Pune",
"addressCountry": "IN"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}
]
}The phone number and address are placeholders. A real page must show the same hours and address in visible text, and they must be the same as on your Business Profile and directories. That consistency work is the entity lesson, Entities, brand mentions and consistency.
Where the facts really live
For many shops and local businesses, markup on the site is only one place. Google separately uses:
- Merchant Center product data (feeds) for shopping surfaces.
- Google Business Profile for local listings and maps.
Google's guidance says to keep them current. An out-of-date Business Profile saying "closed" will hurt customers far more than any missing markup. So, in effort order: correct facts at the source, consistent facts on the site, then markup.
Keeping markup in sync (established practice)
- Generate JSON-LD from the same data as the visible page.
- Test after every template change.
- Review seasonal changes: holiday hours, sale prices, discontinued items.
- For sale prices, show the real current price and do not invent "original" prices that were never charged.
- Remove markup for pages that no longer exist or products no longer sold.
AI answers and facts
If an assistant quotes your opening hours or price, it may take them from your page, a feed, a profile or another site. You cannot control which, so make all of them agree. Wrong information repeated in many places is the difficult case; fix sources, then recheck.
Common mistakes
- Hard-coding the price in markup while the page price is updated by another system.
- Leaving
InStockafter items sell out. - Adding
aggregateRatingwithout displayed real reviews. - Using a business type that does not describe you.
- Putting a keyword-stuffed name in
name("Best Cheap Bakery Pune").
Exercise
- Write Product JSON-LD for a fictional item, then change the visible price in an HTML snippet and mark what you must also change in the markup.
- Write LocalBusiness JSON-LD for a fictional shop and list four other places where its hours must match.
- Parse both blocks in the JSON formatter.
Show a sample answer
Hours should also match the Business Profile, the contact page, social profiles and any directory. Better still, keep one source of truth that publishes to all of them where possible, and put the date you last checked in your fact sheet.
Previous: FAQPage, HowTo and Q&A markup after the deprecations. Next: robots.txt rules for search and AI crawlers.
Key points
- Product and Local business are in Google's structured data gallery (as of 2026-11), so these markup types can support rich results.
- Prices, availability and hours in markup must match what a visitor sees and what is true today.
- Google's AI guidance points commerce and local sites to keep Merchant Center and Business Profile data current.
- Never mark up reviews or ratings you do not genuinely display and hold.
- Markup does not guarantee display or AI mentions.