Safety and compliance
What do LinkedIn's terms say about automation and scraping?
By Viktorio Shopov, co-founder of Sellinger. Reviewed by Asen Levov. Published . Last updated . 8 minute read.
LinkedIn's User Agreement bars bots and other unauthorized automated methods, and software, scripts or browser add-ons that scrape or copy the site. Its Help pages add that members who use such tools violate the agreement and risk restriction. We found no rule that treats cloud tools and browser extensions differently. This is not legal advice.
This is not legal advice. It summarises LinkedIn's public pages as we read them on 19 October 2026. Pages change, so read the originals before you rely on a detail. Evidence levels used below: documented* (LinkedIn says it, and we quote a short phrase), our setting (how Sellinger is configured), our view (our opinion, not a LinkedIn statement).*
What does the User Agreement say?
Evidence level: documented. Section 8.2 of the LinkedIn User Agreement lists things members must not do. Four of them matter here.
| Clause in the version we read | Short phrase from the page | What it covers |
|---|---|---|
| 8.2, item 2 | "Develop, support or use software, devices, scripts, robots" | Software that scrapes or copies the services or profile data. The item names "crawlers, browser plugins and add-ons" |
| 8.2, item 13 | "Use bots or other unauthorized automated methods to access the Services" | Bots. The clause goes on to name adding or downloading contacts and sending or redirecting messages |
| 8.2, item 3 | "bypass or circumvent any access controls" | Getting around limits or blocks |
| 8.2, item 16 | "place an unreasonable load on, the Services" | Traffic that strains the site |
Two things are worth noticing. First, the word "unauthorized" in the bots clause is doing work. The clause bans automated methods that LinkedIn has not authorized, which is narrower than a ban on every kind of automation, though the Help page below reads more broadly. Second, the text we read does not use the word "extension". Browser plugins and add-ons are the closest match, and LinkedIn's Help page, below, does use "extensions".
On consequences, section 3.4 says "LinkedIn reserves the right to restrict, suspend, or terminate your account", and also reserves the right to limit your use of the services. Section 5 says both you and LinkedIn may terminate the contract at any time with notice to the other. So the contract gives LinkedIn the right to act. It does not publish a schedule of when it will.
What do the Help pages add?
Evidence level: documented. The Help Center spells out what the agreement implies.
- Prohibited software and extensions. LinkedIn says "we don't permit the use of any third party software", including "browser extensions that scrape, modify the appearance of, or automate activity on LinkedIn's website". It lists fake accounts and fake engagement as prohibited. Members who use such tools risk "having their accounts restricted or shut down", and the page says any member who uses tools for such purposes is in violation of the User Agreement. It also says that such tools "may become non-operational without notice", which is a warning about reliability and not only about your account.
- Account restrictions. The page names four kinds of restriction: content, profile, identity and automated tools. For automated activity the page says the result may be a "temporary or permanent restriction of your account".
- Automated activity on LinkedIn. If an account is restricted for automated activity, LinkedIn asks you to review and disable any software or extension that automates activity. The account is re enabled at the time stated in the suspension notice. The page also invites you to contact LinkedIn if you want a second look.
- Types of restrictions for sending invitations. LinkedIn says that when it suspects the use of an automation tool it "may suspend or restrict" the account. We cover the numbers in the invitation limits post, so we do not repeat them here.
What do the Professional Community Policies say?
Evidence level: documented. The Professional Community Policies are about conduct more than tools. We found no sentence in them that addresses bots or automation tools directly. They do matter for outreach, because they apply to the messages you send, whoever or whatever sends them.
| Policy line we read | Why it matters for outreach |
|---|---|
| "We don't allow fake profiles or entities." | The profile you automate has to be a real person's |
| "Do not use or attempt to use another person's LinkedIn account" | The clause is about using someone else's account, so no shared or rented logins |
| "Do not use our invitation feature to send promotional messages to people you don't know or to otherwise spam people." | An invitation is not an advertisement |
| "Do not spam members or the platform." | Relevance and volume both count |
| "Don't do things to artificially increase engagement with your content." | Applies to engagement pods and fake reactions |
Our view: the policy on invitations is where a well run sales process and a bad one separate most clearly. A relevant, low volume campaign to a defined audience is a different thing from a promotion sent to everyone.
What about scraping?
Evidence level: documented for LinkedIn's position, and outside the scope of this post for the law. LinkedIn's agreement prohibits scraping with software, scripts, robots, crawlers and browser add-ons, and the Help page prohibits extensions that scrape. Separate from LinkedIn's contract, the law on scraping publicly visible pages has been argued in courts, with outcomes that depend on jurisdiction and facts. We are not lawyers and do not summarise it. If your plan involves collecting data from LinkedIn at scale, ask a lawyer in your country before you start.
How do cloud and browser tools differ?
Evidence level: our view, with the rules above as the baseline. A browser extension runs inside your own browser, on your own computer, and acts through the page you have open. A cloud tool runs on a server and acts through a connection you authorise, so it can work while your computer is off. Our cloud versus browser comparison sets out the trade offs.
| Question | Browser extension | Cloud tool |
|---|---|---|
| Where it runs | In your browser | On the vendor's servers |
| Works with your laptop closed | No | Yes |
| What LinkedIn's rules say | Prohibited as a browser extension that automates activity | We found no rule that treats it differently from other third party software |
| Who sees the credentials | The browser session stays on your machine | Depends on the vendor. Ask whether it stores your password |
| Main practical risk | Page changes can break it, and it may stop without notice | Pacing is set centrally, so the vendor's defaults matter |
The key row is the third. LinkedIn's rules speak of "third party software" and "extensions" together. A cloud tool is not exempt, and we do not claim it is safer in the eyes of LinkedIn. The same goes for us: Sellinger is a third party tool and falls under the same rules as we read them. The decision to use it is the account holder's, and so is the risk.
What does Sellinger do about it?
Evidence level: our setting. You connect your own LinkedIn account through a hosted login, and Sellinger does not store your LinkedIn password. Each account has a daily invitation limit (20 by default, varied by a few each day), a weekly cap (150 by default) and a quiet window with no sending (01:00 to 08:00 account time by default). A person can approve each message before it goes. These are our defaults. They are not LinkedIn's rules, and they are not a promise. When LinkedIn returns a rate limit, Sellinger sets a cooldown on that account before it tries again. See our outreach rules for the content side.
What should you decide before you automate?
- [ ] Have I read section 8.2 of the User Agreement and the prohibited software page myself?
- [ ] Do I accept that the rules prohibit this class of tool, and that the account holder carries the risk?
- [ ] Is the profile one I can afford to have restricted for a week, or longer?
- [ ] Is it my real profile, with no shared or rented logins?
- [ ] Is my audience relevant enough that the policy line on spam does not describe me?
- [ ] Have I told an employer, client or adviser who needs to know?
- [ ] Do I have a second channel, such as email, if the profile is restricted?
If you cannot tick most of these, do not start. If a restriction does happen, our next post covers the steps. For the wider question of risk, read is LinkedIn automation safe.
What can't we promise?
- That LinkedIn will not restrict an account. It decides, and it does not publish how.
- That the pages will say the same next month. We read them on 19 October 2026.
- That this covers your situation. It is a reading of public pages, not advice.
Common questions
Does LinkedIn allow automation tools?
Is scraping LinkedIn against the rules?
Does it matter if the tool runs in the cloud or in my browser?
Can LinkedIn close my account for using a tool?
Is this legal advice?
How Sellinger helps
Read how it works on See how the LinkedIn agent works, or see a real campaign in Read the Sellinger case study.
