This factor reports whether RankGear finds a JSON-LD @type of Hotel in a page’s raw source. It returns 1 when the pattern is present and 0 when it is not — and because it matches source text rather than validating a structured-data graph, a 1 confirms the string appears, not that the markup is valid.
| Factor ID | RG-SCJ-109 |
|---|---|
| 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 Hotel in a page’s raw source. It is a presence check: the signal is 1 when a matching declaration exists in the HTML and 0 when none is found. It describes what the markup declares, not whether the page truly represents a hotel.
How RankGear measures it
RankGear searches the raw HTML for the "@type": "Hotel" declaration, allowing flexible whitespace around the colon and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences in the type value do not change the result.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Hotel",
"name": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A "@type": "Hotel" string was found in the raw HTML. |
| 0 | No matching declaration was found in the raw HTML. |
How to optimize it
Use the Hotel type only for a genuine hotel, with accurate rooms, amenities, location, offers, policies, and booking information, and with properties that match the page’s visible content. Treat the signal as an observation of what your markup declares rather than a target to satisfy for its own sake — adding the string without a real hotel behind it produces a 1 that misrepresents the page.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a 1 does not confirm well-formed structured data.
- A matching string that sits outside valid JSON-LD — in a comment, an example block, or malformed markup — can still produce a 1.
- Capitalization differences in the type value do not affect detection.
- Validate the complete structured data independently with a dedicated tool before relying on it.
- Presence of this markup correlates with, and is a prioritization signal within, a measured result set; it does not by itself cause or guarantee any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.