Agent readiness: Link headers and content signals#173
Open
Conversation
- Add request middleware that attaches RFC 8288 Link headers to HTML responses (sitemap, llms.txt, service-doc, canonical homepage) so agents can discover related resources. - Declare AI content usage preferences with Content-Signal in robots.txt. Markdown content negotiation (Accept: text/markdown) was already handled by the existing llmMiddleware + fumadocs isMarkdownPreferred pipeline. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
superwall-docs-staging | 1344440 | Commit Preview URL Branch Preview URL |
Apr 20 2026, 08:01 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Linkresponse headers to HTML responses, pointing agents at/docs/sitemap.xml,/docs/llms.txt,/docs/llms-full.txt, the/docsservice-doc, and the canonicalsuperwall.comhomepage.robots.txtwithContent-Signal: search=yes, ai-input=yes, ai-train=no.Markdown content negotiation (
Accept: text/markdown) is already handled by the existingllmMiddleware+ fumadocsisMarkdownPreferredpipeline, so no change there.Test plan
curl -sI https://superwall.com/docsreturns aLink:header containingrel="sitemap",rel="service-doc",rel="describedby", andrel="canonical".curl -s https://superwall.com/docs/robots.txt(or the docs host's/robots.txt) contains theContent-Signaldirective.curl -s -H 'Accept: text/markdown' https://superwall.com/docs/iosreturns markdown.🤖 Generated with Claude Code