Fix Webflow “Unable to Verify Domain”
Webflow cannot verify a domain when its current public ownership and routing evidence does not match the site’s Publishing instructions, even if the DNS provider screen appears correct.
Open Site settings → Publishing → Production and copy the exact A, CNAME, and one-time verification TXT records shown for the site. Webflow’s current common setup uses an apex A record at 198.202.211.1, a www CNAME to cdn.webflow.com, and a `_webflow` TXT value beginning with one-time-verification=. Migration values can differ, so the site panel wins. Remove conflicting old-host records, confirm the authoritative DNS, click Check status, and publish after verification.
This guide distinguishes Webflow ownership verification from traffic routing and publishing. It covers the site-specific one-time TXT token, current apex and www records, authoritative nameservers, old Cloudflare-infrastructure ownership, propagation, Site plan and publish state, default-domain redirects, and post-launch canonical checks.
Quick Questions
The token may be copied incorrectly, published under the wrong host, entered in a non-authoritative zone, cached, or replaced after the domain was removed and re-added.
Use the exact records in the site’s Production publishing panel because Webflow migrations can assign values that differ from a general example.
No. Verification proves domain control. The site must also have the required plan and be published to the custom domain.
Webflow verification failure decision tree
| Check | If it fails |
|---|---|
| Current TXT appears at the exact requested host | Correct host syntax or authoritative DNS |
| Apex and www match Site settings | Remove old website routes |
| Domain is detached from the former platform | Remove the old platform connection |
| Webflow says verified | Check Site plan and publish selection |
| Site is live without redirect loops | Correct default host and DNS together |
See which AI crawlers actually reach your website.
Track visits from GPTBot, ClaudeBot, PerplexityBot, search bots, and other discovery agents-then see which public pages attract their attention.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
Main Explanation
Start in the specific Webflow site’s Production publishing panel. Do not use a token from another site or from a previous connection attempt. Webflow can issue a one-time verification value, so removing and re-adding a domain can make an older copied token obsolete. Copy the current hostname, record type, and complete value without quotes or hidden spaces.
Separate ownership from routing. The verification TXT proves control, while A and CNAME records direct visitor traffic. Webflow’s current manual guide commonly lists 198.202.211.1 at the apex, cdn.webflow.com for www, and a `_webflow` TXT containing one-time-verification=. Webflow is migrating hosting infrastructure, so the exact values in Site settings override these public examples.
Verify the record name syntax at the DNS host. Some providers automatically append the domain, so entering `_webflow.example.com` can accidentally create `_webflow.example.com.example.com`. Others want only `_webflow`. Subdomain verification can require a different label. Use the provider’s public lookup or Webflow Check status to confirm the value appears at the exact requested hostname.
Confirm which DNS zone is authoritative. A registrar can display editable records even when nameservers delegate elsewhere. Query NS and make changes at the active DNS host. If authoritative lookup does not show the new TXT, waiting on a public recursive resolver is premature. Correct the source zone first; then allow the published TTL to expire.
Clean old website records carefully. A previous host can leave apex A records, www CNAMEs, redirects, or parked-domain values that conflict with Webflow. Webflow also warns that a domain still attached to another platform using Cloudflare infrastructure can prevent verification. Remove the domain from that former platform before retrying, while preserving unrelated email and service records.
After the TXT is visible, compare the routing values and click Check status. Verification alone does not make the site live. Confirm an eligible Site plan, choose the custom domain in the publish menu, publish, and test it anonymously. If records are correct but verification still fails after Webflow’s documented two-day window, collect DNS evidence and contact support instead of generating another random token.
Choose the default domain with care. Webflow notes that changing the root or www default without matching DNS can create redirect loops. Test apex and www over both HTTP and HTTPS, follow the complete redirect chain, and ensure every version ends on one secure preferred hostname. Avoid stacking registrar forwarding on top of Webflow’s redirect behavior.
Once live, update canonical URLs, sitemap submissions, forms, integrations, analytics, campaign links, and Search Console to the production host. Run a TruboRankAI scan to check what crawlers receive, whether important CMS pages are linked and indexed, and whether the content provides clear answers for SEO, AEO, and GEO. Domain verification enables the launch but does not guarantee discovery.
Practical Steps
- Copy the current site-specific verification record.
- Publish it at the exact requested hostname.
- Confirm the authoritative nameservers and public TXT answer.
- Remove conflicting records and former platform ownership.
- Compare the current apex and www routes with Site settings.
- Click Check status and allow valid propagation time.
- Select the domain, publish, and test redirects.
- Update canonical discovery signals and audit the live site.
Stop guessing whether AI crawlers see your best pages.
Use crawler activity as an early discovery signal, identify pages that receive attention, and find important pages that may need a clearer path.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
Turn AI crawler visits into a repeatable visibility workflow.
Monitor discovery over time, compare activity across important pages, and use the evidence to decide what deserves attention next.
- Monitor leading AI and search crawlers
- Review which public pages receive visits
- Connect crawler activity to your visibility work
FAQ
Why did my old Webflow verification token stop working?
Removing and re-adding the domain can produce a new one-time token. Use the value currently displayed for that site.
How long should Webflow verification take?
DNS often updates sooner, but Webflow says changes can take up to 48 hours. If authoritative DNS is wrong, waiting will not solve it.
Why is the domain verified but missing from publishing?
Verification, Site plan eligibility, domain selection, default-host settings, and the publish action are separate stages. Review each in Production settings.
Sources and methodology
The page maps Webflow’s official preparation, verification, routing, publishing, and redirect guidance to observable stages. Sources were reviewed on 2026-08-16. Site-specific records override examples, and a successful launch does not guarantee indexing, traffic, or AI citations.
These references support the changeable facts and study findings discussed above. Results depend on each source's sample, date, market, query set, and measurement method.