---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/ai-readable-web-research-agenda/
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/) [Research and evaluation](https://optiview.ai/resources/topics/research-methods/)

Research design — October 30, 2026

# The AI-Readable Web Research Agenda: 10 Questions We Still Need to Answer

The AI-readable web is developing faster than many of our assumptions can be tested. Instead of treating plausible mechanisms as proven outcomes, we should identify the questions that still need evidence.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/ai-readable-web-research-agenda.md)

Serving Markdown, adding structured context and improving source quality all sound like reasonable ways to help software interpret a website. But they are different interventions, and their effects may depend on the retrieval system, content type, question and evaluation method.

Optiview's [published methodology](https://optiview.ai/proof/methodology/) separates observed delivery, retrieval accessibility and downstream interpretation. That distinction should carry into future research.

The ten questions below form a prospective public research agenda. They are hypotheses and study designs, not newly executed experiments, reported results or commitments to purchase API access. Existing historical findings retain their original scope and limitations.

## Questions 1–3: Representation and information preservation

| Question | What must be observed or controlled | What remains unknown |
| --- | --- | --- |
| 1\. Does equivalent Markdown preserve more answer-relevant information than HTML in a defined extraction workflow? | Freeze equivalent facts and links; compare extracted content under identical processing conditions. | Whether differences generalize across tools and page types. |
| 2\. Which page structures cause material information loss during preparation? | Use controlled fixtures containing headings, tables, lists, qualifications and linked content; retain outputs. | Which observed failures occur in other conversion pipelines. |
| 3\. Does adding approved contextual information improve answers to otherwise ambiguous business questions? | Hold the base source and question fixed; vary only the approved supplemental context; score repeated answers. | Whether findings transfer to external browsing and retrieval systems. |

Question 1 is a representation study. Question 3 changes available information and therefore cannot establish a format-only effect. The conditions must be reported separately.

## Questions 4–6: Discovery, freshness and citation

| Question | What must be observed or controlled | What remains unknown |
| --- | --- | --- |
| 4\. Under which documented conditions do retrieval clients request alternative source representations? | Use authorized request traces, current provider documentation and fixed public fixtures. | Behavior of providers whose acquisition paths are not observable. |
| 5\. How quickly do different observed retrieval paths reflect an authorized source revision? | Record immutable versions, publication times, provider requests and returned content under defined conditions. | Universal refresh intervals or unobserved intermediary behavior. |
| 6\. When a URL is cited, how often does the cited source support the associated claim in the observed sample? | Retain questions, answers, citation links, source captures and independent support classifications. | The complete internal source-use path or a causal relationship. |

A visible citation and verified source retrieval are different observations. Neither should be inferred automatically from the other.

## Questions 7–8: Context and publication governance

| Question | What must be observed or controlled | What remains unknown |
| --- | --- | --- |
| 7\. Does clearly scoped page-specific context reduce ambiguity compared with broadly applied context in a controlled evaluation? | Create approved fixtures, defined scope conditions and a fixed rubric for factual qualifications. | Whether results apply to different external systems or broader content classes. |
| 8\. Do documented source-review controls reduce material publication errors in a bounded workflow? | Define error categories, compare comparable review procedures and retain approval and correction records. | Whether differences persist across organizations, workloads or time. |

The [W3C provenance overview](https://www.w3.org/TR/prov-overview/) offers concepts for documenting the origins and activities associated with information. It does not validate these hypotheses or certify any proposed governance workflow.

## Questions 9–10: Answer quality and business relevance

| Question | What must be observed or controlled | What remains unknown |
| --- | --- | --- |
| 9\. Which source-information defects are most associated with incorrect answers in a defined question set? | Classify missing facts, contradictions, outdated terms and omitted qualifications against independently scored answers. | Whether association establishes causation across systems. |
| 10\. Under what conditions can a publisher-controlled source improvement be linked to a meaningful downstream business outcome? | Define interventions, comparable observation populations, appropriate controls and authorized business-action measurements. | Whether the full attribution chain can be isolated or measured reliably. |

Question 10 is intentionally the hardest. A corrected source, a citation and a qualified business action are separate events. A credible causal conclusion requires more than observing them in chronological order.

## What evidence standards should govern the agenda?

*   Specify a narrow hypothesis before collecting observations.
*   Use authorized public or explicitly approved source fixtures.
*   Freeze relevant source versions and retain the transformation procedure.
*   Define scoring rules and expected exclusions in advance.
*   Preserve complete observations, including failures and abstentions.
*   Distinguish directly observed delivery from inferred retrieval or answer use.
*   Report sample sizes, denominators, controls and confounders.
*   Publish null and inconclusive results without inventing a positive interpretation.

The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) provides voluntary principles relevant to trustworthy AI evaluation. These proposed study standards are independent research recommendations, not NIST certification requirements.

## How should the research be prioritized?

Prioritize questions by decision value, availability of authorized evidence, ability to isolate variables and cost of uncertainty. A small, reproducible source-preservation study may be more useful than an ambitious experiment requiring opaque retrieval behavior or unavailable commercial data.

The agenda does not authorize new paid experiments, provider requests, customer-data processing or the reopening of previously closed studies. Each proposed experiment would require a separate decision about scope, resources, permissions and publication.

The finished work product is a ten-question research backlog, each with a hypothesis, required observations, controls, limitations and decision owner. The objective is to make future claims more defensible—not to assume the outcome before the work begins.

Use the [reproducible retrieval study protocol](https://optiview.ai/resources/ai-retrieval-experiment-design-template/) to turn a selected question into a bounded study plan before collecting observations.

## Additional source context

The research priority is not proving that one format or product always wins. It is identifying which publishing changes matter, under which observable conditions and with what uncertainty.

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

- [Publishing information doesn’t mean AI receives it.](https://optiview.ai/resources/what-openai-browser-code-taught-us/) — Continue reading
- [How to Design a Reproducible AI Website Retrieval Experiment](https://optiview.ai/resources/ai-retrieval-experiment-design-template/) — Continue reading
- [An Evaluation Rubric for AI Answers About a Business](https://optiview.ai/resources/ai-answer-accuracy-evaluation-rubric/) — 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.