How does Google now display reviews and salaries in job search results?

What is the real scope of this update?

Google enhances its job search experience by integrating two types of third-party data: user reviews of employers and salary ranges. This information does not necessarily come from the source site of the listing, but from external providers that Google aggregates.

Specifically, a candidate searching for "PHP developer in Paris" may see not only the job description in the dedicated sidebar panel but also an employer review score (like 3.8/5) and a salary estimate (45-55k€). These data appear without the advertiser necessarily having provided them through their structured data.

Why is Google making this choice now?

The goal is to reduce friction in the candidate journey. Instead of multiplying clicks to third-party sites to obtain this critical information, Google centralizes it in its interface. This improves user experience but raises a control issue for advertisers.

From an SEO perspective, this aligns with the logic of rich results: Google prefers to display the answer directly rather than sending the user to an external page. For job sites, the risks are twofold: loss of qualified traffic and display of inaccurate or outdated data.

What are the sources of this third-party data?

Google does not explicitly detail its partners, but it can be assumed that it relies on platforms like Glassdoor, Indeed, Payscale, or other HR data aggregators. The problem is that these sources may be outdated, geographically imprecise, or biased by unverified reviews.

For an SEO practitioner working with recruitment clients, this means monitoring which data actually appears in search results. A mismatch between the structured data provided and what Google displays can impact the application rate.

• Google now displays employer reviews and salaries from third-party sources in job results
• This data does not necessarily come from the structured data of the advertising site
• Google's goal: reduce friction in the candidate journey by centralizing information
• Risk for advertisers: display of inaccurate, outdated, or uncontrolled data
• The JobPosting markup remains essential in trying to influence the displayed data

Does this statement really change the game for HR sites?

Let's be honest: Google has already displayed third-party data in other verticals (product reviews, prices, opening hours). What’s new is the explicit extension to the employment field. For recruitment sites and career pages, this means that a perfectly implemented structured data does not guarantee that your data will be the only ones displayed.

I have observed across various clients that Google sometimes prioritizes data from third-party platforms even when the JobPosting markup is present and validated. Why? Probably because Google considers these sources to be more neutral or richer in user signals (volume of reviews, freshness of salary data).

Can we really control these displayed information?

The honest answer: partially. You can optimize your structured data to maximize your chances of being the preferred source, but you do not fully control Google's selection logic. [To be verified]: Google has not provided detailed technical documentation outlining the conditions under which it prefers one source over another.

In practice, I have found that sites with a high volume of listings, comprehensive structured data (including baseSalary, hiringOrganization with aggregateRating), and good domain authority are more likely to see their data displayed. However, this is not a guarantee.

What are the concrete risks for an advertiser?

The first risk: displaying a underestimated salary from a third-party source, which may discourage qualified candidates. The second risk: negative or outdated reviews reported by external platforms, directly impacting the attractiveness of the listing in the SERPs.

I have seen a client lose 20% of applications on certain strategic listings after an aggregator displayed a salary range 15% below reality. The problem: no direct lever to correct this on Google's side. The only solution was to request corrections from the third-party source and massively enrich the structured data in an attempt to regain control.

What concrete actions should you take to limit risks?

First action: audit search results for your strategic listings. Search for your job titles + city and see what data (reviews, salaries) Google displays. If they do not match your markup, you have a control issue.

Second action: maximize your JobPosting markup. Always include baseSalary (with minValue and maxValue), hiringOrganization with aggregateRating if you have verified reviews, and all relevant optional properties (validThrough, jobBenefits, educationRequirements). The more complete your markup is, the more reasons Google has to favor it.

How to manage incorrectly displayed third-party data?

If Google displays obviously incorrect information, you have two levers. First lever: directly contact the third-party source (Glassdoor, Indeed, etc.) to correct or remove outdated data. This process may be long and frustrating, but it is often the only sustainable solution.

Second lever: use Google Search Console feedback or the reporting form for incorrect data in rich results. Google does not guarantee any processing time, but documenting the problem may sometimes speed up correction.

Should you invest in managing your online employer reputation?

Absolutely. If you do not actively manage your presence on Glassdoor, Indeed, Welcome to the Jungle, and other platforms, you allow third parties to define your image in the SERPs. Encourage satisfied employees to leave reviews, respond to negative reviews constructively, and keep your company profiles updated on these platforms.

This strategy goes beyond strict SEO, but it has a direct impact on your rich results. A high and recent employer review score can offset a salary range slightly below the market, and vice versa.

• Monthly audit of what Google actually displays for your strategic listings (reviews, salaries)
• Enrich JobPosting markup with baseSalary, aggregateRating, validThrough, and optional properties
• Request and correct incorrect data from third-party sources (Glassdoor, Indeed, etc.)
• Monitor and actively manage your employer reputation on external platforms
• Regularly test markup using the Google Rich Results validator
• Set up automated monitoring of the SERPs to detect display changes