Hello,
I apologize for the issue you are facing with the Job Posting Schema and Google’s rich results testing tool. To address the problem of having two job postings with the same name, one created by the Job Posting Schema and the existing one, you need to ensure that the Job Posting Schema is used only on pages with individual job listings.
If you are seeing multiple job postings with the same name, it might be due to using the Job Posting Schema on a page that includes multiple job listings. This can lead to a structured data policy violation error in Google Search Console.
To resolve this issue, you should remove the Job Posting structured data from pages that have multiple job listings. The Job Posting Schema should only be used on pages that contain individual job listings.
If you need further assistance or have any other questions, please feel free to ask. Thank you for bringing this concern to our attention.
Sources:
JobPosting Schema Type » Rank Math
Hello,
Thank you for your query and we are so sorry about the trouble this must have caused.
It seems that the job posting plugins you are using are also generating their own JobPosting schema. Please contact them if there’s a way to disable their schema to resolve the validity issue of your page.
Don’t hesitate to get in touch with us if you have any other questions.
Hey, thank you for your feedback.
Pls let me know whether you have any job postings plugin or any such plugin that you support.
I’ve checked your link with supported plugins, but couldn’t find any of them, pls advise.
Hello,
Unfortunately, we don’t have any job posting plugins to recommend.
Most of the time, these type of plugins uses CPTs to generate job posting content and our plugin can integrate the JobPosting schema with the correct configuration and setup from the user.
As for your current situation, the plugin you used is simply creating its own JobPosting schema so it causes duplication of schema and invalidity in the Rich Result.
There must be a way for that plugin to stop generating their own schema so you’ll have to contact their developers.
Looking forward to helping you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
