---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/html-markdown-jsonld-content-parity/
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

# HTML, Markdown and JSON-LD: How to Test Information Consistency

When a business publishes the same facts in multiple representations, they should tell a consistent story. That doesn't mean every format must contain the same fields.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/html-markdown-jsonld-content-parity.md)

HTML, Markdown and JSON-LD serve different purposes. HTML is a web document representation, Markdown is a lightweight text format, and JSON-LD is a way to express structured data. A website may use all three without making them interchangeable.

A product page could describe a subscription in visible text, provide a Markdown representation and include structured data describing an offer. If the price or billing period differs, the problem is not simply formatting. The business may be publishing contradictory information.

This guide establishes a field-level parity review. It differs from an HTTP delivery audit: the objective is to decide whether multiple published representations communicate compatible business facts, not merely to check which content type was returned.

## 1\. Choose a page and define the authoritative facts

Select a page with several independently verifiable facts. Good candidates include a product offer, a service with geographic restrictions or a company page describing a specific capability.

1.  Identify the canonical page and its responsible content owner.
2.  Record the approved facts needed to answer the main customer question.
3.  Include conditions that materially change those facts.
4.  Identify which representations the site actually publishes.
5.  Mark unavailable representations as Not Applicable instead of inventing data.

Use [Schema.org](https://schema.org/) to understand available structured vocabulary, and [Google's structured data guidance](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) when assessing Google-specific requirements. Not every page needs every structured property.

## 2\. Complete the field-level parity matrix

| Fact | HTML | Markdown | JSON-LD | Decision |
| --- | --- | --- | --- | --- |
| Entity name | Record value | Record if available | Record if applicable | Match or explain |
| Offering | Record value | Record if available | Record if applicable | Match or explain |
| Price and period | Record exact terms | Record if available | Record if represented | Check material agreement |
| Availability | Record current status | Record if available | Record if represented | Check freshness |
| Restrictions | Record qualifications | Record if available | Record if represented | No contradiction |
| Canonical destination | Record target | Record links | Record if relevant | Check identity |

These are editorial worksheet columns, not a requirement that each representation contain every listed property. The goal is to surface material disagreements, especially where a customer could make a different decision based on the representation encountered.

## 3\. Classify every difference

*   Equivalent: The same material fact is represented in different but compatible wording.
*   Expected omission: A format does not normally express that detail, and its absence does not create a misleading claim.
*   Material omission: Required context or a qualification disappears from a representation intended to carry it.
*   Contradiction: Two published representations assert incompatible facts.
*   Stale: One representation contains an older value that no longer reflects the approved source.
*   Unknown: Available evidence cannot establish which representation is correct.

An omitted field and a false field are different problems. Structured data often expresses a selected subset of visible content. Avoid adding unsupported properties solely to fill the matrix.

## 4\. Pay special attention to structured annotations

JSON-LD can describe entities, relationships and properties in a form suitable for structured processing. It should not become a separate source of commercial truth maintained without coordination with visible content.

Google's guidance explains that structured data can help its systems understand content and support eligible search experiences. It also documents feature-specific requirements. The presence of valid JSON-LD does not establish that a page will appear in a particular search feature.

Cloudflare's [Markdown for Agents documentation](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) describes preserving source JSON-LD in a fenced block when present. That is a documented output behavior of the feature, not a guarantee that the structured facts are accurate.

## 5\. Resolve conflicts at the source

1.  Assign each contradictory fact to an authoritative business owner.
2.  Confirm the correct value and effective date.
3.  Identify every representation containing the outdated or incorrect statement.
4.  Update the underlying source and dependent publication processes as appropriate.
5.  Reinspect the live representations and record the corrected values.
6.  Retain unresolved conflicts as publication holds rather than choosing the most convenient version.

For sites using Optiview Publish, the [setup guide](https://optiview.ai/docs/setup/) describes source preparation, reviewed contextual publication and delivery checks. The parity worksheet can complement that workflow without implying that every discrepancy is automatically detected or repaired by the product.

## Additional source context

Demand agreement on material facts and qualifications, not identical serialization. Record legitimate omissions separately from contradictions that require correction.

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.