Should Job Listings Include the Salary Range?

should job listings include the salary range

Yes, job listings should include the salary range. A posted range helps candidates decide quickly, reduces back-and-forth on compensation, and makes the role easier to compare with other openings. Google’s job posting guidance also supports structured salary data, and many employers now treat pay transparency as part of a clean job post.

The part people get wrong is thinking salary disclosure is only about being nice to candidates. It is also a filtering tool. When the range is visible, people who would never accept the pay step out earlier, and the people who stay are closer to the offer you can actually make. That saves time on both sides and keeps interviews focused on fit, not on a number that was never realistic.

Google Search Central says job posting structured data can include baseSalary, and its job posting documentation says to use minValue and maxValue for a salary range rather than a single value. That matters because salary is not just a detail for the bottom of the listing, it is part of how the job is understood and surfaced. For the practical posting flow, see DevConnect, where the job listing format is built around clarity and direct comparison.

Candidates read a hidden salary range as a signal. Sometimes the signal is harmless, like an unfinished draft. Sometimes it is a warning that the employer is testing the market without a real budget. Indeed’s employer guidance says including salary information can help candidates quickly understand whether a role aligns with their needs, and it recommends presenting pay as a defined range. That is the standard many applicants now expect.

The inconvenient part is that a real range forces a real compensation decision. If the range is too wide, the listing looks vague and people assume the top number is fantasy. If the range is too low, strong candidates skip it before applying. If the range is too high, hiring managers may attract people the team cannot actually afford. A published range works only when it reflects what the business will truly pay.

Range disclosure also helps internal alignment. When a listing states the pay, recruiters, hiring managers, and candidates start from the same baseline. That cuts down on the awkward late-stage conversation where everyone has spent hours in interviews and then discovers they are far apart on compensation. The problem is not only disappointment, it is sunk time, slower hiring, and weaker trust in the employer brand.

There is a legal side too. In some places, salary disclosure is not optional. Pay transparency laws now require employers in certain jurisdictions to post salary ranges in job ads, and those rules change by state and city. A team that writes one national job post still needs to check the rules where the job is advertised, because one hidden range can become a compliance issue, not just a recruiting miss.

What should be posted is a real range, not a fake band designed to satisfy a form. A range that says one thing in the ad and another thing in the offer stage will backfire. The listing should match the budget for the role, the seniority level, and the actual hiring plan. If the company can only pay one fixed amount, say that amount. If the pay changes with location or experience, say how the range moves.

A useful test is simple: if a candidate asked for the range in the first message, would the team answer with the same numbers that appear in the post If not, the post is not ready. The listing should help the candidate self-select, not force them into a long process just to learn that the pay does not work for them.

Salary range disclosure is especially important for roles that attract many applicants. In those cases, the range acts like a shortcut. People who are overqualified, underpaid in their current role, or balancing family costs can sort faster. Hiring teams then spend less time screening resumes from people who were never likely to accept the offer anyway.

There is also a fairness argument, and it is not abstract. Hidden pay tends to reward the people most willing to negotiate from strength, while posted ranges make the conversation more legible to everyone. That does not remove negotiation. It gives negotiation a starting point. Candidates can still discuss experience, scope, and total compensation, but they do so with the baseline visible.

The best practice is to pair the salary range with enough context to make it meaningful. State whether the number is annual or hourly. Say whether bonuses, equity, commission, or overtime can change the total. If the range varies by location, list the rule that determines where a candidate lands. Clear posting does not reduce flexibility, it makes that flexibility understandable.

If a team cannot publish the range, the reason usually is not technical. It is usually that the compensation plan is not settled, the role is being defined late, or the organization wants room to negotiate from silence. Those are business choices, but they have a cost. They slow the process, lower trust, and make the job harder to compare against better-written listings.

So the answer is yes, include the salary range. It is the cleanest default for most roles, it improves candidate quality, and it avoids a lot of wasted time. When a law requires it, it is not a preference. It is the rule. When a law does not require it, the range still makes the posting stronger and the hiring process easier to run.

Sources and date notes: Google Search Central documentation on job postings and salary fields, Google Search Central blog on job search salary information, Indeed employer guidance on job postings and salary disclosure, and U.S. Department of Labor material on compensation and federal job announcements. The Google documentation cited here was retrieved on August 16, 2026.

FAQ

Do job listings always have to show pay? No. The answer depends on the location and the employer type. Some jurisdictions require disclosure, while others do not. Even where it is not required, posting a range usually improves screening and reduces compensation surprises later.

Is a single number better than a range? A range is usually better because it reflects seniority, experience, location, or scope differences. Google’s job posting guidance specifically points to minValue and maxValue for salary ranges, which matches how real hiring decisions usually work.

What if the company has commission, bonus, or equity? List the base pay range and then explain the variable parts in plain language. Candidates need to know what is guaranteed and what is conditional. Hiding the split between base and variable pay creates confusion when the offer arrives.

What happens if the range is too wide? The posting looks less credible, and candidates usually assume the employer is avoiding a real commitment. Wide ranges can still work when the spread is explained by level, location, or experience, but a vague band without context weakens the listing.

Should salary ranges go in the title or the description? Put them in the body of the listing and, where the platform allows it, in the structured salary field. The point is visibility and consistency. Candidates should not have to dig through paragraphs to find the pay.

Can a company still negotiate after posting a range? Yes. A range sets the starting frame, not the final offer. Good hiring uses the listing to set expectations, then uses interview evidence, scope, and experience to place the candidate inside that frame.