Distinct JSON-LD Type Count totals the unique Schema.org @type strings found across valid JSON-LD. Irrelevant types raise the value just as readily as relevant ones, so breadth here is not quality.
| Factor ID | RG-AIX-018 |
|---|---|
| Family | AI access & extractability |
| Measurement | Count |
| Measured zone | Parseable JSON-LD |
What it measures
This factor describes how many different entity types a page claims to describe. A rich, accurate graph and a page padded with unrelated vocabulary can produce the same number, which is why the value is best read against what the page visibly contains.
How RankGear measures it
RankGear recursively collects unique string values appearing under @type across every parseable JSON-LD block on the page.
How to optimize it
Use only types that accurately represent visible entities and the page’s purpose. Compare relevant competitors without adding unrelated vocabulary for the count alone — structured data that describes things the page does not contain is a liability, not a depth signal.
Important considerations
- Irrelevant types increase the value, so a high count can indicate padding rather than richness.
- Breadth is not quality; one correct type can serve a page better than six loose ones.
- Only parseable blocks contribute, so broken markup is silently excluded.
- 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.