This factor reports whether RankGear finds a JSON-LD @type value of Store in the page’s raw HTML. It returns a simple yes/no signal (1 or 0). Because it pattern-matches source text rather than parsing a JSON-LD graph, a match confirms the string is present — not that the structured data is valid.
| Factor ID | RG-SCJ-249 |
|---|---|
| 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 Store in the raw source. It is a presence check: a page either exposes a Store type in its markup, or it does not. The signal describes what is in the HTML, not whether the surrounding structured data is complete or correct.
How RankGear measures it
RankGear searches the raw HTML for the "@type": "Store" declaration, allowing flexible whitespace around the tokens and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences in the type value do not change the result. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Store",
"name": "Example Retail",
"address": { "@type": "PostalAddress", "streetAddress": "..." }
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of Store was found in the raw HTML. |
| 0 | No Store type string was found in the raw HTML. |
How to optimize it
Use the Store type only for a genuine retail store, and make sure every property reflects content users can verify on the page — accurate products, offers, location, hours, policies, and contact details. Do not add the markup to a page that is not a real store simply to trigger the signal. Treat this factor as an observation of what your markup declares, not a target to chase in isolation; the value of a Store type comes from the accuracy of the data behind it.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a returned 1 confirms the string, not a valid schema.
- A matching string that sits outside valid JSON-LD — for example in a comment or an unrelated script — can still produce a 1.
- Capitalization differences do not affect detection, because matching is case-insensitive.
- Validate your complete structured data independently with a dedicated schema validator.
- Correlation is not causation: this factor tracks the presence of a markup pattern within a measured result set and is a prioritization signal, not a guarantee of any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.