Ten questions we still need to answer about AI and websites

Separate promising ideas from proven results. These are questions for future tests, not findings from studies already completed.

Research design

By OptiviewFor business owners, marketers and agenciesAbout 4 minPublished October 30, 2026Sources checked October 30, 2026Updated October 31, 2026

Editorial illustration · Check AI answers

An interactive overview

Explore the framework.

Select an item to unpack the details, then take the framework with you.

3 items

01Does equivalent Markdown preserve more answer-relevant information than HTML in a defined extraction workflow? 02Which page structures cause material information loss during preparation? 03Does adding approved contextual information improve answers to otherwise ambiguous business questions?

Item 1 of 3

Does equivalent Markdown preserve more answer-relevant information than HTML in a defined extraction workflow?

What must be observed or controlled Freeze equivalent facts and links; compare extracted content under identical processing conditions.

What remains unknown Whether differences generalize across tools and page types.

A few terms in plain English

Markdown A simple text format that keeps headings, lists and links.

HTML The code used to describe a webpage.

retrieval When a tool fetches information from a page or another source.

provenance Where a piece of information came from and what supports it.

causal About whether one thing caused another. Two changes happening together is not enough to prove this.

Serving Markdown, adding approved context and improving source accuracy may help software interpret a website. But each changes something different, and the outcome may depend on the source, retrieval service, question and evaluation method.

Optiview's published methodology separates observed delivery, retrieval accessibility and downstream interpretation. That distinction should carry into future research.

These ten questions form a proposed research agenda. They are not newly executed tests, results or commitments to buy API access. Earlier findings keep their original scope and limitations.

Questions 1–3: Does important information survive?

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: What reaches retrieval systems and answers?

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: Do review and scope choices help?

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 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: Can we establish answer or business effects?

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.

Set evidence standards before running a study

The NIST AI Risk Management Framework provides voluntary principles relevant to trustworthy AI evaluation. These proposed study standards are independent research recommendations, not NIST certification requirements.

Prioritize only research that can inform a decision

Prioritize studies that could change a real decision, have authorized evidence available and can reasonably isolate the variable being tested. A small, repeatable source-preservation study may be more useful than a broad experiment whose retrieval path or commercial data cannot be inspected.

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 to turn a selected question into a bounded study plan before collecting observations.

Go to the source

Keep exploring.

References linked in this guide. Open the original source for its full scope and latest details.

w3.orgW3C provenance overviewOpens in a new tab nist.govNIST AI Risk Management FrameworkOpens in a new tab

Keep going

A useful next read.

Research notes

Why publishing a page doesn’t mean AI has read it

Research design

How to run a useful test of what AI reads from your website

Evaluation guide

Is that AI answer about your business actually correct?

Back to the resource library

Additional source context

Turn uncertain claims into questions you can test. Keep the plans separate from completed findings, including earlier research that is already closed.

An overview of the table in this guide. The full reference and its qualifications remain below.

Your website was built for people. Optiview makes it ready for AI, too.

Try Optiview

See my site with Optiview · Run your free AI Audit

Explore

Publish · Parse · Retrieve · Pricing

Learn

Guides · Developer docs · Research & thinking · Experiments & methods · AI Audit · AI agent directory · FAQ

Company

About Optiview · Agencies · Contact · Privacy · Billing terms

Additional page links


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

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

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.