Clear answers about Optiview and what your team controls.

Optiview turns received website content into a clearer AI-readable source. Inspect existing answers, explore supported suggestions and add information your team approves. Authorized workspace users review and publish updates; the public demo does not save or publish them.

No. The demo can identify question-and-answer disclosures on the submitted page and quote eligible answers with source attribution. A link to an FAQ page is shown as a link, not as acquired answers; submit that page separately to inspect it. AI suggestions are separately labeled drafts and may be withheld when evidence is insufficient.

No. Website extraction and composition use deterministic software. The separate demo recommendation uses Cloudflare Workers AI to draft an answer and a second call to evaluate its claims against inspected excerpts. A model outage or an unsupported suggestion does not invalidate the page transformation.

No. Demo suggestions and local edits are not saved to a workspace or added to live Markdown. You can import a supported original review package as an evidence-backed suggestion draft for your verified website. Importing does not add it to published content. Review a saved suggestion and choose Add to content draft to stage an FAQ for its exact path, or add reviewed text manually. Save, preview and publish as an authorized user. Saving is not publishing; your organization manages factual approval.

The submitted page, plus at most one selected same-origin link shown in the demo when more detail is needed. A question supported by homepage evidence uses that page alone. It does not research the wider web. Selected source passages support the original draft; AI-assessed support does not independently verify the publisher’s claims. An answer may be withheld when evidence is insufficient or conflicting.

The edit stays in your browser and is not automatically evaluated. The original support badge is removed; the displayed evidence supports the original suggestion only. Review every new or changed claim before using it.

Optiview is in private beta. Contact us to discuss access and usage limits. We do not currently publish a verified per-FAQ cost or promise unlimited AI generation. Drafting, evaluation and any browser acquisition are separate processing costs.

The standard single-website offer is USD 199 per month after an eligible 30-day trial. Live Checkout is not open yet. Contact us for private-beta access, trial eligibility and usage limits; requesting access does not start a subscription or charge.

It may already be enough. Some pages contain all the useful information in their initial HTML; others depend on JavaScript or leave important answers scattered across pages. Use the preview to inspect your actual content. Optiview helps you prepare a clearer source and manage approved additions; it does not mean every website has an AI visibility problem.

Not necessarily. Extraction and presentation are separate. Deterministic composition can show equivalent directory groups once while preserving their original link occurrences in the evidence inventory. It does not invent descriptions or fetch linked pages. Inspect facts, qualifications and destinations; shorter output alone is not proof of quality.

It does not rewrite your visible website. Optiview manages the machine-readable version separately. If the original website itself is wrong, you should still fix it in your CMS.

Add approved company descriptions, product facts, FAQs, comparisons and links to supporting pages. Keep facts current and consistent with the visible website. Optiview does not independently verify the claims your team adds.

Yes. Once your website is connected, marketing can add details and FAQs, preview changes and publish from the dashboard without changing website code. Your web team may be needed for the initial connection and later hosting or security changes.

Authorized workspace admins and assigned strategists can save, preview and publish content. Saving a draft does not make it live. Your organization decides who reviews and approves it; the product does not require a separate approval role. Partner suggestions remain unpublished until an authorized workspace user publishes them.

You can hand setup to the person who manages your website. In the dashboard, choose Send setup to my web team to copy a checklist for your domain or open an email draft. The recipient needs their own authorized workspace access. During private beta, any required DNS changes are made by you or your web team. Once connected, marketing can manage content without changing website code.

No. A connected website can serve published Markdown to eligible requests that explicitly prefer text/markdown over HTML, subject to connection, source and publication checks. A crawler’s name alone does not trigger it. AI services decide what they request, retrieve and use; connection and publication do not guarantee indexing, citations or inclusion in AI answers.

No. Optiview improves the source you make available. AI systems still decide whether and how they use it.

Optiview uses explicit format requests, not crawler impersonation. Your normal website remains available to people, and your existing robots, security and access rules stay in place. Keep published claims accurate and consistent with your website. AI systems and search engines still decide how they treat the published source.

Yes. An assigned editor can explicitly check the original evidence for a saved suggestion. Optiview makes a bounded request to up to two original public pages and shows the latest comparison and whether cited excerpts were observed. Older or browser-based captures may not be comparable. A check does not verify facts, rewrite answers or publish anything. Checks are not scheduled automatically.

Optiview prepares a structured source from received website content and adds the context your team approves. That can make the available information clearer to a system that retrieves it. ChatGPT and Gemini choose their own retrieval paths; Optiview does not make either service request Markdown or guarantee inclusion in answers.

Optiview publishes a source for eligible requests, rather than a dedicated Claude or Perplexity integration. Those services decide which pages to retrieve and how to use them. Test the actual delivered representation and measure observed outcomes; the platform names do not imply partnership or guaranteed compatibility.

No. Markdown is a content format. Preparation, delivery, AI retrieval, citation and business outcomes are separate questions. A successful Markdown response does not prove that an AI system read, used or cited it.

llms.txt is a proposed way to give agents website context and links to useful content. Optiview provides source preparation, reviewed additions and controlled publishing and delivery. A discovery file does not replace those workflows, and publishing one does not guarantee that an AI service follows it.

Results depend on the content acquired. Initial HTML may contain useful content or only a shell. The public preview can request browser rendering, but access controls, supported resources and time limits can still prevent a complete result. An installed connection changes the acquisition path; it does not automatically supply missing browser-only content. Your web team must validate the source and rendering configuration.

No. Visibility tools help measure how your brand appears in AI answers. Optiview helps your team prepare, review and publish source improvements. Use both in a measured workflow; a publication record does not establish that an answer or ranking changed because of it.

