Has JSON-LD JobPosting

Abstract illustration of a job-posting card linked to JSON-LD structured data detection, in RankGear indigo and coral.

Has JSON-LD JobPosting reports whether RankGear finds an @type value of JobPosting in a page’s raw HTML source — a simple 1/0 presence signal. It pattern-matches the source text rather than validating a JSON-LD graph, so a 1 means the string was found, not that the structured data is valid.

Factor IDRG-SCJ-129
FamilyStructured Data — JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of JobPosting in the raw source of the page. It answers a single yes/no question: does the markup that describes a job opening appear in the HTML? The result is a presence flag, not a quality or validity score.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "JobPosting", tolerating flexible whitespace around the colon and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.

Back to Top

What RankGear looks for

"@type": "JobPosting"
"@type":"JobPosting"
"@type": "schema:JobPosting"
ValueMeaning
1A JobPosting @type string was found in the raw HTML.
0No matching JobPosting @type string was found.
Back to Top

How to optimize it

Use JobPosting markup only for a real, current job opening. Populate it with an accurate employer, job title, description, location or remote status, posting and validity dates, compensation, qualifications, and application details. Ensure every property reflects content a user can verify on the page itself. Because RankGear detects the string rather than the graph, treat a 1 as confirmation that the markup is present — then validate the full structured data separately to confirm it is correct and eligible.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms presence of the string, not a well-formed JobPosting object.
  • A matching string that sits outside valid JSON-LD — in a comment, a code sample, or a malformed block — can still produce a 1.
  • Capitalization differences do not affect detection; matching is case-insensitive.
  • Validate the complete structured data independently before relying on it for eligibility.
  • This is a correlation-based prioritization signal observed within a measured result set. Presence of JobPosting markup relates to position; it does not make a page rank or guarantee a result.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top