This factor reports a simple yes/no: whether RankGear finds a JSON-LD @type value of HardwareStore in the raw HTML of the page. It returns 1 when that type string is present and 0 when it is not — but because it pattern-matches source text rather than validating a JSON-LD graph, a match does not by itself prove the structured data is valid.
| Factor ID | RG-SCJ-101 |
|---|---|
| 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 HardwareStore in the raw source of the page. It is a presence check for one specific schema.org type — the markup a genuine hardware retailer would use to describe its store — and nothing more. The result is a single bit: the type string is either found (1) or absent (0).
How RankGear measures it
RankGear searches the raw HTML for a match on "@type": "HardwareStore", allowing flexible whitespace around the value and optionally a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection. The check operates on source text, not on a parsed and validated JSON-LD graph.
What RankGear looks for
"@type": "HardwareStore"
"@type":"schema:HardwareStore" <-- schema: prefix allowed
"@TYPE": "hardwarestore" <-- case-insensitive| Value | Meaning |
|---|---|
| 1 | A HardwareStore @type string was found in the raw HTML. |
| 0 | No such string was found. |
How to optimize it
Use HardwareStore only for a real hardware retailer, and only when the page describes an actual store with accurate products, services, location, hours, and contact details. The declared properties should match what a visitor can see on the page. Treat this factor as an observation of whether that markup is present, not as a target to chase: adding the string to a page that is not a hardware store, or whose data does not match the visible content, adds no value and misrepresents the page.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a value of 1 confirms the string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — for example in a comment, an example block, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently, for example with a dedicated schema validator, rather than relying on this presence check alone.
- This is a correlation-based prioritization signal within a measured result set. Presence of the markup relates to how pages are compared; it does not on its own cause or guarantee any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.