fix(seo): exclude robots.txt and sitemap.xml from auth middleware#83
Merged
Conversation
Lighthouse reports robots.txt as requiring authentication. The cause: the auth middleware's matcher does not exclude robots.txt or sitemap.xml, and PUBLIC_ROUTES does not list them either. Unauthenticated requests (every crawler, every Lighthouse run) hit the middleware, fail the isPublicRoute check, and get redirected to /auth/login — so bots see a login redirect instead of the robots policy. Add robots.txt and sitemap.xml to the matcher's negative-lookahead exclusion, alongside favicon.ico. These are crawler metadata files; they must never go through Supabase auth, and the middleware has no reason to run for them at all. Same approach as the existing image/video exclusions. Co-authored-by: Cursor <cursoragent@cursor.com>
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
2 participants
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.
Lighthouse reports robots.txt as requiring authentication. The cause: the auth middleware's matcher does not exclude robots.txt or sitemap.xml, and PUBLIC_ROUTES does not list them either. Unauthenticated requests (every crawler, every Lighthouse run) hit the middleware, fail the isPublicRoute check, and get redirected to /auth/login — so bots see a login redirect instead of the robots policy.
Add robots.txt and sitemap.xml to the matcher's negative-lookahead exclusion, alongside favicon.ico. These are crawler metadata files; they must never go through Supabase auth, and the middleware has no reason to run for them at all. Same approach as the existing image/video exclusions.
Summary
Brief description of changes.
Changes
Claudebin Session
🔗 Session Link
Testing
How did you test this?
Checklist
bun checkpassesbun type-checkpasses