ICIMS Jobs Not Posting to Indeed: 7 Causes and Fixes

We hear some version of this every month: “Our ICIMS jobs are not posting to Indeed and nobody can tell me why.” The recruiter swears the job is live. The ICIMS admin sees it on the career site. The Indeed rep says the integration is active. And the candidate flow for that requisition is flat.

This guide walks through the seven causes we find most often, in the order we check them on client instances. Four of them live in ICIMS configuration. Three live on the Indeed side, and two of those changed in 2026, which is why teams whose Indeed feed worked fine last year are suddenly asking questions.

How an ICIMS job actually reaches Indeed

Before touching a setting, get clear on which path your jobs take. In our experience there are four, and most teams are running at least two of them without realizing it.

If you have not yet set up Path 1, start with our guide to ICIMS job board integrations setup. The rest of this post assumes the integration exists and the question is why a specific job is not showing.

Cause 1: The job was never posted to an eligible career portal

The problem. Every path to Indeed starts at an ICIMS career portal. ICIMS documentation is explicit that jobs must be posted to one or more career sites before they can be sent to a job board posting provider, and the Apply Network follows the same rule. A requisition that is approved and open but not posted to an external portal is invisible to Indeed, no matter how the integration is configured.

The impact. This is the single most common cause we find, and it is usually a process gap rather than a configuration gap. The recruiter opened the requisition, the approval chain finished, and everyone assumed posting was automatic.

The fix. Open the job profile, go to the posting section, and confirm the job is posted to an external portal (not just an internal or employee portal) with a post date that is not in the future. Confirm the requisition is in a status your portal configuration treats as displayable. If the job is not on your own career site either, this is not an Indeed problem at all; work through our guide to ICIMS career site not showing jobs first.

Cause 2: The Indeed integration is not validated or not mapped to the requisition

The problem. The Indeed integration has two halves and two owners. On the ICIMS side, an administrator configures Indeed in the Apply Network, creates an Apply Workflow, validates the connection with the Indeed employer login, and maps requisitions to that workflow. On the Indeed side, an Employer Home administrator with Integrations Hub access connects the integration, confirms the application data guideline, and publishes the jobs.

Indeed’s own install guide budgets about 30 minutes for the ICIMS step and 10 for the Indeed step. In practice the gap between the two steps is where integrations stall, because the ICIMS admin and the Indeed admin are rarely the same person.

The impact. A half-completed integration fails quietly. Jobs may show on Indeed without Indeed Apply, applications may arrive by email instead of landing in ICIMS, or nothing shows at all.

The fix. Work the checklist in order. In ICIMS, confirm Indeed appears in the Apply Network with a validated status, confirm an Apply Workflow exists for Indeed, and confirm the missing requisition is actually assigned to that workflow (new requisitions created from an old job template often are not). Then have the Indeed admin open the Integrations Hub and confirm the ICIMS integration shows as installed and the job list includes the requisition. Also note the current scope: Indeed states the ATS Sync for ICIMS supports US, English-only jobs today, so a job in another country or language will not flow through this path.

Cause 3: Indeed’s 2026 single-source feed policy

The problem. This is the cause that catches teams whose setup has not changed. Effective March 31, 2026, Indeed’s single-source feed policy states that jobs sent through single-source XML feeds will no longer appear for free if they can be sent through an ATS integration. Because ICIMS has an Indeed integration, an ICIMS customer relying on a standalone feed is exactly who the policy targets.

The same policy sets a second deadline: jobs from integrated ATS feeds delivered through ad-agency multisource feeds will no longer be visible after December 31, 2026. If a programmatic agency is pulling your ICIMS jobs and pushing them to Indeed on your behalf, that path is closing too.

The impact. Jobs do not disappear from Indeed’s systems. They move from organic to sponsored-only visibility. From a recruiter’s chair it looks identical to the job not posting: it cannot be found, and the application count is zero.

The fix. Move to Path 1. Indeed’s guidance for affected employers is to check whether your ATS integrates through the Integrations Hub and, if it does, to use that connection instead of the feed. For ICIMS customers that means activating and validating the Apply Network integration, then retiring the standalone feed so you are not also triggering Cause 4. This is also the point at which we recommend confirming your ICIMS source tracking setup, because applications that used to arrive tagged with an agency source will now arrive as Indeed Apply.

Cause 4: The same job is reaching Indeed twice

The problem. Indeed’s Job Posting Integrity and Duplicates policy is short: each job should appear only once on the platform, and employers should update an existing post rather than create a new one. When a job arrives through two of the four paths above, Indeed groups the listings and displays only the one it judges most relevant. Under that policy, first violations can result in posts being hidden, ranked lower, or required to be sponsored, and repeated violations can cost an employer access to free organic visibility altogether.

