XooCode(){

HyperTocEntry

HyperTocEntry is a pending CreativeWork subtype for a single chapter or section in a HyperToc. It adds 3 direct properties: associatedMedia (the underlying MediaObject, often the same one the parent HyperToc references), tocContinuation (a pointer to the default next entry to play), and utterances (Text of spoken words or lyrics at this section).

Time ranges are expressed via inherited startOffset and endOffset (number of seconds from the start of the media). The tocContinuation property enables auto-advance playlists, useful for educational content, radio-style podcast feeds, and audio books.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/HyperTocEntry
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HyperTocEntry",
  "name": "Missing required properties",
  "startOffset": 438,
  "endOffset": 812,
  "associatedMedia": {
    "@type": "VideoObject",
    "name": "Debugging JSON-LD in production",
    "contentUrl": "https://xoocode.com/videos/debug-jsonld.mp4#t=438,812"
  },
  "tocContinuation": {
    "@type": "HyperTocEntry",
    "name": "Enum values that look right but aren't",
    "startOffset": 812,
    "endOffset": 1286
  },
  "utterances": "Most validators fail silently when a required property is missing."
}
</script>

Minimal valid version

The smallest markup that still produces a valid HyperTocEntry 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/HyperTocEntry (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HyperTocEntry",
  "name": "Missing required properties",
  "startOffset": 438,
  "endOffset": 812
}
</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 HyperTocEntry 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

    Time offsets as time strings

    Wrong
    "startOffset": "00:07:18"
    Right
    "startOffset": 438 (seconds as Number)

    startOffset and endOffset expect seconds as a number, not HH:MM:SS strings. Convert before writing.

  2. 02

    Using HyperTocEntry without a parent HyperToc

    Wrong
    Top-level HyperTocEntry floating free
    Right
    Nest HyperTocEntry inside HyperToc.tocEntry

    HyperTocEntry is an item in a TOC, not a standalone object. Without its parent, consumers lose the structural context.

Schema properties in this example

HyperTocEntryCreativeWorknamestartOffsetendOffsetassociatedMediaVideoObjectcontentUrltocContinuationutterancesHyperToc

About the example data

The "Missing required properties" chapter in the Xoo Code lecture TOC, running from 7:18 to 13:32 with a continuation to the next chapter.

Comments

Loading comments...

Leave a comment