HOW IT CONNECTS

A clearer source for AI.
Your infrastructure stays under your control.

Review the connection that fits your website. Your web team controls setup and delivery; marketing manages approved source updates through the dashboard.

Who manages your website?

Start with an assisted setup review, or give your web team the technical checklist.

I MANAGE THE WEBSITE

I manage the website.

Add your domain, verify ownership and open Connection. Optiview checks the public configuration and recommends the next steps.

Open the dashboard

SOMEONE ELSE MANAGES IT

My web team manages it.

In the dashboard, open Website Setup / Connection / Send setup to my web team. Copy the checklist or open an email draft.

Open setup handoff

Setup is assisted during private beta, and automated Cloudflare Domain Connect onboarding is not yet certified for general self-service use. Shopify requires a reviewed integration; automatic proxy setup is not supported. DNS changes are manual during private beta. Opening a handoff does not send email or change DNS. Your web team makes the displayed changes; Optiview checks the result.

Connection options for your website

The right approach depends on your hosting environment, security requirements and technical setup. During private beta, our team reviews the connection path with your web team before activation. Automated DNS-provider onboarding is not available for general self-service use.

DNS

Assisted DNS connection

Optiview checks hosting compatibility and supports the required hostname and HTTPS setup. Your web team completes the prescribed DNS changes only after readiness checks pass.

Your team does: Add validation records, then update the traffic record when the dashboard says it is ready.
Before connecting: Hosting compatibility must pass first.

CLOUDFLARE

Authorized route

Use a route in the Cloudflare account authorized for your workspace.

How delivery works: Once configured and verified, the authorized route handles eligible Markdown requests while ordinary HTML traffic continues through the existing website delivery path. Test both representations and fallback before rollout.
Before connecting: Explicitly authorize the Cloudflare connection for that workspace.

API

Your server or CDN

Keep delivery in your infrastructure. Optiview APIs provide the published source.

Your team does: Build the integration and its fallback behavior.
Before connecting: Contact us for API access and implementation. An API-only integration does not require a DNS routing change; your team must implement and verify delivery.

Asked for a hosting review? Keep DNS unchanged until it is resolved.

Connection steps and rollback

Clear responsibilities.

Marketing

Creates and reviews approved product details, FAQs and supporting links.

Workspace admin

Manages domains, workspace access and credentials.

Web team

Connects delivery, maintains site and security settings, and tests traffic and fallback.

Know what changes.

Verification, extraction and live delivery are separate steps.

Verifying ownership does not change traffic.

Ownership verification supports a DNS TXT record, a server-rendered meta tag or a verification file. HTTP methods require HTTPS and a direct successful response on the exact hostname. Verification does not change routing, activate delivery or approve the source for publication.

For client domains, verification is required before Content Preview. Authorized workspace users can save drafts and inspect draft or published previews while connection is pending. Preview still depends on source access; saving a draft does not publish it or approve a flagged source.

How Optiview gets your content

Optiview can fetch an accessible public page, use bounded browser rendering for supported JavaScript content, or process authorized HTML supplied by your server. Supplied HTML is parsed without executing its scripts.

These options do not bypass access controls or guarantee complete extraction. Review facts, links, table relationships and qualifications. Extraction and deterministic composition are separate: repeated directory groups may appear once while original link occurrences remain in evidence. Review-required sources need exact-source approval from the published preview before Markdown delivery.

Which requests receive Markdown

For eligible website delivery, the request must explicitly prefer text/markdown over HTML. Connection, entitlement, source and publication checks also apply. Ordinary browser requests receive HTML through the configured website path; authenticated, cookie-bearing and range requests are not converted.

If a request cannot receive an approved Markdown source, the edge route falls back to origin delivery. Gateway configuration or origin failures can return an error; API integrations return their documented errors and must implement fallback. A User-Agent label does not verify requester identity. Neither a crawler name nor publishing a source proves AI retrieval, use or citation.

Security, availability and fallback

Use approved public, nonpersonalized content and keep credentials server-side. Test normal pages, forms, login, checkout, redirects and cookies after connecting.

Optiview can fall back to origin HTML, but a DNS-connected gateway remains in the traffic path. Gateway or origin failures can affect availability. Custom API integrations must implement their own fallback. Keep the previous DNS record and test rollback before rollout.

Optiview is a shared, multi-tenant private beta. It does not currently claim a security certification or dedicated deployment. Delivery records confirm responses served; they do not prove AI indexing, citation or recommendation.

Read the security details

Start with one page.

Prove the workflow before expanding your rollout.

Verify the hostname
Add the domain and confirm ownership.
Inspect the received source
Preview a public page. Check retained content, source access and any review warnings.
Prepare and save context
Add reviewed brand details and save the draft. Inspect the combined draft before publishing.
Review connection readiness
Complete the assisted setup checks. Confirm ownership, hosting, HTTPS, authorization and a rollback plan for the chosen path.
Publish, review and verify delivery
Publish reviewed additions, then inspect the published-version preview. If source review is required, an authorized user must approve that exact source before Markdown delivery. Complete authorized activation in the order prescribed for your connection, then verify HTML and Markdown responses. Publication alone does not activate delivery.
Test fallback and rollback
Verify failure handling, disconnect and restoration of the previous setup before expanding the rollout.

A DNS connection applies to the hostname. Testing one page helps assess extraction; it does not limit the routing change to that page.

Delivery and fallback checks

Plan your connection.

Work through the setup guide or talk with us about your infrastructure.

Discuss your setup Read the full setup guide