RankGear’s Has JSON-LD NutritionInformation factor returns a simple yes/no (1 or 0) for whether the page’s raw HTML contains a JSON-LD @type of NutritionInformation. It is a text-pattern check on the source, not a schema validator — a matching string can register a 1 even when the surrounding JSON-LD is incomplete or invalid.
| Factor ID | RG-SCJ-180 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of NutritionInformation in the raw source of the page. NutritionInformation is the schema.org type that carries nutrition facts — calories, fat, protein, serving size and similar nutrient values — typically nested inside a Recipe, MenuItem, or product description. The factor tells you only that the marker is present in the source text, not what the nutrition data contains.
How RankGear measures it
RankGear searches the raw HTML for "@type": "NutritionInformation", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences in the type name do not change the result. Any match sets the factor to 1; no match returns 0.
What RankGear looks for
"@type": "NutritionInformation"
// flexible whitespace and an optional schema: prefix also match, e.g.
"@type":"schema:nutritioninformation"| Value | Meaning |
|---|---|
| 1 | A NutritionInformation @type string was found in the raw HTML. |
| 0 | No such string was found in the raw HTML. |
How to optimize it
Use NutritionInformation only for accurate nutrition facts on a genuine recipe, menu item, or product — with correct serving context and real nutrient values. Every property should reflect content a user can verify on the page. Treat this factor as an observation about what your markup contains, not a target to chase: adding the type where there is no real nutrition content to describe adds noise rather than value, and because the detector only pattern-matches source text, a passing 1 is not evidence that the structured data is valid.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently — for example with a schema validation tool — rather than relying on this presence check.
- This is a prioritization signal that tracks with position across a measured result set; presence of the type does not cause a page to rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.