This factor reports whether RankGear finds a JSON-LD @type of DietNutrition in a page’s raw source. It returns 1 when the string is present and 0 when it is not — a text match, not a validated structured-data graph, so a hit does not guarantee the markup is well-formed.
| Factor ID | RG-SCJ-179 |
|---|---|
| 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 DietNutrition in the page’s raw source. It is a simple presence check: the DietNutrition schema type describes nutrition information — calories, fat, carbohydrate, protein, and similar properties — typically nested inside recipe or food-related structured data.
How RankGear measures it
RankGear searches the raw HTML for "@type": "DietNutrition", allowing flexible whitespace around the pattern and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection. Any match returns 1; no match returns 0.
What RankGear looks for
"@type": "DietNutrition"
"@type":"schema:DietNutrition"
"@type" : "dietnutrition"| Value | Meaning |
|---|---|
| 1 | A DietNutrition @type string was found in the raw source. |
| 0 | No DietNutrition @type string was found. |
How to optimize it
Use DietNutrition only for genuine nutritional guidance or nutrition information that the implemented DietNutrition type actually represents. Ensure every property reflects content users can verify on the page. Treat this factor as an observation of whether the markup is present, not a target to hit for its own sake — adding the type to a page that carries no real nutrition content adds no value and risks misrepresenting the page.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid.
- A matching string that appears outside valid JSON-LD — in a comment, a code sample, or escaped text — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently before relying on it.
- This is a prioritization signal that relates to position within a measured result set; presence of the markup does not cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.