LinkedIn Daily Limits in 2026: What Actually Gets an Account Restricted

What people mean by "the LinkedIn limit"

I'm Hlib Storchak. I build outbound systems for B2B founders and sales teams, and I've booked 2000+ meetings for B2B clients running cold email and LinkedIn side by side. Every few months a client asks me the same question in a different wrapper: "what's the actual LinkedIn limit?" They usually mean one specific thing, how many connection requests they can send before the invite button disappears, but "the limit" on LinkedIn is really at least three separate ceilings stacked on top of each other: a connection request cap, a search and profile-view cap called the Commercial Use Limit, and an informal trust score baked into the algorithm that moves all of the above around depending on your behavior.

This article is about the one people actually get burned by, connection requests, with the Commercial Use Limit covered separately since it's the one LinkedIn will actually confirm exists.

Why LinkedIn has never published a number

LinkedIn's own help center is direct about this for the Commercial Use Limit: "we are not able to display the exact number of searches or views you have left." Source: LinkedIn Help, Commercial Use Limit. There is no equivalent official page for connection requests at all, no confirmed daily or weekly cap, no published threshold for what counts as spam-like behavior. Every number you see quoted, including every number in this article, is reverse-engineered from what automation vendors and outreach practitioners have observed happening to real accounts.

That is a deliberate design choice, not an oversight. A published number becomes a target the moment it's published, and a platform trying to stop bot behavior does not want to hand bots (or automation vendors) the exact ceiling to max out against. The tradeoff is that everyone doing LinkedIn outreach, agencies, in-house teams, and vendors selling automation tools, is working from estimates, and the estimates do not agree with each other.

The numbers actually being quoted in 2026

I pulled the most-cited figures currently circulating and laid them out side by side, because the disagreement between them is itself the useful data point.

Source for the practitioner range and the "soft-lock" mechanics: Taplio's 2026 connection request limit guide. Source for the automation-platform figure: Expandi's 2026 outreach benchmarks, built from 13,218,869 connection requests across 13,302 accounts between May 2025 and April 2026.

The Commercial Use Limit: a separate cap people confuse with it

This one is real and LinkedIn confirms it directly, which makes it worth understanding on its own terms rather than lumping it in with connection requests. The Commercial Use Limit restricts search and profile-browsing activity, not who you can send invites to. It covers things like searching for profiles on LinkedIn.com or mobile, browsing the "People Also Viewed" section, and viewing member profiles from a Page's People tab. It resets monthly, at midnight PST on the first of each calendar month, per LinkedIn's own help page.

The practical effect for outbound teams is that heavy list-building through manual search, not through Sales Navigator, can quietly throttle you mid-month on a free or Premium account, restricting you to a handful of results per search until the reset. Sales Navigator carries a much higher effective ceiling for this specific limit, which is one of the more underrated reasons teams running real prospecting volume upgrade to it, separate from any connection request math.

What actually gets an account restricted

Here is the part that matters more than any number in the table above: LinkedIn's own guidance and every automation vendor's postmortems point the same direction, restrictions are triggered by behavior signals, not by crossing a fixed count. The three signals that consistently show up:

Acceptance rate. Expandi's 2026 benchmark puts the platform-wide average connection acceptance rate at 28.5% across its 13.2-million-request dataset, with individual industries ranging from 17.5% up to 40.1%, and Staffing & Recruiting among the best-performing industries at 36.5%. A rate that falls meaningfully under 30% signals to LinkedIn's systems that your targeting or approach doesn't match who you're contacting, and that's when your effective sending ceiling starts getting quietly tightened, well before you hit any published number.

Report and "I don't know this person" clicks. Every invite sent to someone who doesn't recognize you and clicks that button is a stronger negative signal than a simple ignore. A handful of these on a small, well-targeted campaign is normal. A pattern of them on broad, cold, unqualified lists reads as spam regardless of your raw volume.

Sending velocity and pattern. Sending 20 requests in three minutes, at exactly the same interval, every single day, looks like automation because it is. LinkedIn's detection cares less about the daily total and more about whether the pattern of activity looks human. This is the actual case for pacing sends, not superstition.

