---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/website-platforms-ai-readability/
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
---

# Can AI read the same page your customers see?

Your page may look complete to a customer while an AI tool receives less information. Here is what to check.

Technical guide

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

- [Explore the framework](https://optiview.ai/resources/website-platforms-ai-readability/#interactive-framework)
- [Download guide (.md)](https://optiview.ai/resources/website-platforms-ai-readability.md)

Editorial illustration · Get set up

An interactive overview

## Explore the framework.

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

6 items

01Vercel / Next.js 02React, Vue or Angular applications 03Nuxt 04Shopify themes and apps 05Adobe Experience Manager / headless CMS 06WordPress, Webflow and enterprise commerce

Item 1 of 6

### Vercel / Next.js

**Useful check**
Compare initial HTML with the rendered page. Inspect content fetched only after page load and routes that depend on runtime client behavior. Do not classify Client Components as missing content automatically.

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.

Delivery update — October 29, 2026: Eligible requests can receive prepared Markdown or HTML depending on request preferences, supported tool or crawler classifications and the website’s delivery policy. Traditional search crawlers retain the original response. A declared tool name does not independently verify its identity. See the [Publish setup guide](https://optiview.ai/docs/setup/) for current delivery rules.

## Vercel hosting does not tell you what a crawler can read

A site hosted on Vercel can return complete, useful HTML. It can also return a thin page that relies on JavaScript and later API requests for important content. Hosting alone does not tell you which one you have.

Next.js supports server rendering and prerendering, and Client Components can still be represented in the initial HTML. Using “use client” is therefore not evidence that a page is invisible without JavaScript. Content fetched only after the browser loads still needs checking. [Next.js rendering documentation](https://nextjs.org/docs/app/getting-started/server-and-client-components)

Instead of asking whether a site uses Vercel, ask which important facts are actually included in the response it sends.

## JavaScript can change what a crawler receives

In research published on December 17, 2024, Vercel and MERJ reported that the AI crawlers they tested did not execute JavaScript. Googlebot and Applebot were rendering-capable counterexamples. This was an observation of those systems during that study, not a permanent specification for every AI product or retrieval path. [Vercel and MERJ research](https://vercel.com/blog/the-rise-of-the-ai-crawler)

Fetching a JavaScript file is not the same as executing it. Equally, an AI answer mentioning your business is not proof that a particular crawler rendered your homepage. The answer may rely on another page, an index or other sources.

## What to check on common website platforms

Use these checks to see when important information becomes available to a visitor or crawler.

| Stack or pattern | Useful check |
| --- | --- |
| Vercel / Next.js | Compare initial HTML with the rendered page. Inspect content fetched only after page load and routes that depend on runtime client behavior. Do not classify Client Components as missing content automatically. |
| React, Vue or Angular applications | If a page is client-rendered, check whether useful text exists before scripts run. The framework name alone does not establish the rendering mode. |
| Nuxt | Universal rendering is the default, with client-only and hybrid modes available. Check the actual route configuration and response. |
| Shopify themes and apps | Check whether product information, variants, qualifications and app-provided answers are available in the initial page, rather than only in a widget. |
| Adobe Experience Manager / headless CMS | Inspect the frontend delivery architecture and individual components. A CMS storing a fact does not establish when the frontend publishes it. |
| WordPress, Webflow and enterprise commerce | Inspect real product, article, category and policy pages. Navigation volume, templates and widgets are reasons to review output, not proof of poor AI visibility. |

Angular supports client, server and prerendered routes. Nuxt defaults to universal rendering. Adobe documents JavaScript-driven SPA implementations and their rendering considerations. These options reinforce why implementation matters more than the logo on the stack. [Angular](https://angular.dev/guide/routing/rendering-strategies), [Nuxt](https://nuxt.com/docs/4.x/guide/concepts/rendering), [Adobe](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/journeys/developer/create-spa)

Shopify recommends rendering essential content in Liquid and HTML instead of relying on client-side JavaScript. Start with product details and answers supplied by apps: check whether they arrive with the page or require a later browser request. [Shopify guidance](https://shopify.dev/docs/storefronts/themes/best-practices/performance/render-essential-content-server-side)

## Test the pages customers rely on, not just the homepage

*   Choose a homepage, product or service page, category page, article and policy page where applicable. Record the URL, time and extraction settings.
*   List the important facts first: names, capabilities, prices, units, eligibility conditions, supporting links and qualifications.
*   Check the server-delivered HTML, then compare it with a browser-rendered version. Record which facts require JavaScript and which remain missing.
*   Check the cleaned result. Check for lost facts, detached footnotes, changed table relationships or missing category links. A shorter result is not automatically more useful.
*   If a request fails, report the observed status or challenge. An anonymous fetch cannot establish that OpenAI, Google or another specific service is also blocked.

The public [See my site with Optiview](https://optiview.ai/demo/) can help check a URL with or without bounded browser rendering. It is not a named AI crawler’s session, a complete site audit or an AI visibility score. Resource restrictions and time limits can leave content incomplete.

## Easy to read does not mean the answer is there

Making existing website content accessible is the first problem. A page can be server rendered, easy to crawl and cleanly structured—and still lack the answer a customer is looking for.

Product details may be spread across support documentation. Implementation answers may exist in documentation, sales materials or internal team knowledge without appearing on the page. Important differences between products may be obvious internally but absent from the website.

A product page can load perfectly and still leave customers guessing. Does it explain who the product is for, what is included, which systems it works with, its limitations and how to get started? Rendering and format conversion cannot add facts the business has never published.

*   Can machines retrieve the information you have already published?
*   Have you published the information you want customers and AI systems to be able to find?

Server rendering, prerendering and browser rendering primarily address the first question. The second is a content and publishing problem: gather the answers, confirm them with the people responsible and publish them with supporting links.

## Fix the specific problem you find

If essential facts are absent from initial HTML, server rendering, prerendering or moving the content into the server-delivered page are valid options. If the information itself is missing or inaccurate, update the source content. If the problem is access, investigate the actual security rule instead of removing protections broadly.

Managed rendering is also available from infrastructure providers. Cloudflare’s Browser Rendering crawl API can crawl pages and return HTML, Markdown and JSON output. Rendering and conversion are not exclusive Optiview capabilities. [Cloudflare Browser Rendering](https://developers.cloudflare.com/changelog/post/2026-03-10-br-crawl-endpoint/)

Optiview can address both layers. It turns supported website content into a clearer machine-readable source and gives authorized teams a way to add approved product details, FAQs and supporting content that the existing page does not explain clearly. Your team reviews the combined result before publishing. The web team establishes delivery; content teams can keep that source current without changing application code for every update.

## Readable content still needs a delivery path

Depending on the connection and request, eligible systems may receive prepared Markdown or HTML. Ordinary visitors keep the original website. [See the technical guide for current delivery behavior](https://optiview.ai/docs/setup/).

## Start with a real page, then fix what is missing

Your website technology suggests where to look. The page response shows what was actually delivered.

Next.js, React, Angular and Shopify can all support accessible pages. Important information can also arrive only after browser execution or remain scattered across applications, documents and teams.

Check representative pages, identify what your tests can retrieve, and determine whether the important answers are actually there. Then fix the specific gap: how the content is delivered, what the brand has published, or both.

**The goal isn't to optimize for a particular crawler. It's to make sure your owned source says what it needs to say—and that it is available in a form compatible systems can retrieve.**

## Check the content separately from how it is presented

When reviewing Optiview output, compare the initially extracted content with the final prepared source. Repeated directory groups may be displayed once while their original appearances remain in the evidence inventory; distinct groups must remain distinct. A missing fact is different from a formatting problem. Record the source mode and parser/composition versions, and review any source warnings. See the [release baseline and validation scope](https://optiview.ai/proof/) and [launch checks](https://optiview.ai/docs/setup/#acceptance).

Go to the source

## Keep exploring.

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

[nextjs.org**Next.js rendering documentation**Opens in a new tab](https://nextjs.org/docs/app/getting-started/server-and-client-components) [vercel.com**Vercel and MERJ research**Opens in a new tab](https://vercel.com/blog/the-rise-of-the-ai-crawler) [angular.dev**Angular**Opens in a new tab](https://angular.dev/guide/routing/rendering-strategies) [nuxt.com**Nuxt**Opens in a new tab](https://nuxt.com/docs/4.x/guide/concepts/rendering) [experienceleague.adobe.com**Adobe**Opens in a new tab](https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/journeys/developer/create-spa) [shopify.dev**Shopify guidance**Opens in a new tab](https://shopify.dev/docs/storefronts/themes/best-practices/performance/render-essential-content-server-side) [developers.cloudflare.com**Cloudflare Browser Rendering**Opens in a new tab](https://developers.cloudflare.com/changelog/post/2026-03-10-br-crawl-endpoint/)

- [See my site with Optiview](https://optiview.ai/demo/)
- [Run your free AI Audit](https://optiview.ai/ai-audit/)

Keep going

## A useful next read.

AI discovery guide

### [Four website formats your web team may mention](https://optiview.ai/resources/four-discovery-files/)

Developer guide

### [Convert HTML into Markdown with the Parse API](https://optiview.ai/resources/html-to-markdown-api-guide/)

Developer guide

### [Fetch a public webpage as Markdown with Retrieve](https://optiview.ai/resources/webpage-to-markdown-for-rag/)

[Back to the resource library](https://optiview.ai/resources/)

## Additional source context

Test the important facts on your own pages. Ask your web team to help check information that only appears after the page loads.

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](https://optiview.ai/demo/) · [Run your free AI Audit](https://optiview.ai/ai-audit/)

### Explore

[Publish](https://optiview.ai/products/publish/) · [Parse](https://optiview.ai/products/parse/) · [Retrieve](https://optiview.ai/products/retrieve/) · [Pricing](https://optiview.ai/pricing/)

### Learn

[Guides](https://optiview.ai/resources/) · [Developer docs](https://optiview.ai/developers/) · [Research & thinking](https://optiview.ai/research/) · [Experiments & methods](https://optiview.ai/proof/) · [AI Audit](https://optiview.ai/ai-audit/) · [AI agent directory](https://optiview.ai/agents/) · [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

- [More in this collection](https://optiview.ai/resources/topics/implementation/)
- [AI discovery guide · Four website formats your web team may mention](https://optiview.ai/resources/four-discovery-files/)
- [Developer guide · Convert HTML into Markdown with the Parse API](https://optiview.ai/resources/html-to-markdown-api-guide/)
- [Developer guide · Fetch a public webpage as Markdown with Retrieve](https://optiview.ai/resources/webpage-to-markdown-for-rag/)


---

# 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.
