Book Schema Markup: How to Add Book JSON-LD for Rich Results
Understand with AI
Discuss with your preferred AI assistant
Rich results with images and ratings can lift click-through rate well above plain text listings.
schema.org supports Hardcover, Paperback, EBook, AudiobookFormat, and GraphicNovel as book formats.
A complete, validated Book JSON-LD block takes under two minutes to generate and paste in.
Book schema markup tells search engines that a page is about a specific book — its title, author, ISBN, publisher, and rating. When you add it correctly, Google can show your page with Book rich results: an enhanced listing with the cover, author, ratings, and "where to read or buy" actions that pull more clicks than a plain blue link.
This guide explains exactly what Book structured data is, which properties matter, and how to add valid JSON-LD to your pages in minutes — no developer required.
What Is Book Schema Markup?
Book schema is structured data based on the schema.org/Book type. It's a small block of code, usually written in JSON-LD, that describes a book using a vocabulary search engines understand. Instead of guessing what your page is about, crawlers read the markup and know the exact title, author, ISBN, and edition.
JSON-LD is Google's recommended format because it sits in a single <script> tag and is decoupled from your visible HTML — you can add or edit it without touching the page layout.
Why Book Structured Data Matters for SEO
Structured data doesn't directly boost rankings, but it unlocks features that win attention and clicks:
- Book rich results — eligibility for Google's dedicated book experience with cover image, author, and read/buy actions.
- Knowledge panels — clearer entity signals help Google connect your page to the right book and author.
- Star ratings — a valid aggregate rating can surface review stars that raise click-through rate.
- AI and answer engines — clean schema makes your content easier for AI Overviews and assistants to cite accurately.
Key Book Schema Properties
A complete Book node uses a handful of high-value properties. The table below covers the ones that matter most:
| Property | What it describes | Recommended? |
|---|---|---|
| name | The book title | Required |
| author | Person (or array of Persons) who wrote it | Required |
| isbn | The 13-digit ISBN identifier | Strongly recommended |
| publisher | Organization that published the book | Recommended |
| datePublished | Publication date (ISO 8601) | Recommended |
| bookFormat | Hardcover, Paperback, EBook, or Audiobook | Recommended |
| numberOfPages | Page count for print editions | Optional |
| aggregateRating | Average rating plus the count of ratings | Optional |
How to Add Book Schema to Your Site
1. Generate valid JSON-LD
Enter the book's details — title, author, ISBN, publisher, date, format, pages, and ratings — into the generator above. It validates your ISBN checksum, converts ISBN-10 to ISBN-13, and only emits fields that are correct, so you never ship broken markup.
2. Paste it into the page
Copy the generated <script type="application/ld+json"> block and paste it into the <head> of the page about that book. One book equals one page equals one Book node — don't list every book on a single page with separate markup blocks unless that page genuinely is a list.
3. Validate before publishing
Run the URL through Google's Rich Results Test and the Schema.org validator. Fix any errors (missing required fields) and review warnings (recommended fields you skipped). Then request indexing in Search Console so Google re-crawls the page.
Book Schema Best Practices
- Always use the canonical ISBN-13 — it's the modern global standard and disambiguates editions.
- Only mark up content that's actually visible on the page; hidden or fabricated data violates Google's guidelines.
- Pair ratingValue with ratingCount — an aggregate rating with only one of the two is invalid and will be ignored.
- Use the correct bookFormat URL value (for example, https://schema.org/Paperback) rather than a free-text string.
- Keep one Book node per edition; use separate pages or the workExample pattern for multiple editions.
Common Book Schema Mistakes
- Invalid ISBN — a typo breaks the checksum and search engines discard the identifier.
- Marking up a book that isn't the page's main subject, triggering a structured-data spam penalty.
- Using a plain string for the author instead of a nested Person object.
- Forgetting to validate, then wondering why rich results never appear.
Expert Tips
Always emit the canonical ISBN-13
ISBN-13 is the modern global standard and uniquely identifies an edition. Convert any ISBN-10 to its 978-prefixed ISBN-13 form so search engines map your page to the right book.
Validate before you publish
Run every page through Google’s Rich Results Test and the Schema.org validator. Fix errors, review warnings, and request indexing so Google re-crawls the updated markup.
Frequently Asked Questions
What is Book schema markup?
Book schema is structured data based on schema.org/Book that describes a book — its title, author, ISBN, publisher, format, and rating — in a machine-readable format. Added as JSON-LD, it makes a page eligible for Google's Book rich results.
Do I need an ISBN for Book schema?
An ISBN isn't strictly required, but it's strongly recommended. It uniquely identifies the edition and helps search engines match your page to the correct book and any existing knowledge panel. If you have one, always include the canonical ISBN-13.
Does Book schema improve my SEO rankings?
Structured data is not a direct ranking factor, but it makes your page eligible for rich results and clearer entity understanding. Those enhanced listings typically lift click-through rate, which can indirectly support performance.
Where do I put the Book JSON-LD on my page?
Place the generated script in the <head> of the page about that specific book, or anywhere in the body. Use one Book node per page, then validate with Google's Rich Results Test before publishing.