Private diagnostic brief: build the question before you chase the answer

This worksheet turns a fuzzy worry about AI-search visibility into a set of answerable questions. It produces a fixed action name, a known page path and a structured brief you can keep or hand on. It does not contact anyone, fetch your pages or measure anything for you.

Answers stay in this browser tab. The page script does not use cookies, storage or uploads. Opening the tool is recorded as a fixed action name, and the page's own path may appear in site logs; the content of your answers is not sent with that.

Diagnostic questions

List the specific URLs or page names you are actually asking about, one per line. Absolute URLs are preferable. Keep it to the pages you can name, not the whole site.

Describe the audience and the task they arrive with. One or two sentences is enough; avoid invented personas.

State the issue as a checkable claim, not a verdict. “The page does not appear for X” is testable; “our SEO is broken” is not.

Name what you actually observed and where: a dated search, a screenshot, a log line, a colleague's report. If the evidence is thin, say so plainly.

What are you comparing against? A page that does appear, an earlier observation, or the absence of any result. The comparison is what makes the test interpretable.

Propose one test small enough to run in a bounded session, with a result you could state in advance either way. Separate access questions from content questions.

Say who will use this brief and what decision they need to make. Keep it to a role you can actually reach, not an invented team.

If you want the brief to mark its own strength, choose the closest class.

Anything that limits the test: approvals needed, a template you cannot edit, a recrawl wait, or a deadline. Bounded to a short note.

Name the publisher documentation that governs the mechanism you are testing, so the brief points to a source rather than a hunch.

Fields are disabled until the page script is ready.



  

How to use the brief

  1. Name the pages. A brief about “the site” cannot be tested; a brief about two named URLs can.
  2. Split access from content. Before rewriting anything, check whether the page can be crawled and is eligible to be shown in Search with a snippet. Google documents that AI features require no additional technical requirements beyond Search eligibility, so an access question and a content question call for different next steps.
  3. Check the right control. robots.txt is crawler-specific. A Googlebot rule is not the same setting as OpenAI's OAI-SearchBot rule, and OpenAI describes the two as independent. Google also states that disallowed pages can still be indexed if linked elsewhere.
  4. Write the test before the result. A test whose possible outcomes you cannot state in advance will not settle the claim.
  5. Hand off a question, not a verdict. Give the next person the comparison point and the evidence class so they can act without re-deriving your reasoning.

This is investigation and advice. It does not deliver a service, does not certify any result, and does not present a consultant biography. Claims in the brief are yours; the source documents are the authority on how Google and OpenAI systems behave.