This factor reports whether RankGear finds a GroceryStore @type value in the page’s raw source. It returns 1 when a match is present and 0 when it is not. Because the check pattern-matches source text rather than validating a JSON-LD graph, a match confirms the string is present — not that the structured data is valid.
| Factor ID | RG-SCJ-098 |
|---|---|
| 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 GroceryStore in the raw source of the page. It is a presence signal: 1 means the marker was found, 0 means it was not. It says nothing about whether the surrounding JSON-LD is well-formed or complete — only that the type string appears.
How RankGear measures it
RankGear searches the raw HTML for "@type": "GroceryStore", allowing flexible whitespace around the colon and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect detection. Any occurrence of the marker in source text sets the factor to 1.
What RankGear looks for
"@type": "GroceryStore"
"@type":"schema:GroceryStore" (schema: prefix optional, whitespace flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | The GroceryStore type marker was found in the raw source. |
| 0 | No GroceryStore type marker was found. |
How to optimize it
Use GroceryStore only for a genuine grocery retailer, and back the type with accurate location, hours, products, offers, and contact details whose properties match the visible content of the page. Treat this factor as an observation of whether the marker exists, not a target to chase — adding the string without truthful, well-formed structured data underneath it serves no one.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1, so presence is not proof of correctness.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently — with a schema validator or rich-results test — rather than relying on this presence check alone.
- This is a prioritization signal that relates to patterns within a measured result set. It does not, on its own, make a page rank or guarantee any position — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.