Skip to content

fix(seo): serve /llms-full.txt as direct 200, not 307 redirect - #602

Merged
Flotapponnier merged 1 commit into
devfrom
fix/llms-full-txt-direct-200
Jun 21, 2026
Merged

fix(seo): serve /llms-full.txt as direct 200, not 307 redirect#602
Flotapponnier merged 1 commit into
devfrom
fix/llms-full-txt-direct-200

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Re-exports the /api/llm-context GET handler from /llms-full.txt so the public URL returns 200 with text/markdown directly. Removes the 307 redirect that was confusing llms.txt validators and stricter AI crawlers (Perplexity / certain Bing AI variants). No body change.

The route was redirecting to /api/llm-context, which is fine for
permissive clients but breaks:
- llms.txt validators (llmstxt-checker fails on non-200)
- stricter AI crawlers (Perplexity, some Bing AI variants) that mark
non-standard paths returning a redirect as no-content and skip
- canonical attribution (AI engines citing the body now point at the
internal /api/llm-context path instead of the public /llms-full.txt)
Re-exports the GET handler from /api/llm-context so there is a single
source of truth for the markdown body. No content change.
@Flotapponnier
Flotapponnier merged commit 22d1ca7 into devJun 21, 2026
@Flotapponnier
Flotapponnier deleted the fix/llms-full-txt-direct-200 branch June 21, 2026 09:53
Flotapponnier added a commit that referenced this pull request Jun 21, 2026
…#603)
The route was redirecting to /api/llm-context, which is fine for
permissive clients but breaks:
- llms.txt validators (llmstxt-checker fails on non-200)
- stricter AI crawlers (Perplexity, some Bing AI variants) that mark
non-standard paths returning a redirect as no-content and skip
- canonical attribution (AI engines citing the body now point at the
internal /api/llm-context path instead of the public /llms-full.txt)
Re-exports the GET handler from /api/llm-context so there is a single
source of truth for the markdown body. No content change.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@Flotapponnier