CUSTOMER DOCUMENTATION

Technical setup and delivery guide

Everything your team needs to connect Optiview, publish approved brand information, and verify that your website continues to work as expected.

Reviewed October 21, 2026 · Website setup, content publishing and launch checks

REVIEWED EVIDENCE: October 22, 2026

Single-page parser: semantic-v3.10.14. The deterministic parser includes source-owned title and editorial metadata repairs, responsive heading handling, interface heading exclusion, punctuation serialization, source-backed appendix labels, and valid Markdown for linked cards. Core parsing does not generate FAQs, infer company-wide information or use an LLM. Existing source-review bindings, custom selectors and approved published supplements retain their review controls.

Extraction: semantic-v3.10.14
Composition: composition-v2.1.0
Presentation: presentation-v1.2.0

Source checks, compact directory links and exact-source review are covered below. See validation and evidence.

CHOOSE YOUR STARTING POINT

What are you here to do?

Pick your role to jump straight to the relevant instructions. The full guide is below.

Get ready

Your first successful delivery

For your first setup, start with one public page.

Not the person who manages your website? Choose Send setup to my web team in the dashboard’s ownership or Connection section. Copy the domain-specific checklist or open an email draft. Nothing is sent automatically, and the message contains no credentials or access grant. Your workspace admin coordinates authorized access; never share an admin key.

  1. Add your website and verify ownership.
  2. Open Markdown and preview a public page you know well. Check Parser output against the website.
  3. Build your Narrative Graph, save your answers and review the graph.
  4. Complete the recommended connection and test normal website behavior immediately.
  5. Publish the reviewed graph. Use Markdown / Published output preview to inspect the combined result.
  6. Run the live HTML and Markdown checks below against the connected hostname.
  7. Confirm how to pause delivery and restore your previous routing before expanding the rollout.

Optiview does not replace your CMS or bypass your security. It gives you a separate machine-readable source that your team controls.

Choose a role or browse the guide

Get ready

How Optiview fits together

ComponentPurpose
WorkspaceAn agency or customer tenant containing members, domains, drafts, and usage.
DomainOne exact hostname, such as www.your-domain.com. API keys, settings and publications remain scoped to that hostname. A valid same-workspace root DNS proof can also verify its www counterpart; HTTP proof and a www-only DNS proof cannot authorize the root.
SourcePublic HTML fetched by Optiview, optionally browser-rendered, or HTML supplied by your server.
ParserRemoves interface clutter, preserves supported content structures, cleans links, and identifies some incomplete or error responses.
Approved contentYour approved Narrative Graph additions, plus compatible historical publications. Publishing them does not control an AI model’s answers.
DraftEditable, saved configuration. Saving does not publish it.
PublicationA saved snapshot used for delivery, with a version and optional exact-path override.
DeliveryA proxy response or an API response. It is not evidence of indexing, citation, or verified crawler identity.
1. Website HTML
2. Optiview extraction into clean Markdown
3. Approved, path-matched brand content
4. Versioned publication
5. Optiview edge or your server/CDN

The public demo shows cleaned Markdown and, separately, AI-generated Narrative Graph drafts. In the dashboard, Markdown / Parser output shows the extracted page. Published output preview includes the applicable published configuration and active graph. It does not preview unsaved graph edits or publish anything. Check the response through your real connection after release; a preview is not proof of live delivery.

Choose a role or browse the guide

Get ready

Account access & roles

Contact us to provision workspace access. Contact us if your organization does not yet have a workspace. Submitting the interest form saves your request and alerts hello@optiview.ai. It does not automatically create an account, issue a key, or activate billing. Sign in at app.optiview.ai using your email and personal access key. Store access credentials in your password manager; do not share them in integration code.

RoleScopeCapabilities
Workspace adminAll workspace domainsAdd and verify domains; manage connection settings, credentials, team access, drafts, publishing, and cost assumptions.
StrategistAssigned domains onlyAssigned-domain access to supported source and legacy content workflows. Narrative Graph editing and publishing currently require a workspace admin. Cannot manage routing, API credentials or team access.
ViewerAll workspace domainsRead-only access. Do not assign this role when access must be restricted to one client domain.

