Has JSON-LD is a presence check. It returns 1 when RankGear finds at least one application/ld+json script marker in the rendered HTML, and 0 when it doesn’t — confirming that structured data exists, and nothing about whether that data is valid, relevant, or eligible for a rich result.
| Factor ID | RG-SCJ-001 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Boolean (0 / 1) |
| Measured zone | Rendered HTML |
What it measures
The factor reports whether the rendered HTML contains a script marker for JSON-LD structured data. It measures presence only: it does not parse the JSON, identify every schema type, judge eligibility for a search feature, or confirm that the markup agrees with the visible page.
How RankGear measures it
RankGear lowercases the rendered HTML and searches case-insensitively for a script type attribute whose value is application/ld+json. One or more qualifying markers return 1; otherwise the value is 0. Because the check is marker-based, malformed or irrelevant JSON-LD can still return 1, and unusual ways of declaring the script type may not match.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How we run a controlled SEO experiment",
"author": { "@type": "Person", "name": "Clint Butler" }
}
</script>| Value | Meaning |
|---|---|
| 1 | At least one application/ld+json marker was found in the rendered HTML. |
| 0 | No qualifying JSON-LD marker was found (the page may still use Microdata or RDFa). |
How to optimize it
Add JSON-LD only when a relevant schema vocabulary accurately describes the page and its visible content. Use the most specific appropriate types and properties, keep identity details consistent, and validate both syntax and search-engine requirements. Maintain the markup when prices, availability, ratings, dates, names, or locations change — structured data should make a page easier for machines to understand, not manufacture facts users can’t see.
Important considerations
- Presence does not guarantee validity, eligibility, indexing, or a rich result.
- Irrelevant or misleading markup can create quality and policy problems.
- Structured data implemented with Microdata or RDFa will not satisfy this JSON-LD-specific factor.
- Use schema-type and property factors to understand what the markup actually contains.
- Test deployed pages with a structured-data validation tool.
Related factors
Part of the Factors reference · how RankGear measures · glossary.