Has JSON-LD Plumber is a yes/no check that reports whether your page’s raw HTML contains a JSON-LD @type of Plumber — the schema type that identifies a plumbing business to search engines. It returns 1 when that string is present and 0 when it is not; because it pattern-matches source text rather than parsing the JSON-LD graph, a match confirms presence, not that your structured data is valid.
| Factor ID | RG-SCJ-207 |
|---|---|
| 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 Plumber in the page’s raw source. Plumber is the schema.org business type used to describe a plumbing company, and its presence in JSON-LD is how a page declares that identity to search engines and other machine readers.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Plumber", allowing flexible whitespace around the colon and optionally accepting a schema: prefix. Matching is case-insensitive, so differences in capitalization do not change the result. A single match anywhere in the source sets the factor to 1.
What RankGear looks for
"@type": "Plumber"
"@type":"schema:Plumber"
"@type" : "plumber"| Value | Meaning |
|---|---|
| 1 | A @type of Plumber (with or without a schema: prefix) was found in the raw HTML. |
| 0 | No matching Plumber type string was found in the source. |
How to optimize it
Use the Plumber type only for a genuine plumbing business, and make every property accurate: services offered, service area, credentials, availability, location, and contact details. Ensure each value reflects content a visitor can verify on the page itself. Treat this factor as a check that the correct business type is declared, not as a target to chase — adding the string without truthful, matching content does not help and can mislead.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a passing result is not proof the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or unrelated markup — can still produce 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently (for example with a schema testing tool) rather than relying on this presence check alone.
- This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with, but does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.