FOR WEB TEAMS
Connect Optiview without rebuilding your website.
Your visible site stays in place. Your web team chooses how Optiview receives the page content and how the machine-readable version is delivered.
Who does what?
- Marketing: writes and approves brand details, FAQs and added context.
- Workspace admin: manages domains, access and credentials.
- Web team: connects the site, keeps secrets server-side, sets the eligible paths and tests fallback behavior.
Choose how to connect.
Option 1 — Supported Cloudflare route
Optiview handles eligible Markdown requests on an authorized Cloudflare route. Normal HTML traffic continues to your existing site.
Option 2 — Your server or CDN
Your server calls the Optiview Render API and returns the Markdown response through infrastructure you already control. Your team implements request selection and fallback.
You do not need to change DNS for the Enterprise API option.
How Optiview gets the page content
Public page
Optiview can fetch an accessible public page.
JavaScript-rendered page
For supported pages, browser rendering can load content that appears after JavaScript runs.
Server-supplied HTML
If your site is protected or easier to render inside your own stack, your server can send the HTML directly to Optiview. Submitted scripts are not executed.
None of these methods bypasses your access controls or guarantees that every page can be extracted perfectly.
Proving ownership does not change traffic.
DNS TXT, a meta tag or a verification file proves that you control the hostname. It does not connect Optiview to the site. Routing or API integration happens separately.
The request asks for Markdown. Optiview does not pretend to be a bot.
Eligible requests use the standard Accept: text/markdown header. A crawler name by itself does not trigger the Optiview version. Your existing WAF, robots and access rules remain relevant.
Keep security and fallback under your control.
Keep keys server-side and limit delivery to approved public pages. Do not send private sessions or personalized content.
Reference adapters fall back to origin HTML on errors or timeouts. Waiting for a timeout can add latency. Test this behavior in your own infrastructure.
Optiview is a shared multi-tenant private beta. No security certification or dedicated deployment is implied. Delivery records show responses served, not AI indexing or citations.
Start with one page.
- Choose one public page.
- Verify the hostname.
- Add and approve a small amount of brand context.
- Connect one delivery path.
- Confirm normal HTML still works.
- Confirm the Markdown version and publication version look right.
- Test failures, revocation and fallback before expanding.