Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Salary Range support & add to Google Schema #2629

Open
masteradhoc opened this issue Nov 7, 2023 · 0 comments · May be fixed by #2633
Open

Add Salary Range support & add to Google Schema #2629

masteradhoc opened this issue Nov 7, 2023 · 0 comments · May be fixed by #2633

Comments

@masteradhoc
Copy link
Contributor

masteradhoc commented Nov 7, 2023

Is your feature request related to a problem? Please describe

As i saw on #2263 the salary schema was added. For now it only supports one salary amount but no range.
This was added in the PR as further enhancement but no task was created or followed up as far as i see, right @onubrooks?

Describe the solution you'd like

Ranges should also be supported asap. I would suppose the following. For all current installations we use the _job_salary Field same as it is right now. It will generate a schema like this:

"baseSalary": {
  "@type": "MonetaryAmount",
  "currency": "USD",
  "value": {
    "@type": "QuantitativeValue",
    "value": 40.00,
    "unitText": "HOUR"
  }
}

Additionally we'll add a second field for _job_salary_max. if this field is also filled out we'll generate schema like this:

"baseSalary": {
  "@type": "MonetaryAmount",
  "currency": "USD",
  "value": {
    "@type": "QuantitativeValue",
    "minValue": 40.00,
    "maxValue": 50.00,
    "unitText": "HOUR"
  }
}

It respects the Structure of google requested here: https://developers.google.com/search/docs/appearance/structured-data/job-posting

Describe alternatives you've considered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant