This factor reports whether RankGear finds a JSON-LD @type of DaySpa in a page’s raw source. It is a binary presence signal (1 = found, 0 = not found): it confirms the string is present, not that the surrounding structured data is valid or accurate.
| Factor ID | RG-SCJ-068 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
RankGear checks whether the page declares a DaySpa entity in JSON-LD structured data. DaySpa is a schema.org local-business type used to describe a day spa — its services, hours, location, and booking details. The factor returns 1 when an @type value of DaySpa appears in the raw source and 0 when it does not.
How RankGear measures it
RankGear searches the raw HTML for the text "@type": "DaySpa", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not change the result. This is a text pattern match against the source, not validation of a parsed JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "DaySpa",
"name": "Example Day Spa"
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of DaySpa was found in the raw source (any capitalization, with or without a schema: prefix). |
| 0 | No DaySpa type string was found. |
How to optimize it
Use DaySpa only for a genuine day spa, and make the structured data describe the real business: accurate services, pricing, location, hours, booking, and contact details, with properties that match what a visitor sees on the page. Because this factor pattern-matches source text rather than validating a graph, treat a value of 1 as a starting point — confirm the markup is well-formed and truthful rather than treating the string’s presence as the goal.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a value of 1 does not confirm the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — for example in a comment or an unrelated script — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a schema validation tool.
- This is a correlation-based prioritization signal within a measured result set, not a guarantee of ranking or a cause of it.
Related factors
Part of the Factors reference · how RankGear measures · glossary.