Schema.org is the shared, cross-industry vocabulary that websites use to describe structured data, so search engines and other machine consumers can reliably identify what a page and its content actually are.
| Term | Schema.org |
|---|---|
| Category | Structured Data, Social and Media |
| Also known as | Schema Vocabulary |
| Where it appears | Schema reports and examples |
What it means in RankGear
Inside RankGear, Schema.org is the vocabulary layer behind the schema reports and worked examples. When RankGear inspects a page and its ranking competitors, it reads the Schema.org types and properties each one declares, such as Article, Product, Recipe, LocalBusiness, or FAQPage, and reports which of them are present. This lets you see, at a glance, what structured-data vocabulary the pages competing for a query tend to use and whether your target page carries the same coverage.
How to interpret it
Read Schema.org markup at the property level, not just the type level: check the exact property names, their format, and that they describe content a visitor can actually see on the page. A page can claim a type without populating the properties that make it useful. Treat the vocabulary as a comparative signal too. When most ranking pages for a query declare a particular type, that suggests search engines expect it for that kind of result, not that adding the markup by itself lifts a page. The markup describes content; it does not manufacture relevance.
Example
You are optimizing a recipe page. RankGear’s schema report shows that the pages ranking above you all declare Schema.org Recipe markup with populated recipeIngredient, cookTime, and aggregateRating properties, while your page declares only a generic Article type. That gap tells you the expected vocabulary for this result set, and that your visible ingredients, timings, and reviews are not yet described in a way machines can read.
Important considerations
- Schema.org is a vocabulary, not a delivery format. It defines the terms; a syntax such as JSON-LD or microdata is how those terms are actually written into the page.
- Declaring a type only makes a page eligible for a rich or social presentation. It is never a guarantee that a platform will display that presentation.
- Markup must reflect content the visitor can see. Describing claims or data that are not present on the page is a misuse of the vocabulary and can work against you.
- The presence of a schema type across ranking pages is a comparative indicator of what is expected for a query, not a Google ranking score, and correlation with ranking is not proof the markup causes it.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.