Has JSON-LD SportsClub is a 0 / 1 flag for whether the raw HTML contains an @type value of SportsClub, the schema.org type for a sports club or athletic organization. Important caveat: it pattern-matches the source text rather than validating a JSON-LD graph, so a stray matching string can return 1 even when no valid markup exists.
| Factor ID | RG-SCJ-245 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Boolean presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of SportsClub in the raw source. SportsClub is the schema.org type for a sports club or athletic organization, and its structured data would describe the club’s sport, teams, members, facilities, schedule, location, and contact details in a machine-readable form.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "SportsClub", allowing flexible whitespace around the tokens and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences in the source do not change the result. The factor returns 1 when a match is found and 0 when it is not.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SportsClub",
"name": "Riverside Rowing Club",
"sport": "Rowing",
"address": { ... }
}
</script>
# matched (case-insensitive, flexible whitespace, optional schema: prefix):
# "@type": "SportsClub"
# "@type":"schema:sportsclub"| Value | Meaning |
|---|---|
| 1 | The "@type": "SportsClub" pattern was found in the raw HTML. |
| 0 | No matching pattern was found in the raw HTML. |
How to optimize it
Use SportsClub only for a genuine sports club, with an accurate sport, teams, members, facilities, schedule, location, and contact details. Ensure every property reflects content users can verify on the page. Because this detector matches source text rather than a validated graph, treat the value as an observation of what is present in the HTML, not as a target to chase — the goal is truthful, well-formed structured data, not a matching string.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema validator.
- Structured data correlates with, and does not guarantee, ranking outcomes; it is a prioritization signal measured within a result set, not a cause of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.