Domain verification
Domain verification is a one-time DNS TXT challenge that proves you control the hostname before geodeck activates llms.txt, sitemap, and feed endpoints for your site. Since 2026 we resolve the token live via Cloudflare DNS-over-HTTPS, so propagation typically completes in 1 to 5 minutes on more than 95% of registrars. The token is unique per domain and only needs to resolve once — you can leave the record in place forever without any periodic re-checks.
How does domain verification work?
- Add a domain in the dashboard. We generate a unique token.
- Create a DNS TXT record at
_geodeck.<hostname>with the token as value. - Click Verify. We resolve the record via Cloudflare DNS-over-HTTPS.
What does an example DNS TXT record look like?
Type: TXT Name: _geodeck.example.com Value: gd_v1_abc123...
What if verification fails?
- Propagation: most registrars publish within 1–5 minutes; some take up to 30.
- Apex vs subdomain: the record name is the literal
_geodecklabel below your hostname - do not include the apex twice. - CNAME chains: the lookup follows DNS resolution; CNAME is fine.
- Already verified: you can leave the record in place - we do not periodically re-check.
What else can I read?
Keep reading the rest of the Geodeck documentation, or jump to the platform pages.
- All docs →Three-step quick start and the full guide list.
- CMS webhook →POST publish, update, and unpublish events with HMAC-SHA256.
- llms.txt generator →How Geodeck builds /llms.txt and /llms-full.txt for AI crawlers.
- Indexing & ping providers →IndexNow, Google Search Console, Google Indexing API, and XML-RPC pings.
- Visibility score →How the 0-100 score breaks down across bot access, schema, AEO, freshness, and site basics.