“Has JSON-LD FurnitureStore” returns 1 when RankGear finds the string "@type": "FurnitureStore" in a page’s raw HTML, and 0 when it does not. It is a raw string match, not a validator — RankGear never parses or checks the surrounding JSON-LD graph, so a match that sits outside valid structured data still counts as present.
| Factor ID | RG-SCJ-091 |
|---|---|
| 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 FurnitureStore in the page’s raw source. It is a presence check for one specific schema.org business type — it says nothing about how complete, accurate, or valid the surrounding markup is, only that the type string appears somewhere in the HTML.
How RankGear measures it
RankGear searches the raw HTML for "@type": "FurnitureStore", allowing flexible whitespace around the colon and quotes and optionally a schema: prefix on the type value. Matching is case-insensitive, and the factor returns 1 on the first match or 0 when no match is found anywhere in the source.
What RankGear looks for
"@type": "FurnitureStore"
"@type" : "schema:FurnitureStore"| Value | Meaning |
|---|---|
| 1 | A FurnitureStore type string was found in the raw HTML. |
| 0 | The string was not present anywhere in the source. |
How to optimize it
Use FurnitureStore only for a genuine furniture retailer, with accurate products, offers, location, delivery, and contact details in the markup, and with properties that match the page’s visible content. Treat the 1/0 as an observation of whether the type is present, not a target to game: because the check is case-insensitive and pattern-based, a bare string could flip the factor to 1 without any real, matching business behind it — that misrepresents the page and offers no lasting benefit. If you legitimately are a furniture store, emitting valid JSON-LD with this @type is the straightforward way to make the factor read 1.
Important considerations
- The detector pattern-matches the raw source text; it does not parse or validate the JSON-LD graph.
- A matching string outside a valid JSON-LD block can still produce 1.
- Matching is case-insensitive, so capitalization differences do not affect detection.
- Validate the complete structured data independently — a passing presence check is not a guarantee that the markup is well-formed.
- Correlation is not causation: the presence of this type relates to how comparable pages are structured within a measured result set. It is a prioritization signal, not something that by itself causes or guarantees a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.