LinkedIn Pulled Pin and Gem's Pages. The Ban Clause Targets Your Seat

If your team sources with Pin, Gem or Neuroscale, the useful question isn't whether those vendors survive losing their LinkedIn pages. It's whether your own Recruiter seat is the next thing LinkedIn switches off.

On Oct. 13, ERE reported that the LinkedIn company pages for all three now show "Page not found," and that Pin CEO Steve Lu's personal profile has been gone for more than a month. The vendors will probably be fine. The contract risk sits with you, and it depends on how your tools behave, not whose logo is on them.

What happened to Pin, Gem and Neuroscale on LinkedIn?

Between mid-September and early October, LinkedIn removed the company pages of three AI recruiting vendors, saying only that it "takes action when necessary to prevent our members' information from being scraped and used without their consent." None of the three products was shut down.

ERE's reporting gives this timeline:

• Sept. 12: Steve Lu posts that LinkedIn "raised concerns about our presence on their platform."
• Late September: Gem's company page is gone.
• Early October: Neuroscale loses its page. It had launched its Arbi recruiting platform in July.
• Oct. 13: ERE confirms all three pages return "Page not found." Lu's personal profile has been missing for over a month.

The vendors pushed back. In an AI-generated video, Lu said "LinkedIn doesn't get to determine who's in business or not," and Pin says the product is still fully operational. Gem said "Our customers' partnerships with Gem and/or LinkedIn remain unaffected."

So "LinkedIn banned Pin" isn't quite right. LinkedIn removed a marketing asset. It did not cut off a product.

Does losing a LinkedIn page kill a recruiting tool?

No. The closest precedent is Apollo.io: its page disappeared in March 2025 and was back by July 2026, and the company kept operating the whole time.

On March 6 and 7, 2025, the pages for Apollo.io, Seamless.AI and Prosp.ai disappeared with no official explanation. Apollo's page was live again in July 2026, and both Apollo and Seamless are still in business.

16 months

A company page is the vendor's public face on LinkedIn. The product doesn't run on it. Removing one puts reputational pressure on the vendor and signals disapproval to buyers. It isn't technical enforcement.

That's why the page removals tell you little about your own exposure. The vendor loses some visibility. You could lose access.

Why does your seat carry the risk instead of the vendor?

LinkedIn's User Agreement bans using scraping and automation tools, not only building them, which puts the recruiter running the tool inside the clause. LinkedIn can restrict your seat while the vendor carries on selling to everyone else.

Since Nov. 3, 2025, the agreement has said members won't "develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services." The important word is "use." The member who accepted the agreement and pays for the seat is the easiest party to enforce against.

LinkedIn's Help Center states the consequence directly: people who use prohibited tools risk "having their accounts restricted or shut down," and the tools themselves "may become non-operational without notice."

Even a vendor has said this out loud. HeyReach wrote that "there is no approved outreach automation tool - ours included." When the companies selling automation tell you none of it is sanctioned, a "safe" sourcing tool is a description of how it runs. There is no whitelist.

LinkedIn removed the vendor's page. The contract it can actually enforce against is the one you signed.

Which tool behaviors get a LinkedIn account restricted?

LinkedIn flags behavior and technical footprint, not the brand of the tool. If a sourcing extension got your account restricted, the cause was almost certainly how and where it ran.

A seat restriction is LinkedIn limiting or suspending a member's ability to search, view or message. Published detection guidance points to these signals:

• Injected scripts. Browser extensions change the LinkedIn page, and that leaves a trace LinkedIn can detect. One flagged session puts the whole account at risk.
• Bursts of connection requests. Volume spikes that no human would produce.
• High ignored ratios. Lots of invites that nobody accepts or answers.
• Data-center session origins. Your account active from a cloud server instead of your laptop.
• Rapid-fire profile visits. Profile views in a pattern too fast or too regular to be a person reading.

A session cookie is the token your browser stores after you log in, and it proves to LinkedIn that requests are coming from you. Tools that ask for it can act as you, and every request they make is attributed to your seat.

Here's how the common setups compare:

The table makes one point vendor marketing skips. A well-funded vendor that reads your feed in the background through your session cookie looks the same to LinkedIn as a cheap scraper doing the same thing. Ask where the tool runs. The logo doesn't matter.

HeroHunt reports that the large majority of restrictions are temporary, usually triggered by volume patterns, low acceptance rates or a detected extension. Temporary still costs you. You lose days to weeks of searching and messaging, and pipeline that only exists inside LinkedIn projects is out of reach until the seat comes back.

Who gets hurt most when a seat goes down?

Small sourcing teams and agency or SMB sourcers are most exposed. Their capacity sits in a few seats, and they are more likely to depend on extensions than on enterprise-licensed Recruiter seats.

Refolk's index of professional profiles shows how thin the sourcing function is:

"Sourcer titles" means Sourcer, Talent Sourcer, Technical Sourcer or Sourcing Specialist. Treat the counts as upper bounds. "Sourcing Specialist" also catches procurement roles, especially in the UK, where Deloitte, HSBC and "Procurement Specialist" titles show up in the sample.

