LinkedIn Profile Posts Scraper (No Cookies)

Extract posts from LinkedIn profiles, including content, media, engagement, reactions, comments, and more. No cookies or account required.

Publisher description, verbatim
Last 7 dayson this actor
Each one reaches followers by email the morning after.Follow this actor
Key figures30 readings
Price / 1k$2.00per 1,000 post
Users / 30d9,126↑ 942 over 30 readings
Users, all time36,770↑ 4,734 over 30 readings
Runs / 30d3m↓ 5,407 over 30 readings
Runs / user / mo328runs per monthly user
Standing
#3of 1,383

on LinkedIn, by users in the last 30 days among actors classified to this platform.

Store search presence
7top-10 keywords

best #1 for “linkedin post”

  • linkedin post#1
  • linkedin posts#1
  • linkedin profile#3
  • 4 more#4–#4
re-crawled daily
Recorded changes
  • 2026-09-23changeIcon replaced—on record
  • 2026-09-15searchKeyword rank moveleft top-3 for “linkedin” (#3 → #4)—on record
  • 2026-09-15searchKeyword rank moveleft top-3 for “link” (#3 → #4)—on record
showing 3 of 10 in the last 30 days · followers get all 10 by email

What the reviews say

Good for basic scraping because it provides a date filter and low base cost, but it struggles with strict/truncated date limits, high costs for reactions/comments, incorrect post/author counts, and requires manual multi-field checks.

20 of 20 reviews carry text
ThemeSentimentSaidWhat they mean
Caps and ceilings1 praised · 3 complained4built-in date filter availablestrict exact date-range cutoff“This is a great actor! The only issues are the output and the limit. If the limit was stated, then it would be much better. Regarding the output, it would be nice to have summary columns (number of posts, number of reposts and number of quoted posts) for easy analysis.” — 4/5
What it costs1 praised · 2 complained3affordable for basic scrapingexpensive for reactions and comments“Exceptionally expensive for reactions and comments. Use "supreme_coder/linkedin-post" if you want a more reasonable price - charged by the post, reactions and comments are free.” — 1/5
Does it return everything0 praised · 2 complained2returns more posts than requested“Got excited when i saw this. But sadly the data is not organized in a reliable way. For example, put in 2 posts to scrape as a test. It pulled 10 posts. Sometimes the target person is under one column, while other times they're in another. ihave to check 2-3 fields to see which target person reposted a certain post. I wish there was simply a constant "author name" field that didn't change if it was a repost. Because the goal is to ensure that the scraped post is tied to the original scraped person, not suddenly saying that the author is now a new person. that new person can be nested within. Maybe a repost author category? Otherwise, the data would have been good.” — 3/5
Is the data right0 praised · 1 complained1author field incorrect for reposts
Setup and docs0 praised · 1 complained1requires checking multiple fields to verify

Caps and ceilings

1 ↑ · 3 ↓ of 4
built-in date filter availablestrict exact date-range cutoff“This is a great actor! The only issues are the output and the limit. If the limit was stated, then it would be much better. Regarding the output, it would be nice to have summary columns (number of posts, number of reposts and number of quoted posts) for easy analysis.” — 4/5

What it costs

1 ↑ · 2 ↓ of 3
affordable for basic scrapingexpensive for reactions and comments“Exceptionally expensive for reactions and comments. Use "supreme_coder/linkedin-post" if you want a more reasonable price - charged by the post, reactions and comments are free.” — 1/5

Does it return everything

0 ↑ · 2 ↓ of 2
returns more posts than requested“Got excited when i saw this. But sadly the data is not organized in a reliable way. For example, put in 2 posts to scrape as a test. It pulled 10 posts. Sometimes the target person is under one column, while other times they're in another. ihave to check 2-3 fields to see which target person reposted a certain post. I wish there was simply a constant "author name" field that didn't change if it was a repost. Because the goal is to ensure that the scraped post is tied to the original scraped person, not suddenly saying that the author is now a new person. that new person can be nested within. Maybe a repost author category? Otherwise, the data would have been good.” — 3/5

Is the data right

0 ↑ · 1 ↓ of 1
author field incorrect for reposts
1 more themes · read all 20 →
Every count is a review we read. 13 of the 20 said only that they liked it, with nothing specific — those are excluded from the themes above. Quotes are one reviewer, unedited.Read all 20 →

History

30 readings since 2026-08-27
Users / 30d30 readings
08-27↑ 94209-25
Users, all time30 readings
08-27↑ 4,73409-25
Runs / 30d30 readings
08-27↓ 5,40709-25
Standing30 readings
08-27↓ 109-25

Alternatives on LinkedIn

The actors either side of #3 of 1,383, ranked by users in the last 30 days. Same platform, adjacent adoption — the comparable set.

all 1,383 on LinkedIn →
Sort
#ActorGradePrice / 1kUsers /30dSuccessRatingAgeFresh
1ARES$2.00 /1k17,672161.9K total98.6%4.6 (141)2.1yfresh
2AEVT$4.00 /1k profilehigh price10,31973.1K total100.0%4.6 (92)17mfresh
3AEVT$2.00 /1k postgood price9,12636.8K total100.0%4.4 (55)17mfreshThis
4AEVT$2.00 /1k postgood price6,64029.3K total99.6%5.0 (53)17mfresh
5AEVT$100 /1k search-pagesteep price6,34644.9K total99.6%4.4 (103)17mfresh
6ARES$4.00 /1k6,08122.1K total100.0%4.5 (35)16mfresh
7BEVT$3.00 /1k short-profilefair price5,73329.9K total99.4%3.9 (47)15mfresh
8BRES$0.40 /1k4,28324.6K total98.7%4.7 (26)17maging

Follow this actor, compare it against its rivals, and get every overnight change in one morning report.

Publish it yourself? Claim your publisher page and its full history is yours free, forever.

Open in the app Claim this page

Numbers on this page are measured only by an independent census of the Apify Store — not self-reported.