---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/machine-readable-product-information/
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/) [The AI-readable web](https://optiview.ai/resources/topics/ai-readable-web/)

Technical guide — October 30, 2026

# How to Prepare Product Information for AI Assistants

Product information needs to do more than describe what something is. It needs to explain exactly which product, which version, under what conditions and where a customer can act.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/machine-readable-product-information.md)

Consider the difference between 'This product costs $99' and 'This product costs $99 per month for the specified plan, subject to the published terms.' The first statement may be technically incomplete even when the number is correct. The second carries the qualification necessary to interpret it.

AI assistants can encounter product information through webpages, structured data, search results and other retrieval systems. Businesses should aim for consistency across the representations they control, without assuming that every assistant reads every representation or that complete product data guarantees inclusion in answers.

The template below is an editorial preparation method. For search-specific technical requirements, consult the relevant provider's documentation rather than treating every suggested field as mandatory.

## 1\. Define the exact product

Start with an unambiguous product identity. Capture the public name, brand, model or plan identifier, version, category and canonical URL. Avoid using one generic description for variants with materially different capabilities.

| Field | Editorial requirement |
| --- | --- |
| Name | Use the official public product name. |
| Identifier | Include SKU, model or plan identifier where applicable. |
| Variant | Distinguish size, configuration, term or edition. |
| Description | Explain the product's purpose in plain language. |
| Canonical URL | Identify the authoritative product page. |

The [Schema.org Product type](https://schema.org/Product) defines properties that can describe products and their characteristics. That vocabulary is a useful reference, but the appropriate properties depend on the actual offering.

## 2\. Keep commercial terms attached to the offer

An offer is not merely a price. Currency, billing period, quantity, availability, seller and conditions can all change its meaning. Record terms together so they are not separated during page preparation or content reuse.

*   Price and currency, only when currently confirmed.
*   Billing period, unit of measure or minimum quantity.
*   Availability or inventory status with an update source.
*   Promotion eligibility and expiration where applicable.
*   Shipping, delivery, subscription or cancellation conditions when material.

The [Schema.org Offer vocabulary](https://schema.org/Offer) distinguishes the commercial offer from the underlying item. [Google's product structured data documentation](https://developers.google.com/search/docs/appearance/structured-data/product) also describes eligible product search experiences and their associated markup requirements. Neither source should be interpreted as guaranteeing a rich result.

## 3\. Publish the reasons a product might not fit

Good product information helps someone rule out the wrong option. A reader may need to know that a device works only with particular equipment, that a plan excludes certain capabilities, or that a service requires an existing account.

1.  Identify the three most important purchase or adoption prerequisites.
2.  Document material compatibility, location or account restrictions.
3.  Review claims such as fastest, safest or guaranteed for adequate substantiation.
4.  Place qualifications beside the benefits they materially affect.
5.  Link to the complete official documentation or policy.

Do not create missing restrictions by inference. Request confirmation from the product owner and mark the information unresolved until approved.

## 4\. Test the facts across published representations

A business may publish the same product through a designed webpage, structured data and an alternative machine-readable representation. The objective is substantive agreement, not identical formatting.

| Fact | HTML page | Structured data | Other published source |
| --- | --- | --- | --- |
| Identity and variant | Check | Check if used | Check if used |
| Price and period | Check | Check if used | Check if used |
| Availability | Check | Check if used | Check if used |
| Restrictions | Check | Check if represented | Check if used |
| Canonical destination | Check | Check if used | Check if used |

An empty cell is not automatically a defect; not every format expresses every field. Material contradictions are defects worth investigating. For an HTTP-level inspection, follow the [Optiview HTML and Markdown audit](https://optiview.ai/resources/audit-html-markdown-delivery/).

## 5\. Give each product record an owner and update trigger

Product information changes. Assign responsibility for updates triggered by price changes, new versions, discontinued models, policy revisions or availability changes. Preserve the effective date of commercial terms when it matters.

1.  Choose one product and complete the identity and commercial-term tables.
2.  Have the product owner confirm limitations and authoritative links.
3.  Correct contradictions before publishing new representations.
4.  Validate the rendered content and structured data where used.
5.  Schedule review when a material product or offer change occurs.

If your website uses Optiview Publish, consult the [connection and review documentation](https://optiview.ai/docs/setup/) to understand how prepared source content and approved supplemental context are managed. The source information must still be maintained by its rightful owner.

## Additional source context

Create one authoritative, version-aware product record, then ensure the public page and any additional representations communicate the same important facts and qualifications.

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

- [AI doesn’t have one view of your website.](https://optiview.ai/resources/what-ai-services-see/) — Continue reading
- [Keep the meaning. Simplify the format.](https://optiview.ai/resources/html-versus-markdown-for-ai/) — Continue reading
- [The AI-Readable Website Audit: 25 Checks Before You Optimize](https://optiview.ai/resources/ai-readable-website-audit-checklist/) — 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.