This factor reports whether the page’s raw HTML contains an OnDemandEvent JSON-LD @type declaration — a 1 when the string is present and a 0 when it is not. It is a text match on source, not a validity check, so a match confirms the markup exists but not that it forms a well-formed structured-data graph.
| Factor ID | RG-SCJ-186 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of OnDemandEvent in the page’s raw source. OnDemandEvent is the schema.org type for an event whose recording is available to watch on demand rather than at a fixed live time. The result is a simple present-or-absent reading of that type declaration.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "OnDemandEvent", allowing flexible whitespace around the colon and value and optionally allowing a schema: prefix on the type. Matching is case-insensitive. If a match is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "OnDemandEvent"
"@type":"schema:OnDemandEvent" <!-- prefix allowed, whitespace flexible, case-insensitive -->| Value | Meaning |
|---|---|
| 1 | An OnDemandEvent @type string was found in the raw HTML. |
| 0 | No OnDemandEvent @type string was present. |
How to optimize it
Use OnDemandEvent only for a genuine on-demand event, and make sure the markup carries an accurate recording, access window, location or platform, organizer, and offer details. Every property should reflect content a user can actually verify on the page. Treat this factor as an observation of whether that markup is present — not a target to hit by inserting the string for its own sake. Because the detector reads source text, the honest way to move it from 0 to 1 is to publish legitimate, complete OnDemandEvent structured data.
Important considerations
- The detector pattern-matches source text rather than validating a full JSON-LD graph, so a 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 unrelated markup — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor is not a substitute for that check.
- Presence of this markup correlates with position within a measured result set and is a prioritization signal; it does not by itself cause a page to rank or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.