Has JSON-LD Audiobook

This factor reports whether RankGear finds an Audiobook @type value in a page’s raw HTML — a 1 (present) or 0 (absent) signal. It is a text match against the source, not a validation that a well-formed Audiobook JSON-LD graph exists.

Factor IDRG-SCJ-020
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 Audiobook in the raw source of the page. It answers a single yes/no question: does the markup declare an audiobook entity? It does not weigh the completeness or accuracy of that entity — only whether the type string is present.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "Audiobook", allowing flexible whitespace around the colon and the quotes, and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Audiobook",
  "name": "...",
  "author": { "@type": "Person", "name": "..." },
  "readBy": { "@type": "Person", "name": "..." },
  "duration": "PT9H45M"
}
</script>
ValueMeaning
1An Audiobook @type string was found in the raw HTML.
0No Audiobook @type string was found.

How to optimize it

Use the Audiobook type for a genuine audio edition, and populate it with accurate author, narrator, duration, and access information. Treat the 1/0 result as an observation of what the markup declares, not a target to chase: adding the type string to a page that has no real audiobook edition describes something that is not there, and structured data should always match the visible, truthful content of the page.

Important considerations

  • RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph, so a well-formed schema is not required to score a 1.
  • A matching string that sits outside a valid JSON-LD script — in a comment, a code sample, or unrelated text — can still produce a 1.
  • Capitalization differences do not affect detection; matching is case-insensitive.
  • All structured data must match visible, truthful content on the page.
  • Presence of this markup correlates with pages in a measured result set; it is a prioritization signal, not a guarantee of ranking, and it does not by itself make a page rank.

Related factors

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