Live Coverage Stack
LiveBlogPosting pages with breadcrumb, speakable selectors, and paywall/access signals when applicable.
When to use this stack
- Live coverage pages with continuous updates
- News/event coverage needing navigation and voice selectors
- Pages where access/paywall needs to be clear
What is included
Primary live coverage entity with headline, dates, author, and live status.
Optional voice-friendly selectors for key updates/sections.
Optional access/paywall signals if live coverage is metered or gated.
Navigation context.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- datePublished
- headline
- isAccessibleForFree
- itemListElement[].name
- liveBlogUpdate[]
- speakable.cssSelector
- url
Recommended properties
- author.name
- dateModified
- hasPart.cssSelector
- hasPart.isAccessibleForFree
- hasPart.url
- image
- itemListElement[].item
- publisher.name
- speakable.xpath
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "LiveBlogPosting",
"@id": "https://www.example.com/live/tech-keynote-2026#liveblog",
"headline": "Tech Keynote 2026 — Live Updates",
"datePublished": "2026-02-20T16:00:00Z",
"dateModified": "2026-02-20T16:30:00Z",
"url": "https://www.example.com/live/tech-keynote-2026",
"author": { "@type": "Person", "name": "Jamie Rivera" },
"publisher": { "@type": "Organization", "name": "Example News" },
"liveBlogUpdate": [
{
"@type": "BlogPosting",
"headline": "Opening remarks",
"datePublished": "2026-02-20T16:05:00Z",
"articleBody": "CEO shares the 2026 vision and new product focus areas."
},
{
"@type": "BlogPosting",
"headline": "New hardware announced",
"datePublished": "2026-02-20T16:20:00Z",
"articleBody": "New laptop line with improved battery and AI co-pilot features."
}
]
},
{
"@context": "https://schema.org",
"@type": "WebPage",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [
"h1",
".live-update"
]
}
},
{
"@context": "https://schema.org",
"@type": "WebPageElement",
"isAccessibleForFree": false,
"cssSelector": ".paywall",
"url": "https://www.example.com/live/tech-keynote-2026/preview"
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Live", "item": "https://www.example.com/live" },
{ "@type": "ListItem", "position": 3, "name": "Tech Keynote 2026", "item": "https://www.example.com/live/tech-keynote-2026" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Do I need SubscriptionAndPaywall?
Only if the live blog is paywalled or metered. Otherwise omit that object.
How often should I update dateModified?
On each meaningful content update. Keep it aligned with the latest liveBlogUpdate time.