This factor reports whether RankGear finds an @type value of TireShop in a page’s raw source HTML. It returns 1 when the string is present and 0 when it is not — a text match, not a validated JSON-LD graph, so a stray mention can register as present.
| Factor ID | RG-SCJ-253 |
|---|---|
| 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 for TireShop in the raw source of the page. TireShop is a schema.org business type for a shop that sells tires; its presence signals that the page declares itself as a tire retailer in structured data. The check is a presence test only — it records that the type was declared, not whether the surrounding markup is complete or valid.
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "TireShop", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. Any single match anywhere in the source returns 1; no match returns 0.
What RankGear looks for
"@type": "TireShop"
"@type" : "schema:TireShop" <!-- prefix and spacing tolerated, case-insensitive -->| Value | Meaning |
|---|---|
| 1 | A TireShop @type string was found in the raw HTML. |
| 0 | No TireShop @type string was found. |
How to optimize it
Use TireShop only for a genuine tire retailer, and only where the markup describes content users can verify on the page. Populate the associated properties — products, services, brands carried, location, opening hours, availability, and contact details — with accurate values that match the visible page. Because this factor pattern-matches source text rather than validating a graph, treat a 1 as confirmation the type is declared, not proof the 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, a script sample, or body copy — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently with a schema testing tool before trusting the result.
- This is a prioritization signal that relates to position within a measured result set. It does not by itself cause a page to rank, and a declared type is no guarantee of any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.