Getting Your Jobs to Show on Indeed

Last updated: September 9, 2026

You published a job in Classet and it never showed up in your Indeed account. In nearly every case we've seen, the job did reach Indeed. It just isn't linked to your account yet. Here's how to check, and how to get Indeed to link it.

What's happening

When Classet sends a job to Indeed, it lands under a job source. That's the label Indeed uses to group everything one system sends for one company. Yours might be "Summit Plumbing LLC" or "Brightline HVAC of Central Ohio".

Indeed doesn't connect that source to your employer account on its own. Someone at Indeed has to claim it for you. Until they do, your jobs sit live in Indeed's system where you can't see them, can't edit them, and can't work the candidates who apply.

Nothing is lost while you wait. When Indeed claims the source, every job that already arrived shows up, including ones posted weeks ago. You won't need to repost anything.

Will I need to do this?

Often not. It comes down to whether Indeed already knows your source name when your first job arrives.

If your company already posts on Indeed and you typed your existing Job Source name into Classet exactly as Indeed has it, new jobs join that source and appear right away.

You'll need to get the source claimed when:

  • Your Indeed account is new. With no jobs posted yet, there's no existing source name to copy, so the one you enter is new to Indeed and arrives unclaimed.
  • The name doesn't match exactly. A typo, or "LLC" where Indeed has "L.L.C.", creates a second source instead of joining your existing one. You won't see an error. It just looks like nothing happened.
  • You have more than one Indeed account. The wrong brand or location can end up claiming the source, and your jobs show under a company you didn't expect.
  • A source was moved between accounts. Whoever it moved away from stops seeing those jobs.

One thing that trips people up: connecting Indeed inside Classet doesn't claim anything. Signing in to Indeed from Classet lets us post your jobs and read how they're doing. Only Indeed can make you the owner of a job source. So you can finish every step in Classet, see a healthy connection, and still not find your jobs in Indeed.

Fixing it

1. Find your source name in Classet

Go to Settings → Integrations and open your Indeed connection. The Source Name shown there is what Indeed sees. Copy it character for character, including any "LLC" or location suffix.

2. Get your account details together

Indeed will check that you own the account before changing anything. For each Indeed account involved, have these ready:

  • Last four digits of the phone number on the account
  • Last four digits of the card on file
  • The account owner's email address
  • The exact title of your most recent job post. Indeed accepts this instead when there's no phone or card on file yet, which is common on a new account.

3. Contact Indeed support

Open the chat from your Indeed Employer Console. Ask for the specific thing you need instead of describing the symptom. An agent can act on a named source right away, while "my jobs aren't showing" starts a much longer conversation.

I need the job source [your source name] claimed by my [account owner email] account. The jobs are coming from Classet, our ATS.

They'll ask which ATS. The answer is Classet. They'll then find the jobs and link the source, which takes a few minutes.

4. Check it worked

Your jobs now appear under the All jobs tab in the Employer Console. Open one and confirm the second line under the title reads Job Source: [your source name]. If the job count looks wrong, say so in the same chat before it closes. The agent still has your verification and can fix it on the spot.

How to tell a source is working

All four of these should be true. If one fails, the source isn't fully connected.

  1. Your jobs are listed under All jobs in the Employer Console. If they're missing, the source still isn't claimed.
  2. Each job's Job Source matches the Source Name in Classet. A mismatch means Indeed claimed a different source, most likely another brand or location you own.
  3. Publishing a new job in Classet makes it appear on Indeed. Give it a few hours, since new postings go through review before they're searchable.
  4. Job status reads Active, not Flagged. Flagged means the source is connected but something else is keeping the job hidden. See the next section.

My jobs show up, but they're flagged

If you can see the jobs, the claim worked. Flagged is a separate problem: you can see the job but job seekers can't. Two causes come up most.

The job needs sponsorship to appear. Indeed shows "This job has been flagged and must be sponsored to go live on Indeed" with a Sponsor now button. Adding budget to that job clears it.

Your franchise brand has an exclusive ATS arrangement. Some franchise brands agree with Indeed that only one ATS posts for free. Jobs sent from any other system, Classet included, then need sponsorship before job seekers can see them, even though they post fine. If you're part of a franchise network and every job comes back flagged, ask Indeed whether your brand has an arrangement like this. Your franchisor will know the details. Indeed support may not.

A rejected job is a different case. If Indeed rejected a posting, sponsoring it won't help, and neither will reposting the same content. Open the job in your Employer Console to see what Indeed objected to, change that, then republish from Classet.

If you run more than one Indeed account

Companies with several brands or locations often keep one Indeed account for each. Classet sends a separate source for each connection, so each account has to claim its own.

  • Do them one at a time. Indeed verifies each account on its own, with that account's phone, card, and owner email.
  • Check for a wrong claim first. If one account claimed another's source, the jobs show under the wrong brand. Ask the agent to unlink it in the same conversation. They can move a source, not just add one.

If a source moved, reconnect Classet

Classet checks on your jobs by signing in to Indeed as one specific user: whoever connected the integration. If Indeed moves your source to a different account, Classet is still signed in as the old one. Indeed refuses those requests, and we lose the ability to tell you whether a job is live, rejected, or waiting on sponsorship. Your jobs keep posting. We just can't see what happened to them.

To fix it, go to Settings → Integrations, disconnect Indeed, and connect again, signing in as the account that now owns the source.

Still not showing after all four checks pass? Contact Classet support with your source name and the job title, and we'll look at what Indeed is reporting for that posting.