An admin uses the team area to create an invitation link, choose the role, and assign domains for a strategist. Invitations expire after seven days and are single-use. Share the link privately with the invited person. Admins can revoke invitations and member access. Dashboard sessions expire; signing in again is separate from rotating a domain API key.

  • Business owner: approves factual claims and the scope of publication.
  • Strategist: maps content to paths and reviews draft/output accuracy.
  • Web or CDN engineer: integrates delivery, secrets, fallback, and cache behavior.
  • Security owner: approves source access, public-page exclusions, and any narrowly scoped security changes.
  • Workspace admin: owns credentials, domain configuration, access reviews, and escalation.
Choose a role or browse the guide

Get ready

Prepare your website

  • Identify the canonical HTTPS hostname that serves the final page without a redirect. www.your-domain.com and your-domain.com have separate API access and configuration. Ownership can share a valid root-scoped DNS proof within the same workspace; see verification below.
  • Inventory page types: homepage, category, product, pricing, documentation, article, and policy pages. Include JavaScript-heavy pages, tables, variants, and legal qualifications.
  • Identify your CMS, hosting provider, CDN, existing Worker/middleware, and the team that controls them. A CMS theme editor alone may be insufficient for server-side integration.
  • Decide which pages are public and nonpersonalized. Exclude accounts, checkout, admin, authenticated content, private previews, and pages containing personal information.
  • Choose a content approver, integration owner, and rollback owner. Keep a record of the current origin and routing configuration.
  • Determine whether initial HTML contains the content. If JavaScript is necessary, assess browser rendering or server-supplied, already-rendered HTML.

Add a website hostname, not a separate domain for every page. The setup flow may resolve the website to its canonical serving hostname; check the address shown before installing proof. Use exact page paths in the Narrative Graph, Markdown preview and API requests.

Choose a role or browse the guide

Connect your website

Verify ownership

  1. In Websites or the workspace overview, select Add website. Enter the hostname in Add your website, without a scheme, path, port or wildcard. Select Continue to verification and check the serving hostname shown. This does not connect traffic or change DNS.
  2. Use the generated ownership challenge. Select DNS TXT, HTML Meta Tag, or File Upload (.well-known). Copy the values exactly from the dashboard.
  3. Install one proof, then select Verify ownership. The challenge expires after seven days; wait at least 15 seconds between checks.
  4. After verification, open Settings / Connection. Keep the proof in place: connection and provisioning operations may check it again.

Option A — DNS TXT

Create a TXT record at the exact name displayed by the dashboard. Add your website normally uses the root-scoped name _optiview.your-domain.com, including for its www hostname; an exact-host challenge can instead use _optiview.www.your-domain.com. The value begins with optiview-verification= and contains a unique challenge. DNS consoles may append the zone name; avoid entering it twice. This proves ownership and does not route traffic. A still-valid root-scoped DNS proof in the same workspace can verify the root/www pair. A www-only TXT record or HTTP proof does not prove control of the root, and another workspace’s proof does not grant access.

Option B — homepage meta tag

<meta name="optiview-verification" content="COPY_THE_ENTIRE_DASHBOARD_VALUE" />

Place exactly one matching tag in the homepage’s server-rendered HTML <head>. The verifier fetches https://YOUR_HOSTNAME/ and requires a direct 200 HTML response. It does not execute JavaScript or follow redirects. Inspect the initial HTML, not only the browser’s live DOM. A tag inserted after hydration will not verify.

Option C — public text file

https://YOUR_HOSTNAME/.well-known/optiview-verification.txt

File contents: the entire TXT record value shown in the dashboard

Serve the exact value as a public text file over HTTPS with a direct 200 response. The path is optiview-verification.txt, not optiview.txt. Do not wrap the value in HTML. HTTP proof requires a public DNS resolution and a valid HTTPS endpoint. A redirect from apex to www means you should register and verify www instead.

A hostname already registered to another workspace cannot be claimed again. Ask the workspace operator to reconcile an authorized transfer. Successful verification proves control; it does not change DNS, create a route, bypass a firewall, or publish content. Each newly added website must complete its own Billing setup before connection or publishing: an active website subscription or an explicit website-specific complimentary approval from Optiview. A legacy workspace allowance does not approve additional websites.

Choose a role or browse the guide

Connect your website

Choose your connection

Open Settings / Connection. Verified sites awaiting setup are checked automatically; Check my website repeats the check. Optiview inspects the public page, DNS and available Cloudflare authorization without changing your site. It recommends an authorized route, guides you through DNS setup, or asks for a hosting review. You do not need to select an integration before running this check.

