ServicesPricingProcessMeasurementThe Shift
Create accountSign inFree snapshot
Example

What a real AI visibility finding should look like.

A teardown finding is not 'AI cannot find us.' It is a dated observation tied to a prompt, an engine, cited sources, a confidence label, a target URL, and the next fix.

By Jesús MendozaUpdated

Request a snapshotCompare approaches
Teardown Example resource visual
Guide
Buyer criteria
Compare
Weak vs useful
Buyer questions

A finding is not useful until it names the URL.

A credible teardown shows the anatomy of a finding while separating observed evidence from illustrative structure.

Question

What does an AI visibility teardown evaluate?

An AI visibility teardown should show one finding at a time: the prompt, engine, date, observed answer, cited sources, competitor URLs, confidence label, target page, and recommended fix. A useful teardown does not say AI cannot find us and stop there. It explains which page failed, why the evidence suggests that, and what action should happen next.

The walkthrough remains illustrative; the approved anonymized production excerpt below shows a dated row without customer data or outcomes.

What changes in practice

Readers can inspect how one observation becomes a confidence-labeled finding, target URL, owner, prioritized fix, and retest.

Audit methodologyAudit template
Request a snapshot
Question map

Questions worth answering.

Each question has a page role, proof requirement, answer format, and next step.

Buying decision

What should one AI visibility teardown finding contain?

Answer format
An evidence row that shows the prompt, engine, observation, cited sources, confidence, affected page, and recommended fix.
Proof needed
Exact prompt, engine, test date, answer excerpt, cited owned URL, cited competitor URLs, confidence label, target page, issue type, and action.

Request an audit when findings need validation against the live site.

Trust and caveats

Can a teardown page use example or hypothetical data safely?

Answer format
A caveat answer that separates framework-only examples from approved anonymized production rows and avoids implying customer outcomes, screenshots, or metrics without approval.
Proof needed
Visible framework label, no customer outcome claims, no invented screenshots, no fake metrics, and notes on what requires live testing.

Use the methodology page to explain the evidence standard.

Implementation planning

How should teardown actions be prioritized after findings are collected?

Answer format
A priority table that ranks issues by impact, evidence confidence, affected URL, owner, effort, and next sprint action.
Proof needed
Impact estimate, confidence label, target page, technical/content/proof category, owner, dependency, and next step.

Plan a sprint around the highest-confidence page fixes.

Proof notes

What to verify.

  • Clear label explaining whether examples are real, anonymized, or framework-only.
  • Evidence fields that mirror the prompt matrix and completion notes.
  • No screenshots, metrics, or outcomes unless they are real and approved.
Caveats

Keep the claim bounded.

  • This page should not imply customer results without visible support.
  • Production rows are dated and scoped to Citation Path's own public evidence; they do not imply customer results.
  • Weak proxy observations should not be presented as direct AI-engine proof.
Source assets

Evidence buyers can inspect.

Live assets are linked. Planned assets stay clearly labeled until they are published.

  • Teardown example framework

    Live

    This page shows how to structure findings without inventing customer results or screenshots.

    Inspect this asset

  • Sample report excerpt

    Live

    The public excerpt is an approved anonymized production sample with no customer identifiers or outcomes.

    Inspect this asset
Anonymized production example

Inspect one dated finding before using the template.

This production excerpt makes the report contract concrete without exposing customer data or promising an engine outcome.

