---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/geo-measurement-vs-causal-evidence/
brand_content: included
publication_version: "9.0"
published_at: 2026-10-16T20:36:07Z
composition_version: composition-v2.1.0
presentation_version: presentation-v1.2.3
brand_content_source: narrative_graph
delivery_publication: graph:33
narrative_versions:
  - 33
narrative_version: 33
---

[Resources](https://optiview.ai/resources/) [GEO and measurement](https://optiview.ai/resources/topics/geo-and-measurement/)

Measurement and research — October 30, 2026

# What an AI Visibility Dashboard Can Measure—and What It Cannot Prove

A visibility score tells you something about observed AI answers. To interpret it correctly, you need to know which answers were measured, how the score was calculated and what remains unknown.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/geo-measurement-vs-causal-evidence.md)

AI visibility dashboards compress complex observations into understandable metrics. That makes them useful for monitoring changes and prioritizing investigation. It can also encourage conclusions the underlying evidence does not support.

Suppose a brand's visibility score increases after a website update. The sequence is interesting. But it does not establish that the update caused the increase. Prompt selection, response variability, competitor changes, platform behavior and measurement timing could also matter.

Profound and Semrush publish documentation explaining their respective measurement approaches. Their metrics should be interpreted according to those definitions, not treated as interchangeable representations of an objectively complete AI search universe.

## 1\. Start with the denominator

A percentage cannot be interpreted without knowing what population it represents. Profound's [AEI documentation](https://docs.tryprofound.com/answer-engine-insights/about) defines its Visibility score using responses containing the brand relative to responses containing at least one brand within the analyzed data.

Semrush's [AI visibility data documentation](https://www.semrush.com/kb/1607-semrush-ai-visibility-data) describes a different scoring approach involving topic coverage and mention consistency. Comparing these numerical values directly would overlook differences in construction.

| Metric | Interpretation question |
| --- | --- |
| Visibility | Visible in which defined response population? |
| Mentions | Counted across which unique prompts or observations? |
| Citations | Which URLs and citation events qualify? |
| Average position | Position within what answer structure and dataset? |
| Estimated audience | Derived from which estimates rather than actual visitors? |

## 2\. Record the observation frame

A defensible report identifies the prompts, platforms, regions, languages and dates included. It also records how prompts were selected or grouped and whether the dataset changed between comparisons.

*   Prompt set and selection method.
*   Platforms and relevant model or service context.
*   Region, language and other applicable settings.
*   Observation period and reporting refresh frequency.
*   Metric definitions and available raw response evidence.
*   Changes to the tracked population between reporting periods.

A fixed custom prompt panel and a broader estimated prompt database may answer different questions. Both can be useful; they should not be silently combined into one claimed measurement population.

## 3\. Understand why a score can change

Consider a purely illustrative dataset: a brand appears in four of ten eligible observed responses during one period and six of ten during another. Under a simple response-share calculation, the observed share rises from 40% to 60%.

That arithmetic is descriptive. Before interpreting it, ask whether the ten prompts were identical, whether the same answer engines were used, whether competitors changed and whether repeated observations show similar behavior.

These are invented teaching numbers, not Profound or Semrush results. They are not intended to replicate either vendor's complete scoring methodology.

## 4\. Separate temporal association from causation

Suppose a team publishes a clearer product page on Monday and observes more citations the following week. That result establishes sequence and possible association. It does not isolate the page change from other influences.

1.  State a specific hypothesis before changing the website.
2.  Preserve the previous page revision and measurement settings.
3.  Change one defined treatment where feasible.
4.  Use an appropriate comparison or control condition when the research design permits.
5.  Collect repeated observations and preserve inconclusive outcomes.
6.  Report what the evidence supports and which alternative explanations remain.

