Valid JSON-LD Block Rate reports what share of the page’s declared JSON-LD blocks actually parse as JSON. A page with no blocks returns 0. Parsing is not Schema.org validation — a block can parse perfectly and still describe the page incorrectly.
| Factor ID | RG-AIX-017 |
|---|---|
| Family | AI access & extractability |
| Measurement | Percentage |
| Measured zone | JSON-LD script blocks |
What it measures
This factor separates structured data that is syntactically readable from markup that silently fails. A block that does not parse is invisible to every consumer, so this is a floor check: whatever else is true of the markup, it has to be valid JSON first.
How RankGear measures it
RankGear divides the number of parseable application/ld+json blocks by all such blocks on the page and multiplies by 100. If there are no blocks, the factor returns 0.
How to optimize it
Repair syntax errors, validate the resulting Schema.org graph, and keep the markup aligned with visible content. A rate below 100 with blocks present points at a concrete, fixable defect — something on the page is emitting broken JSON.
Important considerations
- JSON parsing is not Schema.org validation, eligibility, truthfulness or search-feature approval.
- A page with no JSON-LD returns 0, which is not the same as having broken JSON-LD.
- A perfect rate says nothing about whether the declared types suit the page.
- This is a measured correlation within a result set, not a guarantee: the value relates to how the pages ranking for your query are built — it does not, on its own, make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.