Public Trust Profile
An independent public record where the client and outside consumers can inspect identity, current GoGuides context, verification and related evidence.
Give clients an evidence package they can actually inspect
Much of good technical work happens behind the scenes. GoGuides can add a client-facing layer: independently observed public records, verification context, longitudinal state, machine-readable interfaces, crawler evidence, and documented GoGuides assessments that can be revisited over time.
What the client-facing deliverable can include
GoGuides evaluation
AI Rank, grade, trust state and related fields are GoGuides-derived assessments. They are not purchased and are not universal third-party scores.
Verification state
Verification can distinguish passive observation from demonstrated control or authorization under an accepted GoGuides method.
Observation history
A timeline can give the client something more durable than a one-time screenshot of current state.
Web State & Change Intelligence
Technical teams can inspect objective stored state and deterministic changes rather than relying only on a visual report.
Machine-readable capability map
GoGuides publishes machine-use discovery, OpenAPI, focused endpoint documentation, Evaluate, Batch Evaluate, URL Request and other public interfaces.
AI Bot Radar
Observed requests can support reporting about crawler activity while keeping the boundary clear: a request is not proof of indexing, citation, training, ranking or recommendation.
Provenance and source evidence
Verified Text, history, Web State, hashes and related public records give agencies concrete evidence surfaces to explain instead of vague “AI visibility” claims.
A simple agency workflow
| 1. Review the client site | Confirm crawl access, stable identity, source quality, technical consistency and authorization to act for the client. |
| 2. Submit or inspect the domain | Use the public GoGuides flow and inspect the resulting GoGuides records rather than promising an outcome before evidence exists. |
| 3. Complete verification where appropriate | Keep verification separate from ranking or truth claims: it demonstrates accepted control/authorization, not universal source quality. |
| 4. Add the evidence to reporting | Link the client to the profile, Evaluate output, history, Web State, Change Intelligence and Bot Radar evidence that is actually relevant. |
| 5. Revisit longitudinally | Track current state and changes over time instead of treating one successful crawl or one score as a permanent condition. |
How to talk about GoGuides with a client
Defensible
“We are giving your site an independent, machine-readable evidence presence that can be inspected and monitored over time.”
Too strong
“This guarantees ChatGPT, Claude, Google, Perplexity or another independent platform will cite or recommend your site.”
Defensible
“GoGuides observed this request/state/change under its published interfaces, and here is the evidence.”
Too strong
“A crawler request proves the client was indexed, trained on, trusted, ranked or selected for an answer.”
Use the right capability for the reporting question
| Client question | Where to look |
|---|---|
| What does GoGuides currently report about the domain or exact page? | Evaluate |
| What objective state did GoGuides store? | Web State V3 |
| What changed between observations? | Change Intelligence |
| Can we request intelligence for one public URL? | URL Request |
| What public machine capabilities exist? | Developer Hub and machine-use.json |
| Did GoGuides observe qualifying AI/search crawler requests? | AI Bot Radar |
Keep commercial service separate from evidence meaning
Payment or activation does not purchase a higher AI Rank, guarantee a citation, or make an
outside AI system adopt a GoGuides conclusion. Agencies can charge for their own setup,
verification, technical work, analysis, monitoring and reporting, while describing GoGuides
evidence according to what the records actually establish.
Why this can be useful in a retainer
The strongest value is not another decorative badge. It is a set of public, inspectable, machine-readable records an agency can connect to technical SEO, GEO, identity, provenance, verification and change-monitoring work. That gives the client something concrete to revisit while the agency continues improving the underlying site.