Has JSON-LD GeneralContractor reports whether RankGear finds an @type of GeneralContractor in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — but because the check pattern-matches source text rather than validating a JSON-LD graph, a 1 confirms only that the marker is on the page, not that the structured data is valid.
| Factor ID | RG-SCJ-094 |
|---|---|
| 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 GeneralContractor in the raw source of the page. It is a presence check for the schema.org GeneralContractor type — the markup a construction business uses to declare, in machine-readable form, that it coordinates and manages building projects. The result is binary: the marker is either found in source or it is not.
How RankGear measures it
RankGear searches the raw HTML for "@type": "GeneralContractor", allowing flexible whitespace around the colon and an optional schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not affect the result. It reads the raw source text directly; it does not parse or validate the surrounding JSON-LD structure.
What RankGear looks for
"@type": "GeneralContractor"
"@type":"schema:GeneralContractor" (optional schema: prefix, case-insensitive, flexible whitespace)| Value | Meaning |
|---|---|
| 1 | The GeneralContractor @type string was found somewhere in the raw HTML source. |
| 0 | No matching string was found in the raw HTML source. |
How to optimize it
Use GeneralContractor only for a genuine contracting business, and make the markup accurate: real services, credentials, area served, location, and contact data, with every property matching what a visitor sees on the page. Treat this factor as an observation that your page carries the marker — not as a target to force. Adding the string without a truthful, complete structured-data description does not improve the underlying entity the schema is meant to describe.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a well-formed schema and a stray matching string are indistinguishable to this check.
- A matching string that sits outside valid JSON-LD — in a comment, a script example, or escaped content — can still produce a 1.
- Capitalization differences do not affect detection, and an optional
schema:prefix is accepted. - Validate the complete structured data independently (for example with a schema testing tool) rather than relying on this presence signal alone.
- This is a correlation-based prioritization signal within a measured result set. Presence of the marker relates to how pages are described; it does not by itself make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.