Step 1: audit your current account health

Before setting any target, check where you actually stand. Look at your acceptance rate over your last 100 or so sent requests, look at how many pending requests are currently sitting unanswered, and check your account age and whether you've had any prior warnings or temporary restrictions. An account under six months old, or one with more than a few hundred requests sitting pending, should assume it's in the lower end of any range in the table above, not the higher end.

Step 2: set your own weekly ceiling

Given the spread in the data, I tell clients to set an operating ceiling well under the top of any figure they've read, not at it. For a newer or unproven account, that means starting around 40 to 60 requests a week and watching acceptance rate closely for two to three weeks before nudging up. For an established account with a healthy history, 100 to 120 a week is a reasonable steady state that stays comfortably inside every source's range in the table above, including the most conservative one. Treat 200-plus as a ceiling you approach only if your acceptance rate and account age both support it, never as a starting point.

Step 3: protect your acceptance rate

This is the single highest-leverage lever, more than any volume decision. Narrow the list to a real ICP match before you send a single request, not after. A tightly scoped list of the right seniority and industry will consistently clear 30%-plus acceptance where a broad, loosely targeted list won't, independent of how good your note is. If your acceptance rate is currently under 25%, pause volume and fix targeting before you touch anything else, including your daily send count.

Step 4: pace sends like a person, not a script

Spread requests across the day instead of firing them in a burst, and vary the interval and the time of day rather than running on a fixed schedule. If you're using an automation tool, use its built-in randomization and pacing settings rather than maxing out its send speed, since the speed a tool is capable of and the speed that reads as human are two different numbers. This is the setup I run for clients: modest daily volume, randomized timing, and acceptance rate as the metric that decides whether to scale up, not a fixed weekly quota.

Step 5: watch for the early warning signs

LinkedIn typically signals trouble before a full restriction lands. Watch for a "you've reached the weekly invitation limit" message appearing earlier in the week than it used to, a noticeable drop in your acceptance rate over a rolling window, search results capping out faster than normal (a Commercial Use Limit signal, separate from connections but often correlated with the same aggressive-activity pattern), and any in-app warning about automation or unusual activity. Any one of these is a signal to pull volume back immediately, not to push through and see what happens.

Step 6: what to do if you're already restricted

If the invite button has disappeared or you're seeing a weekly limit message, stop sending entirely rather than trying to work around it, and let the rolling window reset. Community-reported recovery timelines suggest a first soft-lock typically clears in three to seven days once the triggering behavior stops, per Taplio's 2026 guide cited above, though LinkedIn doesn't publish an official timeline and I'd treat any specific number here as a rough guide rather than a promise. Repeated restrictions tend to take longer to clear and can come with reduced search visibility for a stretch afterward. While you wait, this is a reasonable window to work other channels, cold email, warm intros, content, rather than trying to force LinkedIn volume back up early.

Multi-seat teams: the limit is per seat, not per company

Every one of these limits, connection requests and the Commercial Use Limit alike, applies per individual LinkedIn account, not per company or per Sales Navigator seat pool. Running outbound across a team means each rep's account has its own independent ceiling and its own independent acceptance rate to protect. The mistake I see most often when I take over a team's LinkedIn motion from a client is one or two accounts running double or triple the volume of the rest of the team because they were the first ones set up, which quietly puts those specific accounts at the most risk while the rest of the team's headroom sits unused. Spreading volume evenly across seats, rather than concentrating it on whoever's account is easiest to automate, protects the whole team's capacity.

Mistakes that quietly trigger restrictions

The most common one is treating a number read in a blog post, including the ones in the table above, as a safe target to hit every single week regardless of acceptance rate. Close behind: running a brand-new account at established-account volume because "the tool allows it." Third: ignoring a dropping acceptance rate for weeks because total sends still look fine on a dashboard. Fourth: bursting all of a week's volume into one or two days instead of spreading it out, which reads as automated even when a human is technically clicking send. Fifth: not distinguishing between the Commercial Use Limit and the connection request limit, and mis-diagnosing which one actually tripped when something breaks.

FAQ