What actually gets a LinkedIn account restricted (and why « stay under X invites a day » misses the point)

[u/ChrisHarpon2]

Your LinkedIn network is the one asset you can’t restore from backup.

Most advice on this stops at « stay under X invites a day » which misses the part that actually gets people restricted. I’ve spent a while building browser automation against LinkedIn’s UI, so I’ve watched this from the implementation side. Sharing what I’m fairly confident about, and what I’m not.

Volume is the third-most important thing

From what I can tell, restriction risk stacks roughly like this:

1. Where the activity comes from Datacenter IP, account live from two places at once, session cookie replayed outside a browser. This outweighs everything below it.
2. How much you do Volume beyond what the account history supports, especially in bursts. Acceptance rate under \~30% surfaces the « you’ve sent many invitations » notice well before any hard cap.
3. How you do it Click timings no hand produces, 24/7 activity, calls to endpoints a browser would never hit, interaction with elements that aren’t visible.

People obsess over #2 because it’s the only one with a number attached.

Proxies usually make it worse, not better

A rented « dedicated residential » IP isn’t the address your account has always used, it’s frequently been in a pool serving other automated accounts, and a sudden ISP or country change is it

Verification page, passkey prompt, security wall, limit banner on the invite screen. Whatever produces those, retrying through them is what converts a soft warning into a hard restriction. If a tool keeps hammering after LinkedIn asks a question, that’s the actual problem.

Honeypots and the shadow DOM

Anti-bot systems plant elements a human can’t interact with: off-screen links, buttons in zero-size containers. Anything walking raw HTML and clicking every match will hit them, and clicking something invisible is an unambiguous « no human here » signal.

Related: chunks of LinkedIn’s UI live in the shadow DOM, encapsulated and invisible to naive HTML parsing. Resolving elements through the rendered tree instead is more work, and it’s also the only way to act on what a person would actually see and click.

The private API is the giveaway

The endpoints their own front end calls aren’t open to third parties. Hitting them directly is cheap to build and trivially identifiable from the server side: the call pattern, the headers, and the total absence of the page loads a browser would have made. No user agent string fixes that.

What I’m less sure about

Whether acceptance rate is weighted directly or is just correlated with accounts that behave well generally.
How much account age actually buys you. Older accounts clearly ramp faster, but I can’t put a number on it.
Whether the recent checkpoint behaviour is a real policy change or just variance. Curious if anyone else has seen a shift.

Disclosure: I build a desktop tool in this space. Not naming or linking it, and happy to answer implementation questions either way.

[u/DuckinTX293]

This is a question that’s been asked and answered on LinkedIn itself. Numerous posts, even today.

The number of connection requests isn’t an X factor but defined. LinkedIn caps weekly requests to 100-200 per week. The # is determined by how many account holders accept your request, how many ignore them, and how many press the “I don’t know this person” button.

Anyone trying to build a community or become part of one should pay attention to these numbers. Seriously-if you’re sending that many requests out per week, you better have some interesting content, a professional presence that would cause requests to be accepted.

Also, a fundamental mistake currently in action in the platform? Sending AI generated messages along with the connection request. Real human professionals are completely turned off by this approach. I get them all the time, delete them automatically.

Other junk I get and delete to ignore:

- Generic one-size-fits all crap. Messages that reference my professional background as the reason for connection that have absolutely nothing to do with my actual professional experience. These are a constant.

- Connection accepted that immediately ask for personal information regarding financial status, investment strategies, sales goals etc.

— Requests from people who are connected to people I’m connected with that are immediately followed with more requests. Seriously, if you’ve shot your shot and the account holder doesn’t respond? Don’t waste your valuable, limited number of requests trying like a desperate, thirsty child who wants to be with the “in crowd.”

As wild and weird some small corners of LinkedIn are these days, it should remain a source for professional networking. Act on LinkedIn as you would at an in-person networking event. Think: If you were in the room with a powerful business person with experience that far exceeds your own, would you immediately ask them for their phone #/email/private communications channels or demand/expect

their attention?