Half the LinkedIn account restrictions we read about began with automation or speed

Why is my LinkedIn account restricted? LinkedIn's own help page on account restrictions answers in one line: "Access to your account may be restricted if you violate our Professional Community Policies." In practice you're locked out. You can't use the account or any feature tied to it, and other people can no longer find your profile or message you.

The same page sorts restrictions under four headings. Each has its own trigger and its own way back.

Some accounts are temporarily restricted and come back. Others are gone for good, and LinkedIn says one violation can be enough: "Some violations of our Professional Community Policies may result in permanent account restriction after a single violation."

We wanted to see which of those headings real people hit. So we read fourteen first-hand stories of a LinkedIn restriction, each told by the person it happened to. Seven began with automation or speed. That meant a tool, a script, a bot sending job applications, a burst of invites from a brand-new account, a login to a third-party service, or reviewing requests faster than LinkedIn expected. The next section lays out those seven.

Here are the seven. We describe each person by role only, and the last column stays as close to their own words as a table allows.

The freelancer's story stings. Their AI tool found people in their niche, sent the invites, messaged them and followed up, and by their account "IT ACTUALLY WORKED pretty well." They added, "I started getting some pretty good clients from it as well." Then LinkedIn banned them for a year. The founder was back after a single day and stopped using the tool.

LinkedIn's help page is plain on this point: "we don't allow the use of third-party software or browser extensions that scrape, modify the appearance of, or automate activity on LinkedIn's website."

The seventh case is the odd one. Their story names no tool and no script. They were going through connection requests and moved fast, and that was the whole of it: "LinkedIn AI just restricted my account for reviewing connection requests too quickly and flagging me as a bot." In their telling, pace alone was enough for LinkedIn to read a person as automation.

To send an invite or a message for someone, a tool has to act as the person behind the account. Tools of this kind generally take one of two things: the member's password, or their session cookie.

A session cookie is the small token your browser keeps after you sign in. It tells LinkedIn it's still you on the next page, and the one after. LinkedIn's is called li_at. Whoever holds a copy can show up as you without typing a password. That's the appeal for a tool. It's also where things get shaky.

One operator wrote up a month of automation failures, and the copy kept dying on them: "LinkedIn cookies rotate aggressively. The li_at cookie expired at least 3 times in the first week." Each time, their LinkedIn automation stopped until someone refreshed the browser by hand. Another developer, asking for help, had watched the same thing get worse. "It used to be good for a couple of weeks but now it logs me out right away," they wrote. They'd tried several workarounds. None of them kept the session alive.

Then there's the account owner in the table above who signed in to a third-party API service. They blamed that login: "I believe LinkedIn detected this as suspicious activity." They said it was their own account activity. LinkedIn still asked them for a government-issued ID.

What follows is our reading, and only ours. LinkedIn doesn't publish how it spots automation, so we can't say what it checks. The reports do share a shape, though. Once a tool takes a copy, one login lives in two places: the browser where you signed in, and a server somewhere else acting on your account. Seen from outside, that second place can resemble the case LinkedIn's help page describes as an account "compromised or taken over by another person or entity." And in the reports we read, it was the tool's access that kept expiring, or that the owner blamed for an ID request.

For two of LinkedIn's four headings, profile and identity, the way back is the same. Log in and prove who you are. For a compromised account the help page reads: "To regain access to your account, please login and follow the steps on screen to verify your identity." On paper that's a short trip. Four people in our set were sent there. None of them, as they told it, had their account back.

The account owner from the third-party login was asked for a government ID, as covered above. Another person forgot their password, found the account restricted, and was asked for details from their ID or passport. They objected: "I should have the right to be able to refuse to share such an information." A paying Premium user was willing to verify. The automated check fails on IDs from their country, they said, so they asked for a human. Someone else, who named no cause, had already tried the recovery and appeal process. "I'm still unable to regain access to my account," they wrote.

Passing the check doesn't settle it either. A computer science student whose account dated to 2019 was permanently restricted. They suspect a job opening they'd shared, which listed an email address for applications. Their legal name also carries a prefix that their profile leaves out. They completed the identity verification LinkedIn asked for, appealed, and still saw the restriction upheld over the "number and/or severity" of violations nobody spelled out. They wrote that "losing years of connections, recommendations, and professional history has a real impact."

A breached account fared worse. Someone else got in and changed the login details. The owner appealed. "I was told that my account would be permanently closed, even after explaining that it had been breached," they wrote. Fresh accounts didn't hold: "About three other accounts were also suspended." Only "One year plus later" could they start over.

LinkedIn's page on permanent account restrictions says what the last two rows mean: "Other people will no longer be able to find your LinkedIn profile or message you."

Speed and tools cover half the stories we read. People who automate put numbers on how fast is too fast, and two people with no automation in their stories got restricted anyway.

• The operators' numbers. An agency owner calls 100 connection requests a day from a new account "a red flag" and puts an older account with a filled-in profile at 40 invites. Another person says "for normal accounts you can barely send 100 connection requests per week." Someone else doing outreach wrote, "This week I hit the 100 connection request limit, so sending isn't the problem." Those are their claims, counted per day by one and per week by others. We don't offer any of them as a safe limit, and none appears on the LinkedIn help pages we read.
• A third restriction with no automation. One person was restricted for the third time and wrote, "I don't have any automation or high volume activity." It keeps coming back every few weeks. To them it's a restriction that arrives for no reason they can see.
• Two requests. Another wrote, "I honestly don't know what went wrong. I only sent 2 connection requests before it was restricted." Two sits far below every number above.
• Pushback from inside that half: a real ID behind an automated decision. The member flagged as a bot for reviewing requests too quickly sees the bigger risk in ID checks. "Imagine an AI banning you for life. If your real ID is tied to that profile, you're locked out forever."
• Also from inside that half: applicants and companies. The job seeker whose bot sent applications asked, "Why is automation celebrated when it saves companies time, but penalized when it saves applicants time?"

Whatever the cause, a restriction takes the network with it. The student in the previous section lost years of connections, recommendations and history. The people you know, and what you've said to them, sit inside an account LinkedIn controls. So the contacts and notes a business depends on are worth keeping somewhere it controls too.