This factor reports whether a page’s raw HTML contains an @type value of Recipe — the JSON-LD signal a page carries recipe structured data. It returns 1 when the string is present and 0 when it is absent. Because it pattern-matches source text rather than validating a JSON-LD graph, presence of the string is not proof of valid, eligible markup.
| Factor ID | RG-SCJ-224 |
|---|---|
| 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 for Recipe in the raw source of the page. It is a straightforward presence check: the page either exposes the Recipe schema type in its markup or it does not. It says nothing about whether the surrounding structured data is complete or valid — only whether the identifying string appears.
How RankGear measures it
RankGear searches the raw HTML for the @type assignment of Recipe, allowing flexible whitespace around the key and value and optionally permitting a schema: prefix on the type. Matching is case-sensitive, so the value must use the exact capitalization Recipe to register. A match anywhere in the source sets the factor to 1.
What RankGear looks for
"@type" : "Recipe"
"@type": "schema:Recipe"| Value | Meaning |
|---|---|
| 1 | The @type value Recipe was found in the raw HTML. |
| 0 | No Recipe type string was found in the raw HTML. |
How to optimize it
Use Recipe only for a genuine recipe, and only when the markup accurately describes ingredients, quantities, instructions, timing, yield, nutrition, images, and author. Every property should reflect content a reader can verify on the page itself. Treat this factor as an observation about which pages expose the Recipe type, not as a target to force onto pages that are not actual recipes — adding the string to a non-recipe page satisfies the detector without improving 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 well-formed or eligible for rich results.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated script — can still produce a 1.
- The source must use the exact capitalization
Recipe; a differently cased value will not match. - Validate the complete structured data independently with a dedicated schema testing tool.
- This is a prioritization signal that relates to position within a measured result set. Presence of Recipe markup correlates with, but does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.