Why Your Indeed Job Postings Are Losing Visibility After 30 Days
By the OnlyForRecruiters team
By the OnlyForRecruiters team | Published August 2026
This article is for in-house recruiters and TA professionals who post roles on Indeed and have noticed applications slowing down faster than before, especially for roles posted directly rather than through an ATS.
A role that used to bring in a steady trickle of applicants for weeks now goes quiet after a few. Nothing about the job changed. Nothing about the market obviously changed either. What changed is Indeed.
TL;DR
Indeed's own employer FAQ confirms it directly: a free job posting generally stays active for up to 30 days or until it hits a performance threshold, after which it may be paused or dropped from search results.
That 30-day window applies to jobs posted directly on Indeed, known as hosted jobs. Jobs that reach Indeed through a connected ATS, known as indexed jobs, are treated differently and get a longer runway, reported at up to 120 days.
A separate change took effect on March 31, 2026: jobs sent to Indeed through a single-source XML or API feed that isn't routed through an ATS supporting Indeed Apply no longer get free organic visibility at all.
If your team posts roles directly on Indeed, or if your ATS integration isn't fully connected to Indeed Apply, this is very likely why applicant flow has been dropping off faster than before.
The fix isn't more postings. Posting the same role twice, once through your ATS and once directly, can actually work against you, since Indeed won't grant free visibility to both versions of the same job at once.
What is organic visibility on Indeed?
Organic visibility is whether a job appears in Indeed's search results without the employer paying for placement. It's separate from sponsorship, which guarantees a higher ranking regardless of how the job was posted. A job can be live and technically searchable while still getting close to zero organic visibility, because visibility decays over time even for jobs that are still open.
That decay is what catches recruiters off guard. A posting doesn't need to be closed, expired, or flagged for a problem to stop showing up. It can simply age out of the window. Indeed, it currently allows for free reach, and the posting stays sitting there, live and invisible, while the recruiter assumes the market has just gone quiet.
What actually changed on Indeed in 2026?
Two separate changes stacked on top of each other, and most of the confusion comes from treating them as one thing.
The first change affects jobs posted directly on Indeed by an employer, without going through an ATS. As of a policy update that took effect in December 2025, free direct postings are capped at three per employer per calendar month, and organic visibility for those postings was cut from 120 days down to 30. Indeed's own employer-facing FAQ confirms the current version of this directly: a free job listing generally stays active for up to 30 days or until it reaches a performance threshold, after which it may be paused or removed from search results.
The second change affects jobs that reach Indeed through a feed rather than a direct post. As of March 31, 2026, jobs sent through a single-source XML or API feed that isn't connected to an ATS supporting Indeed Apply stopped receiving free organic visibility altogether. This closed a route some employers were using to get broad reach without either posting directly or using a fully integrated ATS.
Overall, the practical effect is that the amount of free, unpaid reach available on Indeed has been halved in the space of a few months, and the remaining reach depends heavily on exactly how a job reaches the platform.
What's the difference between a hosted job and an indexed job?
This distinction is the one most recruiters have never had to think about, and it's now the one that determines how long a role stays visible.
A hosted job is one an employer creates and posts directly on Indeed, without going through a career site or ATS. This is the fastest way to post a role, and it's the default for teams without a connected system. Hosted jobs are the ones now capped at three free postings per month, with a 30-day organic visibility window.
An indexed job is one that reaches Indeed by being scanned from an employer's career site, or pushed through an ATS integration. Indexed jobs are reported to be eligible for organic visibility for up to 120 days, four times the hosted window, though staying eligible for that full period isn't automatic. Visibility within it still depends on the usual quality signals: complete job details, accurate metadata, and a posting that isn't a near-duplicate of another listing.
The distinction matters because a team can be doing everything else right and still lose reach simply because of which posting method a role happens to travel through. Two identical job descriptions, one hosted and one indexed, do not get the same runway on the platform.
Why did this happen now?
Indeed has framed both changes as improvements to job seeker experience and search quality, aimed at reducing duplicate listings and low-effort postings. That's a real motivation. It's also not the whole picture.
The shift pushes more employers toward either a full ATS integration or paid sponsorship, and away from treating Indeed as an always-on, no-cost channel. For a platform where sponsored jobs already report getting several times more clicks than free listings, narrowing the free lane has a commercial logic to it as well as a quality one. Neither explanation cancels the other out. What matters operationally is the same either way: free reach on Indeed is smaller and more conditional than it was a year ago, and it's not coming back to the old baseline.
What should recruiters actually do about it?
Check how your roles actually reach Indeed before assuming the market slowed down. If postings go up through an account without a connected ATS, they're hosted jobs on the 30-day clock, no matter how the role was originally created internally.
Confirm the ATS integration specifically supports Indeed Apply. A feed connection alone isn't sufficient after the March 2026 change. If your ATS pushes jobs to Indeed but doesn't support Indeed Apply, that feed may no longer carry free organic visibility even though it looks connected on your end.
Don't post the same role twice. Posting a role directly on Indeed in addition to it already coming through your ATS doesn't add reach. Indeed doesn't grant free visibility to both an indexed and a directly posted version of the same job at once, so the second copy is more likely to compete with the first than extend it.
Watch applications in the first few days, not the full posting life. With a shorter and more conditional visibility window, the early signal matters more than it used to. A role getting few or no qualified applicants in the first 48 to 72 hours is worth investigating immediately rather than waiting out the full 30 days to see if it picks up.
Budget for sponsorship on roles where free reach won't be enough. This isn't a workaround, it's the tradeoff Indeed built into the change. For hard-to-fill or time-sensitive roles, treating sponsorship as the default rather than the fallback may now be the more realistic plan.
Rebuild part of your pipeline outside job boards entirely. A narrower free-reach window is one more reason not to depend on any single platform for candidate flow. Our Boolean search guide for recruiters covers how to source candidates directly instead of waiting on a job posting to surface them.
Frequently asked questions
What is Indeed's 30-day rule?
It's the current limit on how long a freely posted job on Indeed generally stays active in search results before it may be paused, confirmed directly in Indeed's own employer FAQ. It applies to hosted jobs, meaning roles posted directly on Indeed rather than through a connected ATS or career site.
Does the 30-day limit apply to jobs posted through an ATS?
Jobs that reach Indeed as indexed postings, through a career site scan or a full ATS integration, are reported to get a longer window of up to 120 days rather than 30. Reaching that eligibility still depends on posting quality and avoiding near-duplicate listings.
Did Indeed stop free job postings entirely?
No. Free postings still exist, but they're capped and time-limited. Hosted jobs are limited to three free postings per employer per month with a 30-day visibility window, and jobs sent through unintegrated single-source feeds no longer receive free organic visibility at all as of March 31, 2026.
Will posting the same job twice help it get seen more?
No, and it can work against you. Indeed does not grant free organic visibility to both an indexed version and a directly posted version of the same role at the same time, so duplicating a posting is more likely to split or suppress visibility than add to it.
How do I know if my jobs are hosted or indexed on Indeed?
Check how the posting was created. If it went up through a direct Indeed account without a connected ATS or career site feed, it's hosted. If it came from your ATS through an integration, particularly one that supports Indeed Apply, it's indexed. When in doubt, this is worth confirming directly with your ATS provider or Indeed account contact, since the difference now has a real effect on visibility.