Meta Domain Verification: DNS, Meta Tag, or HTML File Steps

How do you complete Meta domain verification?

Meta domain verification is the step where you prove in Meta Business settings that you own a domain. Also, you have three methods: add a DNS TXT record, place a meta tag in your home page head, or upload an HTML file to your root directory. Meta gives you the value.

The sequence below works for most businesses. So one note first: menu names change over time. Read screen names as directions, not as exact button labels. Check the current wording in the Meta Business Help Center.

1. Open your business settings and find the domains section.
2. Add a new domain and type it in root form, without www.
3. Pick one of the three methods and copy the value Meta gives you.
4. Add that value to your DNS panel, your home page, or your root directory.
5. Return to Meta, start the verification, and wait for the result.

Why does Meta domain verification matter?

Verification tells Meta that this domain really belongs to your business. Meta may tie more settings to verification over time. For that reason we only list the benefits we can confirm and leave the rest to the official help pages.

• Verification makes clear which business owns the domain.
• Your business can gain authority over links and shares tied to that domain.
• The setup clarifies which business manages measurement and event settings for the domain.
• Another business finds it harder to claim your domain.

On its own, verification will not improve ad performance. However, it is the foundation of a tidy account structure. On the measurement side, think of it together with our Meta Pixel setup guide and our event match quality guide, because these three pieces complete each other.

Here is an example. In practice, your agency and your in-house team may both run ads for the same domain. Without verification, it can get confusing who manages which setting. Also, with verification, the domain sits clearly under one business. As a result, you cut off authority disputes early and keep the workflow simple.

What should you prepare before you start?

Missing preparation stalls the process. The most common problem is the wrong person working in the wrong panel. Therefore, settle these three things before you begin.

• An account with admin access in your business settings.
• Access to the DNS panel or the site admin panel of the domain.
• The exact domain you want to connect, written in root form like example.com.

If an agency, a developer, or a hosting provider manages your domain, ask them only to add the right record. So you do not need to share your account password. Using someone else’s account is a security risk and it breaks platform rules.

Also settle who holds admin rights. In practice, sometimes a former employee opened the business account and now nobody can reach it. In that case you cannot reach the verification screen. Also, prefer accounts tied to a company email address, since personal accounts create gaps when people leave.

What is the difference between a root domain and a subdomain?

A root domain is the main address, such as example.com. A subdomain is a section under it, such as shop.example.com or blog.example.com. Meta’s help page tells you to enter the domain without www, in root form. So start your verification from the root domain.

Check Meta’s current help page to see how it treats subdomains, because scope rules can change. In practice we suggest this: verify the root domain first, then test the subdomains separately in the campaigns you run on them.

How do you reach the domain verification screen?

Meta’s official page describes the path as the domains section under the brand safety heading in your business settings. So you add a new domain there. Menu names can change, so your screen may not show the exact same words.

If you cannot find it, use the search box or open the help page. Also keep in mind that the section may not show up if you have no admin role in the business portfolio. In that case, talk to the person who can grant the role first.

Taking a screenshot also helps. In practice, when you talk to support or your agency, showing the screen beats a long description. It also documents the step where you got stuck.

How do you do Meta domain verification with a DNS TXT record?

A DNS TXT record is a short text entry in your domain’s DNS settings. Meta gives you a value. You add that value in the records section of your DNS panel, usually at the company where you bought the domain. Also, because it never touches your site content, it is one of the cleanest methods.

1. Choose the DNS TXT option on the Meta screen and copy the value.
2. Log in to the DNS panel of your domain.
3. Create a new TXT record.
4. Paste only the value Meta gave you, with no extra spaces at the start or end.
5. Save the record and wait a little.
6. Return to Meta and start the verification.

You can check whether the record is live with our DNS lookup tool. So that way you confirm the record is visible before you ask Meta to check. The value we use in examples is not real; your screen shows the value Meta provides.

Be careful about what you type in the name field. In practice, some DNS panels fill in the domain automatically. If you add a wrong prefix where you should leave the name empty or use the root symbol, the record lands on a different subdomain. The panel’s own help page guides you here.

How do you do Meta domain verification with a meta tag?

With this method Meta gives you a short tag. Also, you place it in the head section of your home page. For security reasons we do not show the tag code here; you will find it ready to copy on the Meta screen. So what matters is that the tag sits in the head of the home page and is publicly visible.

