Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To verify a domain for Facebook in manual mode, add the verification code Meta gives you to the site’s Integrations > Custom code settings, save and update the website, then complete verification in Facebook. A DNS TXT record is an alternative if that is the method Meta presents to you.

Verify your domain with Meta’s custom-code method

  1. Open the website’s Integrations settings.

  2. Find Custom code and paste the verification code supplied in your Meta/Facebook flow. Use the supplied code as-is; do not create or reuse a token. You can place multiple codes one below another, but do not insert one code in the middle of another.

  3. Save the setting, then update the website so the code is live. If you have just connected the domain, publish the site as well; publishing makes site changes live.

    What’s actually slowing this PC down?

    Pick the symptom - the matching free tool is one click away.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  4. Return to Facebook/Meta and complete its verification step. Your domain is verified for Facebook once you complete verification on Facebook’s end. The Meta interface and timing can vary; there is no universal processing time.

Choose between custom code and DNS TXT verification

Method Where you make the change What to enter Configuration affected
Custom code Website: Integrations > Custom code The code supplied by Meta The website’s custom-code setting
DNS TXT The DNS zone managed by the domain’s authoritative DNS provider The exact TXT value supplied by Meta The domain’s DNS records

Both are verification options, and neither is universally better. Use the method shown in your Meta flow. Support materials do not provide a reusable verification token, so do not substitute a value from a domain-connection setup.

When DNS is managed outside your website provider

Add the Meta TXT record with the provider currently managing the domain’s DNS zone. A TXT record used to verify ownership is distinct from records used to point a website to a hosting service. Keep both purposes clear, and preserve existing records needed for email or other services.

Check domain connection and DNS changes if verification fails

  • For custom code: confirm that you saved the setting and updated/published the intended site. Make sure the domain resolves to that live site before retrying verification.

    Free tools Windows power users keep installed

    One-click scans. No signup required.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • For DNS TXT: confirm the record is in the authoritative DNS zone and that its value exactly matches what Meta supplied. If DNS is hosted elsewhere, changing a record in a different provider’s dashboard will not update the active zone.

  • Allow for DNS propagation: domain connection changes can take up to 24 hours to propagate. That is operational guidance, not a guarantee that Meta will approve verification after a fixed wait.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Know the current manual-mode domain-pointing options

Current manual-mode guidance lists nameservers and CNAME as supported ways to point a domain to a website builder; it says A records are not supported. These are domain-connection settings, not Meta verification tokens. For the documented root CNAME route, remove existing root A and AAAA records first. Review the manual-mode domain-pointing instructions before changing DNS.

Nameservers versus CNAME

If your domain currently uses A records

The A-record connection method stopped being supported on May 20, 2026 for affected domains registered elsewhere, not using the website provider’s nameservers, and connected through an A record. The deprecation guidance warns that switching nameservers can remove custom DNS entries and affect third-party email records. Check the scope of that change and preserve the records your services require before migrating.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.