AI Visibility Strategy

How the site becomes a source assistants cite, and how that will be measured given nobody controls the retrieval layer.

Where This Sits

Components in the finished document

Measured directly, not asserted

Pieces that carry my judgment

This is a Direction deliverable, which means it turns findings into a sequence. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.

It is not a package and not a retainer. It is one document with 6 components, and the list below is the whole of it.

What Is Inside It

Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.

Measured

Pulled straight from tools and logs. No interpretation, so you can re-run any of it yourself and get the same numbers.

Answer block inventory: Passages on the site that already function as a direct answer, and where they sit.
Query fan-out capture: The chain of sub-questions an assistant asks on the way to answering the primary query.

Judged

My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.

Entity map, target state: The entities the site should describe and how they should connect, as a specification to build against.
Sequenced initiative list: Every initiative in execution order, each with its dependency and its reason for sitting where it sits.
Metric definitions: Exactly how each reported number is calculated, so it means the same thing every month.
Attribution caveats statement: What the measurement cannot prove, stated up front rather than discovered in an argument.