---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/ai-bot-identity-verification/
brand_content: included
publication_version: "9.0"
published_at: 2026-10-16T20:36:07Z
composition_version: composition-v2.1.0
presentation_version: presentation-v1.2.3
brand_content_source: narrative_graph
delivery_publication: graph:33
narrative_versions:
  - 33
narrative_version: 33
---

[Resources](https://optiview.ai/resources/) [Implementation and operations](https://optiview.ai/resources/topics/implementation/)

Technical verification — October 30, 2026

# How to Distinguish Claimed AI Bot Identity From Verified Bot Traffic

A request carrying the name of an AI crawler is not automatically a verified request from that provider. Attribution requires evidence beyond the User-Agent string.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/ai-bot-identity-verification.md)

Website analytics may show requests identifying themselves as Googlebot, GPTBot or another automated client. Those labels are useful observations, but a client can generally submit an arbitrary User-Agent header.

Google's [crawler verification documentation](https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests) describes methods for verifying requests through documented IP ranges or DNS checks. OpenAI separately publishes [crawler documentation](https://platform.openai.com/docs/bots) covering named clients and associated network information.

The objective of this checklist is conservative attribution: distinguishing what a request claims from what the available infrastructure evidence supports. It is not a procedure for circumventing bot defenses, impersonating providers or collecting private user information.

## 1\. Establish attribution confidence levels

| Level | Available evidence | Permitted conclusion |
| --- | --- | --- |
| Claimed | User-Agent contains a provider name | Request claims that identity |
| Corroborated | Network information is consistent but not fully verified | Possible provider origin |
| Verified | Provider-documented origin verification passes | Origin supported by verification |
| Unknown | Evidence is unavailable or insufficient | No provider attribution |
| Contradicted | Observed origin conflicts with verified provider criteria | Claimed identity not substantiated |

These labels form a proposed internal classification scheme. They are not provider-issued certifications, and a verified network origin does not reveal every reason the provider made the request.

## 2\. Preserve the minimum request evidence

*   Request timestamp and the requested public path.
*   Claimed User-Agent and other relevant request metadata.
*   Originating address as recorded at a trusted infrastructure boundary.
*   Trusted proxy or CDN context affecting address attribution.
*   HTTP response status and relevant delivery classification.
*   Verification method, reference source and observation date.
*   Investigator decision with unresolved limitations.

Do not blindly trust client-supplied forwarding headers as proof of origin. Determine which infrastructure component actually observed the request and how trusted proxy information is handled. Apply appropriate retention and access controls to operational logs.

## 3\. Apply the relevant provider method

Google describes verification through its published crawler IP ranges or reverse DNS followed by forward DNS confirmation. Its infrastructure documentation also distinguishes crawler categories, so a valid Google origin does not automatically mean the request was ordinary Googlebot.

