Discovery via Link response headers

What is measured

The scanner reads the Link response headers on https://<domain>/ ($home in the probe map) and parses them per RFC 8288: an angle-bracketed URI-reference followed by semicolon-separated parameters. Pass = at least one Link header that advertises a discovery resource with a registered relation, such as rel=describedby pointing at /llms.txt or rel=alternate with type=text/markdown. Partial = a Link header is present but carries no discovery relation (only preload or preconnect, for example). Fail = the homepage response carries no Link header at all.

Reproduce it yourself

You do not have to take our word for any of this. Run the same measurement against your own domain:

              DOMAIN=example.com
curl -sS -D - -o /dev/null "https://$DOMAIN/" | grep -i '^link:'
            

The fix

This is the artifact to ship. It is the complete change, not a description of one.

              Link: </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml", </docs/quickstart.md>; rel="alternate"; type="text/markdown"

# nginx equivalent
add_header Link '</llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml"' always;
            

Standards referenced

• RFC 8288

Related checks