Has JSON-LD HairSalon

Has JSON-LD HairSalon reports whether RankGear finds a "@type": "HairSalon" value in the page’s raw HTML source. It returns 1 when the string is present and 0 when it is not. It is a text match, not a validation of the underlying JSON-LD graph, so a stray match can register even when the structured data is malformed.

Factor IDRG-SCJ-100
FamilyStructured Data – JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of HairSalon in the raw page source. HairSalon is a schema.org local-business subtype used to describe a salon as a structured entity for search engines. The result is a simple presence signal: the type string is either there or it is not.

How RankGear measures it

RankGear searches the raw HTML for the "@type": "HairSalon" string, allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HairSalon",
  "name": "...",
  "address": { "@type": "PostalAddress", ... }
}
</script>
ValueMeaning
1A HairSalon @type string was found in the raw HTML.
0No HairSalon @type string was found.

How to optimize it

Use the HairSalon type only for a real salon, with accurate services, prices, location, hours, booking, and contact details, and make sure the marked-up properties match the content a visitor actually sees on the page. Because this factor only confirms that the type string is present, treat a score of 1 as a starting point rather than proof of correct markup: the string being detectable does not mean the JSON-LD is valid or complete.

Important considerations

  • The detector pattern-matches source text rather than parsing and validating a JSON-LD graph.
  • A matching string that sits outside valid JSON-LD (for example in a comment or an example snippet) can still produce a 1.
  • Capitalization differences do not affect detection, since matching is case-insensitive.
  • Validate the complete structured data independently with a dedicated schema validator before relying on it.
  • This is a correlation-based prioritization signal within a measured result set, not a guarantee of ranking; presence of the type does not by itself cause a page to rank.

Related factors

Part of the Factors reference · how RankGear measures · glossary.