Has JSON-LD Resort is a 0 / 1 flag for whether a page’s raw source contains an @type value of Resort in its JSON-LD structured data, which describes a resort property. Important caveat: it pattern-matches source text rather than validating a JSON-LD graph, so a 1 does not prove the markup is valid.
| Factor ID | RG-SCJ-227 |
|---|---|
| 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 Resort in the page’s raw source. The Resort type describes a resort property — a lodging destination with rooms, amenities, activities, and on-site services — declared in a machine-readable form so search engines can interpret the entity. The value is simply present (1) or absent (0).
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Resort", allowing flexible whitespace around the value and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences in the markup do not affect the result. The factor returns 1 when the pattern is found in the source and 0 when it is not. It is a text match against source, not a parse and validation of the underlying JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Resort",
"name": "Blue Lagoon Resort",
"amenityFeature": [ ... ],
"address": { ... }
}
</script>
# matched pattern (case-insensitive, optional schema: prefix):
# "@type": "Resort" / "@type": "schema:Resort"| Value | Meaning |
|---|---|
| 1 | An @type value of Resort was found in the raw source — but because this is a text match, it can also be produced by a matching string that sits outside valid JSON-LD. |
| 0 | No Resort type string was found in the source. |
How to optimize it
Use Resort only for a genuine resort, and only with accurate details — rooms, amenities, activities, location, availability, policies, ratings, and contact information. Ensure every property in the markup reflects content users can verify on the page. Because the detector matches source text rather than validating structure, treat a passing score as an observation, not a target: do not add or manipulate the string to influence the flag. Validate the complete structured data with an independent tool to confirm it is well formed and eligible for rich results.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 does not confirm well-formed markup.
- 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 rather than relying on this presence flag alone.
- 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.