This factor reports whether RankGear finds a HomeAndConstructionBusiness @type value in a page’s raw JSON-LD structured data. It is a simple presence check (1 or 0) on the source text — it does not validate that the markup forms a correct JSON-LD graph.
| Factor ID | RG-SCJ-105 |
|---|---|
| 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 HomeAndConstructionBusiness in the page’s raw source. HomeAndConstructionBusiness is a schema.org LocalBusiness subtype used by home-service and construction firms — general contractors, HVAC, plumbing, electrical, roofing, and similar trades. The result is binary: the type is present in the source, or it is not.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration, allowing flexible whitespace around "@type": "HomeAndConstructionBusiness" and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. This is a text pattern match against the source — it does not parse or validate the surrounding JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HomeAndConstructionBusiness",
"name": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A HomeAndConstructionBusiness @type string was found in the raw source. |
| 0 | No such @type string was found. |
How to optimize it
Use HomeAndConstructionBusiness only for a genuine home-services or construction business, and prefer its most specific valid subtype (for example GeneralContractor, HVACBusiness, Plumber, Electrician, or RoofingContractor) when one applies. Populate its properties with values that match the visible content of the page. Because this detector only checks for the type string, treat a score of 1 as confirmation the string exists — not as proof your structured data is complete or valid.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present but not that the markup is correct.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated text — 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 to confirm it parses and resolves as intended.
- This is a prioritization signal that relates to pages in a measured result set; presence of the type is correlated with, and does not by itself cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.