---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/markdown-negotiation-cache-validation/
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

# Markdown Content Negotiation: A Cache and Response Validation Checklist

If one URL can produce both HTML and Markdown, the cache must not accidentally confuse the two. Here's how to turn that requirement into testable acceptance conditions.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/markdown-negotiation-cache-validation.md)

A basic source-delivery inspection establishes which response a particular request received. Cache validation asks a harder question: will the right representation continue to be delivered across repeated requests, cache states and content updates?

The distinction matters when content negotiation allows a single URL to return different representations. The server, CDN and any other intermediary must handle cache selection consistently with the intended request policy.

The HTTP standards define the relevant mechanics. [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html) describes representation selection and Vary. [RFC 9111](https://www.rfc-editor.org/rfc/rfc9111.html) describes HTTP caching and cache matching. The matrix below is an Optiview-recommended acceptance procedure, not a claim that every server or cache is configured identically.

## 1\. Record the environment before testing

Choose a public URL whose approved source contains several stable, recognizable facts. Identify the origin, CDN, relevant cache rules and expected representations. Preserve the current deployment version and do not conduct disruptive cache experiments on production without authorization.

*   Target URL and canonical destination.
*   Expected response type for each supported request preference.
*   Known cache layers and configuration owner.
*   Expected freshness or invalidation policy.
*   A reversible, authorized content update for freshness testing.
*   Headers and response bodies retained as evidence.

## 2\. Execute the representation acceptance matrix

| Scenario | Action | Pass condition |
| --- | --- | --- |
| HTML baseline | Request HTML from the selected URL | Expected HTML response and content |
| Markdown baseline | Request Markdown where supported | Expected negotiated response or documented fallback |
| HTML then Markdown | Issue sequential requests in that order | No unintended representation crossover |
| Markdown then HTML | Reverse the request order | No unintended representation crossover |
| Repeated same variant | Repeat each request with unchanged source | Consistent type and required facts |
| Content update | Publish an authorized source revision | New content appears under expected freshness policy |
| Fallback or failure | Inspect a supported error or fallback condition | Documented type, status and safe behavior |

Record actual outcomes even when they differ from expectations. A fallback to HTML may be valid under the deployment policy; it should not be mislabeled as a successful Markdown response.

## 3\. Inspect the headers that govern cache behavior

At minimum, record Content-Type, Vary, Cache-Control, Age and any validators or CDN diagnostic headers that are present. Some fields may be absent by design. Their absence is an observation to evaluate against the configuration, not automatically a defect.

Cloudflare's [Markdown for Agents documentation](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) states that converted responses include Accept in Vary and that certain original-body headers, including ETag and Last-Modified, are removed from converted responses. Those are documented feature behaviors; do not generalize them to every Markdown delivery implementation.

*   Confirm that relevant request dimensions are represented in the cache-selection policy.
*   Check whether a shared intermediary could reuse the wrong representation.
*   Investigate unexpectedly stale bodies or mismatched cache metadata.
*   Do not assume that the presence of Vary proves every intermediary honors the intended key.
*   Preserve both the headers and body needed to reproduce a suspected failure.

## 4\. Test freshness without confusing it with representation

An HTML response and a Markdown response may each be correctly formatted yet contain different revisions of the underlying content. A successful representation check therefore does not establish freshness.

1.  Record a known source revision and its approved factual content.
2.  Capture both supported representations before the update.
3.  Make an authorized, reversible source change with an identifiable version marker.
4.  Observe each representation according to the documented cache policy.
5.  Record when the updated source becomes visible and whether any variant remains unexpectedly stale.
6.  Restore the test fixture if required and retain the outcome, including inconclusive observations.

## 5\. Define the release decision

Pass only when the required scenarios have observed outcomes consistent with the deployment policy. Hold if variants cross over unexpectedly, freshness behavior cannot be explained or important facts disappear.

Keep cache findings separate from indexing and answer-generation claims. The existing [Optiview source-delivery audit](https://optiview.ai/resources/audit-html-markdown-delivery/) explains how to capture individual responses; this matrix extends that procedure into repeated cache, order and freshness validation.

## Additional source context

Validate cache separation, freshness and recovery with controlled request sequences. A correct Vary header is important evidence, but not proof that the complete delivery path behaves correctly.

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.