Most AI-visibility tools sell a single score. Do not buy it. A number that blends how well you rank on a branded identity prompt with how invisible you are on a transactional purchase prompt is not a metric, it is an average that hides the gap you are paying to close. Our own Geoboard baseline, dated 2026-06-11, ranked wppoland.com first in five of six models on the narrow identity prompt “Polish agency for foreign WordPress clients” and showed zero presence on transactional WooCommerce and AI-implementation query families in the same run. One score would have reported that as “strong AI visibility.” The split tells the truth: the mechanism that produces one gap is not the mechanism that produces the other, and they need different fixes. This guide is the monitoring layer of that programme: which query families to track, which metrics actually predict revenue, the stack we run on our own site, and a cadence table you can hand to a vendor or a procurement lead.
We already published the raw material this guide draws on: the 90-day tracking launch that set the baseline, and the Q2 2026 measurement cycle that showed how much the measurement instrument itself can move the reported number. This article turns both into an operating manual: what to track, how often, and what to demand from anyone selling you an “AI visibility” report.
Why a single AI visibility score fails procurement
A composite score exists to make a slide look clean, not to make a decision defensible. It compresses at least four different signals, identity recognition, informational-query presence, transactional citation rate, and competitor share of voice, into one number, and averaging across them destroys exactly the information a buyer needs.
Here is the mechanical problem. Our identity prompt result (first in five of six models) and our transactional result (zero presence) sit in the same Geoboard baseline run, on the same date, for the same domain. Average them and you get a mid-range score that looks like “room for improvement.” Report them as a split and you get the accurate story: a defensible position that costs little to maintain, sitting next to a real gap that costs real off-page work to close. A vendor who hands you one number either has not separated the query families or does not want you to see the split.
Procurement should treat a single AI-visibility score the way it would treat a single “SEO score” from a browser extension: a marketing artifact, not an audit input. Ask for the table instead of the number, every time.
Query families to monitor
Split prompts by intent before you count anything. Four families cover most B2B WordPress and WooCommerce buying behaviour, and each one answers a different business question.
Identity and positioning prompts are narrow, branded questions a buyer asks once they already know you might be in scope: “Polish agency for foreign WordPress clients,” nearshore framing, EU-timezone delivery claims. This family measures whether models resolve who you are. Winning here is necessary and, on its own, worth very little to a sales pipeline.
Informational and practitioner prompts mirror how a technical evaluator researches before an RFP exists: headless WordPress trade-offs, WooCommerce ERP integration approaches, Core Web Vitals on large catalogs. AI answers increasingly substitute for the first search results a practitioner would have opened, so absence here means you are not in the shortlist conversation even when your identity prompt ranks first.
Transactional WooCommerce prompts are where budgets actually sit: hire a WooCommerce developer, WooCommerce and ERP integration partner, fix a slow checkout on a large store, agency for Woo plus AI automation. Our own baseline showed zero presence here.
AI-implementation prompts run parallel to WooCommerce: WordPress AI integration, agent-ready product feeds, governance for AI plugins, MCP exposure for store data. Same baseline result, zero at 2026-06-11, and increasingly bundled into enterprise procurement packages that pair platform work with “AI readiness.”
| Query family | What it tests | Our baseline signal (2026-06-11) | What to demand from a vendor report |
|---|---|---|---|
| Identity / positioning | Entity resolution for your niche | #1 in 5/6 models on anchor prompt | Confirm the exact prompt wording, not a paraphrase |
| Informational / practitioner | Technical shortlist before an RFP exists | Mixed, not the headline metric | Ask which practitioner questions were tested |
| Transactional (e.g. WooCommerce) | Revenue-adjacent hire intent | Zero presence | Ask for competitor domains cited instead of you |
| AI implementation | Agent and automation procurement | Zero presence | Ask whether this family was tested at all |
If a report does not break out these four rows separately, it is not a monitoring report, it is a summary designed to be believed rather than audited.
Metrics that matter
Once query families are separated, four metrics carry the actual signal. Everything else is a vanity aggregate dressed up as data.
Brand mention. Did the assistant name your brand anywhere in the answer, regardless of a link. This is the loosest signal and the easiest to hit, so treat a rising mention rate alone as weak evidence.
URL citation. Did the assistant link your specific page. This is closer to a real referral and much harder to earn than a bare mention, especially in transactional families where models tend to cite directories rather than specialists.
Competitor domains cited. Which other domains showed up instead of you, logged by name, not summarized as “competitors.” In our own transactional checks, the domains that surfaced were general SEO or SEM shops advertising “AI SEO,” not WooCommerce specialists, which is itself a finding: the gap is association and authority, not content quality.
Share of voice. Your citation count divided by total citations across the tracked prompt set, calculated per query family, per engine. This is the only one of the four that behaves like a real KPI over time, because it is relative and comparable across re-runs, as long as the prompt list stays fixed.
What is deliberately absent from this list: a single “AI visibility percentage,” a 0-to-100 “AI SEO score,” or any metric that cannot be traced back to a specific prompt, engine, and date. If a dashboard cannot show you the prompt behind a number, the number is not evidence.
The monitoring stack we actually use
We run four layers on our own site, and each one covers a failure mode the others miss.
Geoboard batch re-runs give repeatable multi-model coverage against a declared prompt set. Our frozen baseline from 2026-06-11 is what produced the identity-versus-transactional split described above, along with the engine skew between ChatGPT and Perplexity. Batch tooling is the right layer for trend comparison, not for daily monitoring, because daily multi-model polling mostly measures interface noise.
Weekly manual spot checks in consumer interfaces, ChatGPT, Perplexity, Copilot, and Claude where applicable, catch product changes fast. We log four fields every time: date, engine, prompt family, and outcome (brand mention, URL cited, competitor domains cited, or none). This layer is the early-warning system when a model adds or removes live browsing.
Brand-radar style tracking for competitor citation domains. Geoboard and manual checks tell you whether you appeared. This layer tells you who appeared instead, which is the input the off-page authority plan actually needs. Knowing that generalist SEO shops, not Woo specialists, are winning the transactional family changes where remediation budget should go.
The rendering gate. None of the above matters if your load-bearing facts are not in the raw HTML response in the first place. Andre Alpar’s June 2026 experiment, published via CitationOne, found that six of seven Western AI assistants read raw HTML only, not executed JavaScript. Before trusting a zero-citation result as a content or authority problem, confirm the content was actually visible to the assistant’s fetch in the first place. A zero caused by client-side rendering is a different fix entirely from a zero caused by missing off-page corroboration.
Cadence: how often to run each layer
Cadence is where most monitoring programmes either burn budget on noise or miss real drift. Three intervals, mapped to what each is good for:
| Cadence | What runs | Why this interval |
|---|---|---|
| Weekly | Manual spot checks, fixed prompt list, consumer UIs | Catches model or UI changes fast; cheap enough to sustain indefinitely |
| Every 6-8 weeks | Geoboard-style batch multi-model re-run | Long enough that off-page and on-page changes have been crawled and associated; short enough to catch regressions before a quarter closes |
| Quarterly | Programme-level readout to stakeholders, tied to budget or vendor review | Matches procurement and marketing reporting cycles; avoids over-claiming a trend from noise |
Daily or even every-few-days polling across many models mostly measures interface variance, not real change in how models associate your brand with a query. We learned this directly: our Q2 2026 measurement cycle showed a proxy snapshot and a consumer-UI snapshot disagreeing enough within the same weeks that the instrument, not the underlying reality, explained most of the difference. Cadence discipline exists to keep that kind of noise from being mistaken for a trend.
Perplexity versus ChatGPT: why the engine split is mandatory
Treating “AI visibility” as one number across engines hides a specific, measurable failure mode. In our own baseline run, ChatGPT showed zero presence across eight tracked prompts in the blind-spot slice of the query set, while Perplexity was the strongest engine in the same run. That is not a coincidence of one bad week. Perplexity grounds heavily on live web search, so it tends to surface fresher, narrower matches. ChatGPT’s default behaviour in the same period leaned differently, and the gap between the two was large enough to change the entire read of the brand’s citation health depending on which engine you happened to check.
The practical consequence for monitoring scope: never report ChatGPT alone as “AI visibility,” and never average ChatGPT and Perplexity results into one figure. A monitoring scope that stops at ChatGPT will under-report a brand that Perplexity already cites, and a scope that stops at Perplexity will overstate how visible you are to the audience still defaulting to ChatGPT. Track both, report both, and if budget forces a choice between adding a third engine or fixing this split, fix the split first. For the full informational breakdown of why the split happens, see why Perplexity cites your brand but ChatGPT does not.
Procurement checklist: what to demand from vendors
Before signing off on any AI-visibility or GEO monitoring vendor, require answers to all of the following. If a vendor cannot answer one of these in writing, treat their reported numbers as marketing collateral, not measurement.
- The exact prompt list, not a category label like “WooCommerce queries.” Wording changes results.
- Which engines were tested, and whether results are reported per engine or blended into one score.
- Whether each number came from a consumer-facing interface or an API proxy. Our own Q2 cycle showed these disagreeing enough that mixing them is misleading by default.
- The date each figure was produced. A citation snapshot from three months ago is not a current status.
- Competitor domains cited in place of you, not just your own presence or absence.
- Query families reported separately: identity, informational, transactional, and any implementation or agent-specific family relevant to your business.
- Whether the monitoring accounted for rendering. If your site or the competitor set uses heavy client-side rendering, ask whether the vendor’s method can even detect content behind JavaScript.
What on-page versus off-page fixes each gap type
Monitoring tells you which family is broken. It does not fix anything by itself, and the fix depends on which gap type you are looking at.
Identity and informational gaps usually respond to on-page work: server-rendered HTML with load-bearing facts present in the raw response, structured data, fact-dense content blocks, and clear entity signals that resolve who you are and what you do. This is the floor, and it is table stakes precisely because most Western AI assistants only read raw HTML rather than executing client-side JavaScript. If your key facts load behind a script, no amount of on-page polish will fix the gap, because the assistant never saw the content to begin with.
Transactional and AI-implementation gaps rarely close with another FAQ block or a rewritten landing page. Models cite what the open web corroborates: independent technical answers, verifiable directory listings, third-party mentions, and off-page signals that reinforce the entity beyond your own domain. Our baseline zero on WooCommerce and AI-implementation prompts persisted despite already-mature on-page content, which is itself the diagnostic: when on-page quality is not the bottleneck, the fix has to move off-page.
The AI and LLM visibility playbook orders these levers the way we implement them in client programmes, on-page first as the floor, off-page second as the lever that actually moves transactional citation rates.
Closing note
Monitoring is not the finish line, it is the instrument that tells you where to spend. A single AI-visibility score will always flatter your easiest win and hide your most expensive gap, which is exactly backwards from what procurement needs. Split by query family, track brand mention, URL citation, competitor domains, and share of voice rather than a blended aggregate, run weekly spot checks and six-to-eight-week batch re-runs, and never quote a number without stating the engine, the date, and whether it came from a consumer interface or an API proxy. If you want this instrumentation built and operated against your own property, tied to the on-page and off-page fixes each gap type actually needs, that is the programme our GEO and LLMO optimization service delivers.
