Technical guide — October 6, 2026
Does your website’s platform affect AI readability?
Your website can look excellent to customers while leaving automated systems with incomplete or hard-to-retrieve information. For marketers, the question is whether your product facts and customer answers are available in the page response. Your technology stack helps your web team decide what to check.
By Optiview · Sources checked October 6, 2026
Vercel has the tools to make content readable
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
The relevant question is not “Does this use Vercel?” It is “Which important facts are present in the response this page returns?”
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
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 in common stacks
Use these checks to find where important information enters the page.
| 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, Nuxt, Adobe
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
Test pages, not just homepages
- 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.
- Inspect the server-delivered HTML, then compare it with a browser-rendered version. Record which facts require JavaScript and which remain missing.
- Inspect 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 Website Preview can help inspect 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.
Readable doesn’t mean complete
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.
Consider a product page that loads perfectly. 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 supply 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.
Choose the fix that matches the finding
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
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
How delivery works
Optiview’s connected website path serves the published Markdown version to eligible requests that explicitly accept text/markdown. Verified AI requests that accept HTML can receive the prepared page and applicable published graph as HTML. Other requests can still receive the original HTML, including any JavaScript dependency. Installing Optiview does not mean every AI service receives this version.
A custom API integration lets an authorized server request the published result and control delivery. Neither method guarantees indexing, citations or better answers. For Google Search, including its generative AI features, Google says sites do not need special AI files, additional markup or Markdown to appear. Google Search guidance
Start with the page, then close the gaps
Your technology stack can tell you where to look. The response tells you what is actually there.
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.
Inspect 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.
Separate extraction from presentation
When reviewing Optiview output, compare the original extracted representation with the composed source. Equivalent directory groups can be displayed once while their original occurrences remain in the evidence inventory. Missing source facts and awkward presentation are different issues. Record the source mode and parser/composition versions, and inspect source-review warnings. See the current release baseline and validation scope and launch checks.
Continue reading
AI Visibility Is a Publishing Problem, Not Just a Reporting Problem
What do ChatGPT, Gemini, Claude and Perplexity actually see when they visit a website?
HTML versus Markdown for AI: what changes?
llms.txt, robots.txt, sitemap.xml and Markdown: four different jobs
Why AI visibility reporting isn’t enough
From AI-readable websites to agent-accessible knowledge
Preview a page · Read the setup guide
Additional source context
Make your brand easier for AI to understand.
Product
Website Preview · Pricing · How it works · How it connects
Resources
Articles & guides · Get started · Setup guide · FAQ · Evidence & methodology · For platforms & API access
Company
For agencies · Contact us · Sign in · Privacy
Published brand narrative
Site-wide brand information
Who we are
Optiview — the publishing layer for AI
Optiview turns complex website content into clean, structured Markdown and combines it with the brand narrative your team chooses to publish. The result is one clear source that supported AI crawlers and other systems can retrieve, alongside your existing website experience.
Built for marketing and web teams, agencies, CMS and commerce platforms, and AEO/GEO providers, Optiview helps turn recommendations into published source improvements. It complements AI visibility tools by giving teams a way to act on their findings.
Applies to: Optiview
Why we matter
Your website. Your narrative. One clear source for AI.
A website can deliver a beautiful human experience while leaving important business facts scattered across pages, buried in markup, or dependent on JavaScript. AI systems may retrieve only part of that information.
Optiview gives businesses control over the source they make available: readable website content plus context only their team can provide. Your web team connects delivery; your content team writes, reviews and publishes the narrative.
Our focus is publishing useful, accurate brand information. Each AI service decides what it retrieves, uses and cites. Optiview does not control an LLM’s answers or guarantee placement in them.
What we offer
Clean website content, owned narrative and controlled delivery
- Website parser: Converts accessible public page content into readable Markdown, retaining supported headings, text, tables and links. The parser does not use an LLM to invent facts or rewrite the page. Browser rendering is available for supported JavaScript-dependent content.
- Narrative Graph: Organizes team-authored content into Identity, Story, Offerings, Trust, Knowledge and Actions. Add multiple items, edit them and review the graph before publishing.
- Site and page scope: Apply an addition to the entire website or one exact page, so the published context accompanies the appropriate content.
- Publishing and delivery: Combine eligible parsed page content with published, path-matched narrative additions through a supported website connection. Draft edits remain separate from the active publication.
- Delivery reporting: Inspect recorded Markdown responses, requester claims, verification evidence and published versions. Delivery records show what was served, not whether it appeared in an AI answer.
- Public demo: Try a public URL, inspect the parsed source and explore AI-drafted narrative examples. Demo results do not connect a website or publish content.
Why trust us
Inspect the source and understand the evidence
Optiview makes the publishing process inspectable. Teams can review parser output and a combined published-output preview, check source information, and inspect publication history before deciding what to make available.
The public demo provides a way to evaluate output using a real public page. Source access and extraction limitations remain visible; blocked or inaccessible content may be missing. A preview is not proof that a live request received the same output.
Delivery reporting distinguishes claimed requester names from available verification evidence. A verified AI category does not by itself verify a named provider. A served Markdown response is evidence of delivery, not proof of ingestion, recommendation, citation or revenue.
Learn more about the evidence and its limits at https://optiview.ai/proof/.
Helpful knowledge
Common questions about using Optiview
Does Optiview replace our website or CMS? No. Optiview adds a publishing layer. It does not rewrite your CMS pages; normal HTML requests retain the website experience through supported connections.
What can we add to the Narrative Graph? Brand descriptions, mission and audience context, products and services, supporting facts, FAQs, policies and next steps. Choose whether each item applies across the website or to one exact page.
Does saving publish our changes? No. Saved edits remain in the draft. An authorized user publishes the graph to activate the reviewed content. Later edits stay separate until published again.
Does every AI system receive Markdown? No. Delivery depends on the connection, request and source eligibility. Some systems explicitly request Markdown; supported delivery paths can also select it for verified AI categories. Other tools retrieve HTML and extract text themselves.
Is Optiview an AI visibility monitoring tool? No. Optiview helps you improve and publish the source. Keep using your visibility tools to study AI answers; use Optiview’s delivery evidence to understand recorded serving activity.
Does the demo save a graph to our workspace? No. The public demo is a separate preview. Its AI-generated proposals require review and are not automatically transferred to a workspace or published.
Do we need a developer? Your web team may need to help establish and verify the connection. Once connected, authorized content users can manage narrative updates in the admin.
Will Optiview guarantee citations? No. You control the source you publish. AI systems decide what to retrieve, use and cite.
What to do next
Try your website, then plan your connection
- Try your website to inspect a public page’s parsed content and explore proposed narrative additions.
- See how Optiview works to understand the parser, Narrative Graph and combined publishing workflow.
- Explore who it’s for if you are an agency, CMS or commerce platform, or AEO/GEO provider bringing recommendations to customers.
- Review connection options and the setup guide with your web team.
- Contact hello@optiview.ai to discuss access, your website and the right setup. Workspace access is invite-only.
Already connected? Review your Narrative Graph, publish when ready, inspect the combined output in the Markdown tab, and check recorded delivery in Activity.