Technical baseline
URL and prompt scope, plus a timestamped technical baseline.
Public web
Establish a read-only baseline for agreed pages and identify reversible changes.
Planned service · Inquiries open · Scope and availability agreed together.
The planned service records what is reachable, rendered, declared, and observed at a point in time. Repeated AI prompts remain observations, with date, locale, full response, and citations captured separately for brand and non-brand prompts.
A website or marketing owner can approve the URLs, audience, markets, and business facts and needs a defensible starting point.
URL and prompt scope, plus a timestamped technical baseline.
An approved-fact register and findings across crawl/index, information architecture, clarity, structured data, and external consistency.
A prioritized list of reversible changes and unchanged pages for comparison.
A follow-up design with separate metrics, rather than one composite visibility score.
Illustrative example
Fictional analytics pages contain outdated pricing, orphaned documents, an unclear category, a structured-data mismatch, and contradictory founding dates. This is illustrative only; it does not report a crawl, ranking, or citation observation.
No. The work is a baseline and a prioritized change list, not a guarantee of an external system’s behavior.
Repeated, fixed panels report citation rates separately for brand and non-brand prompts. They are not combined into one AI visibility score.
No. They are separately scoped, with price and timing agreed after the baseline scope is clear.
Scope, availability, timing, and price are agreed before work starts.
We can agree the scope before work begins.
Discuss search visibility