This factor reports whether RankGear finds a JSON-LD @type of Restaurant in a page’s raw HTML — a simple present/absent (1 / 0) signal. It is a text pattern match, not a validation of the structured-data graph, so a match only tells you the string is on the page, not that the markup is correct.
| Factor ID | RG-SCJ-228 |
|---|---|
| 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 Restaurant in the raw source of the page. It answers a single yes/no question: does the page declare Restaurant structured data at all? It does not grade how complete or accurate that markup is — only that the type is present in the HTML.
How RankGear measures it
RankGear searches the raw HTML for the text "@type": "Restaurant", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. A match returns 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "Example Bistro",
"servesCuisine": "Italian",
"address": { "@type": "PostalAddress", "streetAddress": "..." }
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of Restaurant was found in the raw HTML (whitespace-flexible, case-insensitive, optional schema: prefix). |
| 0 | No matching Restaurant type string was found in the source. |
How to optimize it
Use the Restaurant type only for a page that genuinely represents a restaurant, and make sure every property reflects content a visitor can verify on the page — accurate cuisine, menu, location, hours, reservations, pricing, and contact details. Treat a value of 1 as confirmation that the type string exists, not as proof the markup is valid or eligible for rich results; the goal is correct, verifiable structured data, not the presence of the string for its own sake.
Important considerations
- The detector pattern-matches source text; it does not parse or validate the JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — 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 validator) before relying on it.
- This is a correlation-based prioritization signal within a measured result set. Presence of the type does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.