Facebook Page Followers & Following Count Scraper

Facebook Page Followers & Following Count Scraper Overview

The Facebook Page Followers & Following Count Scraper extracts publicly available metadata from Facebook pages and returns structured page information for analysis, research, enrichment, and automation. It is designed for users who need Facebook page follower counts, following counts, page names, usernames, URLs, biographies, and profile image URLs without manually checking each page.

The Facebook Page Followers & Following Count Scraper accepts one or more Facebook page URLs through startUrls or Facebook page usernames through usernames. It automatically converts usernames into Facebook page URLs and processes each target individually.

The Facebook Page Followers & Following Count Scraper focuses on publicly accessible Facebook page information. Because Facebook may present different content depending on page state, region, access conditions, or login requirements, some fields—especially following counts—may be returned as N/A.

Facebook Page Followers & Following Count Scraper Features

The Facebook Page Followers & Following Count Scraper provides a straightforward workflow for collecting page-level metadata from public Facebook pages.

Public Facebook Page Data Extraction

The actor extracts page metadata directly from the publicly accessible HTML response. Depending on what Facebook exposes on the page, the result can include the page name, page username, page URL, bio, profile picture, followers count, and following count.

Multiple Facebook Page Inputs

You can provide multiple URLs in startUrls or multiple usernames in usernames. This makes the Facebook Page Followers & Following Count Scraper suitable for processing groups of Facebook pages rather than checking pages individually.

Username-to-URL Conversion

The actor supports plain usernames such as katyperry or @neymarjr. Each username is normalized and converted into a Facebook URL before scraping.

Residential Proxy Usage

The implementation automatically creates an Apify Residential proxy configuration and requests a fresh proxy URL for processing. When a request encounters a login wall, temporary block, or request error, the actor can retry using a new proxy.

Retry and Error Handling

The Facebook Page Followers & Following Count Scraper attempts failed requests up to three times. It also detects HTTP errors, page-not-found responses, login walls, and temporary Facebook blocking messages before continuing or skipping the affected target.

How to Use the Facebook Page Followers & Following Count Scraper

Using the Facebook Page Followers & Following Count Scraper requires only Facebook page URLs, usernames, or both.

Step 1: Add Facebook Page URLs

Use the startUrls input when you already have complete Facebook page URLs.

For example:

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/LionelRichie"
    },
    {
      "url": "https://www.facebook.com/BillGates"
    }
  ]
}

Step 2: Add Facebook Usernames

You can instead provide usernames through the usernames array:

{
  "usernames": [
    "katyperry",
    "neymarjr"
  ]
}

The Facebook Page Followers & Following Count Scraper removes a leading @ when necessary and constructs the corresponding Facebook page URL automatically.

Step 3: Run the Actor

After submitting your input, the actor fetches each supplied Facebook page using an HTTP session configured with browser-style request headers and an automatically created residential proxy.

Step 4: Review the Dataset

For every successfully processed page, the Facebook Page Followers & Following Count Scraper pushes a structured dataset item containing the extracted page metadata and count values.

Facebook Page Followers & Following Count Scraper Data Extraction

The Facebook Page Followers & Following Count Scraper uses several extraction strategies to improve coverage of publicly exposed metadata.

The page name is first obtained from Facebook's og:title metadata and falls back to the HTML <title> when necessary. The page username is derived from the processed Facebook URL rather than requiring a separate lookup.

The actor also extracts the page description from the standard meta[name="description"] element and falls back to og:description. The profile image is collected from Facebook's og:image metadata.

For page identifiers, the implementation checks Facebook application metadata and selected embedded page information. The current dataset output, however, does not include the extracted page ID as a separate field.

Followers Count Extraction

Followers are first searched through JSON-LD interactionStatistic information using Facebook's exposed FollowAction interaction data. When that approach does not produce a value, the scraper searches visible page text for patterns such as 10K followers, 1.2M followers, or 500 followers.

The Facebook Page Followers & Following Count Scraper normalizes detected count values into a raw numeric representation and a human-readable representation.

For example, 6.3M can be normalized to 6300000, while the formatted output remains 6.3M.

Following Count Extraction

Following information is searched separately in visible page text using patterns such as 500 following. Facebook does not always expose following information publicly, so the resulting value can legitimately be N/A.

Facebook Page Followers & Following Count Scraper Use Cases

The Facebook Page Followers & Following Count Scraper can support several practical workflows involving publicly available Facebook page metadata.

