LinkedIn Posts Scraper for Companies and Professionals

Extract LinkedIn posts from company pages and professional profiles, including post text, authors, dates, hashtags, links, and engagement metrics.

What You Can Use It For

• Monitor recent posts from company pages or professional profiles.
• Collect post text, dates, authors, hashtags, and engagement metrics.
• Analyze competitor messaging, hiring themes, product announcements, and executive content.
• Export structured results as JSON, CSV, Excel, XML, or through the Apify API.

Input

Paste one LinkedIn company page or professional profile URL per line:

{
  "urls": [
    "https://www.linkedin.com/company/microsoft/",
    "https://www.linkedin.com/company/nvidia/"
  ],
  "startDate": "2026-01-01"
}

Use startDate and endDate to narrow the post date range. The Actor applies the requested range both to the source request and locally after normalizing each returned post, so exported posts do not fall outside the selected window. Direct post URLs are also supported when you need to collect a specific post.

The Actor processes each submitted URL independently. That means every target receives an explicit no-results or error diagnostic, rather than allowing a successful response for one URL to mask another URL in the same batch. For professional profiles, reposts are retained because resharing is an intentional act of endorsing or amplifying third-party content. Where the source omits a date but returns a LinkedIn activity URN, the Actor derives the activity timestamp from that top-level URN.

Output

The Actor emits one linkedin_post row per extracted post. If an input cannot be extracted, it emits a scrape_error row with failureStage and errorMessage so the reason is visible in the dataset.

If the same post is returned through overlapping inputs (for example, a direct post URL and the author's feed), the Actor keeps one post row and reports the number removed in OUTPUT.summary.duplicatePostsRemoved. Diagnostic rows include oldestSeen, stopReason, and, where supplied by the managed source, sourcePostsReturned and sourcePostsDated. pagesFetched stays null when the managed source does not expose raw pagination metadata.

Historical-window diagnostics

The managed LinkedIn posts dataset controls feed traversal and does not expose a cursor or raw page stream to this Actor. If it returns only a recent sample and cannot satisfy an older selected date range, the Actor emits a scrape_error with stopReason: provider_window_miss rather than claiming that the profile has no posts. In that case, sourcePostsReturned and sourcePostsDated expose the source's own diagnostic counts. This is intentionally explicit: a historical range is only complete when the source itself reaches it.

The main table shows diagnostic fields first, followed by fields useful for content analysis:

• recordType
• inputUrl
• targetUrl
• failureStage
• errorMessage
• postUrl
• postId
• datePosted
• authorName
• authorUrl
• companyName
• companyUrl
• postText
• postType
• numLikes
• numComments
• numShares
• engagementCount
• hashtags
• externalLinks
• postQuality
• missingFields

Some fields are best-effort because LinkedIn posts do not expose the same data for every post or author. Rows include postQuality and missingFields so partial records are visible.

Example Output

{
  "recordType": "linkedin_post",
  "targetType": "company",
  "postUrl": "https://www.linkedin.com/posts/microsoft_activity-1234567890",
  "postId": "1234567890",
  "datePosted": "2026-01-15T14:30:00.000Z",
  "authorName": "Microsoft",
  "companyName": "Microsoft",
  "companyUrl": "https://www.linkedin.com/company/microsoft/",
  "postText": "Announcing new AI capabilities for developers...",
  "numLikes": 45230,
  "numComments": 1250,
  "hashtags": ["#AI", "#Developers"],
  "postQuality": "COMPLETE",
  "missingFields": []
}

Notes

This Actor extracts publicly available LinkedIn post data from company pages and professional profiles. It does not access private messages, private profiles, or data behind a login wall.