Has JSON-LD VideoObject

This factor reports whether the page’s raw HTML contains a JSON-LD @type of VideoObject. It returns 1 when the string is present and 0 when it is not. The check pattern-matches source text, so a match is a signal that video markup exists — not proof that the structured data is valid.

Factor IDRG-SCJ-265
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 VideoObject in the raw source of the page. It is a simple presence signal: the markup is either detectable in the HTML or it is not. It does not weigh how many video objects appear, nor how complete any of them are.

How RankGear measures it

RankGear searches the raw HTML for "@type": "VideoObject", allowing flexible whitespace around the value and optionally a schema: prefix on the type. Matching is case-insensitive, so capitalization differences in the type string do not change the result. Any match sets the factor to 1; no match sets it to 0.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to season a cast-iron pan",
  "thumbnailUrl": "https://example.com/thumb.jpg",
  "uploadDate": "2026-02-14",
  "contentUrl": "https://example.com/video.mp4"
}
</script>
ValueMeaning
1A VideoObject type string was found in the raw HTML.
0No VideoObject type string was found.

How to optimize it

Use VideoObject only for a genuine video on the page, and give it an accurate title, thumbnail, upload date, duration, content or embed URL, transcript, and publisher. Every property should reflect content a user can verify on the page. Treat this factor as an observation about whether video markup is present, not a target to force: adding VideoObject to a page with no real video creates markup that misrepresents the page and can be flagged as invalid.

Important considerations

  • The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 confirms the string is present, not that the schema is well-formed.
  • A matching string that sits outside valid JSON-LD — for example inside a comment or an unrelated script — 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 pages in a measured result set; it relates to position as a prioritization signal and does not on its own cause or guarantee a ranking.

Related factors

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