Current measurement contract
S6S records what configured API/search surfaces returned for a defined buyer question. It keeps the supporting response, citations, timestamp, and failure state attached to that observation.
What the public check does
A deterministic technical snapshot
The public check asks whether S6S can fetch the supplied page, inspects the initial HTML and detected structured data, and reads robots.txt policies for the funded retrieval crawlers. It does not query an AI provider, calculate an AI-visibility score, or prove that a brand will be mentioned.
How monitored observations are handled
- Every result belongs to a named provider surface, prompt, configuration, and time.
- Unavailable, failed, blocked, and never-run measurements remain distinct from a measured absence.
- API/search observations are not presented as observations of a provider's consumer application.
- Later observations can show a change; they do not prove that an intervention caused it.
Current boundaries
- Monitored reports are a supervised private-alpha capability, not a public self-service promise.
- A provider surface runs only when the required key, budget, and account right are confirmed.
- Gemini grounded measurement fails closed while the required commercial data rights remain unresolved.
- Recommendations and generated assets are reviewable hypotheses and drafts; S6S does not publish them automatically.
Why the documentation is deliberately narrow
Scoring, local-market behavior, report semantics, and intervention claims are being validated against funded runs and provider rights. Legacy explanatory pages are retired until those contracts are supported by production evidence.
Start with the bounded check
Inspect public-site access and markup without creating an account. Monitored access is discussed separately as a supervised private alpha.