BookFormatType
BookFormatType is a schema.org Enumeration for the publication format of a Book. It is the value of Book.bookFormat.
It has 6 members:
Hardcover: hardback binding.Paperback: softcover binding.EBook: digital edition (Kindle, EPUB, etc.).AudiobookFormat: audio edition (note the unusual suffix; schema.org usesAudiobookFormat, notAudiobook).GraphicNovel: comics-form long-form book.Pamphlet: short, stapled or saddle-bound booklet.
Full example of schema.org/BookFormatType json-ld markup
The markup is verified as valid with Rich Results Test from Google.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Book", "name": "Structured Data: A Field Guide (Hardcover)", "bookFormat": "https://schema.org/Hardcover", "isbn": "978-1-23456-789-0" },
{ "@type": "Book", "name": "Structured Data: A Field Guide (Paperback)", "bookFormat": "https://schema.org/Paperback", "isbn": "978-1-23456-789-1" },
{ "@type": "Book", "name": "Structured Data: A Field Guide (EBook)", "bookFormat": "https://schema.org/EBook", "isbn": "978-1-23456-789-2" },
{ "@type": "Book", "name": "Structured Data: A Field Guide (Audiobook)", "bookFormat": "https://schema.org/AudiobookFormat", "isbn": "978-1-23456-789-3" }
]
}
</script>Multiple formats of the same title
Each edition is its own Book entity with its own ISBN and bookFormat. Use workExample on the abstract work (CreativeWork) to link to every format; each format links back via exampleOfWork.
Minimal valid version
The smallest markup that still produces a valid BookFormatType 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.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Book",
"name": "Structured Data: A Field Guide",
"bookFormat": "https://schema.org/Hardcover",
"isbn": "978-1-23456-789-0"
}
</script>Google rich results this unlocks
BookFormatType is a structural type. It does not produce a rich result on its own.
Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). BookFormatType becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.
Common BookFormatType 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.
- 01
Audiobook instead of AudiobookFormat
Wrong"bookFormat": "https://schema.org/Audiobook"Right"bookFormat": "https://schema.org/AudiobookFormat"Schema.org's audiobook enum member is suffixed 'Format' unlike the others; easy to get wrong.
- 02
Multiple formats on a single Book entity
WrongOne Book with bookFormat: array of formatsRightSeparate Book entity per edition, each with its own bookFormat, isbn, and OfferEach edition has distinct ISBN, price, and availability; collapsing them loses that detail.
Schema properties in this example
About the example data
Four editions of a fictional Xoo Code Press title across hardcover, paperback, ebook, and audiobook.
Comments
Loading comments...