Facebook Get Comments: Best Ways to Collect Post Data

Searching for “Facebook get comments” usually means the user wants more than the visible comment count. The goal is often to collect comment text, replies, dates, reactions, author fields, and source information from one or more Facebook posts and turn that discussion into structured data.

There are several ways to do this. Meta provides official permission-based APIs for supported use cases, while public-data tools can process selected post URLs and return spreadsheet- or API-ready records. The right method depends on whether the team manages the Page, needs public research data, or wants recurring automated collection.

What Facebook Comment and Post Data Can You Collect?

A useful comment dataset normally preserves both the discussion and its connection to the original post.

The CoreClaw Facebook Comments Scraper currently returns structured fields including comment content, commenter information, timestamps, likes and reactions, IDs, reply counts, links, and nested replies for supported public post URLs.

Four Ways to Get Facebook Comments

Use Meta’s API for Authorized Page Workflows

Meta’s official Graph API is the logical starting point when an organization manages the relevant Facebook Page and has the required permissions.

Meta’s current Page Post Comments documentation notes that access to certain comment fields requires the ability to perform the MODERATE task on the Page being queried. This makes the official API suitable for authorized Page workflows, but it should not be treated as unrestricted access to comments from every public Facebook post.

Meta also provides comment access through its Content Library API for eligible research workflows, under a separate access model.

Use a Ready-Made Public Post Scraper

When the starting point is a list of public post URLs, a ready-made scraper is often simpler.

With CoreClaw’s Facebook Comments Scraper, users can enter one or more post URLs, control the amount of comment data collected, retrieve nested replies, and export the results without writing scraping code. CoreClaw handles task execution, proxy rotation, normalization, and structured delivery.

Apify follows a similar URL-based model and supports comment text, timestamps, likes, replies, sorting, date filters, CSV, Excel, JSON, and API integrations.

Use a Comment Exporter for Small Projects

A dedicated exporter can make sense when the only requirement is to move one or two discussions into a spreadsheet.

Current tools such as CommentGrid use a simple workflow: copy a supported Facebook post URL, extract the comments, then download structured data. This is convenient for occasional analysis but offers less flexibility than a recurring Worker or API workflow.

Use an API for Recurring Collection

Repeated monitoring is better handled programmatically.

The CoreClaw API supports server-side Worker tasks and scheduled configurations, allowing teams to reuse input settings and integrate collection into internal systems.

Developer-focused alternatives also exist. ScrapeCreators, for example, exposes a Facebook post-comments endpoint that accepts a post or Reel URL and uses cursors for pagination.

Which Method Should You Choose?

The important distinction is between authorized account operations and public-data research. They solve different problems and should not be presented as interchangeable approaches.

How to Collect Facebook Comments with CoreClaw

Start with the URLs of the public posts relevant to the project. If the research also requires Page, post, event, or other Facebook data, browse the CoreClaw Facebook Scraper collection and select the Worker that matches the source type. CoreClaw currently provides ready-made Facebook workflows across posts, comments, profiles, events, ads, and other supported data categories.

For comments, open the Facebook Comments Scraper, add a small batch of post URLs, and set an appropriate result limit. Run the test and compare several exported records with the original posts.

Next, remove irrelevant records and check reply relationships, timestamps, IDs, and source URLs. Download the resulting data as CSV or JSON, or use the CoreClaw API when the same collection needs to run repeatedly.

How to Turn Comments Into Usable Post Data

A large comment export is not automatically useful.

First, remove duplicate records using comment IDs. Keep parent-comment relationships so replies stay connected to the correct discussion. Standardize dates and engagement fields, and retain the original post and comment URLs.

For customer research, teams can then add categories such as sentiment, question, complaint, feature request, product mention, or manual-review status.

Automated classification should still be checked on a sample. Sarcasm, slang, emojis, multilingual conversations, and missing context can make comment interpretation unreliable.

CoreClaw’s broader platform is designed around structured outputs rather than raw webpage content, helping teams move collected results into databases, analytics systems, or internal workflows with less manual cleanup.

Data Collection Limits and Best Practices

Collect only the fields required for a legitimate project and avoid private messages, friends-only content, access-controlled information, or unnecessary personal data.

Keep source URLs and collection timestamps so records can be verified later. Facebook discussions can change as users edit or remove comments, Pages change visibility, or content becomes unavailable.

For important research or commercial decisions, manually check a sample of the final dataset. Structured scraping reduces repetitive collection work, but it should not be treated as a guarantee that every displayed comment will always be available.

Conclusion

The best way to “get Facebook comments” depends on the source and workflow. Meta’s API is appropriate for supported, authorized Page operations. Simple exporters work for occasional spreadsheet tasks, while public-post scrapers and APIs are more practical for structured research and recurring collection.

With CoreClaw, teams can run ready-made Facebook Workers without coding, obtain cleaned and filtered structured results, and connect repeated collection through an API. CoreClaw uses pay-only-for-successful-results pricing, and its Facebook Comments Worker states that failed results do not count as successful results.

For workflows not covered by an existing Worker, teams can discuss a custom solution. Developers can also publish their own Workers to the CoreClaw Store.

For readers comparing vendors rather than methods, see 5 Best Facebook Comments Scraper Tools.