Facebook Page URL Resolver

Your export has the same page under several different URLs.

/profile.php links, vanity names, numeric IDs, mobile and basic hosts, tracking parameters stapled on by whatever shared the link — all pointing at one page, none of them matching as strings. This canonicalizes them and tells you which ones are the same page.

When two identities cannot be matched with certainty, it says so and shows you the evidence, instead of merging them and quietly corrupting your dataset. An auto-merged rebrand can poison a trend line for months, and the damage is worse than missing data because it still looks like data.

Free, with no allowance to run out.

The problem it solves

The same Facebook page arrives from scrapers under many names: m.facebook.com/SomePage, www.facebook.com/somepage/, facebook.com/profile.php?id=1000…, facebook.com/p/Some-Page-1000…. The same post arrives with and without tracking parameters. Count anything before resolving identity and your numbers are wrong.

What it does

• Canonical page identity — unifies m./www./web. hosts, profile.php?id=, /p/Name-ID/, legacy /pages/Name/ID, and slug case into one stable id (fb:slug or fb:numeric-id; groups as fbgroup:…).
• Post URL deduplication — strips tracking parameters (keeps story_fbid/id), unifies hosts, and counts each post once.
• Format detection — recognizes the official apify/facebook-posts-scraper export (verified field mapping) and falls back to a generic mapper for other exports. The output always states which mapping was used.

What it deliberately does NOT do

• It never guesses. A URL that doesn't carry page identity (a /watch link, a bare post URL, a non-Facebook domain) is reported as unresolved with its evidence — not silently merged, not silently dropped.
• It does not call Facebook, does not scrape, does not enrich. It reads only the dataset you point it at, in your own account.
• Absent fields stay absent. Nothing is filled with zeros.

Input

Any one of: a dataset ID from your account · raw JSON items pasted directly · a plain list of page URLs. Run with no input at all and it processes a small built-in synthetic sample so you can see the output shape.

Output (dataset items)

1. One summary item — rows in, format detected, unique posts, duplicates removed, pages resolved, unresolved count.
2. One page item per canonical identity — id, name, every URL variant observed, post count.
3. unresolved items — each with the reason and the evidence.
4. Optionally one post item per unique post (canonical URL + text head).

See what it returns

Real output of the built-in demo run — including the duplicate it caught and the same-name pair it refused to merge:

Open the full sample output →

(run it yourself with empty input — free, 3 seconds)

📖 Background: The Facebook URL Zoo — every page-link format and how to canonicalize them — the reference article behind this tool’s rules.

Price

Free — no developer fee. You pay only your own Apify compute. If it saves you a bad number, look at our other tools.

Permissions, stated plainly

This Actor requests full permissions for one reason: to read the dataset ID you point it at. It writes only to its own run storage. It never modifies, deletes, or reads anything else in your account.

Mentat Logic — analysis tools that state their coverage, show their working, and render the unknown as unknown.