No Link response headers for agent discovery
Link headers are a standard defined by RFC 8288 that let a web server point AI agents toward useful related resources, like an API catalog or documentation, directly in the HTTP response, without the agent needing to guess or parse the page's HTML. This check found your site sends none of these headers. Most sites omit Link headers entirely, so this is a low-cost way to stand out to AI agents specifically, rather than a widely-expected baseline you're currently failing. There's no real downside case here: it's a small, cheap addition with a genuine, if modest, upside for agent-based discovery of your site's resources. Your developer needs about 30 minutes. Add Link response headers pointing to useful resources, for example: Link: </.well-known/api-catalog>; rel=api-catalog, configured at the web server or CDN level so they apply site-wide. Start with just one or two links to your most useful resources rather than trying to cover everything at once.
Why this matters
Most sites omit Link headers entirely, so this is a low-cost way to stand out to AI agents specifically, rather than a widely-expected baseline you're currently failing. There's no real downside case here: it's a small, cheap addition with a genuine, if modest, upside for agent-based discovery of your site's resources.
How to fix it
Your developer needs about 30 minutes. Add Link response headers pointing to useful resources, for example: Link: </.well-known/api-catalog>; rel=api-catalog, configured at the web server or CDN level so they apply site-wide. Start with just one or two links to your most useful resources rather than trying to cover everything at once.