Lesson 06 · Open campaign

Campaign board

One origin’s punch list. Every task has an owner bot, a checklist, and evidence.

Campaign boardtraining mock — looks like the real screen
doneAETHERRepair SPA fallback 404s
P1 · Local audit
doneNIMBUSIndexNow instant-push
P2 · Local audit
assignedLYRAGrok / X live mention sequence
P2 · Local audit
queuedVESPERDirectory and review listings
P3 · Local audit

Tick a checkbox when you finished the work outside CiteFleet (posted to X, claimed Trustpilot). Local audit re-checks technical tasks against the live site.

Step 1

Priority order

P1 is crawl integrity (SPA fallback, robots, sitemap). P2 is submit doors and Grok/X. P3 is directories, press, and app-health. P4 is ongoing monitor.

Step 2

Local audit and Send to Grok

Local audit on a technical task re-runs the live audit; on a mention or press task it advances the next unchecked item. The BotCentral task row shows List on BotCentral instead, because that button publishes the card (same as the header button). Send to Grok copies the task brief for Grok to work. Checkboxes can also be toggled by hand when you finished the work outside the app.

Step 3

Remove property

Campaign header → Remove property (confirm). Drops the site, its tasks, and its monitor snapshot; the audit log keeps the history and the BotCentral card is not touched. Use it for duplicates or test onboards.

Step 4

Blocked vs done

Blocked means the auditor still sees a problem. Done means the checklist is complete. Waiting on the property card means most technical/submit work is done and you are accumulating citations.