1. Pick the meta tag option on the Meta screen and copy the tag.
2. Open the part of your site admin that edits the head area of the home page.
3. Paste the tag into that area.
4. Publish the change and clear your cache.
5. Press the verify button on the Meta screen.

The cache is the step people forget most. In practice, if your site cache is on, Meta may still see the old page. So after publishing, open the home page source in a private window and confirm the tag is really there.

Look at the page, not just the tag. Also, if the tag landed on an inner page, Meta will not see it. Likewise, if a redirect rule moves your home page to another address, the tag has to sit on the page that loads after the redirect. So skipping this detail is one of the most common mistakes.

How do you do Meta domain verification with an HTML file?

The third method has Meta give you a verification file. In practice, you download it and upload it to the root directory of your domain. In other words, the file must open right under example.com. Also, if you upload it to a subfolder, Meta cannot find it.

1. Pick the HTML file option on the Meta screen and download the file.
2. Do not change the file name or its content.
3. Upload it to the root directory with your hosting file manager or FTP.
4. Open the file address in a browser to check it loads.
5. Start the verification on the Meta screen.

On some site setups you cannot upload to the root directory. So hosted store platforms, for example, do not give you server file access. In that case, switch to the DNS or meta tag method.

Never rename the file. Meta looks for the exact name it gave you. When you open the file in a browser, check that the content shows as plain text. In practice, if your server redirects the file or shows a custom page, Meta cannot read it. So always test it yourself after uploading.

Which verification method should you choose?

The right method depends on who has which access. Also, if you can reach the DNS panel, a TXT record is usually the most durable option. If you can reach the site admin but not DNS, the meta tag is practical. So if you have server file access, the file upload works too.

If you cannot decide, try DNS. A theme, a plugin, or a site redesign does not touch the DNS record. However, if you cannot reach whoever manages DNS, the other two methods will be faster.

You do not need to set up several methods at once. In practice, when one works, adding the others only creates clutter. Still, noting a backup method in your team notes makes sense before a big project. Also, for example, if you lose DNS access, you will know which page can carry the tag.

What is the general path on WordPress and Shopify type platforms?

Platform menus change often, so we do not give exact click paths. The logic stays the same, though. On hosted platforms you cannot reach server files. So for that reason you mostly choose a DNS record or add a tag to the head area.

• On WordPress style systems, look for a plugin or theme setting that adds code to the head area.
• On hosted store platforms, DNS settings live at the company where you bought the domain, while connection settings live in the platform panel.
• Page builder tools usually have a custom head field in the site settings.
• Whatever platform you use, follow the platform’s own help center for the exact steps.

When we build a site from scratch, we add this record on day one. In our web design service, we check measurement and verification steps with you before launch.

What if Meta domain verification says it could not verify?

A failed check usually has a simple cause. Meta may not show the exact same message on every screen, so if you see a similar warning, work through the list below. Check each step and then move to the next.

1. Confirm you typed the domain correctly: root form or with www?
2. Confirm you copied the full value. A stray space at the start or end is common.
3. With DNS, test that the record shows up with a lookup tool.
4. For the meta tag, search the page source in a private window.
5. With the file method, open the file address and confirm the content appears.
6. Check that caching and security plugins do not block Meta’s access.
7. If it still fails, wait a while and try again.

A firewall or bot protection can also cause trouble. The verification request comes from Meta’s servers, so a bot filter may block it. When you hit an error, check access to the site and not only the record.

Many error messages trace back to one root cause. So do not change everything at once. Make one change, test it, and note the result. In practice, that way you see what worked, and going back is easy.

Which symptom points to which cause?

A message alone rarely tells enough. So here is a short table from symptom to cause. It is a starting point based on field experience, not a guarantee.

How long does a DNS change take to propagate?

DNS propagation is the time a change takes to reach servers across the internet. Also, it differs for every domain, and we cannot promise a specific time. Sometimes a few minutes are enough; sometimes it takes longer. So do not panic if it fails right after you add the record.

The best thing you can do is wait and check the record with a lookup tool. So if the record shows up, try Meta again. If it does not, you may have added it to the wrong domain or chosen the wrong record type. In practice, picking another type instead of TXT is a common slip.

Lookup results can differ between servers. Also, some show the record while others do not yet. That is a normal propagation sign. Still, if you wait a long time and the record never appears, recheck the entry in your DNS panel from scratch.

What if another business already verified your domain?

A domain can show as tied to only one business at a time. So users describe this case often in the Meta developer community. First check your own accounts, because you may have connected the domain to another portfolio you own.

