This factor reports whether RankGear finds an @type value of GolfCourse in a page’s raw source. It returns 1 when the string is present and 0 when it is not. The detector pattern-matches source text rather than validating a full JSON-LD graph, so a match is a signal of intent, not proof of well-formed structured data.
| Factor ID | RG-SCJ-096 |
|---|---|
| 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 GolfCourse in the raw source of the page. It is a presence check: the page either declares the GolfCourse type somewhere in its markup, or it does not.
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "GolfCourse", allowing flexible whitespace around the punctuation and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. When a match is found the factor is 1; otherwise it is 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "GolfCourse",
"name": "...",
"address": { ... }
}
</script>| Value | Meaning |
|---|---|
| 1 | The string "@type": "GolfCourse" (case-insensitive, optional schema: prefix) appears in the raw HTML. |
| 0 | No such GolfCourse type declaration was found in the source. |
How to optimize it
Use the GolfCourse type only for a genuine golf course, with accurate location, facilities, hours, reservations, and contact information, and with properties that match the content visible on the page. Because this is a raw-source string check rather than a graph validation, treat a value of 1 as confirmation that the declaration exists, not as confirmation that the structured data is complete or valid. Validate the full JSON-LD independently before relying on it.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a value of 1 confirms the string is present, not that the markup is well-formed.
- A matching string that sits outside valid JSON-LD – for example in a comment, an example snippet, or escaped text – can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently to confirm it parses and describes the page accurately.
- This factor tracks how a measured result set relates to position; presence of
GolfCoursemarkup relates to ranking within that set and does not on its own cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.