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.
Fields are disabled until the page script is ready.
How to use the brief
- Name the pages. A brief about “the site” cannot be tested; a brief about two named URLs can.
- 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.
- 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.
- Write the test before the result. A test whose possible outcomes you cannot state in advance will not settle the claim.
- 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.