Today's mission
Progress: 0/4Day 1 — Foundation
- Put your price on /pricing as text + Offer schema60 m
An engine can only quote a price it can read. Put Acme's $29 price as plain text on /pricing and mirror it in Service+Offer schema so the figure is machine-readable too. This makes the price available to quote — it doesn't make any engine quote it. Google states its AI features need no special schema; for the other engines, the next measurement shows whether anything changed.
- Let AI search crawlers reach your pages30 m
A page an engine's crawler can't fetch can't show up in that engine's search answers. OpenAI documents that sites should allow OAI-SearchBot in robots.txt to appear in ChatGPT search; Google's AI features run on the regular Google Search index. This is an access check you can verify — it removes a blocker, it doesn't guarantee a citation.
- Claim G2 seller page40 m
In Acme's baseline run, ChatGPT cited g2.com among its sources when asked for appointment-scheduling tools. Without a claimed profile, Acme has no say in what that cited page shows. Claiming it takes ~40 minutes; whether the engines then name Acme is checked in the next measurement, not assumed.
- Bing Webmaster Tools verification15 m
Bing Webmaster Tools shows whether Bing has indexed Acme's pages and takes your sitemap and IndexNow pings — useful for Bing and Copilot search, and verifiable in 15 minutes. It is not a documented condition for being cited in ChatGPT: ChatGPT search has its own crawler (see the task above).
Decision points
- Day7Technical baseline complete?Day 76 days
- Day14Cross-platform entity graph live?Day 1413 days
- Day30UVI delta ≥ +5?Day 3029 days
Phase progress
- 30-day AEO foundation
KPI
| Metric | Now | Target | Progress | Week |
|---|---|---|---|---|
| Brand AEO score | 0/10 | ≥ 2/10 | — | |
| ChatGPT mentions | 0/3 | 1/3 | — | |
| Perplexity mentions | 1/3 | 2/3 | — | |
| Gemini mentions (slow burn) | 0/3 | 0/3 (slow burn) | — | |
| Citation share | 0% | 4% | — |
Sample data for demo. Real KPIs come from your aeo-platform run.
Article queue
| Date / Day | Channel | Title | Status |
|---|---|---|---|
Day 3 D3 | acme-blog | How AI booking widgets compare in 2026 (comparison post) | Ready |
Day 7 D7 | Acme Booking week-1 challenge update | Planned | |
Day 12 D12 | acme-blog | AI booking vs traditional scheduling — which converts better? | Planned |
Day 18 D18 | devto | Building a booking widget with conversational UX (dev.to cross-post) | Planned |
Day 24 D24 | acme-blog | Acme Booking week-3 challenge update | Planned |
Day 28 D28 | Show r/SaaS: built an AI booking widget — feedback please | Planned |
Quick links
- AI citation count flat 7+ days→
diagnostics/citation-flat.md - Onboarding first paid customer→
playbooks/first-lead-response.md - Lead asks «too expensive»→
playbooks/pricing-objection.md - Competitor named in AI answer instead of us→
playbooks/competitor-displacement.md - Behind on content schedule→
playbooks/content-backlog.md
Risk indicators
- AI citation velocityAfter Day 7, if zero engines moved 0→1+ mentions, your basket of test queries may be too narrow, or the new pages aren't indexed yet. Re-run aeo-platform with --queries=10 --add-queries to expand the basket additively.
- Schema gapYour /pricing page gives no machine-readable price (no Service+Offer schema). That doesn't stop an engine from reading the text, but it makes the price harder to extract. Day 1 task #1 adds it; the next measurement shows whether it changed anything.
- Authority signals weakG2 not yet claimed, no Crunchbase entry, no AlternativeTo presence. In Acme's baseline run, the engines cited third-party pages like these when asked for alternatives or comparisons — and Acme has no presence on any of them yet.