This factor returns 1 when RankGear finds the string "@type": "SkiResort" in a page’s raw rendered HTML, and 0 when it doesn’t. It is a case-insensitive text match, so a hit signals that SkiResort JSON-LD appears to be present — not that the structured data is valid or complete.
| Factor ID | RG-SCJ-240 |
|---|---|
| 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 SkiResort in a page’s raw source. It is a simple presence check for the SkiResort schema.org type, the JSON-LD entity used to describe a ski resort and its terrain, lifts, conditions, amenities, location, passes, hours, and contact details.
How RankGear measures it
RankGear searches the raw HTML for "@type": "SkiResort", allowing flexible whitespace around the tokens and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection. If the pattern is found anywhere in the source, the factor reports 1; otherwise it reports 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SkiResort",
"name": "Example Mountain Resort"
}
</script>| Value | Meaning |
|---|---|
| 1 | The "@type": "SkiResort" pattern was found in the raw HTML. |
| 0 | The pattern was not found in the raw HTML. |
How to optimize it
Use SkiResort only for a real ski resort, and only when the page presents terrain, lifts, conditions, amenities, location, passes, hours, and contact details that a visitor can verify on the page. Make sure every property reflects the actual content. Because the detector confirms presence of the type string rather than a target to chase, treat this factor as an observation of whether the markup exists — not a lever to force. If a page genuinely describes a ski resort, adding accurate SkiResort JSON-LD is the right move; if it doesn’t, this type should be absent.
Important considerations
- The detector pattern-matches source text instead of validating a full JSON-LD graph, so a reported 1 does not confirm the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — for example in a code sample or comment — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently with a schema validator before relying on it.
- This is a prioritization signal that relates to position within a measured result set. It does not, on its own, make a page rank or guarantee any ranking outcome.
Related factors
Part of the Factors reference · how RankGear measures · glossary.