Setup is assisted. Follow the options offered for your verified hostname. Shopify storefronts require a reviewed integration; automatic proxy setup is not supported. Keep existing DNS unchanged until the supported method is agreed.

Where the dashboard offers provider-assisted DNS setup, your domain administrator signs in to the DNS provider and approves the displayed changes. Otherwise, add the displayed records manually. Send setup to my web team lets marketing hand over that work. Optiview checks the connection afterward.

PathUse whenCustomer work
Guided DNS connectionA verified hostname with a hosting destination that passes the supported HTTPS forwarding checks.Confirm hosting, complete the supplied validation steps, then change the traffic record when HTTPS is ready. Use provider-assisted approval when offered, or enter the displayed records manually. No customer Cloudflare API token is needed for this DNS path.
Authorized Cloudflare routeYour proxied hostname belongs to the Cloudflare account delegated to the workspace.Admin connects the route; technical owner checks origin health, overlapping routes, and security.
Custom API integrationYour team needs to keep delivery within its own server or CDN.APIs are available. Contact Optiview to discuss access and setup.

For API integration, DNS can stay as it is. You still need engineering access to a server or CDN that can call the API and deliver the response. An API key or ownership meta tag alone does not place Optiview into the request path. Do not make a CNAME change merely because a certificate becomes active.

Guided DNS connection — customer steps

  1. After the hosting check recommends Guided DNS connection, review the tested hosting destination. If it cannot be validated, setup stays in hosting review and does not supply traffic changes. Enable Load JavaScript before extraction if important content requires JavaScript.
  2. Confirm the tested HTTPS hosting hostname. Do not enter the public hostname being connected or a Cloudflare proxy IP. Save the original DNS record for rollback.
  3. Click Prepare connection. Optiview tests the hosting destination and forwarded HTML, checks published Markdown through the gateway, then requests the hostname certificate. Preparation does not change customer DNS.
  4. Add the displayed hostname ownership TXT and certificate verification records. When a delegated certificate CNAME is supplied, keep it DNS-only. Do not replace the website traffic record yet. Keep the Optiview ownership proof and certificate delegation records in place.
  5. After the certificate and origin checks pass, the dashboard displays the traffic CNAME to proxy.optiview.ai. Replace only the website record for the exact hostname. For Cloudflare DNS, keep the traffic CNAME Proxied to retain the customer zone in the request path. Root domains require CNAME flattening; otherwise use a supported www hostname or a Custom API integration.
  6. Optiview checks pending connections every five minutes for up to 48 hours. It observes the real public route, checks HTML, and tests published Markdown before marking Connected. The open dashboard refreshes status automatically. Check connection now is also available. If the 48-hour window expires, finish your DNS changes and click Restart automatic checks. You do not need to keep the dashboard open.
  7. Preview the homepage and important internal pages, save and review brand content, then publish. Test forms, login, redirects, cookies and assets before treating the production cutover as complete.
Technical behavior and hosting compatibility

Hosting compatibility: the gateway connects over HTTPS to the saved hosting hostname and passes the public hostname in X-Forwarded-Host. It preserves method, body, query and cookies, and maps same-origin redirect destinations back to the public hostname. For supported shared-hosting destinations, the hostname-preserving relay retains the public Host header and TLS server name, validates the certificate, and connects only to a checked public origin IP. The selected mode is tested before DNS instructions appear. Origins that cannot pass either forwarding mode require a reviewed custom integration. WebSocket upgrades and large transfers are not supported by the bounded relay. Existing connected routes/API sites are not automatically migrated.

Pause optimization and roll back routing

Pause optimization stops Markdown delivery through the website connection while continuing to forward ordinary HTML through Optiview. It does not remove Optiview from DNS. To roll back routing, restore the saved original DNS record. Do not delete forwarding configuration or certificates while customer DNS still points to Optiview. Failed Markdown activation leaves optimization off and reports the issue; ordinary requests continue to the saved hosting destination. Origin outages or gateway/configuration failures can still affect availability.

Your domain administrator approves DNS changes. The number of records depends on ownership and HTTPS validation; this is not a universal one-record setup. Hosting detection is a preliminary check, not a guarantee of compatibility. Connection preparation and live checks still run before activation.

Choose a role or browse the guide

Connect your website

