JSON-LD Main Entity Declaration records whether structured data explicitly identifies what the page is primarily about. It returns 1 when mainEntity or mainEntityOfPage appears anywhere in parseable JSON-LD, and 0 otherwise. Presence does not prove the declared entity is correct.
| Factor ID | RG-AIX-019 |
|---|---|
| Family | AI access & extractability |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Parseable JSON-LD |
What it measures
This factor checks for an explicit statement of the page’s principal subject. Without it, a consumer reading several declared entities has to guess which one the page is actually about. The check confirms the relationship is declared, not that it is accurate.
How RankGear measures it
RankGear returns 1 when mainEntity or mainEntityOfPage appears anywhere within parseable JSON-LD on the page; otherwise it returns 0.
| Value | Meaning |
|---|---|
| 1 | A mainEntity or mainEntityOfPage relationship was found in parseable JSON-LD. |
| 0 | Neither relationship was found. The page may still carry structured data that does not name a principal subject. |
How to optimize it
Declare the main entity when the page and the chosen Schema.org model genuinely support that relationship, using stable identifiers and visible corroboration. If the page does not really have one principal subject, do not invent one to satisfy the check.
Important considerations
- Presence does not prove that the declared entity is correct or that the page supports it.
- The factor looks anywhere in the graph, so a nested declaration counts the same as a top-level one.
- Pages without JSON-LD return 0 for the absence of markup rather than a modelling choice.
- 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.