Sitewide AI visibility audit
A sitewide AI visibility audit is RankEcho's brand-level observation workflow. Across a declared buyer-prompt and engine panel, it records citations, unlinked mentions, absences, competitor appearances, explicit source URLs, unavailable runs, and denominators. The result can organize page, access, or source hypotheses and reviewable next steps; it does not show whether an engine understood or trusted the brand, identify the cause of an omission, or predict a citation.
What does a sitewide audit answer?
A sitewide audit answers the executive question: when buyers ask AI systems about the category, does the brand show up, and if not, who replaces it?
The audit looks across a configured brand-level prompt panel rather than evaluating one URL. It records sampled market visibility, competitor appearances, explicit source mix, prompt classes, and unavailable observations without claiming that public brand signals are strong enough for a provider to cite.
- Which buyer prompts mention or cite the brand.
- Which prompts recommend competitors instead.
- Which engines show the biggest visibility gap.
- Which source types appeared for the category prompts.
- Which evidence-backed hypotheses the team may review next.
How is this different from a page-level audit?
A sitewide audit describes brand-level observations across a declared panel. A page-level audit focuses review on one URL and the prompts it is intended to support.
Use sitewide when the team needs a baseline, board-level story, client intake report, or strategic visibility map. Use page-level when the team already knows the target page, such as a product, pricing, comparison, solution, or guide page.
What RankEcho measures sitewide
RankEcho measures prompt outcomes across AI engines and classifies what happened: cited, mentioned, absent, replaced by a competitor, or skipped because an engine was unavailable.
The scorecard is intentionally evidence-based. It reports citation rate, share of voice, prompt coverage, competitor replacement, engine coverage, source mix, and page-level opportunities that should become the next optimization queue.
- Citation rate and mention rate.
- Share of voice against named competitors.
- Prompts lost to competitors.
- Owned versus third-party source dependence.
- Engine coverage and skipped-engine transparency.
- Page-level workstream candidates.
What the buyer sees
A strong sitewide result page should not feel like a vanity score. It should show audit depth, prompt and engine coverage, a prompt-by-engine matrix, source evidence, competitor losses, and recommended fix sequence.
For agencies, the same output can become a client intake artifact: what the configured runs returned, where the client was absent, which competitors and sources appeared, and which bounded hypothesis is proposed for review.
How the sitewide audit feeds the Fix Engine
The sitewide audit can create a backlog by organizing decision-relevant prompts where the brand was absent and a competitor appeared. The Fix Engine then turns a selected observation into a reviewable proposal package.
Some observations can lead to page-level checks; others can lead to source-coverage, entity-statement, crawler-policy, delivery, or comparison-content hypotheses. The team chooses what to test from the saved evidence, business relevance, effort, and risk rather than treating the audit as a cause finder.
When should teams run it?
Run a sitewide audit before starting AI search visibility optimization, before selling an agency engagement, after a brand or product positioning change, and after major content/source work has shipped.
For active teams, the sitewide audit becomes the quarterly or monthly strategic layer, while page-level audits handle the specific optimization work between baseline checks.
Frequently asked questions
The initial RankEcho audit is free and gives teams a visibility baseline. Paid plans unlock deeper fix generation, proof-loop tracking, exports, and higher prompt volume.
No. Sitewide means brand-level prompt intelligence across the domain and category. RankEcho uses the domain, source evidence, prompt outcomes, and page opportunities to identify where the brand is visible or missing.
Review a decision-relevant competitor appearance, missing observation, or verified access-policy or delivery finding. Choose a bounded proposal, record any shipment, and use page-level or Proof Loop re-tests to compare later observations without attributing movement to the change.
Yes. The sitewide audit is designed to become a client-ready baseline: current visibility, competitor risk, source gaps, and the first recommended workstream.