---
optiview_delivery: edge_optimized
content_type: semantic_markdown
source_url: https://optiview.ai/resources/site-wide-vs-page-specific-ai-context/
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/) [Brand context and governance](https://optiview.ai/resources/topics/brand-context/)

Narrative Graph guide — October 30, 2026

# Site-Wide vs Page-Specific Context: What Should AI Receive?

A fact can be accurate and still appear in the wrong place. The question is whether it describes the entire business or only a particular page, product or audience.

By Optiview · Sources checked October 30, 2026

[Download this article (.md)](https://optiview.ai/resources/site-wide-vs-page-specific-ai-context.md)

A company's identity usually applies across its website. A product-specific compatibility restriction does not. Treating both as universal context risks adding irrelevant or misleading information to otherwise accurate pages.

Optiview's [How It Works](https://optiview.ai/how-it-works/) page documents two Narrative Graph content scopes: Entire website and one exact page. Site-wide additions can accompany pages across the site, while page-specific additions accompany their matching page.

The editorial decision about which scope to choose still belongs to the business. The matrix below is a proposed review method. It does not describe a rule-based inheritance engine, automated conflict resolution, conditional targeting or other features beyond the documented scope choices.

## 1\. Start with a scope decision matrix

| Information | Likely scope | Reason |
| --- | --- | --- |
| Official company identity | Site-wide | Generally applies to the whole business |
| Broad company purpose | Site-wide | Relevant to the organization overall |
| Product compatibility | Exact page | Depends on a particular offering |
| Regional service restriction | Exact page | Applies to a defined service or location |
| Product-specific evidence | Exact page | Supports a particular claim |
| General contact destination | Site-wide when applicable | May serve multiple audiences |
| Specialized next action | Exact page | Depends on the current offering |

These are starting recommendations, not automatic rules. A company with multiple brands or regions may need narrower scope even for information that initially appears universal.

## 2\. Ask four questions before assigning scope

1.  Would this statement remain accurate on every relevant page of the website?
2.  Does its meaning depend on a particular product, location, version or audience?
3.  Could applying it broadly create a misleading impression or conflict?
4.  Who is responsible for approving the wording and its intended scope?

If a statement requires a qualification such as 'only for Enterprise accounts,' do not remove that limitation to make it fit site-wide. Narrow the scope or reconsider the wording.

## 3\. Test the decision with a hypothetical company

Consider fictional company Harbor Analytics, which sells separate reporting products for retailers and manufacturers. Its organization-wide identity may truthfully describe its analytics business. A statement that the retail product supports particular inventory systems should not automatically accompany its manufacturing offering.

The reviewer might approve the company identity for site-wide use and assign the integration statement to the exact retail product page. If the integration applies only to a specific subscription, that qualification belongs in the page-specific content.

This is an illustrative editorial decision, not a tested deployment, real customer or claim about downstream AI behavior.

## 4\. Apply the decision to documented publication controls

Optiview's [technical setup guide](https://optiview.ai/docs/setup/) describes creating Narrative Graph content, choosing site-wide or exact-page scope, saving drafts and explicitly publishing reviewed changes. A saved draft is not automatically made live.

*   Record the approved statement and its source.
*   Select Entire website or the intended exact page.
*   Review the statement in the context where it will appear.
*   Check its qualifications and supporting links.
*   Publish through the documented workflow after authorization.
*   Inspect the resulting source and retain the scope decision.

Do not assume that overlapping entries are automatically reconciled or that one scope takes precedence under an undocumented inheritance rule. Inspect the actual published result.

## 5\. Revisit scope when the business changes

A statement that once applied across the business may become product-specific after a new offering launches. Similarly, a qualification may change when service coverage expands.

The finished work product is a scope matrix containing the statement, intended pages, supporting evidence, owner, decision and review trigger. Use the [claim provenance ledger](https://optiview.ai/resources/brand-claims-provenance-ledger/) to maintain supporting evidence separately.

## Additional source context

Use site-wide scope for information genuinely true across the business. Use exact-page scope for facts whose validity depends on a specific offering, location, audience or context.

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

- [Why Markdown Conversion Is Different From Publishing Approved Brand Context](https://optiview.ai/resources/markdown-conversion-vs-approved-brand-content/) — Continue reading
- [Designing a Narrative Graph: A Practical Relationship Worksheet](https://optiview.ai/resources/narrative-graph-content-model/) — Continue reading
- [Building a Provenance Ledger for Brand Claims Published to AI](https://optiview.ai/resources/brand-claims-provenance-ledger/) — 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.