Book Launch Stack
Book launch pages with Book + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Book launch/landing pages with purchase links
- Author pages announcing a new book release
- Pages where FAQs clarify formats, shipping, and availability
What is included
Defines the book being launched with author and ISBN.
Represents the purchase offer and CTA URL.
Answers questions about formats, shipping, and release timing.
Provides navigation context to the launch page.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- author.name
- availability
- image
- isbn
- itemListElement[].name
- itemOffered.@id
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- price
- priceCurrency
- url
Recommended properties
- bookEdition
- category
- datePublished
- description
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- priceValidUntil
- publisher.name
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": "Book",
"@id": "https://www.example.com/books/launch#book",
"name": "Signals & Story",
"author": {
"@type": "Person",
"name": "Jordan Lee"
},
"isbn": "978-1-4028-9462-6",
"image": "https://www.example.com/images/signals-and-story.webp",
"url": "https://www.example.com/books/launch",
"description": "A practical guide to building durable brand narratives."
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/books/launch#offer",
"name": "Book Pre-Order",
"price": "24.99",
"priceCurrency": "USD",
"availability": "https://schema.org/PreOrder",
"url": "https://www.example.com/books/launch#buy",
"itemOffered": { "@id": "https://www.example.com/books/launch#book" },
"category": "Book",
"description": "Hardcover pre-order with bonus author interview."
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "When does the book ship?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Orders ship on release day, September 10, 2025."
}
},
{
"@type": "Question",
"name": "Is there an ebook edition?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Ebook and audiobook formats will be available on release day."
}
},
{
"@type": "Question",
"name": "Do you offer international shipping?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. International rates are calculated at checkout."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Books", "item": "https://www.example.com/books" },
{ "@type": "ListItem", "position": 3, "name": "Signals & Story", "item": "https://www.example.com/books/launch" }
]
}
]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
Can I list multiple purchase options?
Yes. Use one Offer per format (hardcover, ebook, audiobook), each pointing to the same Book @id.
What if the price isn’t shown?
If pricing isn’t visible, omit price fields and keep availability/url aligned to the purchase CTA.