Most AI-search disputes start before any work begins. Someone asks for "visibility in AI answers", the supplier agrees, and six weeks later nobody can say whether the thing that was promised has happened. The fix is not a better tactic. It is a brief that names what will be measured before anyone claims a result.
This page is a method, not a service description. You can complete it yourself in one sitting, or use the scope builder to produce a private Markdown document you keep. Nothing here depends on buying anything, and nothing here produces a ranking estimate.
Start with the right question
Google's own documentation states that there are no additional requirements to appear in AI Overviews or AI Mode, and that the existing SEO fundamentals remain the relevant best practice (s1). That single sentence kills most of the premises a supplier might bring to the table — special files, special markup, a new discipline with its own rules.
If no special optimisation is required, then the honest scope of an AI-search engagement is not "make us appear". It is a set of testable propositions about a site you control, an audience you can name, and evidence you are willing to accept. Write those down first. Everything else is delivery detail.
Step 1 — Name the business and the public site
Write the business in one sentence a stranger would understand, then the exact hostname that is publicly reachable. Be pedantic: staging domains, subdomains behind a login, and regional mirrors are different properties with different crawl behaviour.
This matters because crawl access is the first thing a scope can verify. Google advises ensuring crawling is permitted in robots.txt and by any CDN or hosting infrastructure (s1). OpenAI documents separate, independent controls per user agent: OAI-SearchBot governs surfacing in ChatGPT search, GPTBot covers content that may be used for training, and ChatGPT-User is used for user-initiated actions rather than automatic crawling (s4).
Two traps to record in the brief. First, robots.txt is not a reliable way to keep a page out of an index: Google states a disallowed URL can still be indexed if other pages link to it, and recommends noindex or password protection instead (s11). Second, a robots.txt rule alone may not be enough — firewalls, CDNs, bot protection, login walls or CAPTCHAs can separately block a crawler's request (s6). Put both on the list of things to check, not to assume.
Step 2 — Name the audience
Not a persona deck. One line: who is asking what, and what they need to do afterwards. Google frames its quality guidance around whether a named reader would find the material useful if they arrived directly, and around original information, demonstrated effort and clear sourcing rather than volume (s12). The same page warns against mass-producing content across topics or extensive uncurated automation.
An audience statement tightens scope in a useful way. If you cannot say who the page is for, you cannot say whether a citation to it was a good outcome or an accident.
Step 3 — Choose one of six fixed intents
AI-search requests collapse when a single engagement is asked to do several unrelated jobs. The brief forces one choice:
- Explain a concept — help a reader understand something.
- Compare options — set alternatives against each other.
- Support a decision — give a reader what they need to choose.
- Troubleshoot a problem — help resolve a specific failure.
- Establish authority on a subject — build a documented position of expertise.
- Be found for a brand or product — be discoverable for a named brand or product.
Indexing eligibility is deliberately not an intent in the builder. Google says that to be eligible as a supporting link a page must be indexed and eligible to be shown with a snippet, meeting standard Search technical requirements, and that meeting requirements still does not guarantee crawling, indexing or serving (s1). Eligibility is a gate you can test. It is not evidence of appearance.
Step 4 — Write down the evidence you will accept
This is the step that most briefs skip, and the one that makes the document auditable. Write it as a list of acceptable artefacts, not adjectives.
Acceptable, checkable evidence includes: a saved response from a named product on a named date; a screenshot showing a link to your URL; server logs showing a crawler request to a specific path; a fetch of your robots.txt showing which agents are allowed. Weak evidence includes: "we rank in AI search", unattributed growth screenshots, and any claim to see a vendor's internal ranking data. Google is explicit that no third-party tool has access to its internal ranking or AI systems, and advises caution with tools promising ranking success (s2).
Microsoft's own description of its reporting is a useful model for honesty about limits: Bing Webmaster Tools' AI visibility features were in preview, labels may be broad for niche domains, and Citation Share is described as observational, not exposing competitor domains and not representing traffic share or quality scores (s9). If a vendor's own documentation hedges that much, your brief should hedge too.
Step 5 — Ask delivery questions that have answers
Replace "what will you do?" with questions that produce a binary answer:
- Who changes robots.txt for each host in the redirect chain, and when?
- Which specific pages are in scope, by URL?
- What content will be created that does not already exist, and who is the named author?
- Which claims in the work will be sourced, and to what?
- What happens if the site is not crawlable after four weeks?
OpenAI's operational guidance notes that fixing crawler access does not guarantee approval of an ad, and that changes should be re-tested with recorded timestamps (s6). That is the right posture for any delivery commitment: a verified action, not a guaranteed outcome.
Step 6 — Set success criteria you can verify alone
Criteria should be checkable without the supplier present. Examples: "the URL is fetchable and eligible, verified by us on two dates", "the page names its author and sources at least three external references", "we have logged crawler requests to the page from at least one search product within 30 days".
Google's guidance that unique, non-commodity content with a distinct point of view will likely matter more in the long run than any other suggestion is qualitative, gives no effect size, and should be written into a brief as a quality commitment rather than a performance target (s2).
Step 7 — State the constraints explicitly
Constraints are the part of the brief that prevents later disputes. Write down what is out of bounds and what you will not supply.
Google warns against "chunking" content for machines, rewriting specifically for AI systems, keyword-variation padding, seeking inauthentic "mentions", and over-focusing on structured data as an AI tactic (s2). Google also states you do not need new machine-readable files or special schema markup for these features, and that Search ignores LLMS.txt (s1). A brief that forbids these explicitly prevents a supplier proposing them later.
Google also treats fabricated author profiles and false credentials as a form of deception and signals low quality (s12). Write that constraint down too, and add a disclosure line for any AI assistance in drafting where a reader would reasonably ask how the page was made.
The four-way distinction
Keep these separate in every status report. Merging them is the most common way an AI-search project becomes unfalsifiable.
| Question | What it means | What it does not prove |
|---|---|---|
| Appearance | Your content contributed to a generated answer surface you observed and saved | That you were cited, or that anyone clicked |
| Citation | Your page is explicitly linked or named as a source in that answer | That search engines can index or serve the page |
| Indexing | The page is crawlable, indexed and eligible to be shown with a snippet | That it will ever appear in a generative answer |
| Traffic | People arrived from a surface and did something measurable | Which mechanism produced the visit without analytics evidence |
Note the honest asymmetry: eligibility is documented and testable (s1), while appearance in a given answer is not guaranteed by anything the vendor publishes — Google describes AI Overviews as shown only when systems judge them additive, and notes they often do not trigger (s1).
Finish the brief and keep a copy
When the seven parts are written, you have a document that can be reviewed against a proposal, a milestone report, or an invoice. Build it in the scope builder, which produces a private Markdown file in your browser — no account, no automatic queries against third-party systems, and no ranking estimates.
Related reading: specify evidence before visibility claims, distinguish citations, referrals and outcomes, and review an AI-search proposal.