JobPosting schema present but missing baseSalary with minValue/maxValue
This check inspects your JobPosting schema, a block of structured data (code search engines read but visitors don't see) attached to each job ad, for a baseSalary field with a minimum and maximum value. Your JobPosting schema is present, but it's missing baseSalary with minValue and maxValue.
Why this matters
The EU Pay Transparency Directive (Article 5) requires member states to apply pay information rules to recruitment from 7 June 2026, and national implementation varies. Vague wording like 'competitive' is unlikely to meet a requirement for a pay range, so check how the rules apply where you hire. Google for Jobs and some job platforms can display salary ranges when they are supplied in structured data, and they may not show a salary for postings that omit it.
How to fix it
Your developer and people team should add baseSalary to the JobPosting JSON-LD as a MonetaryAmount object with a currency, and minValue and maxValue under QuantitativeValue, for example a EUR 60,000 to 80,000 yearly range. This is roughly a day of work to add to every live posting.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit