LinkedIn Post Comments Scraper

LinkedIn Post Comments Scraper: who commented on a public post, and what they said

Paste the URLs of public LinkedIn posts and get the comments back as rows: the comment text, the author's name, a link to their profile, the reaction count on the comment and how old it is. No account, no cookie.

Here is the limit, up front, because it decides whether this is any use to you. LinkedIn shows a signed-out visitor at most 10 top-level comments per post. That is what this returns. On a post with 760 comments you get ten of them, and no input setting changes that.

💬 What LinkedIn Post Comments Scraper does

A public post page carries its top comments in the page itself, for anyone, signed in or not. This reads that block, one post at a time, and turns each comment into a row.

Every row also carries the post it came from: the post author, the total reaction count and the total comment count. Those totals are the post's real numbers, so you can always see how big a slice you are holding. Ten of 760 is still ten of 760, and the row says so.

You can hand it a post URL in any of the shapes LinkedIn hands out: a /feed/update/urn:li:activity:... link, a /posts/...activity-<id> link, a bare activity id, or the urn:li:activity:<id> form. The same post listed twice is fetched once.

📥 What you give it

{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7302346926123798528/",
    "7302346926123798528"
  ]
}

A ugcPost URN is not an activity URN. If your link carries urn:li:ugcPost:, open the post in a browser and copy the activity URL from the address bar instead.

📤 What you get back

A real row from a recent run. The comment URL is cut short and one bookkeeping field is left out:

{
  "ok": true,
  "_sample": false,
  "sourceType": "public_linkedin_post_comment",
  "commentId": "7302369905079660544",
  "commentText": "Surprising that nobody here is discussing data sovereignty. Microsoft, as a US company, is subject to the CLOUD Act and Patriot Act, meaning AI-uploaded data or stored files could potentially be accessed by US authorities. ...",
  "commentUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7302346926123798528/?commentUrn=urn%3Ali%3Acomment%3A...",
  "authorName": "Richard Oerlemans",
  "authorProfileUrl": "https://ch.linkedin.com/in/richardoerlemans",
  "likeCount": 281,
  "commentAgeText": "1y",
  "approximateCreatedAt": "2025-09-20T14:47:23.564Z",
  "postActivityId": "7302346926123798528",
  "postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7302346926123798528/",
  "postAuthorName": "Satya Nadella",
  "postReactionCount": 20352,
  "postCommentCount": 760,
  "retrievedAt": "2026-09-20T14:47:23.564Z"
}

🧾 Reading the output

Three kinds of row, and only comments cost anything.

There is no charged field on these rows. sourceType is what separates a real comment from a sample or a diagnostic.

A diagnostic row carries an errorCode:

Neither a sample nor a diagnostic row fails the run, and neither is charged.

▶️ How to run it

1. Open LinkedIn Post Comments Scraper and click Try for free. 2. Paste post URLs into Public LinkedIn post URLs or activity URNs, one per line. 3. Lower Maximum comments per post if you only want the top two or three. 4. Click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.60 per 1,000 comments. Flat on every Apify plan, no volume tiers.

One charge per comment row. A post that shows no comments to a signed-out visitor costs you nothing for results, and neither do sample or diagnostic rows. A post you list twice is fetched once.

Ten comments per post is the practical ceiling, so a hundred posts is about a thousand rows at most.

💡 What people use it for

• Pulling the people who engaged with a post that matters in your market, then looking them up.
• Reading the objections under a competitor's announcement, in the words customers used.
• Keeping a record of the public responses to your own posts, outside LinkedIn.
• Spotting which commenters keep showing up across a set of posts in one industry.

🚧 What it does not do

• No more than 10 comments per post. Not a setting, not a tier. It is what the page shows

without an account.

• No replies. Top-level comments only.
• No reaction lists. You get the count on a comment, not who reacted.
• No exact timestamps. LinkedIn publishes 1y and 9mo, so that is what there is.
• No image-only comments. A comment with no text is skipped rather than written as an empty

row.

• No comments on private or deleted posts, and none from a post that hides them from

signed-out visitors. Many posts do.

• No emails or phone numbers. You get the profile URL, and the rest is up to you.

🧭 Which LinkedIn scraper do you need?

❓ Questions people ask

Can I get all 760 comments if I pay more? No. Ten is what a signed-out visitor sees, and this never signs in.

Do I need a LinkedIn account? No, and there is no cookie field. Nothing to paste, nothing to renew.

Why did a post return nothing? Because it shows no comments to signed-out visitors. The NO_RESULTS row tells you which post, and re-running it will not change the answer.

Are the dates real? commentAgeText is. approximateCreatedAt is that age subtracted from the run time, so treat it as an estimate.

Can I get the commenters' job titles? Not from here. Take authorProfileUrl into the profiles actor above.

Is scraping LinkedIn legal? This reads only what LinkedIn publishes to the open web. Comments are personal data, which GDPR and similar laws cover, so have a lawful reason for collecting them. Apify's write-up on scraping and the law is a reasonable starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID and the post URL. The errorCode and the details field on the diagnostic row usually explain it on their own.