Has JSON-LD MediaObject

Abstract illustration of a media asset described by JSON-LD MediaObject markup being detected in page source, in RankGear indigo and coral.

Has JSON-LD MediaObject reports whether RankGear finds a MediaObject @type in the page’s raw HTML. It returns 1 when that string is present and 0 when it is not — but the check pattern-matches source text rather than validating the JSON-LD graph, so a matching string outside valid structured data can still return 1.

Factor IDRG-SCJ-141
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 MediaObject in the page’s raw source. MediaObject is the schema.org type that describes a discrete media asset — an image, audio file, or video — along with properties such as its content URL, encoding format, dimensions, duration, creator, caption, and licensing. The result is a simple present-or-absent signal, not a measure of how complete or correct the markup is.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the @type declaration "@type": "MediaObject", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the outcome. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.

Back to Top

What RankGear looks for

"@type": "MediaObject"
"@type": "schema:MediaObject"

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MediaObject",
  "contentUrl": "https://example.com/asset.mp4"
}
</script>
ValueMeaning
1A MediaObject @type string was found in the raw HTML (with or without a schema: prefix, any capitalization).
0No MediaObject @type string was found in the raw HTML.
Back to Top

How to optimize it

Use MediaObject only for a genuine media asset, and give it an accurate content URL, encoding format, dimensions or duration, creator, caption, and licensing details where they apply. Every property should reflect content a user can actually verify on the page. Treat this factor as an observation of whether that markup exists, not a target to hit for its own sake — adding the type without a real media asset behind it adds no value and can create markup that fails independent validation.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
  • A matching string that sits outside valid JSON-LD — in a comment, an example block, or escaped text — can still produce a 1.
  • Capitalization differences do not affect detection, and a schema: prefix is accepted.
  • Validate the complete structured data independently with a schema validator; a 1 here is not proof that the markup is well-formed or eligible for rich results.
  • This is a prioritization signal that relates to position within a measured result set. Presence of MediaObject markup correlates with ranking context; it does not cause a page to rank or guarantee any position.
Back to Top

Related factors

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

Back to Top