A connected delivery path prepares a representation from received website content and combines it with published additions. Your team manages those additions in Optiview rather than hand-maintaining another full copy of each page. Cached source, website changes and published additions can have different ages, so review freshness and response metadata. Optiview does not promise instant synchronization of every website change.

Optiview is in controlled private beta. Your web team reviews and configures a supported connection. Automated Cloudflare Domain Connect onboarding is not yet certified for general self-service use. Ownership verification alone does not activate delivery; contact us to plan a supported setup.

You can use the public Website Preview without signing in, creating a workspace or verifying domain ownership. It does not save or publish content. Dashboard Content Preview is a separate workspace feature that requires authorized access and ownership verification for your website. The demo fetches a public page under preview limits and shows what that request acquired. It does not save or publish content. An installed connection uses an authorized delivery configuration and published workspace content. It may avoid some public crawling constraints, but does not guarantee complete content, browser rendering or AI retrieval.

Yes for DNS and edge connections. The DNS gateway forwards ordinary website traffic to your hosting destination and prepares Markdown for eligible requests. With a custom API integration, your server or CDN chooses when to call Optiview. Your web team should test normal traffic and failure behavior before launch.

For eligible website delivery, a request must explicitly prefer text/markdown over HTML. Connection, entitlement, source-review and publication checks must also pass. Authenticated, cookie-bearing and range requests are not converted. Optiview does not select Markdown from a crawler name or User-Agent alone.

It depends on the reviewed connection method. An authorized Cloudflare route can keep your existing DNS. Guided DNS requires your web team to add the displayed records after hosting and HTTPS checks pass. A custom API integration keeps delivery in your own infrastructure. Automated DNS-provider authorization is not generally available; contact us for assisted setup.

No. Start with Check my website. Guided DNS needs a hosting destination that passes Optiview’s HTTPS forwarding and Markdown checks without looping back to the public hostname. Shared hosting can use hostname-preserving forwarding when its origin supports it. Optiview can identify a candidate hosting destination; your web team must confirm it and test site behavior. Restricted or incompatible hosting needs a review before any DNS changes. Direct server IPs are not supported in this path.

Public Shopify pages can be previewed when their content is accessible, but that does not certify a complete store integration. Submit FAQ, collection and product pages separately. Shopify requires a reviewed connection; automatic DNS proxy setup is not supported. Keep existing DNS unchanged until a supported integration is agreed.

The public demo may show a qualified preview from initial HTML when useful content is available. It keeps the rendering failure visible; static fallback is not a successful rendered capture. Some browser-loaded content may be missing, and unusable sources receive no cleaned preview. An installed connection does not automatically remove these limitations.

Not for guided DNS connection. Your web team adds the records at your DNS provider. The separate authorized Cloudflare route requires scoped account access; it is an alternative integration, not an extra step.

Extraction is intended for authorized public, nonpersonalized content. URL fetching and browser rendering do not use a visitor’s login session. For direct HTML submission, your server must remove private, confidential and personalized information before sending it. Do not use Optiview to publish logged-in content.

For a reviewed API integration, your server can supply authorized HTML directly to Optiview. That avoids an external page fetch, but it does not bypass your security controls.

No. Keep your existing Schema.org and JSON-LD where they are useful. Optiview can combine website content, structured Brand Details and approved Added Content into the published source.

Fallback depends on the connection. The edge path can return origin HTML when optimization fails, but a DNS gateway remains in the traffic path and an origin or gateway outage can still affect the site. A custom API adapter must implement its own origin fallback. Your web team should test failures and keep the original DNS record for rollback.

Source checks found evidence that needs human inspection, such as unresolved relationships or competing states. Publishing brand content does not approve a flagged source. An authorized workspace user reviews the Published version preview and approves that exact page source. Relevant source, settings or content-version changes require another review.

Yes. You can manage the content workflow for clients while their web teams control the website connection. Your existing reporting can continue to measure what happens in AI answers.

For the initial client connection, yes. Day-to-day content updates can then happen in the dashboard without coding.

No. Optiview provides a publishing workflow for acting on findings. Keep using your existing tools to monitor answers, citations and other outcomes. Publication and delivery alone do not prove those outcomes improved.

Contact us to review your use case, supported API workflow, access and integration requirements. Customer-controlled publication remains separate from partner suggestions.

No. When authorized, partner credentials can submit unpublished suggestions for customer review, but they cannot publish them.

The customer’s authorized workspace admins and assigned strategists control publication. Partner credentials can read published content and, when explicitly permitted, submit unpublished suggestions. They cannot publish or render pages. Your integration must preserve those boundaries.

Preview the saved draft, publish a reviewed version, and check both normal HTML and an eligible Markdown request. Inspect retained facts, supporting links and your additions, then confirm the expected publication version and delivered content. Delivery records show responses served; they do not establish AI outcomes.

Delivery telemetry alone does not establish a verified AI requester. A crawler name or Markdown preference is not identity verification. Correlating delivery with independently validated requester identity requires additional evidence; indexing, model use and citations require further evidence.

Define questions, reference facts, baseline observations and evaluation dates before publication. Use your existing monitoring tools to track answers and citations afterward. Model changes, competing sources and retrieval updates can also affect results, so before-and-after movement alone does not prove causation.

The recorded composition release passed 660 fixed-corpus source executions with no composition invariant failures. Checks covered original inventory and prose, destination preservation, occurrence mapping and deterministic output. This is internal engineering evidence for that corpus, not universal extraction accuracy or proof of AI visibility gains. See Evidence & methodology for scope and the reviewed release baseline.