This factor reports whether RankGear finds a MotorizedBicycle @type declaration in the page’s raw HTML — a simple present-or-absent (1 / 0) signal. It is a text match on the source, not a validated JSON-LD graph, so a string in the wrong place can still register as present.
| Factor ID | RG-SCJ-157 |
|---|---|
| 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 MotorizedBicycle in the raw source of the page. It answers a single yes-or-no question: does the markup declare a MotorizedBicycle schema type at all? It does not judge whether that declaration is complete, well-formed, or correctly nested inside a valid structured-data block.
How RankGear measures it
RankGear searches the raw HTML for "@type": "MotorizedBicycle", allowing flexible whitespace around the colon and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect detection. If the pattern is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "MotorizedBicycle"
"@type":"schema:MotorizedBicycle" (prefix optional, whitespace flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | A MotorizedBicycle @type string was found in the raw HTML. |
| 0 | No such string was found in the raw HTML. |
How to optimize it
Use MotorizedBicycle only for a page about a specific motorized bicycle, and populate it with accurate make, model, identifiers, specifications, condition, and offer details. Ensure every property reflects content a user can verify on the page itself. Because RankGear only confirms the type string exists, treat a value of 1 as evidence that markup is present — not proof that the structured data is valid or that it will influence ranking.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD — for example in a comment, a code sample, or unrelated script text — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a schema validator; RankGear’s check is presence only.
- This is a correlation-based prioritization signal within a measured result set. Presence of the type does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.