This factor reports whether RankGear finds a JSON-LD @type of ToyStore in a page’s raw HTML — a simple present/absent (1 / 0) check. It is a text match on the source, not a validation of the underlying structured-data graph, so a match confirms the string is there, not that the markup is well-formed.
| Factor ID | RG-SCJ-254 |
|---|---|
| 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 ToyStore in the raw source of the page. ToyStore is a schema.org business type for a retailer that sells toys, and marking it up tells search engines the page represents that kind of local business or store entity. The check answers one question: is that type declared in the HTML, yes or no.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "ToyStore", allowing flexible whitespace around the colon and quotes and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. Any match returns 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ToyStore"
}
</script>
/* also matches, case-insensitive, with optional prefix: */
"@type": "schema:ToyStore"| Value | Meaning |
|---|---|
| 1 | A ToyStore @type string was found in the raw HTML. |
| 0 | No ToyStore @type string was found. |
How to optimize it
Use ToyStore only for a genuine toy retailer, and only when the page’s content backs it up — accurate products, brands, offers, age guidance, location, hours, and contact details. Every property in the markup should reflect information a user can verify on the page itself. Treat this factor as an observation of what your markup declares, not a target to chase: adding the type to a page that is not actually a toy store misrepresents the entity and helps no one.
Important considerations
- The detector pattern-matches source text rather than validating a JSON-LD graph, so it confirms the string is present, not that the schema is valid.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated 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 schema validator) before relying on it.
- Presence of this type correlates with, and does not cause, any ranking outcome. It is a prioritization signal within a measured result set, never a guarantee of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.