Has JSON-LD HVACBusiness

Abstract illustration of an HVAC unit inside JSON-LD schema brackets, in RankGear indigo and coral.

Has JSON-LD HVACBusiness reports whether a page’s raw HTML contains a JSON-LD @type of HVACBusiness — the schema.org type for a heating, ventilation, and air-conditioning business. It returns 1 when that string is present and 0 when it is not; because RankGear pattern-matches the source text rather than parsing the JSON-LD graph, a match confirms the markup exists, not that it is valid or accurate.

Factor IDRG-SCJ-120
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 HVACBusiness in a page’s raw source. HVACBusiness is the schema.org type reserved for a genuine heating, ventilation, and air-conditioning business, and it is one of many local-business subtypes RankGear can detect. The factor is a simple binary observation of the markup’s presence — it does not grade the quality, completeness, or correctness of the structured data.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the "@type": "HVACBusiness" string, tolerating flexible whitespace around the colon and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. Any occurrence of that string in the source sets the factor to 1.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HVACBusiness",
  "name": "..."
}
</script>

# also matched (schema: prefix, flexible whitespace, any case):
"@type":"schema:HVACBusiness"
ValueMeaning
1The HVACBusiness @type string was found in the raw HTML.
0No matching HVACBusiness @type string was found.
Back to Top

How to optimize it

Use HVACBusiness only for a real heating, ventilation, and air-conditioning business, with accurate services, service area, credentials, location, hours, and contact details. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation that the correct markup is present, not a target to force — adding the string without a valid, honest JSON-LD graph behind it gains nothing and can misrepresent the business.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a full JSON-LD graph, so a 1 confirms the string exists — not that 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; matching is case-insensitive.
  • Validate the complete structured data independently with a schema validator — this factor is not a substitute for that check.
  • Correlation is not causation: this factor tracks the presence of a signal within a measured result set and helps prioritize work; it does not by itself make a page rank or guarantee any position.
Back to Top

Related factors

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

Back to Top