Playbook 01November 2026Free PDF
The AI TrafficPlaybook.
How to get your startup named and cited by ChatGPT, Claude, Gemini and Perplexity. Plain English first, then the full technical version, with Claude Code prompts you can paste.
- Inside
- 10 chapters4 gates to get cited
- Read
- 20 minutesor build it in a weekend
- Sources
- 62 citedeach one dated



Every chapter is written twice.
The playbook is for founders, marketers and whoever builds the website. Each chapter comes twice, so you can stop wherever your job stops.
The short version
20 minutes.
The first page of every chapter. Plain English, no code: what it is, why it matters, and three things to do today. Read only these and you'll know what to fix this week.

Technical
A weekend.
Every page after it. How it works under the hood, config you can copy, tables to check against, and Claude Code prompts that do the work inside your own site's code.

Four gates decide who AI names.
This is the model the playbook is built on. Pass all four gates and you're in the running. Fail one, and the answer usually goes to someone else.
Gate 1
Readable.
Can AI crawlers fetch and read the page?
Chapter 02
Gate 2
Answered.
Is there a page that answers this exact question?
Chapter 03
Free tools
Gate 3
Liftable.
Can an engine lift the answer in one piece?
Chapters 04 and 05
Gate 4
Corroborated.
Do other sites vouch for you?
Chapter 06
Free tools
Result
Named.
You're in the answer.
Then measure it
Chapter 07 sets up a GA4 channel for AI traffic, reads your server logs and runs a weekly prompt check, with tools you already have.
What's inside.
Pick a chapter to see its first page. That page is the short version, and the technical pages follow it.

Try one prompt before you download.
This one is from page 9. It has Claude Code check your site the way AI crawlers see it. Open Claude Code in your website's code folder, swap in your own URL and pages, and paste it.
Paste into Claude Code
Audit this site for AI crawlers. Our live site is [https://yoursite.com]. 1. Read /robots.txt the way RFC 9309 does (a named group overrides "*", the longest path wins). For OAI-SearchBot, ChatGPT-User, GPTBot, Claude-SearchBot, Claude-User, ClaudeBot, PerplexityBot and Google-Extended: is each of our key pages allowed? 2. Fetch [/, /pricing, /product, /blog/our-best-post] with curl (no JavaScript). For each: status, <title>, H1, and whether the main text is in the raw HTML. 3. Find where robots.txt and those pages are generated in this repo. 4. Propose fixes as a diff. Don't change any files until I approve.
- What it does
- Reads your rules the way a crawler does, fetches pages the way a bot sees them, then traces each problem back to the file that causes it.
- Expect
- A bots-by-pages table of allowed and blocked, a list of pages whose text only appears after JavaScript runs, and a diff to review.
Some prompts also use Rankbox's free MCP server
It adds three research tools to Claude Code: the questions buyers ask AI, content briefs and meta descriptions. No sign-in, key or Rankbox account. Connect it once, in your terminal:
claude mcp add --transport http rankbox https://rankbox.xyz/mcpQuestions about the playbook.
Is the playbook free?
Yes. Enter your email and the PDF downloads straight away. There's no account to make and nothing to pay.
Who is it for?
Founders and marketers who want to know what to fix, and whoever builds the website. Every chapter opens with a one-page short version, then the technical pages for the person doing the work.
Do I need Claude Code to use it?
No. The short versions need nothing but a browser. The technical pages include Claude Code prompts because Claude Code can read your site's code and propose fixes, but every prompt says what it checks, so you can do the same by hand.
Do I need Rankbox?
No. Everything in the playbook works without Rankbox. The back cover lists the free Rankbox tools for each gate, and what the paid product automates if you'd rather not do it by hand every week.
How do I measure AI traffic with it?
Chapter 07 covers it with tools you already have: a GA4 channel for AI referrals, your server logs, and a weekly check of the prompts your buyers ask. Rankbox doesn't track citations, so the playbook shows the free way.
How current is it?
It's the November 2026 edition. AI search moves fast, so dates sit next to anything likely to change, and each fact is credited to the company that published it, with 62 sources listed at the back.
The AI Traffic Playbook
Get the playbook.
44 pages, 10 chapters and a Claude Code prompt for every step. Free.









