Playbooks, checklists & templates

Concepts and execution are two different jobs, so they live in two places. The Learn hub answers the "what" and "why" — what AI search visibility is, how generative and answer engines pick the sources they cite, and the four signals that decide whether your brand shows up. This Resources page is the "how": the concrete, repeatable artifacts you use to do the work. If a step below assumes something you are not sure about, the underlying concept is one click away in Learn. Treat the playbooks as your sequence, the checklists as your quality gate, and the templates as your starting structure — together they turn the theory into shipped pages and measurable movement.

Playbooks: step-by-step workflows

Each playbook is a short, repeatable procedure. Run them in order the first time — audit to find gaps, competitor-replacement and page-fix to close them, proof-loop to confirm the change — then re-run whichever one a given prompt needs.

The AI visibility audit playbook

Establish a truthful baseline of where AI engines name, cite, or ignore your brand.

1. List the questions that matter — category prompts, comparison prompts, alternative prompts, and use-case prompts a buyer would actually ask.
2. Run each prompt across the AI engines you care about and capture the full answer plus any citations.
3. Record, per prompt, whether your brand is named, whether it is cited, and which competitors appear instead.
4. Group the gaps by type: missing entirely, mentioned but not cited, or lost to a specific competitor.
5. Prioritize the gaps with the highest buying intent and the clearest path to a fix.

The competitor-replacement playbook

Win back prompts where AI recommends a rival instead of you.

1. Isolate the prompts where a competitor is named or cited and you are not.
2. Read the sources the engine drew on — owned pages, reviews, roundups, or forums — to see why the rival is visible.
3. Publish a stronger, more extractable answer on the right page on your own site.
4. Earn independent corroboration: pursue the reviews, roundups, and mentions the engine already trusts.
5. Re-test the same prompts after the work ships and track whether the named brand changes.

The page-fix playbook

Turn one URL into a page AI engines can quote.

1. Lead with a concise, direct answer to the page's core question in the first paragraph.
2. Rewrite headings as the questions people actually ask, then answer each one underneath.
3. Add Article, FAQPage, and BreadcrumbList structured data so engines can parse and attribute the page.
4. Fix crawlability: make sure the answer renders server-side and nothing blocks the crawler.
5. Publish, request a re-crawl, and add the page's prompts to your proof loop.

The proof-loop playbook

Prove that AI answers actually changed after you shipped a fix.

1. Lock the exact prompt set and engines you will measure so runs are comparable.
2. Capture a baseline before any change: who is named, who is cited, and your share of voice.
3. Ship one fix at a time so movement can be attributed to a specific change.
4. Re-run the same prompts on a fixed schedule, since a single run can vary.
5. Record observed movement over time — citations gained, rank, and share of voice — not a one-off snapshot.

Checklists: tick before you ship

Use these as the last gate before publishing a page you want AI engines to cite. They turn the GEO and AEO principles into concrete, checkable items.

On-page GEO/AEO checklist

• A direct answer to the page's main question appears in the first 1–2 sentences.
• Headings are phrased as questions and each is answered immediately below.
• Key facts, numbers, and comparisons are specific and current, not vague claims.
• Article, FAQPage, and BreadcrumbList schema are present and valid.
• The page renders its content server-side and is not blocked from crawlers.
• Internal links connect the page to related concepts and product pages.
• A clear entity statement says what you are, who you are for, and how you compare.

Citation-readiness checklist

• The brand is described consistently across your site, not only on the homepage.
• Independent sources (reviews, roundups, editorial) mention the brand by name.
• Comparison, alternative, and pricing pages exist for high-intent prompts.
• Claims that matter are sourced and quotable in a single sentence.
• The page title and meta description match the question the page answers.
• Freshness is signaled with a visible, accurate last-updated date.

Pre-publish checklist

• The target prompt for this page is written down and the page answers it directly.
• The answer block is under ~60 words and stands on its own out of context.
• Structured data validates with no errors.
• No competitor is described more clearly on this page than you are.
• The prompt is added to the proof loop with a baseline recorded.

Templates: copy-paste structures

Reusable structures for the page types that earn the most AI citations. Adapt the wording to your brand, but keep the shape — it is the shape engines find easiest to extract.

Pair these with the concepts

These resources assume the fundamentals covered in the Learn hub. If a step is unclear, the underlying concept is explained there: what AI search visibility is, how engines choose sources, and the four signals that decide whether you get cited.

One habit matters more than any single template: change one thing at a time and always re-test the same prompts. AI answers shift on their own between runs, so a page that looks better today might just be noise. The discipline of a locked prompt set, a recorded baseline, and a scheduled re-test is what lets you tell a real win from a lucky draw — and it is the difference between guessing at AI visibility and managing it. Work the playbooks in order, gate every page with a checklist, and let the proof loop, not your intuition, tell you when the work landed.

• Learn: AI search visibility, GEO and AEO explained
• Product: how RankEcho automates the audit and proof loop
• Solutions: workflows by team and use case