• Your former agency or developer may have connected the domain to their own business account.
• You may have opened a separate portfolio and forgotten about it.
• A former employee may have used their own business account.

The solution follows the rules: ask the current owner to remove the domain, or use the access request path and the support channel Meta offers. In practice, forging documents, entering someone else’s account without permission, or opening a new account to get around the system breaks the rules and makes things worse. We cannot promise any result.

Do not trust strangers who offer to “recover” the domain for money either. The only authorized channel is Meta’s own support path. Keep your emails and notes throughout the process.

Is it a problem to remove the tag or record after verification?

The safe path is to leave the verification record in place. Meta may recheck the status from time to time, and if the record disappears, verification can drop. So when you rebuild your site or change themes, remember to carry the verification value over.

The risk is highest with the meta tag method. A theme update can reset the head area. With DNS the risk is lower, but a domain renewal or a DNS move can delete the record. Also, therefore, export your current records before any migration.

Site migration projects raise the risk further. So when you move to a new server, old files, head settings, and DNS records move separately. Add domain verification to your post-migration checklist. Also document the verification status with a screenshot before and after the move.

What security rules apply during verification?

The verification value is specific to you and works only for your domain. Still, a few security rules surround the process. They protect both your account and your domain.

• Give the admin role only to people you trust.
• Turn on two-step login for your DNS panel.
• Check the sender before you click links in emails that claim to come from Meta.
• Do not share the verification value in public places.
• If you work with an agency, give them a role on your account instead of your password.

Security is not only about outside threats. A wrong person acting with the wrong permission is also a risk. So review roles regularly and remove access for people who no longer work with you. In practice, each person should hold a role on their own account instead of sharing credentials.

How does verification relate to Meta Pixel and event match quality?

Verification does not replace measurement setup. Also, installing the pixel, defining events, and improving match quality are separate jobs. We already cover them: the Meta Pixel setup guide explains installation, and the event match quality guide covers data quality.

Verification is the ownership link in that chain. In other words, Meta ties the domain to you first, and then measurement and campaign settings work on top of that base. For tag management, our Google Tag Manager guide may also help.

Which checks should you run after verification?

The job is not over when verification completes. A few minutes of checking prevents later problems. Go through the list below with your team.

• Confirm the verification status of your domain on the screen.
• Check that your ad account and Page connect to the right business.
• Make sure your campaign links use consistent tags, for example through the UTM builder.
• Write the method and value in your shared team notes.
• If you plan a site rebuild, add moving the verification to the task list.

While you measure efficiency, tools like the ROAS calculator help too. So that way you track the effect of your measurement setup on results with clear numbers. If you get stuck on the ad side, our guide to Meta ads stuck in review can guide you.

Repeat this checklist a few times a year. Also run it once before an important campaign starts. A permission or verification issue that appears mid-campaign costs both time and budget. In practice, preparing ahead is always cheaper.

Which mistakes come up most often?

Most of the errors we see come from small details. The list below is a summary based on field experience; the order is not a guarantee.

• Entering the domain with www or with a protocol prefix.
• Leaving a space when copying the verification value.
• Placing the meta tag on an inner page instead of the home page.
• Uploading the HTML file to a subfolder.
• Skipping the cache clear after a change.
• Changing the theme after verification and losing the record.
• Retrying again and again without giving Meta enough time.

None of these is a big problem alone. However, when several combine, you can lose hours. So make one change at a time and test each one.

What does an example scenario look like for a small store?

This is an example scenario, not a real client case. A store owner wants to connect example.com to a Meta business account. Because the site runs on a hosted store platform, the owner has no server file access. So the owner picks the DNS method.

The owner logs in to the company where the owner bought the domain and adds Meta’s value as a TXT record. Then the owner checks the record with a lookup tool and starts the verification on the Meta screen. If the first try fails, the owner waits a while and retries. Also, this way, even a later theme change does not remove the record.

When should you get expert help?

In the cases below, getting help costs less than struggling alone for a long time. The process gets messy if the domain sits in a former agency’s account, if nobody knows who manages DNS, or if bot protection blocks the check.

At Talha Aslan and team, we handle this kind of setup together with the ad account structure. So within our Meta ads management service, we can review the domain, Page, pixel, and account structure as a whole. We never guarantee an outcome; we only move forward in ways that follow the rules.

For the current official steps, the domain verification help page is the most reliable source. In practice, when menu or option names change, check there first.