Facebook Posts Scraper avatar

Facebook Posts Scraper

Pricing

from $0.0005 / result

Go to Apify Store
Facebook Posts Scraper

Facebook Posts Scraper

Scrape public Facebook page and post metadata into structured post candidate records for brand monitoring and social research.

Pricing

from $0.0005 / result

Rating

0.0

(0)

Developer

Peter PANG

Peter PANG

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Share

Facebook Posts Scraper is an original Apify actor for collecting public Facebook page and post metadata into structured post candidate records. It is intended for social media monitoring, brand tracking, competitor research, public communications audits, campaign review, and market intelligence workflows where teams need exportable records from Facebook page or post URLs.

The actor accepts pageUrls, postUrls, maxPosts, an includeEngagement toggle, and Apify proxy configuration. It fetches each public target with browser-like headers, extracts page title and description metadata, scans visible text for substantial post-like content, and saves normalized records with page URL, post URL, post index, text, description, engagement columns, and timestamp. If a page exposes only metadata, the actor still saves a useful metadata record. If a request fails because of access restrictions or blocking, a structured error record is saved so the run remains auditable.

This package does not copy proprietary Apify Store actor code. It provides a maintainable public-web alternative with the same basic user promise: provide Facebook targets, run the actor, and export structured social data. Facebook frequently gates content, changes markup, and restricts unauthenticated requests, so public extraction quality depends on target visibility, region, and proxy reputation. Enable Apify proxy and test smaller batches before scaling.

The dataset schema is explicit for Apify preview and CSV or JSON export. The actor includes Docker setup, pinned Python dependencies, status messages, input schema, dataset schema, changelog, and documentation. It is suitable as a publishable starting point for public Facebook monitoring products and can later be extended with Playwright-based browsing if deeper dynamic extraction is required.