📣 LinkedIn Post Scraper: Search Posts by Keyword, No Login

Part of the Social & Market Research MCP. This actor's data is also available to AI agents through our Social & Market Research MCP server — eight social, news and search-interest tools behind one endpoint. No result, no charge.

⚡ 328/328 runs succeeded in the last 30 days · no login, no cookies, no ban risk. 💸 You're only charged for delivered posts. Empty searches are never billed.

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.

🧾 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).

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

1. Enter a Search query like artificial intelligence startup or SaaS pricing strategy.
2. Set Max results (default 25, up to 200).
3. Leave Proxy on the default GOOGLE_SERP group. RESIDENTIAL works as a fallback.
4. Click Start. The actor paginates Google's index and extracts each public post.
5. Export the dataset as JSON, CSV, or Excel, or pull it via API or MCP into your dashboard or agent.

🔁 Run on a schedule

Turn this from a one-off pull into a standing feed with Apify's built-in Schedules — no code, no cron server of your own.

1. Run the actor once with the input you want repeated, then click Save as a task (top of the run form) — this keeps your exact input attached for every future run.
2. In the Apify Console, go to Schedules (left sidebar) → Create new.
3. Name it, set your timezone, and pick a frequency — a preset (hourly / daily / weekly) or a custom cron expression (e.g. 0 6 * * * for daily at 6am).
4. Under Actors or tasks to run, add the task you saved in step 1.
5. Save. From then on it runs unattended on your schedule, billed the same pay-per-post way as a manual run — nothing is charged just for the schedule existing.

Prefer to automate the setup itself? Same thing via the API:

curl -X POST "https://api.apify.com/v2/schedules?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "linkedin-post-search-daily",
    "cronExpression": "0 6 * * *",
    "isEnabled": true,
    "actions": [{ "type": "RUN_ACTOR", "actorId": "themineworks/linkedin-post-search" }]
  }'

Full options — time zones, run notifications, pausing a schedule — are in Apify's Schedules documentation.

Monitor mode — pay only for NEW posts

Set monitorMode: true and this actor remembers what it delivered last time (keyed on post_url) — on the next scheduled run, only genuinely new posts are pushed and charged. Re-running the same input daily costs you for the new posts each day, not the whole feed every time.

{ "monitorMode": true }

Pairs directly with Run on a schedule above: save a task with monitorMode: true, attach it to a daily schedule, and you have a standing "what's new" feed with no duplicate charges. The summary row reports new_this_run and skipped_duplicates so you can see the dedup working. First run establishes the baseline (everything is "new"); every run after that is incremental.

💵 Pricing

Event	Price	You pay when
Post delivered	$0.002	A post record lands in your dataset

$2.00 per 1,000 posts — under the ~$3.00/1k social-category median for paid-and-used actors on the Store. Zero-result searches are never charged.

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. Empty searches, Google bot walls, and failed runs are never charged.

Can you scrape LinkedIn posts without logging in? Public post search results are visible without an account; that's all this actor reads. No credentials, no cookies, nothing to ban.

How fresh are the results? Each run queries live search — you see what a logged-out visitor sees at run time. Every one of the last 328 runs completed successfully.

Is scraping LinkedIn legal? Courts have repeatedly addressed scraping of public LinkedIn data (hiQ v. LinkedIn); this actor touches only public content and never logs in. Public data can still contain personal data under laws like the GDPR — collect only what you have a legitimate purpose for.

🤖 Use from Claude, ChatGPT & any MCP agent

Hosted MCP endpoint — no install, OAuth on first connect:

https://mcp.apify.com/?tools=themineworks/linkedin-post-search

Claude Desktop / Cursor config (token auth):

{
  "mcpServers": {
    "linkedin-posts": {
      "url": "https://mcp.apify.com/?tools=themineworks/linkedin-post-search",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Ask your agent: "What are people saying on LinkedIn about [topic] this week? Summarize themes and link the top five posts."

For multi-platform social research in one connection, use our Social & Market Research MCP server — eight tools behind one endpoint.

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.