Has JSON-LD Occupation reports whether RankGear finds an @type value of Occupation inside a page’s raw HTML. It returns 1 when the string pattern is present and 0 when it is not — and because the detector matches source text rather than validating a JSON-LD graph, a 1 confirms the marker exists, not that the structured data is valid.
| Factor ID | RG-SCJ-182 |
|---|---|
| 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 for Occupation in the raw source of the page. It is a binary observation: the Occupation schema marker is either present in the HTML or it is not. It relates to whether a page describes a defined role — its responsibilities, qualifications, compensation, region, and related skills — using the schema.org Occupation type.
How RankGear measures it
RankGear searches the raw HTML for flexible whitespace around "@type": "Occupation", optionally allowing a schema: prefix on the type value. Matching is case-sensitive, so the source must use the exact capitalization Occupation to match. Any match anywhere in the source text returns 1; no match returns 0.
What RankGear looks for
"@type": "Occupation"
"@type": "schema:Occupation"| Value | Meaning |
|---|---|
| 1 | The Occupation @type string was found in the raw HTML (optionally with a schema: prefix). |
| 0 | No matching Occupation @type string was present in the source. |
How to optimize it
Use Occupation only for a genuine occupation with accurate responsibilities, qualifications, estimated compensation, region, and related skills. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of whether the marker is present rather than a target to force onto pages that do not describe a real role — adding the type where it does not belong misrepresents the page without any measured benefit.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the marker exists, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or plain text — can still produce a 1.
- The source must use the exact capitalization
Occupation; a different case will not match. - Validate the complete structured data independently with a schema validator before relying on it.
- This is a prioritization signal that relates to position within a measured result set. It does not make a page rank or guarantee any position — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.