Improve documentation SEO and agent retrieval - #573
Open
ayushflow wants to merge 14 commits into
Open
Conversation
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.
Description
Improves site-wide SEO, accessibility, freshness governance, and AI-agent consumption for the FlutterFlow documentation.
llms.txt,llms-full.txt, bounded topic packs, page-level Markdown, an agent manifest, clean sitemap metadata, andTechArticlestructured data.Type of change
Validation
npm run typechecknpm run buildnpm run audit:seo-agent:builtnpm run eval:agent-retrievalgit diff --check origin/main...HEADBuild output covers 379 canonical pages and 12 bounded topic packs. All eight static audit categories score A+ at 100%. The fixed retrieval evaluation covers 50 intents and 300 query variants with 100% top-1 accuracy, recall@5, and evidence support.
Public repository safety
The complete branch delta, final tree, and branch history were scanned before publication. No private implementation paths, private code excerpts, credentials, new secret material, symlinks, submodules, hidden payloads, or local audit reports are included.