JobPostingSchemaPulse / report

JobPostingSchemaPulse report: https://demo-co.example/jobs/123

Demo report on a fictional sample site.

Try a live example in 1 click:

53 / 100

5 of 8 checks need attention (0 high priority).

  • ✓ JobPosting structured data present (high): 1 JobPosting item(s).
  • ✓ Required fields: title, description, datePosted, hiringOrganization (high): 1 of 1 complete.
  • ✓ Location or remote type given (high): 1 of 1.
  • ✗ Remote jobs state eligible countries/states (medium): applicantLocationRequirements on remote postings.
  • ✗ validThrough not in the past (medium): Some postings are past validThrough (Google drops them).
  • ✗ Salary range (baseSalary) published (medium): 0 of 1 include baseSalary.
  • ✗ employmentType set (low): FULL_TIME, PART_TIME, CONTRACTOR, ...
  • ✗ Description at least 300 characters (low): Thin descriptions rank poorly.

Markdown version

Fix it in minutes

Get copy-paste fixes for every failing check.

See options

One read-only page request; checks JobPosting structured data in the HTML as served. Search engines decide whether to show job listings. Pay-transparency rules vary by state and city; this is not legal advice.

Often used together