This factor reports whether RankGear finds a HomeGoodsStore @type value in a page’s raw source. It returns 1 when the string is present and 0 when it is not. Because the check pattern-matches source text rather than validating a JSON-LD graph, a 1 confirms the markup was written, not that the structured data is valid.
| Factor ID | RG-SCJ-106 |
|---|---|
| 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 HomeGoodsStore in the raw source of the page. It is a binary presence signal: the markup is either detected (1) or it is not (0). It says nothing about the completeness or accuracy of the surrounding structured data — only that the declared type string appears in the HTML.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration set to HomeGoodsStore, allowing flexible whitespace around the key and value and optionally accepting a schema: prefix. Matching is case-insensitive, so differences in capitalization do not change the result.
What RankGear looks for
"@type": "HomeGoodsStore"
"@type" : "schema:HomeGoodsStore" <!-- prefix and extra whitespace allowed -->| Value | Meaning |
|---|---|
| 1 | The HomeGoodsStore type string was found in the raw HTML. |
| 0 | No matching HomeGoodsStore type string was found. |
How to optimize it
Declare HomeGoodsStore only for a genuine home-goods retailer, and make the structured data describe the real business: accurate products, offers, location, delivery options, and contact information, with properties that match the content a visitor can see on the page. Treat the 1/0 result as an observation of whether the type is present, not as a target to force — adding the string without a valid, honest graph behind it does not improve the underlying data quality.
Important considerations
- The detector pattern-matches source text rather than validating a full JSON-LD graph, so a 1 does not confirm the structured data is well-formed.
- A matching string that appears outside valid JSON-LD — for example in a comment or a code sample — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with, and never guarantees, a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.