For OpenAI, use the current [official crawler documentation](https://platform.openai.com/docs/bots) and the published information applicable to the claimed client. Do not assume Google's DNS patterns or verification procedure applies to every provider.

1.  Identify the exact claimed client.
2.  Locate that client's current official verification guidance.
3.  Determine whether the trusted request metadata is sufficient.
4.  Apply only the documented origin-verification procedure.
5.  Record the result and supporting reference.
6.  Classify the request as verified, unverified or contradicted.

## 4\. Separate origin verification from behavioral claims

| Observed event | What it establishes | What remains unproven |
| --- | --- | --- |
| Verified crawler request | Supported origin and observed request | Indexing or subsequent answer use |
| Successful Markdown delivery | A response was delivered | That a model used the content |
| Repeated requests | Observed request frequency | Unique users or commercial demand |
| Citation in an answer | Visible answer reference | Exact internal acquisition path |

An IP verification result is not evidence that a model read the entire page. An observed request is also not proof of inclusion in an index, answer generation or customer intent.

## 5\. Produce an auditable traffic report

The deliverable is an attribution ledger identifying the request, claimed identity, applicable verification evidence, confidence classification and observed delivery outcome. Aggregate only records sharing compatible definitions.

Optiview's [setup guide](https://optiview.ai/docs/setup/) distinguishes response delivery from verified crawler identity and downstream AI use. Maintain that boundary when reporting bot activity to business stakeholders.

## Additional source context

Treat User-Agent as a claim, not proof. Attribute traffic to a named provider only when the request evidence satisfies an appropriate current provider verification method.

Make your brand easier for AI to understand.

### Explore

[Website publishing](https://optiview.ai/products/publish/) · [Developer tools](https://optiview.ai/products/#developers) · [Pricing](https://optiview.ai/pricing/)

### Learn

[Guides](https://optiview.ai/resources/) · [Developer docs](https://optiview.ai/developers/) · [Research](https://optiview.ai/proof/) · [FAQ](https://optiview.ai/faq/)

### Company

[About Optiview](https://optiview.ai/about/) · [Agencies](https://optiview.ai/partners/) · [Contact](https://optiview.ai/#contact) · [Privacy](https://optiview.ai/privacy/) · [Billing terms](https://optiview.ai/billing-policy/)

## Additional page links

- [Does AI receive the page your visitors see?](https://optiview.ai/resources/website-platforms-ai-readability/) — Continue reading
- [Four files. Four different jobs.](https://optiview.ai/resources/four-discovery-files/) — Continue reading
- [How to convert HTML to Markdown for AI applications](https://optiview.ai/resources/html-to-markdown-api-guide/) — Continue reading
- [Preview a page](https://optiview.ai/demo/) — Continue reading
- [Read the setup guide](https://optiview.ai/docs/setup/) — Continue reading


---

# Published brand narrative

# Site-wide brand information

## Who we are

### Optiview — Parse, Retrieve and Publish for AI

Optiview helps businesses and developers make website information easier for AI to use. Parse converts supplied HTML into clean Markdown and source metadata. Retrieve fetches an eligible public HTTPS webpage and prepares its content. Publish helps a verified business prepare its own website content and make approved Narrative Graph context available through a supported connection.

Parse and Retrieve use application keys and a prepaid developer wallet. Publish has separate website setup, ownership checks and a subscription. Optiview does not control whether an outside AI service discovers, uses or cites the resulting content.

Applies to: Optiview

## Why we matter

### A clearer source, from website content to business context

Webpages mix useful information with navigation, layout and application code. Businesses may also have important qualifications, answers and context that are not clearly published.

Optiview gives developers a way to prepare source content for their applications, and gives businesses a way to publish the context their teams approve. Your application chooses how to use Parse and Retrieve results. Your business controls what it publishes through Publish.

Clearer publishing makes information available; it does not determine an AI system’s answer. Each outside service chooses its own retrieval, recommendations and citations.

## What we offer

### Three products, with separate jobs and clear pricing

- **Optiview Parse:** Supply complete HTML and a source URL. Receive clean Markdown, source and output hashes, parser details and processing warnings. Parse does not fetch the URL or execute JavaScript. A successful page uses 1 credit.
- **Optiview Retrieve:** Supply one eligible public HTTPS URL. Optiview checks supported access and publisher policies, fetches anonymous static HTML and parses it. It does not search the web, execute JavaScript, bypass a login or access private networks. A successful page uses 5 credits total, including parsing.
- **Developer credits:** USD $20 buys 20,000 credits shared by Parse and Retrieve. There is no developer subscription, automatic recharge or scheduled credit expiration. Failed jobs consume no credits. Applicable taxes and the total appear at checkout. Source size, quotas and retention limits apply.
- **Optiview Publish:** USD $99 per website per month plus applicable tax. Connect a verified website, review the prepared source and optionally maintain approved Narrative Graph context in Identity, Story, Offerings, Trust, Knowledge and Actions. Choose site-wide or exact-page scope. Saving drafts does not publish them. Eligible AI tools can receive prepared Markdown or HTML through supported delivery, while ordinary visitors keep the normal website.

Developer credits do not purchase Publish subscriptions. Parse and Retrieve do not add a customer’s private Narrative Graph to arbitrary third-party pages. See https://optiview.ai/pricing/ and https://optiview.ai/developers/ for the current offer and limits.

## Why trust us

### Inspect the output and understand what the evidence establishes

Developers can inspect the prepared Markdown, job status, source metadata, processing warnings and credit ledger. Retrieve records the public source response it observed; Parse identifies supplied HTML rather than claiming to verify the current origin.

Publish administrators can review parser output, the combined published-output preview, source checks and publication history. A preview is separate from a recorded live delivery. Saved edits remain separate from the active publication until explicitly published.

Our experiment pages contain selected first-party AI conversations and source comparisons. Delivery records establish what was served, not downstream ingestion, recommendations, citations or revenue. Observed language matches do not establish causation or a consistent visibility improvement. Explore the evidence and limitations at https://optiview.ai/proof/.

## Helpful knowledge

### Common questions about the three products

**Which product should I use?**
Use Parse when you already have HTML. Use Retrieve when you need Optiview to fetch one eligible public page first. Use Publish when your business wants to prepare its verified website and publish approved context.

**Do Parse and Retrieve require website ownership or DNS changes?**
No website connection is needed for these developer products. You remain responsible for source rights and permitted downstream use. Public availability does not grant a reuse license.

**How do developer accounts and keys work?**
Create a developer workspace and save the personal sign-in key and offline recovery code. Create scoped service keys for server-side applications. Email is an unverified contact identifier, not account-ownership proof or an email-only recovery method. Keep all credentials private.

**Can my agent use Optiview?**
The authenticated developer API returns prepared content for your application or model. A downloadable JavaScript client and local MCP adapter are available. Your host must authorize sources and any credit expenditure. Compatibility does not establish adoption or a partnership with an AI provider.

**Does the API include my private Narrative Graph?**
Parse and Retrieve are source-only. Verified website publishing and approved publisher context belong to the separate Publish workflow.

**Does Publish replace our website or CMS?**
No. Your website stays in its existing system. Your web team establishes and tests a supported connection. Your team reviews and explicitly publishes any Narrative Graph additions. Ordinary visitors retain the normal website experience.

**Does every AI tool get the prepared version?**
No. Delivery depends on the website connection, source eligibility and the request. Some tools explicitly request Markdown; supported AI requests may also receive prepared Markdown or HTML through eligible delivery paths. Traditional search crawlers retain the original website response. A claimed tool name does not prove the requester’s identity.

**Does the demo publish or save to our workspace?**
No. The public demo is a separate preview. Its AI-generated examples require review and do not transfer automatically into an approved publication.

**Will Optiview guarantee citations or recommendations?**
No. Optiview prepares and publishes sources. Outside AI services choose what to retrieve, use and cite.

## What to do next

### Choose your starting point

- [Compare Parse, Retrieve and Publish](https://optiview.ai/products/) to choose the right workflow.
- [Create a developer workspace](https://app.optiview.ai/developers) for self-service Parse and Retrieve, then add credits and create an application key.
- [Read the API quickstart and agent-tool setup](https://optiview.ai/developers/) for request examples, supported sources, errors, quotas and downloads.
- [Review pricing and terms](https://optiview.ai/pricing/) for prepaid credits and the separate Publish plan.
- [Preview your website](https://optiview.ai/demo/) to inspect prepared content and explore unapproved narrative examples without connecting or publishing.
- [Plan Publish setup](https://optiview.ai/onboarding/) with your web team. Publishing requires ownership checks, review and a supported connection; contact [hello@optiview.ai](mailto:hello@optiview.ai) for assisted setup.

Already using Publish? Review your Narrative Graph, publish approved changes explicitly, inspect the combined source in Markdown and check recorded delivery in Activity. Keep your existing visibility tools to study downstream AI answers.