Check AI answers for first users, then fix or abandon pages

You have a website and no distribution yet. The first question is which pages are already explaining your product to strangers, and which are just taking up space. As of August 31, 2026, Google made the generative AI performance report available to all websites worldwide through Search Console, and it reported only impressions, not clicks. Use it to see where your pages appear in AI answers, not to count clicks.

That limitation is useful. It forces you to ask whether your pages can be seen, cited, or used before you try to explain why someone did not buy, sign up, or email you.

Google said on August 28, 2026 that AI Overviews may automatically expand for certain queries when its systems judge a longer answer most useful. Those expanded answers occupy more vertical space and push standard blue-link results lower on the page. A page can retain position one yet lose clicks when the query above it triggers Google's expanded AI Overview format.

For a founder with no distribution, that changes the job. You are looking for the few pages that can survive being summarized, quoted, or cited by an answer engine. You may still do the unscalable work: answer emails, call prospects, and explain the product in a meeting. The audit only tells you where the explanation is already happening without you.

The report measures visibility before it measures clicks

Start with the page slice, because it tells you which pages are being seen. The country and device slices tell you whether the signal is broad or local. But the starting question is simpler: which pages are being seen in AI answers at all?

If a page has no AI visibility, do not treat that as a crisis. It may be the wrong page, the wrong query, or the wrong stage. If a page has AI visibility but no clear answer, that is the page to fix or abandon. The test is whether a stranger can get the core answer from it without scrolling, guessing, or reading your marketing language.

The audit comes before the tactics

Keep the checklist short enough that you can finish it before your attention drifts to a tactic that needs scale to work. Each item is quick to test. The opening items establish the signal. The middle items test whether the page can carry a citation. The final item is a guardrail.

• Open the generative AI performance report and confirm the date range covers the period you care about.
• Slice by page first, then by country and device, because the report can slice its table by page, country, or device.
• Compare AI Overviews and AI Mode impressions with total impressions for the same page, and note where AI visibility is meaningful rather than a stray impression.
• For each page with meaningful AI visibility, check whether the page answers the query directly near the top, with a definition, step, comparison, or clear recommendation.
• Check whether the page contains a quotable line: a sentence an answer engine could lift without distorting your product, pricing, or claim.
• Keep feeding the strongest citable pages by reformatting them: move the direct answer near the top, add a clear heading, and keep the quotable line intact.
• Stop feeding weak pages: mark them for rewrite or deletion when they receive AI visibility but cannot answer the query directly, because adding more content will not make them citable.
• Use the Search Console control introduced in June 2026, which allows a site to remove its pages from AI Overviews, AI Mode, and AI-generated Discover grounding, only if AI grounding is harmful, such as when it pulls outdated pricing, unsupported claims, or pages you do not want represented.

Only citable pages deserve fixes

Most early-stage sites have too many pages that sound useful but cannot be cited. They describe the problem, promise the outcome, and bury the answer. AI answers reward the opposite: a short, direct statement that can stand alone.

If a page can answer the query in a short sentence, reformat it so that answer appears early. If it cannot, stop treating it as a first-user channel. You can keep it for humans, but do not expect it to earn trust through an answer engine.