No agent.json observed at the sampled discovery path
If this finding appears in a report, the sampled /.well-known/agent.json location did not provide a recognised manifest. agent.json is a convention for clients that explicitly support the Agent Web Protocol; it is not robots.txt or a universal permission file. The proposal's current quick start documents /agent.json at the domain root, so absence at the sampled path does not establish absence at every supported location. This reference page does not test your integration.
Why this matters
A discovery manifest matters only to a client and workflow that use it. Its absence does not prove that Claude, a computer-use agent or a search system cannot read the public site or recommend the business. Google documents no additional machine-readable file requirement for its AI search features. A manifest also does not grant authorisation to perform private actions.
How to fix it
Identify a real client and supported protocol before adding a file. Check that client's current discovery path and schema rather than copying a path from this finding. If it actually supports the Agent Web Protocol, publish accurate capabilities at the documented location and test the intended integration end to end. Keep authentication, permissions, confirmation and rate limits in the service itself; do not publish private endpoints or invent supported actions merely to satisfy a scan. If no supported integration needs the manifest, retain the existing public site and record this item as inapplicable instead of treating it as a search blocker.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit