Documentation
Build with geodeck
These docs walk you through every step you need to ship with geodeck: how to connect your CMS over a signed webhook, how to verify your domain with a single DNS TXT record, what an llms.txt file actually contains, and how indexing and pings work in 2026 across IndexNow, Google Search Console, and the optional Indexing API. Each guide includes copy-paste examples and the exact HTTP responses you should expect.
Quick start — 3 steps
- 1
- 2
- 3Publish something— Geodeck auto-generates llms.txt, queues pings, and runs audits within 6 minutes.
How do I connect my CMS to geodeck? →
Send publish events from WordPress, Ghost, Webflow, Sanity, Strapi, or any custom stack. Copy-paste HMAC examples for each.
What is the llms.txt format? →
What geodeck creates, where the files live, and when they update.
How do I verify my domain? →
One DNS TXT record. Propagates in 1–5 minutes. Troubleshooting tips included.
How do indexing and pings work? →
What geodeck tells search tools after you publish, and when direct Google push is appropriate.
How does the visibility score work? →
What the 0-100 number measures, and how to push your domain from 90 to 100.
What else can I read?
Keep reading the rest of the Geodeck documentation, or jump to the platform pages.
- Domain verification →Add a single DNS TXT record so Geodeck can manage your site.
- 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.