Lesson 02 · Command → campaign → BotCentral
The full CiteFleet path: onboard an origin, prove it crawls, list it on BotCentral, submit Google/Bing, then earn citations. Do not skip ahead.
List a website — the real buttonstraining mock — looks like the real screenThose three controls are the real Command buttons. Audit first. List on BotCentral after crawl is clean. Mentions last.
Step 1
Sign in at /login with Google, X, or email if you are not already (the console is gated; customer hooks and /health are not). Then in the top nav click Command. This is the only place you add a site. You should see Onboard a property on the right of the board.
Step 2
Site name = human label (Acme Dating). Origin URL = https:// plus the host only — no /pricing, no trailing slash required. Example: https://acme-dating.com. IndexNow key is optional; leave blank and one is generated, or paste the key the live site already serves at /{key}.txt.
Step 3
CiteFleet creates the property, copies the playbook into live tasks, and pins each task to one bot (Aether, Orion, Helios, Nimbus, Lyra, Vesper, Cassian, Forge, Sentinel). Properties on the KPI row increments. A new card appears for that domain.
Step 4
CiteFleet fetches the origin for real: homepage and public routes with and without Accept: text/html, robots.txt, sitemap.xml, llms.txt. A JSON 404 without a special header is an SPA fallback bug — stop here and fix the site (Aether) before any listing.
Step 5
Work P1 first: Repair SPA fallback, robots.txt AI crawlers, sitemap. Tick a box only when the live URL is actually fixed. Local audit on a technical card re-checks HTTP; Send to Grok hands that task's brief to Grok. Do not open Product Hunt while Aether is still blocked.
Step 6
First prove control: put botcentral-verify=citefleet-app in an apex DNS TXT record on the domain (Name @ — no deploy, live in about a minute), or serve that same line as plain text at /.well-known/botcentral.txt (Push origin files from the campaign, then deploy). Either one alone is enough. Files CiteFleet wrote before already pass. Then on Command or the campaign header click List on BotCentral. Orion publishes a BotCentral 1.0 card. This is the bot-search catalog at botcentral.org. Assistants do not fill a submit form. You never paste a ChatGPT URL to get listed here.
Step 7
Command shows Listed on BotCentral. Click it — that is the Card Inspector (human page) at botcentral.org/site/{domain}. Machine card is the JSON at /v1/site/{domain}. Search botcentral.org/v1/search?q=your-topic and the domain should appear. Refresh listing updates the card without wiping existing topics.
Step 8
Helios: verify the domain in Google Search Console, submit the sitemap, URL-inspect key pages. Nimbus: Bing Webmaster Tools + IndexNow. That feeds Google, Gemini, AI Overviews, Bing, ChatGPT search, and Copilot. There is no ChatGPT webmaster portal.
Step 9
Indexing finds you. Citations need third-party pages. Lyra: three X posts with the exact domain. Vesper: Trustpilot, SmartCustomer, Product Hunt (Tue–Thu AM), AlternativeTo, SaaSHub. Cassian: press kit, then pitch. Always write the domain (acme-dating.com), not just the brand name. Tick the campaign boxes when each claim is actually live.
Step 10
Sentinel’s Local audit is the HTTP 200 sweep. Weekly: GSC + Bing AI Performance. If a route regresses to 404, re-dispatch Aether before more mentions. Listed on BotCentral plus GSC/Bing submitted = the site is in the CiteFleet pipeline. Mentions keep accumulating for months.