This factor reports whether RankGear finds a SportingGoodsStore @type value in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — but it pattern-matches text, so a match does not prove the surrounding JSON-LD is valid.
| Factor ID | RG-SCJ-244 |
|---|---|
| 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 SportingGoodsStore in the page’s raw source. It is a presence check: 1 means the SportingGoodsStore type declaration was detected in the HTML, and 0 means it was not. SportingGoodsStore is the schema.org type used to describe a retailer that sells sporting goods, sports equipment, and related merchandise.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "SportingGoodsStore", allowing flexible whitespace around the tokens and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SportingGoodsStore",
"name": "...",
"address": { ... },
"openingHours": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A SportingGoodsStore @type string was found in the raw HTML. |
| 0 | No SportingGoodsStore @type string was found. |
How to optimize it
Use SportingGoodsStore only for a real sporting-goods retailer, and only when the markup describes the business accurately — products, brands, offers, services, location, hours, and contact details. Every property should reflect content a user can verify on the page. Because this check reads source text rather than a validated graph, treat a 1 as an observation that the declaration is present, not as confirmation that your structured data is correct. Validate the complete JSON-LD independently before relying on it.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 does not confirm the markup is well-formed or complete.
- A matching string that appears outside valid JSON-LD — for example in a comment or an example snippet — can still produce 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Always validate the complete structured data with an independent tool before trusting it.
- This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with pages in that set and does not on its own cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.