Has JSON-LD Chapter

Abstract illustration of a book chapter tagged with JSON-LD Chapter schema markup, in RankGear indigo and coral.

Has JSON-LD Chapter reports whether RankGear finds an @type value of Chapter in a page’s raw HTML source. It returns a simple yes/no (1 or 0); because RankGear pattern-matches text rather than parsing the JSON-LD graph, a match confirms the string is present, not that the surrounding structured data is valid.

Factor IDRG-SCJ-047
FamilyStructured Data — JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of Chapter in the raw source. Chapter is the schema.org type used to mark up a distinct chapter of a larger written work — a section of a book, report, or serialized publication — so a page that carries it is declaring that its content is one chapter within a parent work. The reading is a binary observation: the type string is either present in the source or it is not.

Back to Top

How RankGear measures it

RankGear performs a case-insensitive raw-HTML search with flexible whitespace around "@type": "Chapter", and permits an optional schema: prefix. The match is made against the raw source string rather than a parsed JSON-LD graph, so capitalization differences and extra whitespace between the key and its value do not affect detection.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Chapter"
}
</script>
ValueMeaning
1The @type string Chapter (optionally schema:Chapter) was found in the raw HTML.
0No matching Chapter type string was found in the raw HTML.
Back to Top

How to optimize it

Use Chapter only for a genuine chapter — a real section of a larger written work — with an accurate title, position, parent-work reference, and text relationships, and supply properties that match the visible content. Treat this factor as an observation of whether that markup is present, not a target to chase: pasting the type string onto a page that is not actually a chapter creates markup that misrepresents the content and reflects no real advantage.

Back to Top

Important considerations

  • RankGear pattern-matches text rather than parsing or validating the JSON-LD graph, so a reading of 1 confirms the string is present, not that the structured data is well-formed.
  • A matching string that sits outside valid JSON-LD — in a comment, a code sample, or an escaped snippet — can still produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently with a schema.org or Google validator; this factor does not do that for you.
  • Presence of the Chapter type correlates with position within a measured result set and acts as a prioritization signal — it does not by itself make a page rank or guarantee a position.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top