JSON-LD is a script-based structured-data format that expresses Schema.org entities and their properties in a self-contained block, kept separate from the visible HTML that a person reads on the page.
| Term | JSON-LD |
|---|---|
| Category | Structured Data, Social and Media |
| Also known as | JavaScript Object Notation for Linked Data |
| Where it appears | JSON-LD examples report and schema factors |
What it means in RankGear
RankGear surfaces JSON-LD in two places: the JSON-LD examples report, which pulls the actual markup blocks found on competing pages, and the schema-related factors that flag whether a given entity type is present. Because JSON-LD lives in a <script type="application/ld+json"> block rather than being woven through the body copy, RankGear can read it as a discrete object and tell you which Schema.org types the ranking set declares, versus what your own page declares.
How to interpret it
Read JSON-LD as a description of the page, not as a ranking lever. When RankGear shows that top pages carry a particular type, the useful question is whether your markup names the same properties and whether those properties describe content a visitor can actually see. Markup that asserts a rating, a price, or an author that never appears on the rendered page is the kind of mismatch that gets ignored or penalized. Validate the exact property and its format, and confirm the visible page supports the claim before treating a gap as something to close.
Example
You are working a product-review page and RankGear’s JSON-LD examples report shows that four of the five ranking pages declare a Product object with nested AggregateRating and Review properties, while your page ships only a bare WebPage type. The schema factors mark the difference. The fix is to add the same properties, populated from the ratings and reviews already rendered on your page, so the markup mirrors what the visitor sees.
Important considerations
- JSON-LD only describes content; it does not create it. Every property should map to something visible on the page.
- Presence of a schema type on ranking pages is a comparative signal, not a Google score. Matching competitors’ markup does not, on its own, make a page rank.
- Eligibility for a rich or social presentation is not a guarantee that a platform will display it. Search engines and social networks choose whether to render enhanced results.
- Validate each property and format against Schema.org and the target platform’s requirements rather than copying a competitor’s block wholesale.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.