Anonymized production evidence sample with prompt, engine, citation, confidence, finding, and page action.
PromptEngineCitationConfidenceFindingPage action
Citation Path AI SEO agencyBRD-001 · 2026-08-16ChatGPT SearchCitation Path production homepage citedDirectThe answer described Citation Path accurately, but its source treatment relied on owned public pages rather than independent proof.Keep the homepage entity and offer facts synchronized; publish inspectable proof without implying third-party validation.
Citation Path AI SEO agencyBRD-001 · 2026-08-16Google organic resultCitation Path production homepage cited; a similarly named domain also appearedDirectThe organic result returned the canonical production site and a separate similarly named result. No AI Overview was visible in the capture.State the canonical Citation Path entity and site on the homepage, then keep branded result checks in the monitoring cadence.
Best AI SEO agencies for companies that need implementation, not just reportsCMP-001 · 2026-08-16PerplexityNo Citation Path citation observed; competitor sources were listedDirectThe answer listed implementation-oriented agencies but did not compare Citation Path's public evidence, pricing, or methodology.Publish factual agency-versus-software criteria and link an inspectable audit sample from the agency guide.
What does an AI visibility audit include?SER-001 · 2026-08-16GeminiNo Citation Path citation observedDirectThe answer gave generic multi-engine audit components but did not retrieve Citation Path's methodology, pricing, or sample report.Make the methodology and sample report canonical on the audit service, pricing page, and template resource.
What does an AI visibility audit include?SER-001 · 2026-08-16Bing CopilotNot verifiable on the public surface; sign-in was requiredWeak proxyThe public surface redirected to authentication, so the result cannot support a positive or negative citation claim.Keep this row as an access limitation and retest an authenticated Copilot surface before drawing conclusions.

Dated 2026-08-16. Citation Path's own public evidence only; this is not a client case study or outcome claim. No citation, recommendation, ranking, or conversion is guaranteed.

Read the methodOpen the template
Key takeaways

What a teardown finding must include.

A useful finding names the prompt, the source, the confidence label, the target page, and the next action.

01

A teardown should show the diagnostic logic without pretending framework examples are customer outcomes.

02

Each finding needs a prompt, engine, cited source, confidence label, target page, and recommended action.

03

When real data is unavailable, label the material plainly and keep the illustrative framework separate from observed evidence.

Guide sections

How to read an evidence row.

The format matters because vague issues like AI cannot find us do not tell anyone what to fix.

A finding needs anatomy

The useful format includes prompt context, observed answer behavior, cited owned URLs, cited competitor URLs, issue type, confidence, affected page, and recommended action.

Evidence comes before interpretation

Separate direct observations from weak proxy signals. A screenshot without a date, prompt, source URL, or confidence label is not enough to plan implementation.

Examples still need boundaries

Customer outcomes, screenshots, and filled prompt rows should only appear when they are real, approved, anonymized if needed, and clearly labeled.

Comparison

A teardown vs a dramatic screenshot.

The useful version separates observation, confidence, target URL, and recommended fix.

CriteriaWeak approachUseful approach
Finding formatA vague issue such as AI cannot find us with no prompt or cited source.Prompt, engine, date, observation, cited URLs, confidence, target page, owner, and recommended fix.
Proof handlingCustomer-style claims without supporting evidence.Real, anonymized, or clearly labeled example data with caveats and no invented outcomes.
RoadmapA long backlog where technical fixes, page edits, and proof gaps all have the same priority.A prioritized table grouped by crawlability, answer quality, schema, proof, source assets, owner, and next step.
Decision guide

When a teardown earns trust.

Use it when a buyer needs to see the diagnostic logic before funding the full audit.

Use this page when

a buyer needs to see what an audit finding looks like before trusting the diagnostic process.

Do not overclaim when

screenshots, customer permissions, or real prompt evidence are not available yet.

FAQ

Questions about teardown evidence.

What does an AI visibility teardown evaluate?

It evaluates a specific observation: what prompt was tested, which engine answered, whether the brand appeared, which sources were cited, whether competitors were used, and which page should be fixed.

Can this page show customer results?

Only when results are real, approved, and visibly supported. Without that evidence, Citation Path labels the material as an illustrative finding format or anonymized framework—not a case study.

What makes a teardown useful?

A useful teardown does not stop at 'visibility is low.' It ties the observation to a target URL and action: crawl fix, answer block, source asset, internal link, schema update, or page rewrite.