feat(seo): improve AI-readiness#4192
Draft
navillanueva wants to merge 11 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
feat(seo): add llms.txt directive to markdown + CI guardrails
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
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.
Makes build.avax.network easier for AI agents to read, and adds a CI guardrail so it can't quietly regress.
What changed
/llms.txtindex — a hand-picked map of the content we want agents to find: all docs + blog, the Avalanche L1 and Entrepreneur academies, and the x402 course. It deliberately leaves out integrations and the rest of the Blockchain academy..md), and fix a bug where index pages didn't serve their.mdversion.A caveat on the score
We can't realistically hit a literal 100% — our docs are too big for the checker's size limit. It's a trade-off: index everything and the file gets large enough that some AI tools cut it off mid-read, or curate the important pages (what we did) and the checker flags "incomplete coverage" because it expects the index to list every single page. We went with the curated index.
Known follow-up
A few pages where the markdown doesn't fully match the rendered page (interactive components) — content-side, separate effort.