Advanced Source Diagnostics
Optional tools for inspecting what Optiview found in the source. You do not need these features for normal publishing. Observations are not verified business facts or publication approval.
Product and offer data
Inspect supported product names, SKUs, prices and offers. When values disagree, Optiview keeps the disagreement visible instead of silently choosing one.
Optional discovery for supplied HTML
Add include_discovery: true to receive a separate discovery object.
It preserves up to 200 observed destinations from navigation, footers and page content, with labels, source selectors and link context.
Variant query parameters remain distinct.
Its commerce section records supported source-declared JSON-LD and microdata entities and explicit relationships, including products, offers and variants, with field-level evidence.
Conflicts and visible evidence
The profile reports conservative page-type signals without changing pruning. reconciliation preserves conflicting or missing SKU, price, currency and availability declarations. visible_evidence separately checks explicitly labeled SKU and price text in an identifiable product region; agreement is not independent verification or freshness.
Its role_observations keep supported source labels distinct, such as product code versus SKU and starting price versus current bid or shipping price.
Generic price/code labels remain unknown roles.
A source label is not proof of product attribution; unresolved observations carry no product references.
The relationships section preserves supported quantity/unit-price table rows and explicit plan-card rate, allowance, overage and billing-qualification statements.
Each has source selectors.
Product attribution is withheld without a matching item boundary.
A dollar symbol alone does not identify an ISO currency, monthly rate cadence does not establish contract length, and CSS-conditional statements do not establish the active browser selection.
Unsupported layouts remain unparsed; these are bounded source relationships, not a comprehensive pricing model.
Variants
The variants view keeps explicit ProductGroup membership and direct variant offers separate.
It can also retain numeric variant parameters from same-product Offer URLs with offer-local identifiers; a unique matching DOM radio marker may supply a source option label.
Parent SKUs, family prices and aggregate ranges are never inherited.
Duplicate IDs and unresolved references stay unresolved; no active selection or inventory is established.
These are unverified source assertions: they may be stale, incomplete or contradictory.
They are not appended to your published Markdown or treated as approved policy.
No linked pages are fetched.
Truncation and unresolved relationships are reported.
This option currently requires supplied HTML; the existing tokens count describes the Markdown payload, not this additional diagnostic object.
Pricing and plans
Optiview recognizes some plan cards, quantity-price tables, add-ons, usage limits and pricing qualifications. These are source observations, not verified checkout prices.
Pricing source evidence: relationships.plans.groups preserves supported explicit or repeated rate-and-signup plan containers.
Streamed plan records identify their source boundary/segment and label reconstructed-DOM selectors; JavaScript is not executed.
Recovery supports bounded standalone completion calls and an exact fingerprint of a reviewed runtime; unknown variants remain unsupported.
Pricing-feature icons with explicit text labels retain those labels.
Unlabeled or conflicting icons are marked unresolved, not assumed to mean included.
Structured plan feature_states carry the same distinction.
Storage allowances and explicit overage thresholds remain source observations.
Minimum usage commitments and included usage credits are separate records; a credit period does not establish the commitment billing period.
Supported inline or immediately preceding From/Starting at labels are retained as lower-bound rate evidence.
Other qualifiers may remain only in the local source text; do not treat a recognized rate as a complete invoice.
Page currency statements are separate notes, not inferred currency assignments. relationships.addons keeps explicitly labeled add-ons separate from base plans.
Supported pricing records distinguish per-seat or per-developer rates, hourly rates, monthly caps, starting prices and minimum commitments.
Paragraph-named repeated offer lists carry explicit name provenance.
Add-on rates can retain per-dataset units and their source eligibility section. relationships.summaries contains corroborated priced entity summaries, such as deployment options, without classifying them as subscriptions.
Source context and the dashboard preserve their full descriptions.
Named plan components retain their own rates and source units in components.groups; multiple source prices remain source_alternatives_unresolved rather than selecting a billing state or summing an invoice.
An explicit + usage suffix remains a usage_qualifier, not a computed charge.
Explicit Support sections may yield priced_service_tier summaries with the support tier, rate and full local description; these are not base subscription or compute rates.
Repeated offer containers and heading groups are supported only when local name, rate and action evidence meet the bounded rules.
A price heading can be paired with its immediately adjacent unit region when the bounded structure is unambiguous; amount_evidence and unit_evidence retain separate source references.
Billing, savings and trial labels remain source conditions.
Repeated plan names and CSS-hidden or invisible states do not establish distinct products or an active billing choice.
Subordinate feature headings are accepted only with local list/table structure and without a separate commercial offer.
These are bounded source observations; responsive billing choices, inferred invoices and eligibility decisions are not resolved. relationships.plans.free_tiers retains local Free-label, usage-limit and signup context; conditions elsewhere may be missing. comparison_columns preserves supported named rate-bearing table headers and unmerged same-table rows.
Separate tables are not joined by visual order, icon-only cells are not interpreted, and dynamic expressions remain unevaluated.
These beta views are bounded and incomplete; review qualifiers, truncation and source references before use.
Content Preview displays the additional evidence without approving or publishing it.
Continue a discovery link map
For supplied HTML with include_discovery: true, discovery.next_cursor is either a continuation string or null when that source is exhausted. Send the same URL and byte-identical HTML with discovery_cursor to retrieve the next page. Each response remains limited to 200 destinations and 2,000 processed anchors; existing authorization, billing and request budgets still apply. A changed source or URL rejects the cursor. Cursors are continuation hints, not authorization credentials.
Continuation discovery objects use kind: link_continuation and contain link/page metadata rather than repeated commerce analysis. Published Markdown and its publication version follow the normal render flow; publication may change between requests. Links can repeat across pages, and occurrence counts cover the current anchor window only. Deduplicate by URL; do not sum occurrences as sitewide counts. Stop at a null cursor. Returned destinations are not fetched. Do not combine a cursor with source_query; query selection currently examines the initial discovery page only.
Optional query-specific source selection (beta)
Optional source selection (beta): add source_query, a non-empty string of at most 500 characters, to a supplied-HTML request.
The separate source_context object selects bounded, complete supported variant, quantity-price and plan records, or unfetched discovery links.
It includes the source SHA-256, selectors, qualifiers, omitted-match counts and unresolved identifier hints.
Selection is lexical source evidence, not a generated answer, exhaustive retrieval, verified policy or publication approval.
Unknown or ambiguous queries may return no match.
Link-only selections use discovery_links_only and source_record_matches: 0; they do not establish facts about the destination.
This option does not change the published Markdown, make external fetches or call an AI model.
Existing domain-key authorization, billing and request limits apply.
URL-fetch mode does not support source_query.
Limits
Diagnostics are conservative. Unsupported layouts may not be recognized. Missing data does not mean the website does not contain it.