Has JSON-LD ImageObject reports whether RankGear finds an "@type": "ImageObject" declaration in a page’s raw HTML — a 1/0 presence check. Because it pattern-matches the source text rather than parsing a JSON-LD graph, a 1 confirms the string is present, not that the structured data is valid or complete.
| Factor ID | RG-SCJ-122 |
|---|---|
| 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 ImageObject in the page’s raw source. It is a binary signal: the page either declares that type somewhere in its HTML (1) or it does not (0). The check speaks only to the presence of the string — not to whether the surrounding markup forms a valid, complete ImageObject.
How RankGear measures it
RankGear searches the raw HTML for an @type declaration of ImageObject, allowing flexible whitespace around the key and value and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not change the result. Any occurrence of the pattern anywhere in the source is enough to return 1.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ImageObject"
}
</script>
# also matches (case-insensitive, flexible whitespace, optional prefix):
"@type": "schema:ImageObject"| Value | Meaning |
|---|---|
| 1 | An ImageObject @type declaration was found in the raw HTML. |
| 0 | No ImageObject @type declaration was found. |
How to optimize it
Use ImageObject only for a meaningful image, and give it an accurate content URL, dimensions, caption, credit, a representative-of-page relationship, and licensing details where they apply. Make sure every property reflects content a user can verify on the page. Treat this factor as an observation of what your markup declares rather than a target to hit: adding the type is only useful when it describes a real image honestly, and this detector cannot tell you whether the rest of the object is correct.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms a string, not a correct object.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still return 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate your complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with — and does not cause or guarantee — a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.