The impact. The duplicate Indeed keeps is often not the one you want. We have seen the agency copy win over the Apply Network copy, which means candidates redirect to a third-party page, Indeed Apply is off, and source data in ICIMS is wrong. And a recruiter who closes and reopens a requisition to “refresh” it on Indeed is creating a repost that the policy treats as a duplicate.

The fix. Pick one path and shut the others down. In ICIMS, unpost the job from any Posting Center vendor that also targets Indeed. On the Indeed side, close any manually created copies. Tell recruiters that the way to refresh a job is to edit the existing requisition, not to clone it. If you use multiple ICIMS career portals, check that the same job is not posted to two external portals with different URLs, because Indeed may index both.

Cause 5: The job content fails Indeed’s quality standards

The problem. Indeed moderates every job it receives, including jobs from an ATS, and it does so on its own side, so ICIMS never shows an error. Its published reasons for flagging or removing a job include titles that lean on buzzwords or exaggerate seniority, descriptions that are thin or spammy, keyword stuffing, missing key elements such as working conditions or required skills, incorrect location, application methods that require phone calls or a separate application on another site, and non-inclusive language.

In ICIMS terms, the usual offenders are a posting title that carries the requisition number or shift code, a job description iForm or field that was left as a two-sentence placeholder, a remote role whose location was left as headquarters, and instructions in the description to email a resume to the recruiter.

The fix. Compare the failing job against a job from the same portal that is showing on Indeed. In our experience the difference is usually the title or the location. Clean the posting title so it describes the work, make sure the location fields (city, state, country, postal code) are complete because those are the fields Indeed reads, and remove any apply-by-email instructions. Then edit the job in place rather than creating a new one. If your ICIMS career portals setup exposes a separate posting title field, that is the one Indeed sees, not the internal requisition name.

Cause 6: Something is wrong on the Indeed account side

The problem. Indeed’s own help article on why an employer cannot find a job lists several account-level reasons: the employer account is unverified, the account is under review and has reduced visibility, a sponsored job hit its daily budget limit and was removed from results until the next day, or the job was paused or closed inside Indeed even though it is still open in ICIMS.

One more that is specific to integrated setups: the integration was installed under a different Indeed employer account than the one your recruiters log into. Larger companies often have more than one Indeed account, and the ICIMS integration only knows about the one it was validated against.

The impact. Nothing in ICIMS will surface this. The job is sent, Indeed accepts it, and then Indeed’s account state decides whether anyone sees it.

The fix. Have the Indeed Employer Home administrator log in and check three things: account verification status, the job’s status in the Jobs tab, and, for sponsored jobs, whether the daily budget was exhausted. Confirm the account they are looking at is the one the ICIMS Apply Network was validated against. If the account is under review, Indeed will tell you what it needs; that is a conversation with Indeed support, not an ICIMS change.

Cause 7: You are checking the wrong way, or too soon

The problem. The most common “proof” that a job is missing is a recruiter searching Indeed for the job title and not finding it. Indeed says plainly that its search results are personalized based on the searcher’s activity, location, and interests, and that searching for your own job is not a reliable way to confirm it is live.

Timing matters too. The Apply Network path is fast, but a vendor pulling from the ICIMS Standard XML Feed is working from a file compiled three times a day, then applying its own processing window. A job posted at 4pm may not be with the vendor until the next morning and not on Indeed until later still. Organic listings also fall back in search results as newer jobs are posted, so a three-week-old job legitimately sits lower than it did on day one.

The fix. Verify the way Indeed recommends: open your Company Page and check the Jobs tab, or use the Jobs tab inside the employer account. Give a newly posted job a full business day before escalating. And if a job that is confirmed live is simply not getting applications, that is a job content or sponsorship question, not a posting failure.

Ten-minute diagnosis checklist

Run this top to bottom on one missing requisition. Stop at the first failure.

If a job passes all seven and still is not on Indeed, the remaining suspects are a job template or workflow profile that routes new requisitions away from the Indeed Apply Workflow. Those are the kinds of hidden dependencies an ICIMS system audit surfaces quickly, because we read the configuration end to end rather than one screen at a time. And when the answer is that the Indeed connection needs to be rebuilt or the agency feed retired, our ICIMS integration consulting team handles that work alongside ICIMS Professional Services.

One last recommendation. Assign an owner for the Indeed integration on the TA side and put a quarterly check on the calendar. Indeed’s feed policy changed in March 2026 and has another cutoff in December 2026, and the teams that noticed early were the ones with someone accountable for the connection. If nobody on your team has the bandwidth, that is precisely the kind of ongoing task our ICIMS managed services plan covers on a flat monthly basis. The measured ICIMS results we publish, including 90% fewer support tickets in 90 days for one client, came from exactly this kind of ownership.

Frequently asked questions