Demonstration guide
Questions about the delivery experiment.
The answers below describe the scope of this public prototype and its safety boundaries.
Does this demo alter visible website content?
No. The scope is metadata delivery only. The origin pages provide the visible evidence, while a later phase will append an approved machine-readable annotation to the HTML response without changing the page’s design or copy.
Does JSON-LD guarantee an AI citation, search ranking, or rich result?
No. It can make supported information easier to interpret, but platforms decide independently what to crawl, understand, rank, cite, or present. The prototype measures technical delivery and verification, not those downstream outcomes.
Can an annotation describe information that is not on the page?
Not for this workflow. Each delivered property must be backed by text that a visitor can see on the page or by an approved organization identity fact. Claims that are uncertain, stale, or unauthorized are excluded.
Why not generate the annotation during every request?
Live generation adds latency, nondeterminism, cost, and a greater chance of accidental unsupported claims. This design generates and approves content offline, then serves a stable version at the edge.
How can a change be removed?
The delivery policy has an explicit disablement path. When no active annotation is selected for a URL, the response passes through unchanged. A subsequent public crawl can confirm the rollback.