A controlled study still has limitations, particularly when external AI systems and retrieval paths cannot be fully observed. For research discipline and reporting boundaries, consult the [Optiview methodology appendix](https://optiview.ai/proof/methodology/).

## 5\. Build a measurement interpretation record

| Record field | Required entry |
| --- | --- |
| Question | What are we trying to learn? |
| Measure | Exact metric and vendor definition |
| Population | Prompts, responses and filters included |
| Change | Observed difference and time window |
| Intervention | What website or content revision occurred? |
| Limitations | Uncontrolled factors and missing observations |
| Conclusion | Descriptive finding, hypothesis or causal result |

Use the [Semrush Visibility Overview guide](https://www.semrush.com/kb/1596-visibility-overview-report) and [Profound interpretation documentation](https://docs.tryprofound.com/answer-engine-insights/interpret) to preserve the original meaning of reported metrics. Do not substitute an internal definition without labeling it.

## 6\. Decide what the dashboard supports

Visibility tools can support monitoring, comparison, investigation and evaluation of change. They do not automatically prove that a specific source revision caused a measured difference or that every real user encountered the same answers.

When a dashboard reveals a potentially correctable content issue, use a separate [remediation brief](https://optiview.ai/resources/ai-visibility-report-action-plan-template/) to document the intervention. Keep the measurement interpretation record intact so the original observation is not rewritten after the outcome is known.

## Additional source context

Always define the numerator, denominator, sampling frame and observation window. Use dashboard changes as evidence of measured movement, not automatic proof of what caused it.

Make your brand easier for AI to understand.

### Explore

[Website publishing](https://optiview.ai/products/publish/) · [Developer tools](https://optiview.ai/products/#developers) · [Pricing](https://optiview.ai/pricing/)

### Learn

[Guides](https://optiview.ai/resources/) · [Developer docs](https://optiview.ai/developers/) · [Research](https://optiview.ai/proof/) · [FAQ](https://optiview.ai/faq/)

### Company

[About Optiview](https://optiview.ai/about/) · [Agencies](https://optiview.ai/partners/) · [Contact](https://optiview.ai/#contact) · [Privacy](https://optiview.ai/privacy/) · [Billing terms](https://optiview.ai/billing-policy/)

## Additional page links

- [Measuring AI visibility doesn’t change the source.](https://optiview.ai/resources/ai-visibility-publishing/) — Continue reading
- [Turn an AI visibility finding into an action.](https://optiview.ai/resources/why-visibility-reporting-isnt-enough/) — Continue reading
- [From Profound AI Visibility Findings to Source-Level Content Improvements](https://optiview.ai/resources/profound-ai-visibility-to-source-action/) — Continue reading
- [Preview a page](https://optiview.ai/demo/) — Continue reading
- [Read the setup guide](https://optiview.ai/docs/setup/) — Continue reading


---

# Published brand narrative

# Site-wide brand information

## Who we are

### Optiview — Parse, Retrieve and Publish for AI

Optiview helps businesses and developers make website information easier for AI to use. Parse converts supplied HTML into clean Markdown and source metadata. Retrieve fetches an eligible public HTTPS webpage and prepares its content. Publish helps a verified business prepare its own website content and make approved Narrative Graph context available through a supported connection.

Parse and Retrieve use application keys and a prepaid developer wallet. Publish has separate website setup, ownership checks and a subscription. Optiview does not control whether an outside AI service discovers, uses or cites the resulting content.

Applies to: Optiview

## Why we matter

### A clearer source, from website content to business context

Webpages mix useful information with navigation, layout and application code. Businesses may also have important qualifications, answers and context that are not clearly published.

Optiview gives developers a way to prepare source content for their applications, and gives businesses a way to publish the context their teams approve. Your application chooses how to use Parse and Retrieve results. Your business controls what it publishes through Publish.

Clearer publishing makes information available; it does not determine an AI system’s answer. Each outside service chooses its own retrieval, recommendations and citations.

## What we offer

### Three products, with separate jobs and clear pricing

- **Optiview Parse:** Supply complete HTML and a source URL. Receive clean Markdown, source and output hashes, parser details and processing warnings. Parse does not fetch the URL or execute JavaScript. A successful page uses 1 credit.
- **Optiview Retrieve:** Supply one eligible public HTTPS URL. Optiview checks supported access and publisher policies, fetches anonymous static HTML and parses it. It does not search the web, execute JavaScript, bypass a login or access private networks. A successful page uses 5 credits total, including parsing.
- **Developer credits:** USD $20 buys 20,000 credits shared by Parse and Retrieve. There is no developer subscription, automatic recharge or scheduled credit expiration. Failed jobs consume no credits. Applicable taxes and the total appear at checkout. Source size, quotas and retention limits apply.
- **Optiview Publish:** USD $99 per website per month plus applicable tax. Connect a verified website, review the prepared source and optionally maintain approved Narrative Graph context in Identity, Story, Offerings, Trust, Knowledge and Actions. Choose site-wide or exact-page scope. Saving drafts does not publish them. Eligible AI tools can receive prepared Markdown or HTML through supported delivery, while ordinary visitors keep the normal website.

Developer credits do not purchase Publish subscriptions. Parse and Retrieve do not add a customer’s private Narrative Graph to arbitrary third-party pages. See https://optiview.ai/pricing/ and https://optiview.ai/developers/ for the current offer and limits.

## Why trust us

### Inspect the output and understand what the evidence establishes

Developers can inspect the prepared Markdown, job status, source metadata, processing warnings and credit ledger. Retrieve records the public source response it observed; Parse identifies supplied HTML rather than claiming to verify the current origin.

Publish administrators can review parser output, the combined published-output preview, source checks and publication history. A preview is separate from a recorded live delivery. Saved edits remain separate from the active publication until explicitly published.

Our experiment pages contain selected first-party AI conversations and source comparisons. Delivery records establish what was served, not downstream ingestion, recommendations, citations or revenue. Observed language matches do not establish causation or a consistent visibility improvement. Explore the evidence and limitations at https://optiview.ai/proof/.

## Helpful knowledge

### Common questions about the three products

**Which product should I use?**
Use Parse when you already have HTML. Use Retrieve when you need Optiview to fetch one eligible public page first. Use Publish when your business wants to prepare its verified website and publish approved context.

**Do Parse and Retrieve require website ownership or DNS changes?**
No website connection is needed for these developer products. You remain responsible for source rights and permitted downstream use. Public availability does not grant a reuse license.

**How do developer accounts and keys work?**
Create a developer workspace and save the personal sign-in key and offline recovery code. Create scoped service keys for server-side applications. Email is an unverified contact identifier, not account-ownership proof or an email-only recovery method. Keep all credentials private.

**Can my agent use Optiview?**
The authenticated developer API returns prepared content for your application or model. A downloadable JavaScript client and local MCP adapter are available. Your host must authorize sources and any credit expenditure. Compatibility does not establish adoption or a partnership with an AI provider.

**Does the API include my private Narrative Graph?**
Parse and Retrieve are source-only. Verified website publishing and approved publisher context belong to the separate Publish workflow.

**Does Publish replace our website or CMS?**
No. Your website stays in its existing system. Your web team establishes and tests a supported connection. Your team reviews and explicitly publishes any Narrative Graph additions. Ordinary visitors retain the normal website experience.

**Does every AI tool get the prepared version?**
No. Delivery depends on the website connection, source eligibility and the request. Some tools explicitly request Markdown; supported AI requests may also receive prepared Markdown or HTML through eligible delivery paths. Traditional search crawlers retain the original website response. A claimed tool name does not prove the requester’s identity.

**Does the demo publish or save to our workspace?**
No. The public demo is a separate preview. Its AI-generated examples require review and do not transfer automatically into an approved publication.

**Will Optiview guarantee citations or recommendations?**
No. Optiview prepares and publishes sources. Outside AI services choose what to retrieve, use and cite.

## What to do next

### Choose your starting point

- [Compare Parse, Retrieve and Publish](https://optiview.ai/products/) to choose the right workflow.
- [Create a developer workspace](https://app.optiview.ai/developers) for self-service Parse and Retrieve, then add credits and create an application key.
- [Read the API quickstart and agent-tool setup](https://optiview.ai/developers/) for request examples, supported sources, errors, quotas and downloads.
- [Review pricing and terms](https://optiview.ai/pricing/) for prepaid credits and the separate Publish plan.
- [Preview your website](https://optiview.ai/demo/) to inspect prepared content and explore unapproved narrative examples without connecting or publishing.
- [Plan Publish setup](https://optiview.ai/onboarding/) with your web team. Publishing requires ownership checks, review and a supported connection; contact [hello@optiview.ai](mailto:hello@optiview.ai) for assisted setup.

Already using Publish? Review your Narrative Graph, publish approved changes explicitly, inspect the combined source in Markdown and check recorded delivery in Activity. Keep your existing visibility tools to study downstream AI answers.