XooCode(){

Chapter

Chapter is a CreativeWork subtype for a named or numbered section of a Book. It adds three properties: pageStart, pageEnd, and pagination. Everything else (name, author, position, isPartOf) is inherited.

Chapters link to their parent book via isPartOf. Their ordering inside the book is expressed via position. For a multi-volume work, chain Chapter → isPartOf → Book → isPartOf → BookSeries.

Full example of schema.org/Chapter json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/Chapter
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Chapter",
  "name": "How crawlers consume JSON-LD",
  "position": 3,
  "pageStart": 45,
  "pageEnd": 78,
  "author": { "@type": "Person", "name": "Jane Xoo" },
  "isPartOf": {
    "@type": "Book",
    "name": "Structured Data Fundamentals",
    "isbn": "978-1-66566-111-1",
    "author": { "@type": "Person", "name": "Jane Xoo" }
  },
  "url": "https://xoocode.com/book/chapter-3"
}
</script>

When to mark up individual chapters

Chapter markup is useful for books sold chapter-by-chapter, educational texts with deep-linkable sections, and scholarly monographs where chapters are citeable units. For a standard trade book, marking up every chapter is overkill; a single Book entry with hasPart pointing to a few named chapters is usually enough.

Minimal valid version

The smallest markup that still produces a valid Chapter entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/Chapter (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Chapter",
  "name": "How crawlers consume JSON-LD",
  "position": 3,
  "isPartOf": { "@type": "Book", "name": "Structured Data Fundamentals" }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

Common Chapter mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Chapter without isPartOf

    Wrong
    Chapter as a standalone entity with no book reference
    Right
    Always link up via isPartOf to the Book

    A chapter without its book is meaningless to consumers. isPartOf is the link that connects citation, indexing, and next-in-book suggestions.

  2. 02

    pagination alongside pageStart/pageEnd

    Wrong
    Populating pagination AND pageStart/pageEnd simultaneously
    Right
    Use pagination for non-contiguous ranges ('1-6, 9, 55'); use pageStart/pageEnd for continuous ranges

    The two are alternatives. Populating both introduces ambiguity; consumers may pick either.

Schema properties in this example

ChapterCreativeWorknamepositionpageStartpageEndpaginationauthorPersonisPartOfBookisbnurl

About the example data

Chapter 3 ("How crawlers consume JSON-LD") of Jane Xoo's book "Structured Data Fundamentals".

Comments

Loading comments...

Leave a comment