This factor reports whether RankGear detects an @type of ProfessionalService in a page’s JSON-LD, returned as a simple present-or-absent (1 / 0) signal. It pattern-matches the raw HTML source rather than validating the structured-data graph, so a match confirms the string is present — not that the schema is valid.
| Factor ID | RG-SCJ-212 |
|---|---|
| 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 ProfessionalService in the raw source of the page. It is a presence check: it tells you that the ProfessionalService schema type appears in the markup, which is the structured-data vocabulary used to describe a business that provides a professional service to clients.
How RankGear measures it
RankGear searches the raw HTML for the text "@type": "ProfessionalService", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so capitalization differences in the markup do not change the result. If the pattern is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfessionalService"
}
</script>
<!-- also matched (schema: prefix, extra whitespace, any case) -->
"@type" : "schema:professionalservice"| Value | Meaning |
|---|---|
| 1 | A ProfessionalService @type string was found in the raw HTML. |
| 0 | No ProfessionalService @type string was found in the raw HTML. |
How to optimize it
Use ProfessionalService only for a page that genuinely represents a professional service, and make the markup describe expertise, credentials, offerings, service area, location, and contact details accurately. Every property should reflect content a user can verify on the page itself. Treat this factor as an observation of what your markup contains, not a target to hit for its own sake — adding the type to a page that is not a professional service misrepresents the page and gains nothing.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still return 1, so a positive result is not proof of correct structured data.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set — it does not, on its own, cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.