---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/audit-html-markdown-delivery/
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/) [Implementation and operations](https://optiview.ai/resources/topics/implementation/)

Technical guide — October 30, 2026

# Audit HTML and Markdown delivery before testing AI answers

Before asking whether AI understands your website, establish which response your own test actually received.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/audit-html-markdown-delivery.md)

A delivery test and an answer-quality test answer different questions. The first records a response. The second investigates what an AI system does with information. Keeping separate records makes both easier to interpret.

Use this procedure on a public page you control. Start with one concrete buyer question and the facts needed to answer it, rather than a target word count.

## 1\. Define the facts before fetching the page

Choose a service, product or policy page. Write down three facts that matter to a customer, such as a named offering, an eligibility condition and a supporting link. Include any qualification that changes the meaning of the main claim.

This small inventory is your comparison checklist. If a fact is missing from the original published page, a different delivery format cannot establish that the business has published it. Ask the responsible team to confirm the information before adding it.

## 2\. Save two explicit requests

The HTTP Accept header communicates a media-type preference. It does not force a server to produce that representation. Inspect the response Content-Type and body instead of assuming the preference was honored. See [HTTP Semantics, sections12 and12.5.1](https://www.rfc-editor.org/rfc/rfc9110.html#section-12.5.1).

These curl commands save headers and bodies separately. They follow redirects, use a bounded timeout and fail on HTTP errors. The example uses Optiview’s public homepage; replace it with a public page you own. No API key or account is needed for these ordinary webpage requests.

bashCopy

```
curl --fail --show-error --silent --location --max-time 30 \
  --header "Accept: text/html" \
  --dump-header html-headers.txt --output page.html \
  https://optiview.ai/

curl --fail --show-error --silent --location --max-time 30 \
  --header "Accept: text/markdown" \
  --dump-header markdown-headers.txt --output page.md \
  https://optiview.ai/
```

Read the final response header block when a redirect produced more than one. If the request fails, preserve the status and error. Do not replace the failure with a sample result or a successful fetch from another URL.

## 3\. Compare the response with your checklist

*   Record the URL, UTC time, request headers, final status and Content-Type. Keep the response body with that record.
*   Look for each required fact, its qualification and its link in both bodies. A price without its billing period is an incomplete observation.
*   If both responses are HTML, record that outcome. The page may not offer Markdown negotiation, or its delivery policy may select HTML for your request.
*   If Markdown is returned, inspect what it retains. Fewer bytes or fewer words do not establish that the required information survived.

On a supported Optiview Publish connection, eligible requests can receive a prepared representation according to the site’s configured delivery policy. The [Publish setup guide](https://optiview.ai/docs/setup/) explains current behavior and acceptance checks. An arbitrary website is not expected to behave like the Optiview example.

## 4\. Investigate inconsistent responses

Repeat the pair of requests in both orders if responses appear inconsistent. Record cache-related headers and whether cookies, authentication, redirects or request preferences differ. These observations identify variables to investigate; they do not diagnose a cache defect on their own.

HTTP’s Vary field identifies request fields that influenced representation selection for cache matching. Check the actual edge configuration too; observing Vary alone does not establish that every intermediary implements your intended cache key. See [HTTP Semantics, section12.5.5](https://www.rfc-editor.org/rfc/rfc9110.html#section-12.5.5).

## 5\. Keep delivery, indexing and answers separate

A curl request is your request. Changing its User-Agent string does not turn it into a verified request from OpenAI, Google or another provider. Record named-service retrieval only when you have evidence for that particular service and event.

Google lists public crawl access, a successful response and indexable content among its technical requirements. Meeting the requirements does not guarantee indexing. Use Search Console to inspect Google’s own observations rather than treating this local response check as an indexing verdict. [Google Search technical requirements](https://developers.google.com/search/docs/essentials/technical)

An answer study needs its own record: the question, model or service, date, settings, answer, cited sources and repeated observations. A successful delivery check does not prove that a later answer used the saved response or that the delivery change caused an improvement.

## Choose the next action from the finding

If a required fact is absent from the published source, improve the source. If it exists in one response but disappears in another, inspect the delivery and extraction path. If both responses preserve it, proceed to a separate answer evaluation instead of repeatedly changing the format.

Use [Website Preview](https://optiview.ai/demo/) to inspect a supported public page. For application workflows, [Parse](https://optiview.ai/developers/parse/) processes HTML you supply and [Retrieve](https://optiview.ai/developers/retrieve/) acquires supported public webpages. Those developer results are separate from publishing an approved website source.

## Additional source context

A successful source-delivery check establishes what your request received. It does not establish what a named AI service retrieved, indexed or cited.

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

- [Does AI receive the page your visitors see?](https://optiview.ai/resources/website-platforms-ai-readability/) — Continue reading
- [Four files. Four different jobs.](https://optiview.ai/resources/four-discovery-files/) — Continue reading
- [How to convert HTML to Markdown for AI applications](https://optiview.ai/resources/html-to-markdown-api-guide/) — 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.