feat: add jobPosting support for 'confidential' #1186
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change(s):
Adds a new "confidential" option to a JobPosting's
hiringOrganization
. Noted in #956.Noted in Google's Structured Data docs: "If the organization is hiring anonymously (for example, a staffing agency on behalf of an anonymous employer or an employer directly on your platform), use the confidential value for the HiringOrganization field." - https://developers.google.com/search/docs/appearance/structured-data/job-posting#job-posting-definition
To help get PR's merged faster, the following is required:
Please link to relevant Google Docs or schema.org docs for what you are adding so we can review.
Please have a read of the Contributing Guide for full details.
https://github.com/garmeeh/next-seo/blob/master/CONTRIBUTING.md