Source evidence
FAQ answers and summaries retain the span of origin content used to support them.
Trust & Control
Know what was generated, why it can publish, and how to stop it
SigilEdge separates generation from publication with evidence, review gates, previews, exclusions, and rollback.
Publication gates
Only published review items are materialized into the edge cache used for crawler delivery.
Confidence thresholds
Teams can set separate automatic-approval thresholds for FAQ and summary content.
Entailment check
Summaries require an entailment verdict before they are eligible for automatic approval.
Claim-risk routing
Volatile statements about price, inventory, shipping, and policy do not automatically publish.
Day-two operations
Control after onboarding
AI-facing content changes as your origin changes. These controls make refreshes and exceptions part of the product instead of an emergency engineering task.
Preview
Inspect bot-facing output through signed previews before changing live behavior.
Review and edit
Approve, reject, or edit pending FAQ and summary items with their source context.
Exclude
Keep selected URLs out of enrichment when the content is unsuitable or sensitive.
Regenerate
Refresh one page or queue a domain-wide regeneration after source changes.
Rollback
Restore an earlier configuration if a rollout needs to be reversed.
Audit
Sample automatically approved items and preserve review history for operational follow-through.
Traffic and tenant boundaries
Domain ownership is verified during onboarding. Tenant configuration and content are scoped to that tenant, and platform hostnames are kept separate from customer-domain routing.
Honest limitations
This page makes no claim of a certification, formal compliance program, uptime commitment, complete crawler identity verification, or perfect generated-content accuracy.
Review the workflow on your own content
Apply for early access and evaluate the evidence and controls before rollout.
Start Early Access