seo: spell out explicit Allow stanzas for AI / search bots in robots.txt#97
Merged
Conversation
The wildcard `User-agent: *` block already permits every named crawler, so this change is technically cosmetic. But the external SEO audit flagged the absence of explicit GPTBot / ClaudeBot / PerplexityBot stanzas as a reason their tooling couldn't confirm the site welcomes AI indexers — and several SEO-grading tools key off explicit per-bot rules rather than the wildcard. Add explicit Allow blocks for the major AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended) plus Googlebot and Bingbot. All preserve the same `Disallow: /api/` so the demo backend stays out of indexes. The block comment above explains the redundancy so future readers don't mistake it for a different access policy.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
The wildcard
User-agent: *block already permits every named crawler, so this change is technically cosmetic. But the external SEO audit flagged the absence of explicitGPTBot/ClaudeBot/PerplexityBotstanzas as a reason their tooling couldn't confirm the site welcomes AI indexers — and several SEO-grading tools key off explicit per-bot rules rather than the wildcard.Add explicit
Allowblocks for:GPTBot,OAI-SearchBot,ChatGPT-User,ClaudeBot,Claude-Web,PerplexityBot,Google-ExtendedGooglebot,BingbotAll preserve the same
Disallow: /api/so the demo backend stays out of indexes. The block comment explains the redundancy so future readers don't mistake it for a different access policy.Test plan
npx vitest run tests/seo-static.test.ts— 13/13 pass (the wildcard rule the existing test asserts on is preserved)curl https://www.statewave.ai/robots.txtshows the new per-bot stanzas