2.4%

The employer mix explains the gap. In a 25-profile sample, the 140 sourcers who tag LinkedIn Recruiter cluster at large in-house tech teams: MongoDB, Meta, Anduril, Tesla and Early Warning. A 25-profile sample of the broader US sourcer set is spread across very different employers, including Rippling, Fetch, EvolutionIQ, Church's Texas Chicken and Equipment Depot.

My read, and it is an inference from those samples, is that sanctioned Recruiter seats are bought at enterprise scale. Sourcers at agencies and smaller companies are more likely to fill the gap with extensions, so enforcement under the "use" clause falls hardest on them.

The concentration math makes this worse. With only 482 people holding sourcer titles across the whole UK, sourcing teams there are small, and one restricted seat can take out a big share of a team's capacity for days to weeks.

That's the case for separating where you find people from where you log in. Refolk is not an extension running on your seat. You describe the person you want in plain English and get a ranked shortlist, and it keeps working if your Recruiter seat is restricted.

Is LinkedIn clearing the field for Hiring Assistant 2?

Possibly. The timing fits, but nobody has shown it was planned: LinkedIn is closing third-party access in the same weeks it ships its own AI sourcing agent.

The dates:

• Sept. 12 to early October: Pin, Gem and Neuroscale pages removed.
• Oct. 1: Hiring Assistant 2 launched at Talent Connect.
• Oct. 14: iCIMS announces it will integrate with LinkedIn Hiring Assistant through RSC+, expected in Spring 2027. LinkedIn's Larry Nelson, head of talent partnerships, is part of the announcement.
• November 2026: Hiring Assistant 2 reaches current users automatically.

The iCIMS deal is what LinkedIn's preferred route looks like: AI sourcing that runs inside LinkedIn's agent and connects out through an approved integration.

Once a platform ships its own product, enforcing its terms against third-party tools is good for business as well as defensible on principle. LinkedIn's stated reason, protecting member data from being "scraped and used without their consent," can be true at the same time.

For you, the practical result is the same whichever motive is real. The approved way to run AI inside LinkedIn is narrowing to Hiring Assistant and integration partners like iCIMS. Anything else that touches your session is something you choose to tolerate, and it isn't protected.

How do you build a sourcing workflow that survives a LinkedIn cut-off?

Treat LinkedIn as one source and one outreach channel among several, keep automation off your logged-in session, and keep your pipeline in a system you own. Do all three and a restricted seat slows you down for a while without stopping you.

Here's the order I'd do it in, starting this week:

1. Audit every extension and connected tool. For each one, ask the vendor three questions. Does it run in my browser? Does it use my session cookie? Does it read my feed or visit profiles in the background? A yes to any of them puts your seat in the high-risk rows of the table above.
2. Separate search from your seat. Do discovery against data that sits outside LinkedIn: GitHub repos, personal sites, conference talks, papers, open-source commit history. This is where Refolk fits. You ask for "senior Rust engineers who have contributed to async runtimes," get people back from the open web, and your LinkedIn seat is never involved.
3. Keep invites at human pace. Bursts and high ignored ratios are named triggers. Watch your acceptance rate. If it drops, your targeting is off, and LinkedIn will notice before you do.
4. Store pipeline outside LinkedIn. Candidates kept only in Recruiter projects are lost to you while the seat is down. Sync to your ATS or CRM every day.
5. Keep a second outreach channel. Verified work email, a GitHub-based intro, or a mutual referral. If LinkedIn messaging is your only way to reach someone, a restriction cuts off every open conversation.
6. Use the sanctioned path for in-LinkedIn AI. If you want an agent working inside Recruiter, use Hiring Assistant or an integration partner like iCIMS. Don't use a cookie-based tool and hope.
7. Don't run the whole team through one seat. If your agency routes all search through one power user's account, that account is a single point of failure.

The aim isn't to stop using LinkedIn. The aim is that losing access means a slower week, not lost requisitions.

FAQ

Did LinkedIn ban Pin's recruiting tool?

LinkedIn removed Pin's company page and CEO Steve Lu's personal profile, but Pin says the product is still fully operational. Removing a page is reputational pressure on the vendor, not a technical shutdown. Apollo.io's page was removed in March 2025 and restored by July 2026, and Apollo kept operating throughout.

Will using Gem or Pin get my LinkedIn account restricted?

It depends on how the tool touches LinkedIn, not on the vendor. Gem says customer partnerships are unaffected. But LinkedIn's terms ban members from using scraping tools, and detection looks for injected scripts, data-center logins, rapid profile visits and invite bursts. If a tool does any of those through your session, your seat is exposed whatever the vendor's page status.

Are LinkedIn seat restrictions permanent?

Usually not. HeroHunt reports that the large majority of restrictions are temporary and are triggered by volume patterns, low acceptance rates or detected extensions. The real cost is the downtime, which can run days to weeks: lost searches, stalled conversations and unreachable pipeline. That's why keeping search and candidate data outside your seat matters more than any appeal process.