What a search visibility audit should answer
A practical outline for turning an audit from a list of issues into a set of decisions.
This is an early working note. We will add examples, sources, and fuller evidence as this topic develops.
Start with the question
An audit is most useful when it begins with a decision. Is the team choosing which pages to improve, which topics to cover, or which technical constraints to address? The answer changes what evidence is worth collecting.
Connect findings to work
A useful output describes the affected pages, the reason the issue matters, the proposed action, and what could be checked afterward. That gives editors, designers, and engineers enough context to judge the tradeoff.
Name the uncertainty
Search results change. An audit should separate observations from hypotheses and explain where more evidence is needed. The goal is a clearer next step, not a false sense of certainty.