Competitor Analysis

Marketing teams can collect follower and following counts from selected public Facebook pages and use the structured results to compare page audiences and maintain internal research datasets.

Social Media Research

Researchers can collect page names, descriptions, profile image URLs, usernames, and audience-related counts for social media analysis and data exploration.

Lead and Prospect Research

Organizations researching businesses, creators, public brands, or organizations on Facebook can use page-level metadata as part of a broader prospecting or enrichment workflow.

Brand Monitoring

The extracted page metadata can help maintain datasets of selected public Facebook pages and compare collected follower information across repeated actor runs.

Business Intelligence

Structured page-level data can be exported and analyzed with other datasets for reporting, segmentation, benchmarking, or internal analytics.

Content Research

Content and marketing teams can use public Facebook page information to identify relevant pages and organize research around page descriptions, audience counts, and publicly exposed metadata.

Input

The Facebook Page Followers & Following Count Scraper has two optional input fields. Neither field is required by the actor schema, but at least one usable URL or username is needed for the actor to process targets.

Input	Type	Required	Default	Description
startUrls	Array	No	None	One or more Facebook page URL objects.
usernames	Array	No	None	One or more Facebook page usernames or handles. Leading @ characters are accepted and removed.

startUrls

startUrls is an array using Apify's request-list source editor. Each item contains a URL, such as:

{
  "url": "https://www.facebook.com/katyperry"
}

The actor reads the url value, trims unnecessary whitespace, and processes each target individually.

usernames

usernames is a string array for users who prefer to enter page handles rather than complete URLs.

For example:

{
  "usernames": [
    "BillGates",
    "@katyperry"
  ]
}

The implementation strips @ and whitespace before generating the Facebook URL.

Facebook Page Followers & Following Count Scraper Output Data

Each successful result contains the following fields.

Field	Type	Description
page_name	String / null	Facebook page name extracted from og:title or the HTML title.
page_username	String / null	Username derived from the processed Facebook page URL when available.
page_url	String	Facebook page URL that was processed.
bio	String / null	Public page description extracted from metadata.
profile_picture_url	String / null	Profile image URL from Facebook's og:image metadata.
followers_count	String	Normalized numeric follower count, or N/A when unavailable.
following_count	String	Normalized numeric following count, or N/A when unavailable.
followers_count_formatted	String	Human-readable follower count such as 6.3M, 55K, or 500.
following_count_formatted	String	Human-readable following count or N/A.

The Facebook Page Followers & Following Count Scraper returns count values as strings. Numeric counts are normalized into plain digits for easier downstream processing, while the formatted fields preserve a compact human-readable representation.

A value of N/A does not necessarily indicate an error. It can mean that Facebook did not expose the requested information in the publicly retrieved page content.

Example Input

A combined input using both supported input types can look like this:

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/LionelRichie"
    },
    {
      "url": "https://www.facebook.com/BillGates"
    }
  ],
  "usernames": [
    "katyperry",
    "@neymarjr"
  ]
}

The actor combines the supplied usernames with the URL targets and processes all valid entries.

Example Output

A realistic result can look like the following:

{
  "page_name": "Example Facebook Page",
  "page_username": "examplepage",
  "page_url": "https://www.facebook.com/examplepage",
  "bio": "Example page description",
  "profile_picture_url": "https://example.com/profile-picture.jpg",
  "followers_count": "6300000",
  "following_count": "500",
  "followers_count_formatted": "6.3M",
  "following_count_formatted": "500"
}

The exact values depend on what Facebook exposes publicly when the actor processes the page. In particular, follower and following information can vary over time and may be unavailable for some pages.

Data Quality and Reliability

The Facebook Page Followers & Following Count Scraper is built to handle common variations in publicly retrieved Facebook page content.

The scraper uses browser-style HTTP headers and an Apify Residential proxy configuration. Each URL can receive a newly generated proxy URL, and retry attempts can request another proxy when an access problem occurs.

The actor performs up to three request attempts for each target. A response containing Facebook's login wall or temporary-block message is treated as an unsuccessful scrape attempt and can trigger another request through a new proxy.

HTTP 404 responses are logged as page-not-found conditions. Other non-success responses are retried before the target is skipped.

The Facebook Page Followers & Following Count Scraper also uses fallback extraction techniques. For example, follower information can be obtained from structured JSON-LD data or from visible text when structured metadata does not provide the count.

