Crawler Tester for Next.js sites
Test whether GPTBot, PerplexityBot, ClaudeBot and Google-Extended can actually fetch your pages. Most blocked sites do not know they are blocked. SaaS products, marketing sites owned by engineering teams, and everything we build ourselves.
- Free
- 10 second test
- 6
- checks
- Live
- status
What Next.js sites usually get wrong
- The Metadata API covers titles and Open Graph but not JSON-LD; schema needs a script tag in the layout or page.
- Vercel's bot protection is off by default; if Attack Challenge Mode is on, AI crawlers get a challenge page.
- generateStaticParams makes programmatic pages cheap, which is why thin templated pages are the common failure.
Applying the result on Next.js
- How to change crawler rules on Next.js. Export a robots() function from app/robots.ts with explicit allow rules per AI user agent.
What Crawler Tester checks
- GPTBotOpenAI crawler access.
- PerplexityBotPerplexity crawler access.
- ClaudeBotAnthropic crawler access.
- Google-ExtendedGemini grounding access.
- robots.txtDirectives that apply to each agent.
- Edge rules403 and 429 responses that robots.txt does not explain.
100
Lighthouse performance on this site. Same for SEO, accessibility and best practices
5
products of our own in production
3
practices, each with a named lead
1 day
reply time on every enquiry
4.9
from 9 reviews
Questions people ask
- Does Crawler Tester work with Next.js?
- Yes. It reads the public site, so the platform does not matter. The notes above cover where to apply the result on Next.js.
- Should I allow every crawler?
- Not necessarily. This tells you what is happening so the choice is deliberate.
- Does it slow my site?
- No. It is a handful of requests.
- Can I test staging?
- Only if it is publicly reachable.