Technical proof
Final-domain readiness check passes, sitemap URLs return 200, canonical URLs point to the final domain, and proof files return valid JSON.
New domain SEO launch checklist for AI crawler visibility
Use this checklist when a new domain is ready to move from preview to production. It focuses on the boring proof that actually matters: DNS, HTTPS, crawlable files, Search Console, IndexNow, real referrers, and activation events.
Launch rule: do not use fake searches, fake clicks, mass comment links, or Google search URLs as ranking tricks. Link directly to useful pages and measure real visits.
1. Domain and DNS
- Register the final domain and save the registrar proof.
- Point DNS to the chosen host.
- Confirm the apex and www host resolve as expected.
- Wait for HTTPS to return a valid certificate before submitting search packets.
2. Required final-domain files
| File | Why it matters |
|---|---|
/robots.txt |
States crawler access policy and points to the sitemap. |
/sitemap.xml |
Gives search engines canonical URLs to discover and monitor. |
/llms.txt |
Provides a curated AI-readable site map for tools that choose to use it. |
/.well-known/live-proof.json |
Shows public URL health, crawler evidence, and funnel event proof. |
/.well-known/distribution-proof.json |
Lists planned legal distribution placements and tracked URLs. |
/db565bace03e0c4b9200371a5a7411b1138bc1cefb16a8f9db845eb63c41ae4b.txt |
Verifies ownership for IndexNow URL notification. |
3. Search Console launch
- Create a Google Search Console Domain property for the final domain.
- Verify ownership with the DNS TXT record Google provides.
- Submit the final-domain sitemap URL.
- Use URL Inspection on the homepage, tools, benchmark, and best guides.
- Record impressions, clicks, and indexing notes in a launch log.
4. IndexNow launch
Only submit after the final domain and key file are live. IndexNow responses prove notification, not guaranteed indexing.
npm run indexnow:packet npm run indexnow:submit
5. First legal distribution
Use direct UTM links from the distribution ledger. The goal is real referral traffic and useful answers, not artificial ranking signals.
- Answer relevant Reddit, webmaster, CMS, and founder questions only when the asset helps.
- Use GitHub README, issue, and PR snippets only for real docs/crawler policy discussions.
- Share the crawler policy benchmark where people are comparing AI crawler controls.
- Share the log analyzer when people ask how to prove bots are visiting.
- Refresh proof after distribution to capture UTM and referrer evidence.
6. Proof threshold
Search proof
Search Console is verified, the sitemap is submitted, and impressions or clicks begin appearing for target queries.
Referral proof
Access logs or analytics show real UTM/referrer visits from relevant communities, GitHub, newsletters, or directories.
Activation proof
Visitors use the generator, checker, validator, log analyzer, copy buttons, or audit request links.
Useful next assets
- Community answer templates
- GitHub README snippets
- Free traffic tricks research
- Public proof dashboard