Mention, direct citation, search presence and competitive position, read across the national query panel.
The cost of a narrow map. If a roster never reaches a surface, your absence there and its blind spot read the same from the outside. A content budget then goes to a gap nobody measured. Every surface below is named, and CiteAngle seals each one to the same protocol.
Why the width of a roster decides what a number means
Ask a narrow roster whether your brand appears in AI answers and it will happily tell you no. Absence and a blind spot come back as that same word. A company then rebuilds a content programme around a gap that was really a blind spot. Or it relaxes about a category nobody measured.
This page exists to be checked. The arithmetic behind the widest panel is public — 50 buyer questions, 21 engines, 7 runs each. Hold that against anybody else's roster before you buy either. What no outside party can observe sits in the execution layer. We label it that way instead of reporting it as a measured figure.
The whole map — what we measure, and what we fix
Search, AI answers, local, commerce, media, social and the technical layer underneath. Those are the seven areas where a US brand gets found, and they sit on one map. Anything we can observe runs through the same grid, on the same queries. The rest gets prescriptions bound to the platforms’ own documentation. A result never crosses between the two.
ChatGPT · Perplexity · Claude · Grok · Google AI Mode · Bing Copilot — citation and mention read separately
Quotable page patterns · third-party evidence carriers · misinformation correction
Voice and personalized screens: covered in the execution layer
Google Search + AI Overviews · Bing Search · Yahoo Search · DuckDuckGo search assist — organic read against the AI read, same queries
Technical SEO gate patches · structured data
Local-intent queries in the grid · local entity precision inside answers · Business Profile completeness read
Profile, review-source and NAP-consistency prescriptions
Map-screen rank: confirmed downstream through traffic you own
Purchase-decision queries read across the AI answer surfaces
Product feed hygiene · in-store AI readiness
In-store AI answers: covered in the execution layer
Google News and Bing News surfaces · publisher-class citation breakdown · publisher AI-openness review
Republication on AI-open outlets · wire design · correction channels
YouTube search and Google short-form in the grid · channel access table built from public crawler policies
In-app search prescriptions for YouTube, Instagram, TikTok and the app stores
In-app search rank: covered in the execution layer
AI crawler ledger · rendering-gap checks · citation-to-visit crosswalk
Freshness, IndexNow and crawler-access alignment
Traffic connection runs on your account permissions
Stateless measurement, stated in writing. Every paid audit measures through stateless API calls — the state the platforms themselves define as pre-personalization, the same layer as a temporary chat with memory off. Real users’ answers start there and diverge, which is why a before-and-after comparison has to be read at that baseline. Sealed repeated runs accumulate into a time series. Both reads keep the same monthly rhythm — a spot check on the core question set, and a full grid re-run that resets the baseline. What separates the tiers is how much of the fixing we take on, not how often we measure.
Every surface, and which tier measures it
The free AI visibility check is a fast read on the AI engines. Paid audits add the search cross-check and, on Panorama, every source the answer engines pull from.
Scope, deliverables and the decision each tier drives: the diagnostics page.
Measuring is step one of five — the loop closes
Grid measurement
5, 20 or 50 buyer questions — every measurable position, run in full.
Execution design
Priorities, target URLs and completion criteria, bound into the report.
Build and publish
Technical gate patches, core pages and evidence assets — each with a change receipt.
Matched delta
Before and after read on the same queries, same conditions — reported as observed change.
Accumulate and watch
Sealed repeated runs, accumulated — and major engine-update windows are avoided on the remeasure.
The monthly programs turn step five back into step one. Buy an audit within thirty days of starting a program and it comes off that first payment in full, on any program.
Every rung on this loop carries a published US-dollar list price: see the pricing page.
US regional visibility map
Behind a national average sit state-by-state gaps. As a quote-based add-on, we open a controlled 50-state + DC panel. State metrics stay on their own denominator, read alongside the national baseline.
How the state panel stays honest — location receipts, gates and denominators
Every engine call in the panel fixes explicit location parameters — city, state, country and timezone. Your state selection is sealed with a sha256 receipt, checked fail-closed against the stored hash on every run. A state score publishes only from panels that pass that location-receipt gate.
The selected state becomes hash-bound intake provenance. A dedicated USD regional scope adds location-capable API or exact browser receipts. It also adds contracted coverage and acceptance gates before the panel is frozen. National and state figures are reported on separate tables and separate denominators.
State and DC scorecards, competitive intensity and priority-state actions under verified location signals.
Which of the seven areas is hurting?
Most buyers arrive with exactly one. Usually it is a category question they never appear in, a competitor who always does, or a fact the answers keep getting wrong. Match it to a starting point on the fit page, then read the list price on the pricing page.