LinkedIn Posts Search Scraper 🔍 [No Cookies] — Only $2.5/1K 💰

You need to find public LinkedIn posts about your topic without a login, a cookie, or a session that expires by Friday.

No login · no cookies · results in 3–5s · search by keyword, hashtag or topic

---

🔎 Where the data comes from — read this first

This actor does not query LinkedIn search. It runs a site:linkedin.com/posts/ query against a search engine (DuckDuckGo) and returns the indexed results. Consequences you should price in:

• text is the search-result snippet, not the body of the post. It is truncated by the search engine, not by this actor.
• authorName is derived from the post URL slug (/posts/jane-doe_... → jane doe). It is not a verified display name.
• Coverage is whatever the search engine has indexed. A post published minutes ago is usually not in it yet. "Real-time" is not what this actor does.

---

⚡ Highlights

• 100% No Cookies / No Login — plain HTTP, nothing to expire, nothing to get banned.
• Cheap discovery — $0.0025 per post found ($2.50 per 1,000).
• Nothing found, nothing charged — a run with zero results returns a labeled diagnostic and charges no PPE event.

---

📥 Input

Field	Type	Description
searchQueries	array	Keywords, hashtags or topics to search
maxPosts	integer	Total posts returned by the run, across all queries (default 20)
proxyConfiguration	object	Proxy settings (optional)

maxPosts is a whole-run budget, not a per-query cap. With two queries and maxPosts: 20, the first query can consume all 20 and the second returns nothing.

📤 Output

Every field the actor emits — there are six, plus scrapedAt:

{
  "searchQuery": "Artificial Intelligence",
  "authorName": "jane doe",
  "headline": "Jane Doe on LinkedIn: In July's edition of The Monthly Tech-In...",
  "text": "In July's edition of The Monthly Tech-In, we explore how AI is helping clinicians...",
  "postUrl": "https://www.linkedin.com/posts/jane-doe_...",
  "scrapedAt": "2026-08-27T20:45:00.000Z"
}

✅ Capabilities & Limits

Stated up front, so you do not pay a run to find out.

Built here: text is a search-engine snippet. Two posts whose snippets are truncated at the same sentence look identical in this dataset even when the posts differ — open postUrl before acting on the content.

Input / feature	Supported	Notes
Keyword / topic	✅	searchQueries accepts plain keywords and hashtags
Hashtag	✅	pass it inside searchQueries (e.g. #AI)
Post URL	✅	postUrl — the one field you can act on directly
Full post body	❌	snippet only, truncated by the search engine
Author profile URL	❌	not emitted; only the slug-derived authorName
Publication date	❌	not emitted — the search result does not carry it
Likes / comments / shares counts	❌	no engagement metric of any kind is emitted
Comment text	❌	not emitted
Author handle search	❌	this actor searches content, not profiles — use linkedin-posts-scraper-pro
Private / member-only posts	❌	public indexed results only
Real-time freshness	❌	limited by search-engine indexing lag, typically hours to days
Per-query result cap	❌	maxPosts is a global budget

🎯 Use cases

1. Discovery — build a list of public post URLs on a topic, cheaply, then fetch what you need
2. Competitor listening — see whose posts on your category are indexed
3. Lead sourcing — surface authors already publishing about your problem space

❓ FAQ

Do I need a LinkedIn account or cookie? No. The actor reads public search results over plain HTTP.

Is this LinkedIn's own search? No. It is a site:linkedin.com/posts/ search-engine query. See the note at the top.

Can I get comments, likes or the publication date? No. This actor emits six fields and none of them is an engagement metric or a date. If you need those, take postUrl into an actor that fetches the post itself.

Why is authorName lowercase and odd-looking? It is the URL slug with hyphens replaced by spaces. It is an identifier, not a display name.

💰 Pricing

Pay Per Event — event post-found.

Metric	Cost
Per post found	$0.0025
Per 1,000 posts	$2.50

You are never charged for a run that returned nothing. When the search is blocked or matches nothing, the actor returns a labeled diagnostic row and charges no PPE event.

---

🇧🇷 Português

Este actor não consulta a busca do LinkedIn. Ele executa uma consulta site:linkedin.com/posts/ em um buscador (DuckDuckGo) e devolve os resultados indexados. Consequências:

• text é o snippet do resultado de busca, não o corpo do post — truncado pelo buscador.
• authorName vem do slug da URL (/posts/jane-doe_... → jane doe), não é nome verificado.
• A cobertura é a do índice do buscador. Post publicado há minutos normalmente ainda não está lá: isto não é monitoramento em tempo real.

Não são emitidos: corpo completo do post, URL do perfil do autor, data de publicação, curtidas, comentários ou qualquer métrica de engajamento. São seis campos, listados na seção em inglês.

maxPosts é orçamento global da execução, não limite por consulta.

Execução que não retorna nada não é cobrada: o actor devolve um diagnóstico rotulado, sem cobrar evento.

Campos de entrada, saída, limites e FAQ estão nas seções em inglês acima.