When ICIMS jobs not showing on Google for Jobs becomes a recruiter complaint, the cause is almost always a career portal setting rather than Google. ICIMS sets up customer career portals for Google to retrieve standard job information by default, so something has usually changed or been customized.
This guide covers the seven fixes we check, in order, and what is in your control versus Google’s.
How ICIMS jobs reach Google for Jobs
ICIMS partnered with Google as one of the first ATS providers in Google’s job search experience, which launched in 2017. Two mechanisms put your jobs in front of searchers:
- Structured data on the career portal. ICIMS maps Job profile fields to Schema.org JobPosting properties, such as title, job location, date posted, description, and hiring organization, so Google can read them from the job page.
- Indexing. Public career portals that allow indexing can be crawled by Google and by job aggregators.
7 fixes for ICIMS jobs not showing on Google for Jobs
ProblemNo jobs from a portal appear in Google job search at all.
ImpactEvery opening on that portal loses its largest free source of candidates.
ExampleA portal was set to private during a soft launch and never switched back.
FixGo to Admin > System Configuration > Career Portals > Portal Settings, pick the portal in the User Group dropdown, and check Allow Indexing (Google, etc.). ICIMS calls this the most common reason jobs fail to reach job board aggregators.
ProblemJobs posted to one portal show up in search while jobs on another never do.
ImpactRecruiters post to the wrong portal and lose visibility without knowing it.
ExampleInternal-only roles are posted to a hub portal and expected to appear publicly.
FixOnly career portals qualify. A hub or new hire portal does not, and the portal type is set when the portal is provisioned, so it cannot be reconfigured. Post public jobs to a public career portal.
ProblemJobs are posted and indexing is on, but nothing appears.
ImpactSearch engines and aggregators cannot read the job pages.
ExampleSecurity added a login wall or network restriction to the careers domain.
FixThe career portal must not require login to view job details or run searches, and must not have IP restrictions that interfere with the feed. ICIMS Technical Support configures both, so open a case.
ProblemSome recruiters’ jobs never reach the public portal.
ImpactVisibility depends on who posted the job.
ExampleA new recruiter user group was created without access to the public portal.
FixCheck Admin > System Configuration > Career Portals > User Group Settings > Allowed Portals so the right groups can post to the public career portal.
Jobs missing from Google?
We will check your portal indexing, access settings, and Postable Fields mapping on the call and tell you which of these seven fixes applies.
Book a discovery callFixes 5 to 7: schema mapping, company name, and job content
ProblemJobs appear but with missing salary, location, or description details, or not at all for some templates.
ImpactWeaker listings and lower visibility.
ExampleYour team replaced the standard location or salary fields with custom fields on the portal.
FixCustom fields have no default mapping. Go to Admin > System Configuration > Career Portals > Portal Settings, select Configure beside Configure Postable Fields, choose the portal and a section (Job Card, Job Header, or Job Description, the only sections search engines scrape), and set the Schema.org JSON-LD Property. Use Schema.org Only to share a field with Google without showing it to candidates. Settings are per career portal.
ProblemJobs show under an unexpected company name, or are hard to find under your brand.
ImpactCandidates searching your company name miss the listing.
ExampleA multi-brand company leaves the portal set to the parent name.
FixThe hiring organization comes from the Schema.org JobPosting Hiring Organization Name setting in System Configuration, which can be set per career site. Make it match your company name on job boards exactly. For multiple brands, ICIMS Technical Support can help set the brand per job instead of per portal.
ProblemSome jobs appear and others with the same settings do not.
ImpactInconsistent visibility that looks random.
ExamplePostings with only a city, no salary, and a two-line description, or titles stuffed with marketing text.
FixICIMS notes that boards look for job title, full location (at least city, state, country), salary information, posted date, job type, and a full description. Avoid reposting jobs frequently to refresh them and keep marketing text out of titles; ICIMS warns that boards can remove organic visibility for those behaviors.
The check order we use
- Open a job on the public career portal in a private or incognito window. If you cannot view it without logging in, start with fix 3.
- Confirm the portal is a career portal and Allow Indexing (Google, etc.) is checked.
- Confirm the posting user group has the portal in Allowed Portals.
- Review Postable Fields for custom fields without a Schema.org property.
- Check the Hiring Organization Name setting for each portal.
- Review job content against the fields boards look for.
- Wait, then escalate. After confirming the job is posted to a public portal that allows indexing and enough time has passed, contact ICIMS Technical Support with example job IDs.
Keeping expired jobs out of search
The opposite problem also comes up: closed jobs that linger. ICIMS maps Job Post End and the Post End Date field to the Schema.org Valid Through property by default. Keeping post end dates accurate tells search engines when a listing should stop showing.
If you also use a paid job board posting tool, remember that ICIMS does not remove those listings when a job closes. Jobs must be unposted manually from posting vendors through the Posting Center, so add that to your requisition close checklist.
How to keep your jobs visible
Frequently asked questions
Get your jobs back in search
Book a discovery call and we will review your career portal settings with you, then hand back a fix list your team can own.
Book a discovery call
