LinkedIn Post Search Scraper
Pricing
$3.00 / 1,000 linkedin posts
LinkedIn Post Search Scraper
Search public LinkedIn posts by keyword with no login: post URL, author, headline, profile, snippet. No ban risk. $3/1k. Works in Claude & ChatGPT.
Pricing
$3.00 / 1,000 linkedin posts
Rating
0.0
(0)
Developer
The Mine Works
Maintained by CommunityActor stats
0
Bookmarked
10
Total users
7
Monthly active users
a few seconds ago
Last modified
Categories
Share
📣 LinkedIn Post Scraper: Search Posts by Keyword, No Login
Overview
LinkedIn Post Scraper turns any keyword or phrase into a structured feed of public LinkedIn posts. Give it lab grown diamond or SaaS pricing strategy and it returns clean JSON for each match: post URL, author name, author headline, author profile URL, and a text snippet. No cookies, no account, no login of any kind.
The actor never touches LinkedIn directly. It reads posts from Google's public index, which has already crawled public linkedin.com/posts/… pages. Because every byte comes from Google, there is no LinkedIn session to flag and nothing on your account to ban. That makes it the safest way to run keyword based social listening on LinkedIn at scale.
Reliability posture: empty searches, Google bot walls, and failed runs are never charged. You only pay for a post record that was actually delivered.
✅ No login required | ✅ Never hits LinkedIn | ✅ Pay only for posts returned | ✅ MCP-ready for AI agents
Features
Keyword and phrase search. Point the actor at any topic, brand, or competitor and paginate up to 200 posts. Per post record. Post URL, author name, author headline, author profile URL, and text snippet. Zero ban risk. Requests hit only Google SERPs, never LinkedIn. Your account is never involved. Trend and lead discovery. Surface people actively posting about the problem your product solves. Pay per post. Empty searches, Google bot walls, and failed runs are never charged.
How it works
The actor issues Google search queries in the shape site:linkedin.com/posts "your keyword" through the GOOGLE_SERP proxy group, which returns raw Google SERP HTML. Each result is parsed into a structured post record and deduplicated by canonical post URL. The RESIDENTIAL proxy group works as a fallback if you prefer to route through residential IPs.
Author headlines and profile URLs are extracted best effort from the Google result and the LinkedIn post slug. post_url and author_name are the most reliable fields. Google typically indexes 50 to 150 unique posts per phrase before the index is exhausted, so vary phrasings to go deeper. The first 10 posts on every account are free for life.
🧾 Input configuration
{"query": "lab grown diamond","maxResults": 25,"proxy": { "useApifyProxy": true, "apifyProxyGroups": ["GOOGLE_SERP"] }}
📤 Output format
Real record delivered by a live run against query: "SaaS pricing strategy" on 2026-07-15:
{"post_url": "https://www.linkedin.com/posts/raj-vardhman_saas-pricingstrategy-startuptips-activity-7295622726138871808-4eh9","author_name": "Raj Vardhman's Post","author_headline": "SAAS Pricing Strategy","author_profile_url": "https://www.linkedin.com/in/raj-vardhman","post_snippet": "Raj Vardhman's Post - SAAS Pricing StrategyLinkedIn · Raj Vardhman4 reactions · 1 year agoLinkedIn · Raj Vardhman4 reactions · 1 year agoSAAS Pricing Strategy: The Art of Getting It Right Three pricing models that actually work: 1. Free","scraped_at": "2026-07-15T01:15:13.514Z"}
author_name and author_headline are extracted best effort from the Google result title and often include LinkedIn's own boilerplate (e.g. "'s Post"), as shown above. post_url and author_profile_url are the most reliable fields. A final _type: "summary" record is appended to every run with counts (posts found, charged, free tier usage).
Every post record contains these fields:
| Field | Description |
|---|---|
🔗 post_url | Canonical LinkedIn post URL |
🙍 author_name | Name of the post author |
💬 author_headline | Author's job title or headline when available |
🔗 author_profile_url | Best effort LinkedIn profile URL for the author |
📝 post_snippet | Text excerpt of the post from the Google SERP result |
🕒 scraped_at | ISO timestamp when the record was captured |
💼 Common use cases
Brand and product monitoring Capture every public post mentioning your name, product, or launch. Schedule the actor to re run on your keyword and diff new URLs against your previous dataset.
Lead generation
Reach out to people already discussing your topic publicly.
Turn a topic like retention strategy or first hire into a warm outbound list.
Competitor watching Track mentions of a rival's brand, launch, or campaign as they happen. Compare share of voice across weeks by counting unique authors per phrase.
Content and trend research Study the trending post angles and hooks in your category. Surface the authors driving conversation on a subject before they saturate your feed.
🚀 Getting started
- Enter a Search query like
artificial intelligence startuporSaaS pricing strategy. - Set Max results (default 25, up to 200).
- Leave Proxy on the default
GOOGLE_SERPgroup.RESIDENTIALworks as a fallback. - Click Start. The actor paginates Google's index and extracts each public post.
- Export the dataset as JSON, CSV, or Excel, or pull it via API or MCP into your dashboard or agent.
FAQ
Does this log in to LinkedIn or need cookies? No. It never sends a single request to LinkedIn. There is nothing to log in to and no ban risk. All data comes from Google's public index.
Is this compliant? It collects only public posts Google has already indexed. Use the results in line with GDPR, CCPA, and your local laws. You are responsible for how you use them.
Why is the snippet not the full post?
Snippets are excerpts from Google's index, not the full post body. Open post_url for the complete post.
Why do I get fewer posts than expected? Google typically indexes a limited number of posts per phrase (often 50 to 150 unique posts before the index is exhausted). Try varied phrasings to go deeper.
Are author profile URLs always accurate?
They are extracted best effort from the post slug and may not always resolve. post_url and author_name are the most reliable fields.
Can I monitor a topic continuously?
Yes. Schedule the actor to re run on your keyword and diff new post_url values against your previous run.
How is pricing calculated? Pay per event: $0.003 per post delivered, which is $3 per 1,000 posts. The first 10 posts per Apify account are free for life. Empty searches, Google bot walls, and failed runs are never charged.
Use in Claude, ChatGPT & any MCP agent
https://mcp.apify.com/?tools=themineworks/linkedin-post-search
Or call it programmatically with the Apify client:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });const run = await client.actor('themineworks/linkedin-post-search').call({query: 'lab grown diamond',maxResults: 25,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
🛠️ Related LinkedIn actors
Posts are the signal. Turn them into people, companies, and outreach with the full LinkedIn wedge:
- LinkedIn Profile Scraper: turn a post author's profile URL into full profile detail.
- LinkedIn Company Scraper: public company firmographics.
- LinkedIn Employees Scraper: find a company's people as B2B leads (no login).
- LinkedIn Jobs Scraper: public job listings by keyword and location.
- LinkedIn Candidate Finder: a matched candidate shortlist from role, skills, and location.
- B2B Leads Finder: named decision-maker contacts with business emails and phone numbers from a company or domain list.
Typical flow: post search finds the conversation, profile scraper enriches the individual authors, employees and company scrapers add the org context, and jobs scraper flags hiring accounts inside the same topic.
Disclaimer: This actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a registered trademark of LinkedIn Corporation. All trademarks are the property of their respective owners. Use scraped public data in line with GDPR, CCPA, and your local laws.
Found a bug or have a feature request? Open an issue on the actor's Apify Console page or reach out through the Apify profile.