You’re not imagining it: Indeed free job postings are effectively capped for many U.S. employers. If you post jobs directly on Indeed, you can typically run up to three free hosted jobs per calendar month, and each can stay live up to 30 days.
The catch is that “free” only means you can publish the job. It doesn’t buy you visibility or steady applicant flow. In this guide, you’ll see what triggers the cap in practice (hosted vs indexed jobs and one-source rules), plus how to plan around three slots without guessing, including when it’s worth sponsoring and when you should rely on your ATS or careers page feed instead.
Indeed Free Job Postings: the 3/month Rule
Indeed now says U.S. employers who post directly on Indeed can publish up to three free jobs per calendar month, with each free job live for up to 30 days under current indeed job posting rules. If you’ve been treating Indeed as always-on for 5, 10, or 30 reqs at a time, that approach stops scaling even when hiring volume stays the same.
What “free” doesn’t promise is visibility in the organic vs sponsored jobs indeed dynamic. A free job can be live and still generate little to no applicant flow because placement depends on how Indeed ranks and surfaces listings, and sponsored jobs get priority. Treat the three free posts as a limited allowance. Think of them like three exam rooms for triage, not a guarantee you’ll show up in search. Operationally, plan your month around three slots and avoid post and pray. Watch one simple signal: did you get qualified applicants within the first 24–72 hours of going live, or did the post fade from view?
What Triggers the Cap in Practice
You post a role you’ve posted a dozen times before, hit publish, and the results look nothing like last month. The surprise usually isn’t your job description, it’s how Indeed is deciding which version of your job counts as the real one.
Most teams hit the wall while posting hosted jobs directly on Indeed using their usual workflow. Indeed’s guidance treats free posting as a monthly allowance capped at three direct posts, each running up to 30 days. Running eight similar roles across three locations isn’t user error. It’s simply beyond the allowance.
The next gotcha is that “free on Indeed” isn’t one universal lane. Indeed has pushed a one-source model for organic visibility. That’s a good thing, because duplicate sources create messy data and worse decisions: if your jobs already reach Indeed through an ATS feed or an indexed careers page via indeed ATS integration, your attempt to also post the same jobs directly can get treated as a second source and nudged toward sponsorship. As an example, an HR generalist at a multi-site urgent care might have 25 openings flowing from their ATS and then try to add a direct post for a hard-to-fill MA role, only to find the direct option behaves like paid inventory.
Old “reset” tactics usually don’t change how the listing is counted or surfaced anymore. Reposting “the same job” to create a fresh free slot, or pushing a new copy of the req from your ATS, may not generate a truly new ad in Indeed’s system, especially in ATS-to-Indeed workflows.
A quick self-check you can run before you burn time troubleshooting copy:
-
Are you posting hosted jobs in Indeed (you created the job inside Indeed), or are jobs indexed/synced from elsewhere?
-
Do you have more than one pipeline feeding Indeed (ATS feed plus manual posts, staffing account plus client account)?
-
Are you trying to “refresh” by reposting the same title/location over and over, instead of treating it as one continuing opening?
Choosing Your Path After 3 Posts
After you’ve used the three free hosted posts, stop framing it as “How do I get the next job up?” That mindset turns into spray and pray. Start deciding what you’re buying: speed, coverage, or efficiency.
| Situation (after 3 free hosted posts) | Primary goal | Default move on Indeed | What to do instead/alongside |
|---|---|---|---|
| Urgent, business-critical role | Speed | Sponsor the job | Use free slots only if they still produce qualified applicants in 24–72 hours |
| Many similar openings (non-urgent) | Coverage/efficiency | Route via ATS/careers page feed | Run fewer, longer-lived postings; consider consolidating by region/shift when it matches hiring |
| Lower priority / can’t justify spend | Efficiency | Limit reliance on free hosted posts | Shift volume to alternatives: past applicants, referrals, local/community channels, role-specific boards |
For example, if you need a CNA this week because shifts are going uncovered, you’re solving a different problem than when you’re hiring three cashiers sometime this month.
Default to sponsorship when the role is urgent and business-critical. Otherwise, you’re just putting out fires tomorrow. Indeed publicly lists a floor of $5/day or $150/month to sponsor in its indeed posting pricing. Treat that as the cover charge to get into the room. For non-urgent, high-volume hiring, rely on your ATS or careers-page feed and reduce the number of active postings, using consolidation only when it matches how you staff. If you can’t justify spend and the role is lower priority, shift volume to alternatives you control, like reactivating past applicants or referrals, and keep Indeed for the positions where speed matters.
Budgeting and Workflow Adjustments
You stop burning a free slot on a Wednesday panic and start the month knowing exactly which roles get visibility and why. The payoff is fewer last-minute spend decisions and fewer awkward conversations about why a job is technically live but effectively invisible.
Indeed runs more predictably when free postings are planned inventory rather than a fallback. Start each month by forecasting your three free slots against known demand (urgent backfills and seasonal ramp). Pick the roles that will get paid visibility up front. Deciding spend in the middle of a panic req is a bad operating rhythm.
Operationally, set a baseline budget tied to Indeed’s published minimums ($5/day or $150/month) and a cadence that matches your throughput in Greenhouse (ATS): keep one or two “always hiring” roles live for the full 30 days and rotate the third slot only when the first 24–72 hours show weak qualified flow. Then reset stakeholder expectations in plain language. If a hiring manager wants five roles live this week across three locations, the outcome is either sponsorship or consolidation, not more “free” posts.
Contact Discover.ai for a personalized demo and consultation.
Content