Because the actor works with publicly accessible page content, it cannot guarantee that every Facebook page exposes every field. Facebook page layout, metadata availability, access restrictions, and dynamic content can affect the resulting dataset.

SEO and Search Intent

The Facebook Page Followers & Following Count Scraper is designed for users searching for practical ways to collect Facebook page follower information, following information, page metadata, and public Facebook page data.

Common search intent includes finding a Facebook page scraper, extracting Facebook follower counts, collecting Facebook page data, researching Facebook audiences, and automating public page metadata collection.

The actor is particularly useful when the goal is to turn Facebook page information into structured records that can be analyzed, stored, or used in downstream workflows.

Instead of manually opening every Facebook page and recording its visible information, the Facebook Page Followers & Following Count Scraper provides a repeatable automated extraction workflow through Apify.

Frequently Asked Questions

What is the Facebook Page Followers & Following Count Scraper?

The Facebook Page Followers & Following Count Scraper is an Apify Actor that extracts publicly available Facebook page metadata, including page name, username, URL, bio, profile picture URL, followers count, and following count when those values are publicly exposed.

How does the Facebook Page Followers & Following Count Scraper work?

The actor retrieves each supplied Facebook page using an HTTP session, residential proxy, browser-style headers, retry logic, and HTML parsing. It then extracts the supported metadata and pushes each result to the Apify dataset.

What data can I extract from Facebook pages?

The Facebook Page Followers & Following Count Scraper can return page name, page username, page URL, bio, profile picture URL, follower count, following count, and formatted versions of the two count fields.

Can I scrape multiple Facebook pages?

Yes. Multiple page URLs can be provided through startUrls, and multiple page usernames can be supplied through usernames. Both input types can be processed in the same run.

Can I use Facebook usernames instead of URLs?

Yes. The Facebook Page Followers & Following Count Scraper supports usernames such as katyperry, BillGates, and @neymarjr. The implementation converts these values into Facebook URLs automatically.

Why is following_count sometimes N/A?

Facebook does not always expose following information in publicly retrievable page content. The actor searches for publicly visible following data, but it does not log in or bypass private access restrictions.

Why can followers_count be N/A?

Follower information may not be present in the publicly retrieved HTML, structured metadata, or visible page text. In those cases, the actor returns N/A rather than inventing a value.

Are follower counts returned as numbers?

The raw output fields are strings. A numeric follower count is normalized into digits, while followers_count_formatted provides a human-readable version such as 6.3M.

Does the actor use proxies?

Yes. The implementation automatically creates an Apify Residential proxy configuration and obtains proxy URLs for Facebook page requests.

Does the actor retry failed requests?

Yes. The Facebook Page Followers & Following Count Scraper uses up to three attempts for each target and can generate a new residential proxy URL when a request fails or Facebook's login/block page is detected.

Does the actor access private Facebook pages?

No. The implementation is designed around publicly retrieved Facebook page content. It does not provide authenticated access to private or restricted information.

Why Use the Facebook Page Followers & Following Count Scraper

The Facebook Page Followers & Following Count Scraper reduces repetitive manual work by converting Facebook page metadata into structured dataset records.

It accepts both URLs and usernames, supports multiple targets, automatically handles URL normalization, uses residential proxies, and retries failed requests. These behaviors make the extraction process easier to repeat across collections of public pages.

The structured output also makes the collected information easier to analyze. Raw and formatted follower values can be useful for different downstream workflows: numeric values are convenient for calculations, while formatted values are convenient for reports and human review.

For teams researching public Facebook pages, the Facebook Page Followers & Following Count Scraper provides a focused extraction workflow without requiring users to manually copy page information from individual pages.

API and Automation

The Facebook Page Followers & Following Count Scraper runs as an Apify Actor, so its results are produced in an Apify dataset after successful processing.

This makes the actor suitable for automated workflows where Facebook page URLs or usernames are supplied as input and structured results are consumed after the run. The actor itself does not define additional external API integrations beyond its Apify execution and dataset output behavior.

For recurring research or data collection workflows, users can run the actor repeatedly and compare the resulting datasets over time, subject to the availability of public Facebook page information.

Support

For issues with the Facebook Page Followers & Following Count Scraper, review the Actor run logs and dataset output first. When reporting a problem through the relevant Apify Actor or support channel, include the affected input format, target URL or username, run details, and the observed output or error message.

Providing reproducible information helps identify whether the issue is related to page availability, Facebook response content, temporary access conditions, or extraction behavior.