This factor reports whether RankGear finds a JSON-LD @type of BowlingAlley in the raw HTML of a page — a 1 when the string is present, a 0 when it is not. It is a text match, not a schema validator, so a match confirms the marker is on the page, not that the structured data is valid.
| Factor ID | RG-SCJ-038 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor records whether the page declares a BowlingAlley entity in JSON-LD structured data. RankGear reports a 1 when it finds an @type value of BowlingAlley in the raw source, and a 0 when it does not. It is a presence signal for a specific schema.org type used to describe a bowling venue, not a judgement of how complete or correct the surrounding markup is.
How RankGear measures it
RankGear runs a case-insensitive search over the raw HTML for the @type declaration, with flexible whitespace around the colon and value and an optional schema: prefix on the type. Capitalization differences do not change the result. Because it matches text rather than parsing the JSON-LD graph, the check looks for the literal type declaration wherever it appears in the source.
What RankGear looks for
"@type": "BowlingAlley"| Value | Meaning |
|---|---|
| 1 | A BowlingAlley @type declaration was found in the raw HTML. |
| 0 | No BowlingAlley @type declaration was found. |
How to optimize it
Use BowlingAlley only for a genuine bowling venue, and give it accurate properties — location, hours, contact, and any offer details — that match the content visitors can see on the page. The type should describe the real business, not be added to trigger the marker. If the page does not represent a bowling alley, this factor is simply an observation that the type is absent rather than a gap to fill.
Important considerations
- RankGear pattern-matches text rather than parsing or validating the JSON-LD graph, so a 1 means the string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — for example in a comment or a code sample — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- 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.