Get authorization
Only act for a client when you are authorized to submit, configure or verify the domain on the client's behalf.
Submit a client website without overstating what the result means
This page is for agencies acting with client authorization. The goal is straightforward: submit accurate information, inspect the resulting GoGuides evidence, complete verification where appropriate, and report only what the records actually support.
Before submitting
Use accurate information
Do not create a stronger identity, ownership or verification story than the public site and client authorization support.
Review the site first
Check crawl access, redirects, canonical behavior, identity, public contact information and major source-quality problems before submission.
Set expectations
Explain that GoGuides is an independent evidence and evaluation source, not a guaranteed route to third-party citation or ranking.
Submission workflow
| 1. Enter the client URL/domain | Start at the public GoGuides submission flow. |
| 2. Review the GoGuides evaluation | Inspect AI Rank, grade, trust state, policy/eligibility context and the evidence available for the represented scope. |
| 3. Continue only under the current public terms | Use the live submission flow for whatever activation or payment terms are currently offered rather than copying old pricing into an agency proposal. |
| 4. Verify control where appropriate | Use accepted owner/authorized-agent verification methods when verification is part of the client engagement. |
| 5. Inspect public records | Review the Trust Profile, Evaluate output, history, Web State, Change Intelligence and machine-readable surfaces that actually exist. |
| 6. Add the evidence to reporting | Link to the records and explain their limits instead of converting them into unsupported promises. |
After submission: use the right evidence for the right question
Current evaluation
Evaluate for the authoritative GoGuides root/domain or exact-URL assessment.
Stored objective state
Web State V3 for supported latest stored evidence.
Historical differences
Change Intelligence for deterministic observation-pair comparison.
Crawler requests
Bot Radar for qualifying observed request evidence without implying downstream use.
Machine integration
Developer Hub for the current public API and capability map.
Longitudinal context
Use profile and history surfaces to distinguish current state from evidence accumulated over time.
What the agency should never sell as guaranteed
Submission, activation, verification, AI Rank, Bot Radar activity or machine-readable records
do not guarantee that an outside AI/search system will crawl the client's own site, index it,
train on it, cite it, rank it, recommend it, or include it in an answer.