subimpact WhatsApp us

Facebook Pages Scraper alternative: pages, posts and comments

Both actors read public Facebook Pages and return JSON rows on the Apify Store. Apify's Facebook Pages Scraper charges $12.00 per 1,000 pages at list price, $5.40 on higher plans, and ours charges $1.00 per 1,000 posts or $2.00 per 1,000 page records. The trade-off is focus: theirs returns contact fields, rating and ad running status, and ours adds the latest posts, reactions and comment rows.

Prices checked 20 Nov 2026. Both actors run on Apify, so the numbers come from the same Store listing pages.

Key facts side by side

Fact Facebook Pages Scraper This API (Facebook Pages Scraper: Posts, Pages & Comments)
Price per 1,000 posts (Free plan) $12.00 $1.00
Higher plans (Gold) $5.40 $1.00
Start fee per run None None
Platform usage Included Included
Users on the Apify Store 77,973 17
Rating 4.7 (56 reviews) No reviews yet
Last build 16 Nov 2026 20 Nov 2026
Pricing model Pay per event Pay per event

Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price.

Head-to-head test

page details for 2 Facebook pages (NASA, BBC News)

Measure Facebook Pages Scraper This API
Status SUCCEEDED SUCCEEDED
Items returned 2 4
Run time (seconds) 6.8 33.2
Average filled fields per item 27.5 15.0
Distinct fields 30 30
List price of the job $0.024 $0.004
Measured platform usage $0.00 of compute, included in the price $0.00044 of compute, included in the price

One run each on 20 Nov 2026, same input, default memory. Small samples; your results will vary with input.

Which one to choose

When to choose Facebook Pages Scraper

  • Contact fields such as email, phone, address and messenger are the point of the job
  • Rating, price range or ad running status is needed per page
  • A Standby endpoint for single page lookups fits your architecture
  • Their long review history and high rating support your internal sign-off

When to choose this API

  • You want page details, recent posts and engagement counts in one dataset
  • Comment text for single post links belongs in the same run
  • Paying per post and per page keeps a wide pull proportionate to what you use
  • You would rather avoid cookies and browser automation in the pipeline

Switching from Facebook Pages Scraper

Their input field Our input field Note
startUrls pageUrls Page and profile links go in the pages list; depth is set with maxPostsPerPage.
startUrls postUrls A link to one post belongs in the single post list, which is where comments are read.

Example input

{
  "pageUrls": [
    "https://www.facebook.com/NASA",
    "https://www.facebook.com/bbcnews"
  ],
  "maxPostsPerPage": 20,
  "includeComments": true,
  "maxCommentsPerPost": 20,
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Actor id: subimpact/facebook-pages-scraper. Paste the input above into the Apify Console and press Start.

Where each one is stronger

Where Facebook Pages Scraper is stronger

  • Contact fields such as email, phone, address and messenger on each page
  • Ad running status, rating and price range alongside the page profile
  • Also works as a Standby endpoint for single page lookups

Where this API is stronger

  • Latest posts, comments and engagement counts in the same dataset
  • Post and comment rows are the unit you pay for, so wide page pulls stay proportionate
  • No cookies and no browser needed

Questions people ask

How do the units differ between the two actors?

Theirs charges $12.00 per 1,000 page records at list price and $5.40 on higher plans, one charge for each page returned. Ours charges $1.00 per 1,000 posts and $2.00 per 1,000 page records, so a wide pull with many posts per page is priced on what it returns.

Do you return email, phone and address fields?

No. Our rows carry page name, category, follower counts, about text, avatar, recent posts and engagement figures, and contact fields such as email, phone, messenger and price range are not included. Theirs returns those fields, so a pure contact lookup belongs there.

How do I move an existing run across?

Move the links from startUrls into pageUrls, set maxPostsPerPage for how many posts you want, and add postUrls if you need comments. Rows are typed by rowType, so page rows and post rows can be filtered apart in the same dataset.

Can I collect comments?

Yes, but only for single post links. Add the post URL to postUrls, set includeComments, and use maxCommentsPerPost to control volume. Page level pulls return post rows with comment counts but not the comment text.

What are the limits of the Facebook side?

Around twenty latest posts per page, public pages only, and no personal profiles, groups or Marketplace listings. Follower and talking-about counts can be empty when Facebook serves a page in a non English interface.

Do I pay Apify platform usage on top?

No. The per post and per page prices include platform usage, and our actor has no start fee. Theirs also publishes page prices with platform usage inside them.

Need a data source that is not here?

We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.