Guide
How to auto-apply to jobs on Indeed (and what breaks)
We build an applying engine for Indeed, which mostly means we have met its failure modes. This is the practical version: what the two apply buttons mean, why tools stall, and how to automate without handing your account over.
Updated September 9, 2026
Indeed is really two sites
Every automation decision on Indeed follows from one fact: some postings are applied to inside Indeed, and some are applied to on the employer's own system. The search results look identical. The work behind the button is not remotely the same.
Indeed's own flow is short and predictable — a handful of steps, screener questions, a resume already on file. The handoff postings drop you into whatever ATS the company bought, with its own field names, its own required answers, and its own idea of what a phone number looks like. Coverage lives or dies on that second group.
Five steps that make automated applying actually work
This works whether you use HireDrop, something else, or a keyboard and a free evening.
- 1
Separate the two kinds of posting before you automate anything
Read the button, not the listing. Apply nowkeeps you inside Indeed's own apply flow. Apply on company sitehands you off to the employer's applicant tracking system — Greenhouse, Lever, Ashby, Workday and dozens more, each with its own form.
Any tool that only handles the first kind quietly skips a large share of the good postings. Any tool that claims to handle the second kind has to actually understand ATS forms, not just fill two text fields.
- 2
Get your profile complete enough that forms don't stall
The fields that stop an automated application are rarely the obvious ones. Work authorisation, sponsorship, years of experience per skill, notice period, salary expectation, city and postcode, and the disability/veteran self-identification blocks are what forms hang on.
Fill these once, properly. A half-filled profile turns every multi-step form into a dead end halfway through, and a dead end mid-form is worse than not applying — some ATSes record the partial submission.
- 3
Be logged in where it actually counts
This one costs people whole evenings. Indeed treats browsing and applying as different sessions. The header on the search pages can show you as signed in while the apply flow does not recognise you at all — so the automation sails through the search and fails at the last click.
Before a batch, open one posting and start an application by hand. If the apply screen asks you to sign in, that is the session that matters — fix it there, not on the search page.
- 4
Cap the day and spread it out
Pick a daily number you could plausibly have done yourself — a few dozen, not a few hundred — and let it run across hours rather than minutes. Job boards detect automation by rhythm: bursts, identical payloads, activity at 4am every day.
Also watch the timezone your cap resets in. If the tool counts “today” in UTC while you live in California, your day ends at 4 or 5pm and the evening looks like a second day of activity.
- 5
Read the first ten before you trust the next hundred
Whatever you use, keep a review step on at the start. Look at ten finished applications: did it answer the screener questions sensibly, did the cover letter reference the actual posting, did it pick roles you would have picked?
This is the cheapest quality control there is, and it is the step every volume-first tool encourages you to skip.
What we learned the hard way
A few specifics, since they cost us real debugging and they generalise to any tool you try:
Buttons lie by position. Forms often have two plausible primary buttons on one screen — a search or filter action and the real Continue. Click the wrong one and the flow loops forever while reporting no error at all.
Not every platform ends in “Submit”.Some apply flows finish on a differently-labelled final action, so a tool that waits for the word “Submit” sits there believing it has not finished — and you think nothing was sent when it was, or the reverse.
Dropdowns are frequently not dropdowns. On Indeed many selects are custom components rather than native HTML ones, so naive automation fills nothing and moves on, leaving required answers blank.
A challenge screen is a stop sign. When a bot-check interstitial appears, the correct behaviour is to pause and tell you, not to defeat it. Anything that routes around challenges is buying short-term throughput with your account.
How HireDrop does it
HireDrop watches Indeed and ZipRecruiter plus company boards on Greenhouse, Lever and Ashby. When a posting matches, it reshapes your resume toward that posting and writes the cover letter from the posting's own text, then fills the form — including the screener questions — in the Chrome window on your computer.
Then it waits for you. Tap mode is the default: you see the finished application and approve it, from your phone if you are not at the desk. Up to 30 a day, 20 per platform, paced across the day. The ATS guide covers what happens to the resume after you hit send.
Questions people ask
Does Indeed have an auto-apply feature of its own?
No. Indeed has saved searches, alerts and a stored profile that speeds up its own apply flow, but it does not apply on your behalf. Anything described as Indeed auto-apply is third-party software driving the site — either from your browser or from someone's server.
Is automating Indeed applications against the rules?
Indeed's terms restrict automated access to the site, and we are not going to pretend the line is crisp for a browser assistant that a human supervises. What we do to stay on the defensible side: applications run in your own browser under your own login at a human pace, we never solve captchas, we don't run server-side submission bots, and every application can be reviewed by you before it sends. Tools that blast from data-centre IPs or crack challenges are a different category of risk.
Why do auto-apply tools fail on some Indeed jobs?
Three reasons, in order of frequency. The posting hands off to a company ATS with a multi-step form the tool never learned. The apply session isn't authenticated even though the search session is. Or the flow throws a challenge — a captcha or a bot-check interstitial — which an honest tool has to stop at rather than defeat.
Will auto-applying get my Indeed account banned?
Nobody can promise it won't — the decision is Indeed's. What changes the odds is behaviour: where the requests come from, how fast they arrive, and whether challenges get answered or bypassed. Applying from your own browser at a few dozen a day looks like a motivated job seeker. Hundreds a day from a server looks like what it is.
How many applications a day is reasonable?
We cap at 30, with 20 per platform, and that is a deliberate ceiling rather than a technical one. It fits inside normal human activity and leaves room for every application to be individually written, which is the part that actually converts.
Automate Indeed — first 40 applications free
Your first 40 applications are free — no card. After that, $12/week or $39/month, cancel in one click.
Start applyingKeep reading
HireDrop vs LazyApply
Volume blasting at 150 applications a day versus 30 human-paced ones you approve. What each approach actually costs you.
HireDrop vs AIApply
A toolbox of AI career tools with auto-apply sold in credit packs, versus one pipeline that applies for you. Which fits your search.
How ATS resume screening actually works
What Greenhouse, Lever and Ashby really do with your file, which myths waste your time, and the fields that quietly disqualify you.