Facebook Page Reviews Scraper · URLs, IDs & History

Extract publicly visible Facebook Page reviews into structured records for reputation analysis, customer-feedback research, reporting, and scheduled data collection. Use Page URLs or numeric Page IDs, set firm page and row limits, and export the resulting review rows to JSON, CSV, or Excel.

Watch the demo

What this Actor returns

Each default-dataset item is one public review, written to the dataset exactly as it is returned. This Actor is a raw pass-through: no field is added, renamed, or dropped, so every key present in the source response is preserved as-is. Commonly present keys include type, post_id, recommend, message, author, reactions_count, comments_count, share, photos, tags, created_time, rating, url, and review_url. Any additional key the source returns is kept too.

Facebook commonly represents Page reviews as recommendations. This Actor does not convert a recommendation into a star rating, invent sentiment, or fill unavailable text. A key that the source does not return is simply absent.

Input

Use at least one Page input. Existing integrations can keep using pageId and maxPages.

Field	Type	Required	Default	Description
pageUrls	array of strings	Conditional	none	Public Facebook Page or /reviews URLs.
pageIds	array of strings	Conditional	none	Numeric Facebook Page IDs.
pageId	string	Conditional	100063543614476	Backward-compatible single Page ID and existing demonstration default. The untouched default is ignored when a URL or batch field is supplied.
pageUrl	string	Conditional	none	Single Page URL alias.
maxItems	integer	No	1000	Hard cap on unique review rows across the run; 1–10,000.
maxPages	integer	No	1	Maximum result pages per supplied Facebook Page; 1–100.
since	ISO date or timestamp	No	none	Excludes records with a parseable earlier source date. Undated records remain included.

Example:

{
  "pageUrls": [
    "https://www.facebook.com/nasa/reviews"
  ],
  "maxItems": 250,
  "maxPages": 5,
  "since": "2026-01-01"
}

The exact key set and value shapes come from the source response and can vary per Page or review. Only the keys the source returns are present. For example:

{
  "type": "review",
  "post_id": "987654321098765",
  "recommend": true,
  "message": "Helpful team and a smooth experience.",
  "author": {
    "id": "1234567890",
    "name": "Example Reviewer",
    "url": "https://www.facebook.com/profile.php?id=1234567890",
    "profile_picture": {"uri": "https://scontent.example/reviewer.jpg"}
  },
  "reactions_count": 4,
  "comments_count": 1,
  "share": 0,
  "photos": [],
  "tags": [],
  "created_time": "2026-09-01T10:30:00Z",
  "url": "https://www.facebook.com/example/posts/987654321098765"
}

Empty, restricted, and partial results

Only successful review records are written to the paid default dataset. RUN_SUMMARY separately reports each requested Page as succeeded, empty, restricted, failed, partial, or cancelled, along with safe functional error codes, pages fetched, deduplication counts, stop reason, and billing reconciliation.

An empty result can mean that the Page has no publicly visible reviews within the selected bounds. A restricted result means the Page or its reviews are not available to the public retrieval path. A partial result can occur when a safety limit is reached, a cursor repeats, or one Page fails after other rows have already been delivered.

Common uses

• compare publicly visible customer feedback across brands or locations;
• export review text and recommendation status for analysis;
• build bounded recurring snapshots with Apify schedules and webhooks;
• refresh dashboards, spreadsheets, and research datasets;
• track stable review IDs between your own scheduled runs.

The Actor creates snapshots. It does not yet maintain a cross-run change ledger or send review-change alerts. Build monitoring by storing prior results and comparing review_id, or wait for a separately reviewed stateful monitoring workflow.

Limits and responsible use

Coverage depends on what Facebook exposes publicly for each Page at collection time. Pages may disable reviews, limit visible history, restrict access, or return incomplete optional fields. Results are not guaranteed to be chronologically sorted. Use maxPages, maxItems, and since to keep history and spend bounded.

Review data can include personal data. Collect and use it only for a lawful purpose, follow applicable privacy and platform rules, and avoid sensitive profiling.

API and automation

Run the Actor from Apify Console, the Apify API, schedules, webhooks, Python or JavaScript clients, or supported integrations. Successful review records are available in the default dataset; run-level reconciliation is available in the RUN_SUMMARY key-value-store record.

Pricing

Billing follows this Actor's existing pay-per-event model: one small Actor-start event per run plus one event for each review row written to the default dataset. Empty, restricted, invalid, unavailable, and summary-only outcomes do not create review-result charges.

Support

For reproducible help, open an issue on the Actor's Issues tab with the public Page URL or ID, input limits, run ID, and expected outcome. Do not post private credentials or personal data.