Start
Run the whole flow in six steps
Create a site → verify ownership → run audits → read the impact. Every step is copy-paste runnable; set two variables once and go.
Updated 2026-11-08
On this page
What each step does
Set two variables
Use an admin-issued key or create one in Console → Access (presets or individual scopes; all sites or a selected list). The same key drives REST, A2A, and MCP — each agent tool takes its own scope (audit:read, or radar:read for radar reads).
ShellCreate a site under your key
verificationMethod is dns, file, or meta. Returns 201 with verification material.
ShellPlace the proof, then ask for a check
For file verification, serve the returned token at /.well-known/seo-watch.txt first.
ShellTrigger your own audit
Verified sites only — unverified sites get SITE_NOT_VERIFIED and no job is created.
ShellRead findings and your quota
ShellCall A2A / MCP with the same key
message/send and site/finding tools need audit:read, the radar tool needs radar:read; without a key both answer 401 (JSON-RPC code -32002). Handshake methods need no key.
Shell