How do you actually get banned on LinkedIn?
Almost nobody is banned for using a tool. Accounts get restricted for a pattern: volume on a young account, mechanical timing, identical copy at scale, falling acceptance that nobody slowed down for, and "I don't know this person" reports. Enforcement arrives as a ladder, and the first rung is survivable.
The tool is not the trigger
LinkedIn does not keep a list of vendor names it bans on sight. It scores how an account behaves, and automation makes it cheap to behave in ways a person never would. That is the whole mechanism. Browser extensions that inject into the page are detectable directly, which is a real difference between architectures, but it is not what ends most accounts.
The restricted accounts almost always did something a reviewer could describe in one sentence. A two week old profile sending at the ceiling. A list so loose that a third of recipients had no idea who was writing to them. The tool made it possible. The pattern did the damage.
The useful test before any campaign: could you describe this week of the account's activity to a person without it sounding strange? A seat that sends for nine hours, never reads anything, never replies to the people who accepted, and writes the same sentence four hundred times fails that test whichever software produced it.
The five patterns that actually score
Volume on a young account. A seat with no connections, no history and a half finished profile, sending at full rate, is the most reliable way to get stopped. Age and ordinary activity buy headroom, and on day one you have none to spend.
Mechanical timing and around the clock activity. Sends spaced at an identical interval, or arriving at 3am local time, separate trivially from a person working a list between meetings. Then the one most operators miss: volume that holds steady while acceptance rate falls. If fewer people accept each week and you keep sending at the same rate, you are telling the platform you are not reading the feedback.
And the two that involve other people. "I don't know this person" reports are a human complaint rather than a model inference, and they are weighted accordingly. Identical copy at scale is easy to cluster across accounts, which is how one flagged sender becomes a flagged cohort.
The ladder, and why the first rung matters
Enforcement arrives in stages. A warning first. Then an invitation restriction, where invites stop and the rest of the account works normally. Then a temporary account restriction, usually with an identity check attached. Then permanent closure.
Almost nobody jumps straight to permanent closure. The cheap rungs come first and they are survivable, which makes them the most valuable feedback you will get. What actually kills accounts is treating a warning as noise, or switching to a second tool and continuing at the same pace.
The ladder also tells you enforcement is graduated on purpose. LinkedIn would rather slow an account down than lose a user, which is why the early stages remove one capability and leave the rest working. The accounts that come back are the ones that read an invitation restriction as information about the list rather than an obstacle to route around.
The two numbers that see it coming
Restriction is rarely a surprise if you were watching acceptance rate and pending invitations. Acceptance sliding week over week means the list has drifted away from people who recognise why you wrote. A growing stack of unanswered pending invitations is that same fact seen from the platform's side.
Treat both as operational metrics rather than reporting metrics. If acceptance falls under 20%, the correct move is to stop and rebuild the list, not to send more to compensate for the ones that did not land. Sending more is the specific behaviour that turns a soft signal into a restriction.
Both numbers are cheap to watch and neither appears on a standard outbound dashboard, which tends to report sends, opens and meetings. Sends are the input. Acceptance is the only one of those that tells you what the platform makes of the input, and it says so days before anything is enforced.
What we will not tell you
We will not publish a ban rate. Ours is still inside its measuring window: restrictions per managed seat per rolling 90 days, and the denominator is not yet large enough for the number to mean anything. A percentage quoted with no methodology, denominator or date is marketing, and it is easy to produce by choosing a window.
What we will state is the order we believe the levers sit in. Targeting first, because acceptance rate is both the outcome you want and the signal that protects the seat. Then caps you cannot type over. Then a warm up ramp. Then working hour pacing with real jitter. A dedicated IP sits well below all of those.
That ordering has a practical use when you compare vendors. If a product's entire safety story is infrastructure, proxies, addresses and device fingerprints, it is answering the 2019 version of the question. Ask instead what the tool does when acceptance falls: whether anything slows down on its own, or whether the ramp is purely a calendar.
What actually protects a seat
Caps enforced server side rather than typed into a settings field, so no instruction can overshoot them, including an impatient one of yours. New seats here run at 20 invitations a day and 80 a week, multiplied by 0.5x in week 0 and 0.75x in week 1 before full rate. Suppression memory, so nobody receives a duplicate first touch. An approval gate before every send, which reads as friction until you see what an unreviewed queue produces.
And the one almost nobody sells: a list where every person has a nameable reason to be on it. Two of our own audiences accepted at 32% and 2.6% with comparable copy. The account risk was not distributed evenly between those two campaigns, and no pacing setting would have evened it out.
None of this makes a restriction impossible. It makes the common causes structurally harder to hit, which is a narrower and more honest claim. The residual risk sits in judgment calls about who belongs on a list, and those stay yours.
The restriction ladder, and what each rung stops
| Stage | What stops | What it usually takes to clear |
|---|---|---|
| Warning | Nothing yet | Cut volume and fix the list |
| Invitation restriction | New invitations only | Days to a few weeks of quiet |
| Temporary account restriction | The whole account | Identity verification plus a waiting period |
| Permanent closure | Everything, for good | An appeal with a narrow success path |
Questions people ask next
Can LinkedIn tell which automation tool I am using?
Sometimes directly, especially browser extensions that modify the page. More often it does not need to. The behavioural pattern is what gets scored, and that looks the same whichever tool produced it.
How many 'I don't know this person' reports does it take?
LinkedIn publishes no threshold, and any specific number you read is a guess. Treat it as the most expensive negative signal available, and target so that recipients can see why you wrote.
Is a second account a workaround?
No, and it usually escalates things. A fresh seat run at the pace that stopped the first one reproduces the pattern faster, because the new account has no history to spend.
Does uninstalling the tool help after a restriction?
Not by itself. Enforcement responds to the account's recent behaviour, so stopping sends and letting pending invitations resolve does more than removing any software.
Why this page exists: r/LinkedInTips: "After years of building LinkedIn tools, here is how you actually get banned"
LinkedBoost is the LinkedIn MCP server: your agent sources, drafts, sends and works the inbox, inside caps the server enforces rather than suggests.
Related answers
No. LinkedIn restricts accounts for behaving like automation, not for using it. The tool is invisible to the platform; the pattern is not. Mechanical timing, around-the-clock activity, and volume that ignores falling acceptance are what get scored.
Spend the first week looking like a person: profile finished, a handful of real comments, invitations only to people who will obviously accept. Then ramp. Our new seats run at 20 invitations a day and 80 a week, multiplied by 0.5x in week 0, 0.75x in week 1, and full rate from week 2.