Facebook Page Posts Monitor - Public Page Posts & Engagement

Check a list of public Facebook Pages in one run and export the post links, text snippets, images, external links and engagement counts that Facebook exposes on each Page. If Facebook shows no posts to a logged-out visitor, you still get a Page metadata row (name, ID, description, image) instead of an empty result. Optional: add your own Cookie header for better coverage.

What can Facebook Page Posts Monitor do?

• Check many public Pages per run from Page URLs or handles (paste one per line).
• Extract visible posts: post URL and ID, publish time, text snippet, image and video URLs, outbound links.
• Collect engagement signals where Facebook includes them: reactions, comments and shares counts.
• Fall back to Page metadata (name, Page ID, description, cover image) when posts are not exposed, so every Page returns something you can track.
• Report diagnostics: for each Page the run records the HTTP status, whether Facebook returned a login or checkpoint page, and how many posts were found.
• Use your own session (optional): paste a Cookie header from an account you are allowed to use, and route requests through Apify Proxy.

Good for lightweight brand and competitor Page checks, social listening exports, and quick audits of which Pages are active.

What data can I extract?

Field	Description
pageUrl, pageName, pageId	The Page you supplied, its name and numeric ID when available
postId, postUrl	Post identifier and permalink
text	Text snippet around the post, or the Page description for metadata rows
publishedAt	Post time (ISO 8601) when Facebook exposes it
imageUrl, videoUrl	Media URLs near the post
externalLinks	Non-Facebook links found in the post area (up to 20)
reactionsCount, commentsCount, sharesCount	Engagement counts when exposed, otherwise null
extractionMethod	embedded_json for post rows, meta_fallback for Page metadata rows
fetchedAt	Collection time

Output example

{
  "pageUrl": "https://www.facebook.com/examplebrand",
  "pageName": "Example Brand",
  "pageId": "100064000000000",
  "postId": "pfbid0ExamplePostId",
  "postUrl": "https://www.facebook.com/examplebrand/posts/pfbid0ExamplePostId",
  "text": "Our autumn collection is live. Free shipping this week only...",
  "publishedAt": "2026-10-23T14:05:00.000Z",
  "imageUrl": "https://scontent.example.fbcdn.net/v/t39.30808-6/example.jpg",
  "videoUrl": null,
  "externalLinks": ["https://shop.example.com/autumn"],
  "reactionsCount": 312,
  "commentsCount": 41,
  "sharesCount": 18,
  "extractionMethod": "embedded_json",
  "fetchedAt": "2026-10-25T00:56:44.210Z"
}

How much does it cost?

• $3.00 per 1,000 rows ($0.003 per post or Page metadata row)
• $0.00005 per Actor start (per GB of memory)

Checking 20 Pages with up to 25 rows each costs at most about $1.50. Check the Pricing tab for current rates.

How to use it

1. Paste Facebook Page URLs or handles into Page URLs (or one per line in the text box).
2. Set maxPostsPerPage (default 25).
3. Optional: add Apify Proxy, and a Cookie header from your own account for Pages that require login.
4. Click Start and export the dataset as CSV, Excel or JSON. Review SUMMARY for per-Page diagnostics.
5. To monitor over time, save the input as a task and schedule it. Compare postId values between runs to spot new posts.

Input example

{
  "pageUrls": ["https://www.facebook.com/nasa", "https://www.facebook.com/natgeo"],
  "maxPostsPerPage": 25,
  "dedupe": true,
  "requestDelayMs": 1000,
  "maxConcurrency": 2,
  "proxyConfiguration": { "useApifyProxy": true }
}

Input reference

Field	Default	Notes
pageUrls / pageUrlsText	-	Page URLs or handles
maxPostsPerPage	25	Visible post rows kept per Page
cookie	-	Optional Cookie header from your own Facebook account
dedupe	true	Remove duplicate post URLs across Pages
requestDelayMs / maxConcurrency	1000 / 2	Keep modest for Facebook
proxyConfiguration	none	Apify Proxy recommended

Limits

• Facebook decides how much a logged-out visitor can see. Many Pages expose only metadata, so expect meta_fallback rows for some Pages.
• The Actor reads one Page view per Page. It does not scroll the full Page history, and it does not scrape comments, groups, private profiles or Marketplace.
• text is a snippet extracted from the Page HTML near the post link, not a guaranteed full post body.
• New-post detection between runs is not automatic: compare postId values across runs, or use the dataset in your own workflow.

Use with AI agents (MCP)

Connect the Apify MCP server at https://mcp.apify.com?tools=groupoject/facebook-page-posts-monitor in Claude Desktop, Cursor, VS Code or any MCP client, and your AI assistant can call this actor as a tool. Example prompt: "Get the latest public posts from these three Facebook pages and summarize which ones got the most engagement."

FAQ

Does it require a Facebook login? No. A Cookie header is optional and only improves coverage for Pages that hide posts from logged-out visitors.

Why are engagement counts null? Facebook did not include them in the HTML it served for that Page view.

Can it scrape Facebook groups or personal profiles? No. It is designed for public Pages.

Is it legal? It reads publicly available Page content. If you supply a cookie, use only an account and data you are authorized to access, and follow Facebook's terms and privacy law.

Related Actors

• Meta Ads Library Scraper (No Login) - ads a Facebook Page is running
• Meta Ads Library Monitor - get alerts when competitors launch new ads
• X (Twitter) Account Monitor - new posts and profile changes on X