Has JSON-LD Motorcycle returns 1 when RankGear finds an @type of Motorcycle in a page’s raw HTML, and 0 when it does not. It is a text-pattern check on source markup, not a validation of your structured-data graph — so a matching string outside valid JSON-LD can still register a 1.
| Factor ID | RG-SCJ-155 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether the page’s raw source contains an @type value of Motorcycle. It is a presence signal for the Schema.org Motorcycle type — the markup used to describe a single, specific motorcycle (make, model, identifiers, specifications, condition, and offer details). The factor answers one question only: does that type appear in the HTML, yes or no.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Motorcycle", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences in the type name do not change the result. It reads source text directly rather than parsing and validating a JSON-LD graph.
What RankGear looks for
"@type": "Motorcycle"
"@type": "schema:Motorcycle" <!-- schema: prefix allowed -->
"@type":"motorcycle" <!-- whitespace and case ignored -->| Value | Meaning |
|---|---|
| 1 | A Motorcycle @type string was found in the raw HTML. |
| 0 | No Motorcycle @type string was found in the raw HTML. |
How to optimize it
Use the Motorcycle type only for a page about one specific motorcycle, and give it accurate make, model, identifiers, specifications, condition, and offer details. Every property should reflect content a visitor can verify on the page. Treat this factor as an observation of whether that markup is present, not a target to chase: adding the string to a page that isn’t genuinely about a single motorcycle serves no reader and misrepresents the page.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is correct.
- A matching string that sits outside valid JSON-LD — in a comment, a script, or prose — can still produce a 1.
- Capitalization and whitespace differences around the type do not affect detection.
- Validate your complete structured data independently (for example, with a Schema.org or Rich Results validator) — this factor is not a substitute.
- Presence of this markup correlates with, and does not cause, ranking position; it is a prioritization signal within a measured result set, never a guarantee that a page will rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.