Connect a Cloudflare route

  1. Confirm the exact hostname is verified, its existing A/AAAA/CNAME record is proxied through Cloudflare, and the zone belongs to the configured delegated account.
  2. Open Settings / Connection / Authorize Cloudflare access. Click Check Cloudflare access to test the existing workspace token. If access is missing, expand Authorize this website with a scoped token.
  3. Create a Cloudflare API token with Zone Read, DNS Read and Workers Routes Edit, limited to Include / Specific zone for this website. Enter the Zone ID and token in the secure admin form, then click Validate & save authorization. Tokens are encrypted server-side and never returned. Do not paste tokens into page content or client-side application code.
  4. Check for overlapping Worker routes and confirm the origin is healthy. Resolve conflicts with the route owner before changing routing.
  5. After access checks pass, click Connect Route. Read-only access checks confirm zone, DNS and route visibility; Cloudflare checks route-write permission during connection. Connecting creates or reconciles the hostname/* Worker route without changing DNS records or security rules.
  6. Publish approved content and run the HTML/Markdown checks in this guide. Inspect real origin behavior and security logs before expanding the rollout.

A verified domain in a different Cloudflare account is not automatically eligible for this delegated route. Use guided DNS connection when the hosting origin is compatible, or the Custom API integration. If you specifically need a delegated route, ask the operator to configure account access. Do not broaden token access just to suppress a connection error.

Use Disconnect Route to remove the managed route while retaining drafts. If route ownership changed or cleanup failed, stop and ask the operator to reconcile it. Do not delete unrelated Workers or routes. Retest ordinary HTML after disconnecting.

To rotate access, replace the saved token in the same form. To remove it, disconnect the managed route first, remove the saved credential, and revoke the unused token in Cloudflare. Removing a domain credential does not remove any separate workspace-level authorization. The route token cannot grant itself more zone permissions.

Choose a role or browse the guide

Connect your website

APIs & custom integrations

Optiview APIs are available. Contact us to discuss access, your hosting setup and integration requirements. We’ll provide the technical documentation for your use case.

Choose a role or browse the guide

Connect your website

Source extraction settings

Open Settings / Extraction to review the main content selector. New website configuration starts with main, article, .content, with parser fallback behavior. Test the selector against each important page type: a description-only selector can omit prices, variants or qualifications elsewhere on the page. Brand additions belong in the Narrative Graph, not extraction settings.

Extraction preserves meaningful source content, structure and links where supported. The established deterministic extraction and presentation pipeline is the default for public sources. Custom selectors, existing source-review bindings and approved published supplements retain their original representation. If conversion or source checks fail, Optiview preserves the existing source rather than silently publishing incomplete Markdown.

In Settings / Connection / How Optiview reads this website, an admin can enable Load JavaScript before extraction. The toggle is saved immediately, separately from graph drafts. Browser work consumes the rendering budget. Some API rendering results can be cached for up to 15 minutes; website delivery, URL acquisition and graph composition can bypass that cache. Do not rely on a 15-minute cache for every request.

Browser rendering is bounded and restricts resources. Cross-origin dependencies, login flows, challenges, canvas content, and some component architectures may remain incomplete. Rendering is not a WAF bypass. For controlled applications, supplying already-rendered HTML can be a better integration than depending on an external browser.

See Evidence & methodology for the restoration comparison and separately scoped parser validation. The public demo, previews and delivery use the same global parser selection policy; acquisition settings and source responses can still differ. Inspect the parser version returned with each result. A changed parser does not inherit an earlier source approval.

Regional pages, language and redirects

Preview the exact regional URL you intend to publish, and check its language, prices, dates and qualifications. The demo displays the actual source URL after bounded redirects; it does not infer your preferred market or translate the page.

Live delivery preserves origin redirects. URL-based API rendering requires a direct public HTML response. A successful anonymous demo does not establish live-delivery eligibility.

The source can differ by request language, cookies or network location. Test each intended variant. Browser fallback cannot assume it matches a language-specific request; unsupported contexts keep the original response.

Generated link labels can gain source-backed separators in the versioned presentation pass. Original labels and Markdown remain in evidence. This does not assign meanings to prices or combine regional content.

Choose a role or browse the guide

Prepare & publish

Prepare brand content

The parser extracts, cleans and organizes the page without an LLM. The Narrative Graph is the single place to edit brand additions: Identity, Story, Offerings, Trust, Knowledge and Actions.

  1. Open your website and select Narrative Graph. Follow the six guided steps on first use.
  2. Enter your content and choose Entire website or a specific page under Applies to. For a page, enter its exact path. Save the draft.
  3. After setup, select a node in the graph to add, edit or delete items. Saving an edit made from the graph returns you to the graph for review.
  4. Review the Graph, then select Publish graph or Publish changes. That action approves the saved items and activates the publication. Saving alone never publishes.

Scope and publication

Site-wide information is added first, followed by approved content for the exact requested page path. Page content supplements site-wide content; it does not silently overwrite it. Match the site’s trailing-slash convention. Scope edits need fresh review and publication. The existing live snapshot stays unchanged until then.

Existing content

Previous schemas, added blocks, metadata, page-guide text and saved optimization drafts remain accessible as read-only records. Existing Graph records can be copied into the element editor as a new proposal. This does not retire their original publication. Migration and retirement require an explicit content decision; saved records and history are not deleted automatically.

Public demo

The public demo runs the deterministic parser, then uses OpenAI to propose six Narrative Graph elements from up to 24,000 characters of combined source text. It may capture up to two observed, same-site About, FAQ or policy links in addition to the submitted page. Review the supporting passages; missing facts require your input. Demo drafts are not saved to a workspace or published. The combined preview includes the parser output and generated drafts. If drafting fails or reaches its allowance, the parser result remains available.

Choose a role or browse the guide

Prepare & publish

Page Guide & frontmatter

Historical Page Guide text is available as a read-only record. Edit brand content in Narrative Graph elements. Your web team can maintain a separate llms.txt file at your origin; saving Graph content does not install a discovery endpoint.

# Your organization
> A factual one-sentence description.

## Public resources
- [Product](https://www.your-domain.com/product/): Approved product information.
- [Documentation](https://www.your-domain.com/docs/): Technical integration details.
- [Policies](https://www.your-domain.com/policies/): Published policies and conditions.

An API-only integration does not automatically create a public /llms.txt endpoint on your site. Your team must serve it through its own infrastructure if desired. The file is a guide, not an enforceable instruction to crawlers or a replacement for robots.txt.

Frontmatter is the metadata block between --- lines at the start of Markdown. Inspect the source URL, delivery metadata and available publication identifiers. Extraction publication identifiers and Narrative Graph versions describe separate layers; do not treat a single published or brand_content field as proof that your graph is present or absent. Check the actual graph additions in Published output preview and in the live response. Publication timestamps describe saved snapshots, not the last time your website changed. Existing custom metadata cannot override engine-owned provenance fields.

Choose a role or browse the guide

Prepare & publish

Preview & publish

  1. Open Narrative Graph. Save your answers or edits, then review the graph. Check the facts, links and whether each item applies to the entire website or an exact page.
  2. Select Publish graph or Publish changes. This approves the saved graph items and activates that graph version. Saving a draft alone does not publish it.
  3. Open Markdown, enter a Page path such as /, and select Preview page. Choose Published output preview to inspect the source with its published additions. Parser output shows the extracted page separately.
  4. Check headings, product facts, links, tables, prices, qualifications and the matching narrative additions. Expand Source checks & technical details to inspect source status and evidence.
  5. If source review is required, inspect the evidence and approve the exact page source only when it is accurate. Publishing the graph does not approve a flagged source. Approval is bound to the page, source, extraction settings and publication; relevant changes require a new review. Resolve source-unavailable errors before Markdown delivery.
  6. Fetch through the connected website or your API integration. Inspect the response format, published content and available version metadata. Compare actual delivery with the preview.

Ownership verification unlocks the Markdown preview before connection, including optional JavaScript rendering. Preview fetches only public content without visitor credentials. Supported language preferences are preserved during live browser acquisition; wildcard language does not select a locale. Unsupported device or request context, cookies and cache restrictions may limit live delivery even when preview works. Inspect X-Optiview-Delivery-Status and X-Optiview-Delivery-Reason when an eligible request receives its original response. API-only sites can preview here and test delivery separately through their server integration.

Saving increments the draft version. If someone else saves or a partner submits a suggestion, stale saves and publications can return a conflict. Reload, review the latest changes, and reapply your edits rather than overwriting them blindly.

Advanced extraction publications can have global or exact-path snapshots, separate from Narrative Graph item scope. An exact-path snapshot applies only to that path; publishing a global extraction snapshot clears those overrides. Check the applicable configuration when diagnosing different results across pages. Publishing selects a new cache version for subsequent requests; it does not alter responses already delivered.

To correct graph content, edit it, save, review and publish again. To withdraw graph additions, use Unpublish in the graph. This is separate from stopping all Markdown delivery. For urgent delivery withdrawal, pause optimization for a guided DNS connection, disconnect a managed route or disable your own adapter, as appropriate. Retain the original DNS record for routing rollback. Revoking a render key stops API delivery for that key; it does not disconnect an independent edge route.

Choose a role or browse the guide

Launch & maintain

Test your delivery

Use the exact HTTPS address that serves the final public page. Verify ownership, finish the connection and publish the graph before expecting its additions in live Markdown. These commands do not connect or publish anything. Test the homepage and important internal pages, and compare the returned content with the website and graph.

Run these commands in a terminal with curl (macOS, Linux or Git Bash). In Windows PowerShell, use curl.exe rather than the curl alias. The first example uses Optiview’s live homepage so it works without editing placeholders or supplying an API key. It prints response headers and Markdown directly in the terminal.

curl --silent --show-error --compressed --connect-timeout 10 --max-time 60 \
  --header 'Accept: text/markdown' \
  --dump-header - \
  'https://optiview.ai/'

Expect HTTP 200 and Content-Type: text/markdown, followed by the document. Header names are case-insensitive. A 200 HTML response is not a successful Markdown check. Do not use curl -I for this test: it sends HEAD and does not download the document.

Check your own connected website

Set OPTIVIEW_TEST_URL to your final, public page URL. The runnable default below is Optiview’s homepage. It saves separate HTML and Markdown responses in a new temporary folder, prints the HTTP status and content type, then displays the Markdown headers and first 40 lines. Use the printed folder path to inspect the complete files. No dashboard access key is required for public website delivery.

# Replace this with your connected website's final HTTPS page URL.
OPTIVIEW_TEST_URL='https://optiview.ai/'
OPTIVIEW_TEST_DIR=$(mktemp -d)

curl --silent --show-error --compressed --connect-timeout 10 --max-time 60 \
  --header 'Accept: text/html' \
  --dump-header "$OPTIVIEW_TEST_DIR/html.headers" \
  --output "$OPTIVIEW_TEST_DIR/page.html" \
  --write-out 'HTML check: HTTP %{http_code}; %{content_type}\n' \
  "$OPTIVIEW_TEST_URL"

curl --silent --show-error --compressed --connect-timeout 10 --max-time 60 \
  --header 'Accept: text/markdown' \
  --dump-header "$OPTIVIEW_TEST_DIR/markdown.headers" \
  --output "$OPTIVIEW_TEST_DIR/page.md" \
  --write-out 'Markdown check: HTTP %{http_code}; %{content_type}\n' \
  "$OPTIVIEW_TEST_URL"

cat "$OPTIVIEW_TEST_DIR/markdown.headers"
sed -n '1,40p' "$OPTIVIEW_TEST_DIR/page.md"
printf '\nComplete responses saved in: %s\n' "$OPTIVIEW_TEST_DIR"

The two-request script uses POSIX shell syntax (macOS, Linux or Git Bash). For PowerShell, run the first single curl.exe command twice with your URL, once with Accept: text/html and once with Accept: text/markdown. Copy commands from the code blocks only.

Read the result

ResultWhat to do
200 + text/html for the HTML checkOpen page.html and confirm the normal website response.
200 + text/markdown for the Markdown checkInspect page.md for expected page facts, links and the published graph additions that match this path.
301, 302, 307 or 308Inspect Location in the headers. Set the test URL to the final HTTPS serving address and rerun. The examples intentionally do not follow redirects, so a hostname change stays visible.
200 + text/html for the Markdown checkThe website returned HTML instead of Markdown. Confirm its connection, optimization state, public-page eligibility and source checks. Inspect X-Optiview-Delivery-Status and X-Optiview-Delivery-Reason when present; custom adapters may use different diagnostics.
401, 403, 429, 5xx or a curl errorRead the response and terminal error. Check access, Security & WAF, capacity, DNS and TLS as appropriate. Do not interpret an error page as parsed website content.
  • Use an ordinary browser User-Agent with Accept: text/html to test visitor HTML. A recognized tool name can qualify for optimized public content but does not authenticate the provider. Test tool requests separately and inspect the response body, delivery headers and requester verification in reporting.
  • Optiview serves Markdown to requests that explicitly prefer text/markdown. Recognized AI tool names and supported Cloudflare bot categories can also qualify: AI tools with absent or wildcard Accept receive Markdown, while requests accepting HTML can receive the same prepared source and applicable published graph as HTML. Traditional search crawlers, including Googlebot, bypass Optiview conversion and receive the original site response, even if they request Markdown. A declared tool name permits public content delivery but does not verify identity. Published provider IP ranges and Cloudflare category evidence are reported separately. Ordinary browsers retain the original page. Connection, entitlement, source-review and publication checks still apply; authenticated, cookie-bearing and range requests are not converted. Delivery does not guarantee indexing, AI use or citations.
  • Assert factual retention: product names, prices and currencies, variants, meaningful category links, technical tables, and qualifiers. Check for placeholder text, UI controls, duplicate blocks, and malformed links.
  • Inspect source-review status. A flagged source needs exact-source approval for delivery; publication alone is insufficient. Compare composed links with the original occurrence inventory when evidence is available. Repeated groups may be compacted, but destinations and source qualifications must remain represented.
  • Check homepage, deep product, category, documentation/article, and policy pages where applicable. Test trailing slashes and exact-path versus global publication.
  • Confirm private/cookie-bearing routes are excluded and no sensitive data enters payloads or logs. Verify cache variants cannot mix HTML with Markdown or one customer with another.
  • After an approved content update, confirm a new publication version and the changed content. Confirm your own CDN cache refreshes too.
  • Verify telemetry appears in the expected API or proxy channel. Preview traffic must not be used as evidence of organic crawler adoption.

An API-only setup needs your server or CDN adapter installed for these public website URL checks to return Markdown. API credentials are for the API endpoint, not these public requests. A separate /llms.txt resource is optional: test it only if your web team has actually installed one.

Choose a role or browse the guide

Launch & maintain

Usage & operations

Open your website’s Activity tab to inspect recorded Markdown delivery, crawler activity and response details for that website. The default is the last five days; use the date-range control to change the period. Performance in the sidebar covers the workspace. Production metrics exclude identified preview and demo activity. Recorded requests are not proof of AI citations or recommendations, and telemetry may arrive after a short delay.

Current configured limits — reviewed October 14, 2026

Implementation controlCurrent limit or behavior
Domain browser rendering100 attempts per domain and 500 per workspace per day. Attempts, including unsuccessful ones, consume budget.
Public Website Preview10 requests per IP per UTC hour; three per minute; 30 per hostname per hour; 500 globally per UTC day. Shared capacity can be exhausted.
Public demo AI draftingTen admitted jobs per IP per UTC hour and 1,000 globally per UTC day. A capture receipt can be used once. Failed admitted jobs also consume allowance; these limits are separate from page parsing.
Rendered page cacheUp to 15 minutes for cacheable API rendering results. Website delivery, URL acquisition and graph composition may bypass this cache.

These are current implementation limits, not a contracted capacity or SLA. Confirm capacity with the operator before a launch, automated bulk test, or customer rollout. Do not rotate keys to evade quotas. Retry transient failures with bounded backoff and keep your origin fallback active.

Monitor extraction failures, partial content, latency, delivery counts, budget use, and stale publications. Recheck representative pages after CMS/theme releases. Review teammate access and key owners regularly. If service eligibility is paused, optimization/publishing can stop while drafts and history remain accessible; the edge falls back to origin. Customer-managed adapters must implement their own fallback.

Choose a role or browse the guide

Launch & maintain

Troubleshooting

SymptomAction
Verification failsCheck exact hostname, unexpired challenge, exact TXT/token value, public HTTPS, and direct 200. Meta proof must be in initial head HTML.
Verified, but Connect Route failsCheck delegated account, scoped operator token, proxied DNS, origin health, and overlapping routes. Verification alone is insufficient.
409 or stale draft warningReload and reconcile current draft/credential revision, ownership state, or publication scope. Avoid blind retries of state changes.
429A rate or shared compute budget was reached. Back off, inspect the message, and coordinate capacity; do not hammer the public demo.
502 / rendering failureServe origin, capture sanitized diagnostics, and retry later within budget. Inspect browser dependencies and source accessibility.
Missing prices/categories/table labelsCompare initial and rendered HTML, inspect selector scope and partial warnings, and test the actual page. Do not compensate by inventing source facts.
Saved content absentCheck saved versus published state, path match, publication override, and external CDN cache. Public preview examples are not your saved content.
Blocked sourceInspect origin/security logs and response details. A denial or system error alone does not identify which WAF blocked it or prove other crawlers are blocked.
Repeated or awkward link groupsCompare original compiler Markdown and source_composition. If information exists in the inventory but is poorly presented, report a composition issue with URL, source mode and versions.
Review required after publicationRun a new Markdown preview, select Published output preview and inspect Source checks & technical details. Approve the exact source only if appropriate. Publishing content alone does not approve a flagged source.
Output changed after a parser releaseRe-run representative pages, compare original and composed output, record versions, and renew source approval where required. Do not assume an old approval covers a new representation.

A client-side shell can benefit from rendering if content is available to the bounded browser. A security denial needs authorized access or supplied HTML. No extraction mode automatically defeats your firewall. Avoid removing security controls broadly; diagnose the exact rule and request first.

Choose a role or browse the guide

Launch & maintain

Security & privacy

  • Treat ownership proof, dashboard access, render credentials, and partner credentials as separate controls. Use least privilege and exact-host scope.
  • Only submit content you are authorized to process. Strip personal, authenticated, confidential, and personalized information before Push ingestion.
  • Keep existing robots, authentication, and WAF decisions under your team’s control. Content negotiation is not authentication and is available to any compatible requester.
  • If a security exception is necessary, have your security team inspect the actual blocking component and use narrowly scoped rules. Do not allowlist a crawler solely by its User-Agent string.
  • Review provider processing, retention, and your organization’s requirements before sending source content. Optiview should not be assumed to meet an unprovided certification, data residency requirement, or contractual SLA.
  • Never include tokens, customer records, or private HTML when escalating an issue. Supply a sanitized URL/path, timestamp, status, source mode, publication version, and redacted error instead.

See the Privacy Policy and Evidence & methodology for public boundaries. Content availability and delivery can be tested; better AI answers, indexing, and citations require separate evidence. There is no guarantee that a named crawler requests Markdown or uses any delivered payload.

Delivery and fallback boundaries

Optiview serves Markdown to requests that explicitly prefer text/markdown. Recognized AI tool names and supported Cloudflare bot categories can also qualify: AI tools with absent or wildcard Accept receive Markdown, while requests accepting HTML can receive the same prepared source and applicable published graph as HTML. Traditional search crawlers, including Googlebot, bypass Optiview conversion and receive the original site response, even if they request Markdown. A declared tool name permits public content delivery but does not verify identity. Published provider IP ranges and Cloudflare category evidence are reported separately. Ordinary browsers retain the original page. Connection, entitlement, source-review and publication checks still apply; authenticated, cookie-bearing and range requests are not converted. Delivery does not guarantee indexing, AI use or citations.

If a request cannot receive approved Markdown, the edge route falls back to origin delivery. Gateway or origin failures may return an error. A DNS-connected gateway remains in the traffic path and can affect availability. Custom API integrations must implement their own fallback. Keep the previous DNS record and test rollback.

Optiview is a shared multi-tenant service; no security certification or dedicated deployment is claimed. Use approved public nonpersonalized content and server-side credentials. Delivery records confirm responses, not AI indexing, citations or recommendations.

Optiview may fetch accessible public pages, use bounded supported JavaScript rendering or process authorized supplied HTML without executing its scripts. These methods do not bypass access controls or guarantee complete extraction. Source-review-required results need exact-source approval through the published preview.

Choose a role or browse the guide

Launch & maintain

Go-live handoff

  • Record the workspace, exact hostname, integration mode, public-path allowlist, and responsible business/technical owners.
  • Store keys in your secret manager, record rotation ownership, and remove temporary credentials from local test files.
  • Attach approved content, source evidence, publication version, and representative before/after payload checks to your internal release record.
  • Document timeouts, quota handling, cache invalidation, private-route exclusions, and the tested origin fallback.
  • Assign monitoring and an escalation owner. Schedule content review after material pricing, policy, product, or CMS changes.
  • Document how to disable your adapter or disconnect the managed route, plus the origin checks to run afterward.

Use your established Optiview onboarding contact or workspace operator for provisioning and incident escalation. If you do not have one, contact us. Provide sanitized reproduction steps and observed responses; do not send credentials. Capabilities, limits and supported integrations may change as the platform develops.

Open the dashboard · API access · Frequently asked questions

Choose a role or browse the guide