Pakistan
USA
Canada
UK
Dubai
Australia
Germany
- Domains sit under Brand safety and suitability in Business Settings.
- DNS TXT is the most durable method; meta tag is the quickest.
- Verify the root domain, not www or a subfolder.
- Keep the record or tag in place after verification.
Why does domain verification matter?
Verification links your website to your business portfolio in Meta. Once verified, your business controls who can edit link previews for that domain, so others cannot change the headline or image when sharing your links in ads. It also gives you a clear ownership record if you work with agencies or need to grant another business access.
In the past, verification was required before configuring web events under Aggregated Event Measurement. Meta has since removed that configuration step for accounts with the newer set-up, so verification is no longer needed for most event purposes. It is still good practice and some features and permissions continue to rely on it, so treat it as a standard part of setting up any account.
How do I verify with a DNS TXT record?
This method survives website rebuilds and theme changes, so we prefer it.
- Open Business SettingsIn Meta Business Suite, go to Settings, then Brand safety and suitability, then Domains.
- Add the domainClick Add and enter the root domain, for example example.com, without https or www.
- Copy the TXT recordChoose DNS verification and copy the TXT value Meta shows.
- Add it at your DNS hostLog in to the provider that manages your DNS, which may be your registrar, hosting company or Cloudflare, and add a TXT record on the root.
- Return and verifyDNS changes can take from minutes to a day or more to propagate. Click Verify in Meta once the record is live.
What about the meta tag and HTML file methods?
The meta tag method asks you to paste a short line of code into the head section of your home page. On WordPress, a header plugin or your SEO plugin's verification field usually handles this. It is quick, but a theme change or plugin update can remove the tag, and Meta may then show the domain as unverified.
The HTML file method asks you to upload a small file Meta provides to the root folder of your site, so it loads at your domain followed by the file name. This suits sites where you have file access but not DNS access. The same risk applies: if a developer rebuilds the site and deletes the file, verification can lapse.
How do I verify with Cloudflare or cPanel?
If your domain uses Cloudflare, the DNS record must be added in Cloudflare, not at the registrar, because Cloudflare is answering DNS queries. Go to the DNS section, add a record of type TXT, put @ as the name for the root, and paste Meta's value as the content. Save and wait a few minutes before verifying.
In cPanel, open the Zone Editor, choose your domain, and add a TXT record with the root name and Meta's value. Some hosts use their own DNS panel instead of cPanel, but the fields are the same. If you are not sure who manages DNS, look up the domain's nameservers, which tell you where records must go.
Why does verification fail?
These are the usual causes when Meta cannot confirm the domain.
Record at the wrong provider
The TXT record was added at the registrar while DNS is managed elsewhere, such as Cloudflare.
Wrong domain entered
A subdomain or www version was added instead of the root domain.
Not propagated yet
DNS changes can take time. Wait and try again before changing anything.
Tag removed or cached
A caching plugin served an old version of the home page without the meta tag. Clear the cache.
Already claimed
Another business portfolio verified the domain first. The owner must remove it or you must contact Meta support.
What is the next step after verification?
Once the domain is verified, check your events. Make sure the Meta pixel is installed, the right standard events fire on the right pages, and the Conversions API sends server events with deduplication. Our guide on setting up the Meta pixel correctly walks through that, and our page on why Meta and GA4 numbers differ explains what to expect in reporting.
Also assign the domain to the right people and partners. If an agency manages your ads, share access through Business Settings rather than giving out personal logins, and keep ownership with your own business portfolio. That way, changing agency later does not mean losing control of your domain, pixel or ad history.
How we handle this for clients
We confirm who manages DNS, verify the domain in the client's own business portfolio, and record which method was used and where. We prefer DNS verification so the status survives website changes, theme updates and hosting moves. If another portfolio has already claimed the domain, we help the client recover it first.
We then move straight to event set-up, testing the pixel and Conversions API together and checking deduplication in Events Manager. This work is part of our Meta Pixel and Conversions API setup service within our wider Meta Ads management work, and access always stays with the business that owns the site.
Pakistan, Gulf and UK advertisers
Many Pakistani businesses buy domains through local resellers or a developer's account, and nobody remembers the login. Before verifying, find out who controls the DNS for your .pk or .com domain and move it into your own account if possible. Domain ownership problems are much harder to fix later, when ads depend on them.
In the UAE and Saudi Arabia, businesses often run separate domains or subfolders for Arabic and English sites. Verify each root domain you use for ads. UK businesses with several brand sites should verify each one in the business portfolio that owns it, so agencies and partners get access only through shared permissions.
Junaid has more than 18 years in SEO, paid media, web development and custom software. He founded SEOnumber1, builds WordPress plugins, CRMs and web applications, has served 500+ clients in 48 countries, and holds Google Ads, Analytics and Google Blue and Green Belt certifications. He is a National Level Award Winner in Digital Marketing. Read his story or ask a question about this article.