The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Your website might be invisible to ChatGPT. Your browser will never tell you.
You open your site. It loads. It looks fine.
But GPTBot, ClaudeBot and PerplexityBot do not visit the way you do. One robots.txt line, one CDN toggle or one bot challenge page, and they get a block while you get a homepage.
Usually nobody on the team chose that. It just shipped that way.
I wanted a straight answer to one question: who can actually read my site? So we built it at Codevibe.
One command:
npx ai-bot-access (your site URL)
It visits your site as 24 different bots:
• 15 AI crawlers and assistants (GPTBot, ClaudeBot, PerplexityBot and more)
• 4 search engines (Googlebot, bingbot and more)
• 5 link preview bots (LinkedIn, WhatsApp, Slack and more)
For each one you see allowed or blocked, plus a fix list for your host or CDN.
Free. Open source. No signup. Nothing is sent to us.
Run it on your site and reply with what it found. I will help you read the report.
codevibe.in
AI Crawler Checker: Can ChatGPT Read Your Site? | Codevibe
Free open-source tool: check whether GPTBot, ClaudeBot, PerplexityBot, Googlebot and 20 more bots can read your site, verify bot IPs and read your access logs.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Noise Reveal, a premium reveal component for Framer
I built a component that gives Framer sites cinematic reveals for images, video and live layouts. It has a soft, film-like edge with glow and grain, and can play on load, on view, from a variant or scrubbed by scroll.
It’s built for production: the reveal is prepared before it scrolls in, it’s accessible with reduced-motion support, it falls back when WebGL isn’t available, and pages stay plain HTML when nothing is moving.
Launched on the Framer Marketplace. Open to custom Framer and interaction work.
The WebGL fallback and reduced-motion support are the parts most reveal effects skip, so it's great to see them called out. Does the fallback keep some of the grain edge with CSS, or does it drop to a simple fade?
Zencastr came to us with a complex mix: they hosted their homepage on a custom server, blog on a separate platform and the rest of the pages on Webflow.
They had 3 days before the launch to tie it all together. This is their review:
Three platforms behind one domain in three days is a real test. I'd guess the reverse proxy and keeping the nav and footer identical across all three took more care than any of the page building. Did you match the shared header in Webflow or pull it from one source?