LinkedIn’s safe scraping limit in 2026 is roughly 150 actions per account per 24 hours – counting profile visits, detailed extraction, messaging, follows, and connection actions combined. The safe volume depends heavily on method: up to 50 profiles per day via direct profile URLs, but up to 2,000 per day on standard search and 5,000 on Sales Navigator when collecting from search-result pages. Search-based collection is safer because it mimics normal browsing; direct URL-to-URL navigation is flagged faster.
The absolute daily limit: 150 actions per account
Regardless of the tool you use, the single most important number for LinkedIn scraping in 2026 is 150 actions per account per 24-hour period. We treat this as the absolute maximum – the ceiling above which account restrictions become likely no matter how careful the rest of your setup is.
An "action" is any meaningful interaction the account performs with LinkedIn. The 150 cap is a shared budget across all of these:
| Action type | Counts toward the 150/day cap |
|---|---|
| Profile visits | Yes |
| Detailed profile extraction (opening + parsing a full profile) | Yes |
| Messaging (connections or InMail) | Yes |
| Auto-following | Yes |
| Connection requests & withdrawals | Yes |
| Other account activity (endorsements, likes, follows) | Yes |
The key insight most scraping guides miss: these actions share one budget. If your account sends 80 connection requests and visits 70 profiles in the same day, you have already hit the 150-action ceiling – there is no separate allowance for "scraping" versus "outreach." LinkedIn’s anti-automation systems look at total account activity, not the category of each action.
This is why teams that run both outreach campaigns and data collection on the same account hit limits faster than they expect. The two activities compete for the same daily budget.
Why the collection method changes everything
The 150-action cap is the hard ceiling, but the safe volume below that ceiling varies enormously depending on how you collect data. There are three distinct methods, each with a different risk profile:
- Direct profile URL loading – jumping straight from one profile URL to another. Highest detection risk.
- Search result collection – paginating through LinkedIn search or Sales Navigator results. Lowest detection risk.
- Detailed extraction – opening each profile fully to parse all fields. Risk depends on which of the above two methods feeds it.
Understanding the difference between these three is the single biggest factor in whether your account survives sustained scraping or gets restricted within a week.
Direct profile URL extraction: the 50/day cap
When profiles are loaded directly by URL – your tool feeds a list of profile URLs and navigates to each one in turn – the safe limit drops to around 50 profiles per day per account.
The reason is behavioral. Direct URL-to-URL navigation is far more sensitive and easier to flag than normal browsing. Real users almost never jump from one profile URL straight to another, dozens of times in a row, with no search, feed scrolling, or notification checks in between. That pattern is a textbook automation signature, and LinkedIn’s detection systems weight it heavily.
Our recommendation for URL-based detailed profile extraction:
- Up to 50 profiles per day per account via direct profile URLs.
- Higher volumes should only be attempted with fully warmed-up accounts and with the elevated ban risk explicitly accepted.
If you have a list of profile URLs to extract – say, exported from a CRM or a previous campaign – this 50/day cap is the figure that applies. Pushing to 100+ URL-based extractions per day on a single account is possible, but the restriction rate climbs sharply and is only justified when the account is disposable or the data is worth the risk.
Search result collection: the higher ceiling
Collecting profiles from search results is a different workflow with a much higher safe ceiling. Because the account moves through normal search pagination – exactly what a human researcher does – the activity looks natural and LinkedIn tolerates far more of it.
| Search type | Per single query | Approx. per day |
|---|---|---|
| Standard LinkedIn search | Up to 1,000 profiles | ~2,000 profiles |
| Sales Navigator search | Up to 2,500 profiles | ~5,000 profiles |
The per-query caps (1,000 on standard search, 2,500 on Sales Navigator) are partly LinkedIn’s own result-pagination limits – the platform simply won’t show you more than that for a single search. The daily figures (~2,000 and ~5,000) assume you run several different queries across the day and collect from each.
Search-based collection looks more natural because the account navigates through normal LinkedIn search pages instead of jumping directly from profile URL to profile URL. You are reading a list, not teleporting between individual profiles. That single behavioral difference is why the safe ceiling is 40-100x higher than direct URL loading.
The critical distinction: collection vs detailed extraction
This is the nuance that trips up the most experienced teams, so it is worth stating plainly: the high search-collection numbers (1,000-5,000) are collection limits, not detailed extraction limits.
"Collection" means pulling the data that already appears on the search-results page – name, headline, location, current company, profile URL. The account never leaves the search pages, so even thousands of these stay relatively safe.
"Detailed extraction" means opening each profile individually to capture the full record – complete work history, education, skills, contact info, about section. The moment you open a profile, that is a profile visit, and it counts against the 150 actions/day cap (and, if you reach those profiles by URL, against the 50/day URL ceiling).
So the practical reality is layered:
- Need only the search-page surface data? You can collect up to ~2,000/day (standard) or ~5,000/day (Sales Navigator).
- Need to open and fully extract each profile? The lower limits bind – roughly 150 detailed extractions per day at the absolute ceiling, and only ~50/day if you reach them by direct URL.
A workflow that collects 5,000 profiles from Sales Navigator search and then tries to deep-extract all 5,000 on the same account in one day will be restricted almost immediately. The collection step is fine; the 5,000 profile opens are 33x over the action ceiling.
What happens when you exceed LinkedIn scraping limits
LinkedIn enforces scraping limits through the same escalating system it uses for outreach:
Soft throttling. The first sign is silent – profiles load slower, search returns fewer results, and pages occasionally show "We couldn’t load this content." The account isn’t restricted yet, but it has been flagged for elevated review.
Feature restriction. Sustained over-limit activity triggers a temporary restriction: search is capped, profile viewing is throttled to a fraction of normal, and automation tools lose access. This typically lasts 1-3 weeks.
Account restriction. Aggressive scraping – especially high-volume direct URL extraction, or detected automation tooling – leads to a full account lock requiring identity verification to recover. Scraping-triggered restrictions have a lower recovery rate than outreach restrictions because LinkedIn treats bulk data extraction as a more serious ToS violation.
If you see soft throttling, stop scraping on that account for 48-72 hours and resume at half volume. Pushing through the early warning signs is what turns a recoverable throttle into a permanent ban.
How to scale scraping safely beyond one account
The math is unavoidable: a single account is capped at ~150 actions per day, or ~50 detailed extractions if you work from URLs. If your project needs 1,000 fully-extracted profiles per day, no amount of careful pacing makes that possible on one account.
The standard solution is horizontal: spread the workload across multiple accounts, each staying comfortably under its own daily ceiling. Five accounts at 30 extractions/day each is far safer than one account at 150, because every individual account looks like light, human-scale activity.
Three rules make multi-account scraping sustainable:
- Dedicated proxy per account. Each account needs its own consistent IP. Sharing IPs across accounts is one of the fastest ways to get a whole cluster restricted at once.
- Warm up before scraping. New accounts have far lower tolerance. A freshly created account scraping 50 profiles on day one will be flagged immediately; see our LinkedIn account warm-up guide for the ramp schedule.
- Stay under, not at, the limit. The 150/50 figures are ceilings, not targets. Sustainable operations run at 50-70% of the ceiling to leave headroom for the account’s other activity.
Teams running data collection at scale typically operate a pool of warmed-up accounts with matched proxies rather than pushing a single profile to its limit. Renting aged LinkedIn accounts with dedicated proxies is one way to build that pool without the months of warm-up each account otherwise requires; our guide on running multiple LinkedIn accounts covers the rotation mechanics. If you are building a SaaS or data product on top of this, see our pillar on sourcing LinkedIn data at scale.
Do these limits depend on the scraping tool?
No. The limits above are account-level limits enforced by LinkedIn, not tool-level limits. They apply identically whether you use a cloud automation platform, a browser extension, a residential-proxy scraping service, or a custom script.
A common misconception is that a more sophisticated tool "unlocks" higher volumes. It doesn’t – LinkedIn counts actions per account, and the account hits the same 150/day ceiling regardless of what software performs those actions. What a good tool can do is make each action look more human (randomized timing, natural navigation paths, realistic delays), which improves your survival rate within the limits. It cannot raise the ceiling itself.
This is also why the only real lever for higher total volume is more accounts, not better software. The per-account ceiling is fixed; the number of accounts is not.
FAQ
How many LinkedIn profiles can you scrape per day?
It depends on the method. Via direct profile URLs, the safe limit is about 50 profiles per day per account. Via search-result collection, you can collect surface data from up to ~2,000 profiles/day on standard LinkedIn search and ~5,000/day on Sales Navigator. But detailed extraction (opening each profile fully) is always bound by the 150-actions-per-day account ceiling.
What is the LinkedIn scraping limit per account in 2026?
The absolute maximum is 150 actions per account per 24 hours, counting profile visits, detailed extraction, messaging, follows, and connection actions combined. This is a shared budget – scraping and outreach activity draw from the same 150-action pool.
Why is direct URL scraping more risky than search scraping?
Direct URL-to-URL navigation is a strong automation signal because real users almost never jump between dozens of profile URLs with no search or browsing in between. Search-result collection mimics normal human research behavior – paginating through a results list – so LinkedIn tolerates 40-100x higher volumes from it.
Does Sales Navigator allow more scraping than standard LinkedIn?
For search-result collection, yes: Sales Navigator allows up to 2,500 profiles per query and roughly 5,000 per day, versus 1,000 per query and ~2,000 per day on standard search. But the 150-action-per-day ceiling for detailed profile extraction is the same on both – Sales Navigator does not raise the account-level action limit.
Will a better scraping tool let me extract more profiles?
No. The limits are account-level and enforced by LinkedIn, not by the tool. A better tool can make each action look more human and improve your survival rate within the limits, but it cannot raise the 150-action ceiling. The only way to increase total volume is to use more accounts.
What happens if I exceed LinkedIn’s scraping limits?
You’ll first see soft throttling (slow loads, fewer search results), then a temporary feature restriction lasting 1-3 weeks, and in severe cases a full account lock requiring ID verification. Scraping-triggered restrictions have a lower recovery rate than outreach restrictions because LinkedIn treats bulk extraction as a more serious violation.
