Fix: Homepage sends RFC 8288 Link headers pointing at agent resources

Web-audit fix skill for the link-headers check (Discoverability, SHOULD).

Goal

Advertise machine surfaces in a Link response header on / for header-only discovery.

Fix

Send a Link response header on / (RFC 8288) whose rel points at your machine surfaces, so an agent reading only response headers finds them without parsing HTML or probing /.well-known. Use the RFC 8631 service trio and the RFC 9727 catalog: rel="service-desc" at a machine-readable description (OpenAPI, or an MCP server card), rel="service-doc" at the human-readable doc, rel="service-meta" at the service-context declaration, and rel="api-catalog" at your /.well-known/api-catalog index. Example: Link: </.well-known/api-catalog>; rel="api-catalog", </.well-known/mcp/server-card.json>; rel="service-desc".

Resources

Copy-paste prompt

Paste this into your coding agent, replacing the Issue line with the Result line from your audit:

Verify

Re-run the audit at https://anc.dev/web-audit or call the audit_website MCP tool; the link-headers check should report pass.