Download websites that use Facebook Domain Verification

About Facebook Domain Verification

Strictly speaking, this is not software at all. Nothing executes, nothing renders and no visitor is affected in any way. What sits in the page is a short meta tag holding a code issued by Meta Platforms, Inc., placed there so the platform can confirm that whoever added it controls the domain. The detection is a record of an administrative act rather than a technical choice, and that is exactly what makes it interesting to read at scale.

The act in question is a business claiming its own website inside an advertising platform. Verification is a prerequisite for the things a serious advertiser needs, configuring conversion events, deciding which pages and partners may edit link previews, and delegating permissions to an agency without handing over an account. Nobody adds the tag out of curiosity. Somebody added it because there was an advertising operation to run, and because the platform refused to proceed until ownership was proved.

So the signal is unusually clean. Most technology detections tell you how a site is built, which is only loosely connected to whether the company behind it is spending money. A verification tag tells you the organisation has an advertising presence, has connected the site to it, and has at least one person in the business or in an agency who administers that connection. As of October 2026 we record the tag on 1,169,557 sites, and the reasonable inference across that population is commercial activity rather than a hobby project.

For anyone selling into marketing teams, that inference is the whole job. Advertising technology vendors, tracking and analytics providers, consent management platforms, conversion rate consultancies and agencies pitching for accounts all need a way to separate businesses that advertise from businesses that merely exist online. Firmographic data does not carry this, because a company's size says nothing about whether it runs paid social campaigns. A tag placed by hand in a page head does carry it, and the Verification category exists in our dataset largely for that reason. The tag also acts as a durable ownership marker for research into corporate domain portfolios, since related properties often carry codes from the same business account.

The limits are simple and should be taken seriously. The tag proves that verification happened at some point, not that campaigns are running now, because nobody removes it when spending stops. It also lives only in the page head we fetched, so a site that placed the code on its main entry point but not on the pages we sampled, or that verified through a hosting record instead of a page tag, will not appear. Detection here is a floor and a historical marker rather than a live indicator of budget.

The exported list is the only practical way to use any of this. A per-domain lookup answers a question about a company you have already identified, and identification is the expensive part of the work. Running the query in reverse, from the tag to the sites, and then filtering by country, where United States accounts for 579,534 of the total, or by suffix, where .com is the one we record most often, or by the rest of the stack a site runs, produces a segment of advertising businesses that no directory would have assembled for you.