Developer checks AI crawlers against their own site: all eight returned 200
10/03/2026 — 10/05, 03:19·1 sources·1 reports
Story overview
On 30 September 2026, a developer ran an AI crawler access check on his own site. The test works by requesting a page under each bot's name and reading the status code that comes back, which shows whether the crawlers behind ChatGPT, Claude, Perplexity and similar services can fetch the pages at all. Eight crawler names were tried, and all eight requests returned 200. Nothing was keeping the machines out.
The account was published on 3 October 2026 in the AI section of DEV Community; the author notes it first appeared on yappatyih.com. The write-up leads with the result: eight crawler names, eight answers of 200.
What the same audit did find sat elsewhere on the site. A single line in robots.txt — Disallow: /og/ — was blocking the preview image on every page. So the one problem the check surfaced was not about crawler access at all, but about robots.txt shielding the per-page preview images.
The piece is framed as a self-check developers can run on their own sites: probe the site with each bot's name, read the status codes, and see whether AI crawlers can reach the pages. The reported outcome of this particular pass is two-part: unrestricted access for all eight crawler names, and a robots.txt rule that hides the preview images.
AI-generated from 1 reports · updated 9 minutes ago
Latest turnA developer tested whether the bots behind ChatGPT, Claude, Perplexity and others could fetch pages on his site by requesting each with a bot name and reading the status code. All eight returned 200. The real problem surfaced elsewhere: a single Disallow: /og/ line in his robots.txt was blocking the preview image on every page.
- Heat index
- 31
- Sources
- 1
- Reports
- 1
- First seen
- 2 days ago
Reports on this story headlines open the original
A developer tested whether the bots behind ChatGPT, Claude, Perplexity and others could fetch pages on his site by requesting each with a bot name and reading the status code. All eight returned 200. The real problem surfaced elsewhere: a single Disallow: /og/ line in his robots.txt was blocking the preview image on every page.
DEV Community · AIAI score 58
Other stories people are talking about
- Heat index 41A GEO checklist for developers: getting cited by ChatGPT and others1 sources
- Heat index 84Diagnosing and fixing GPTBot blocks by Cloudflare WAF rules1 sources
- Heat index 68Manual 30-minute audit: is your brand recommended by ChatGPT?1 sources
- Heat index 43NetPulse: one command lets an AI agent health-check multiple VPS hosts1 sources
- Heat index 38Tour app Your Next Tours ships a remote MCP server for Claude and ChatGPT1 sources
- Heat index 37Claude API Returns 400 on Exhausted Balance, Breaking the Whole Pipeline1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion
