Which sites block Claude-User?

Anthropic · declared purpose: on-demand fetch for a user's prompt · latest sealed date 2026-08-07.

On 2026-08-07, 1,477 of the 61,552 panel domains that served a parseable robots.txt name claude-user explicitly. 739 of them (1.2% of parsed) disallow it from the entire site, 344 restrict it to part of the site, and 394 name it and allow it. The remaining 60,075 parsed domains do not mention it at all — their wildcard group governs it.

What the denominator is. On 2026-08-07 we attempted /robots.txt on 100,000 panel domains. 24,130 could not be reached at all (DNS failure, TLS failure, timeout, refused connection) and 14,318 answered with something other than a 200. Both of those groups have no observed AI-crawler policy, and neither is counted as allowing anything — an unreachable site is UNKNOWN, not permissive. Every crawler figure below is out of the 61,552 domains that returned a robots.txt we could parse on that date.

Blocks outright — the file has a group for that exact product token containing Disallow: / with no overriding allow. Partly restricts — a group exists with at least one non-empty Disallow, but not the whole site. Names & allows — a group exists with no effective Disallow. Everything else is not mentioned: the wildcard * group governs it, and wildcard effects are counted separately rather than folded in, because a site that blocks everything has not made a decision about any AI crawler in particular. Matching is exact and case-insensitive per RFC 9309 — never substring.

Get told when Claude-User change their AI crawler rules

Sites publish today's robots.txt and overwrite it — no archive, no history, no notification. We keep a dated daily copy. Leave your email and we'll send you what moved for Claude-User: who started blocking, who stopped, and on which day.

Email me changes for Claude-User →

Work email only. No newsletter, no obligation.

Prefer to just buy it? See the sealed-archive monitoring offers, priced, with a dated sample.

What moved: Claude-User verdict changes

Counted domains whose robots.txt changed what Claude-User may do, between one sealed date and the previous one. Aggregate only — we do not publish which site.

Across the whole archive: 691 Claude-User verdict transitions, of which 149 moved TO a full block and 90 moved AWAY from one.

Sealed date	Verdict moved	Domains
2026-08-07	not mentioned → partly restricted	4
2026-08-07	not mentioned → named and allowed	3
2026-08-07	blocked outright → named and allowed	2
2026-08-07	not mentioned → blocked outright	1
2026-08-07	named and allowed → not mentioned	1
2026-08-07	named and allowed → partly restricted	1
2026-08-06	not mentioned → named and allowed	5
2026-08-06	not mentioned → partly restricted	2
2026-08-06	named and allowed → not mentioned	2
2026-08-06	blocked outright → not mentioned	1
2026-08-05	not mentioned → partly restricted	3
2026-08-05	not mentioned → named and allowed	3
2026-08-05	not mentioned → blocked outright	1
2026-08-05	blocked outright → not mentioned	1
2026-08-05	named and allowed → not mentioned	1
2026-08-05	named and allowed → partly restricted	1
2026-08-04	not mentioned → partly restricted	11
2026-08-04	not mentioned → named and allowed	5
2026-08-04	named and allowed → partly restricted	2
2026-08-04	partly restricted → not mentioned	1
2026-08-04	partly restricted → named and allowed	1
2026-08-04	named and allowed → not mentioned	1
2026-08-03	not mentioned → partly restricted	2
2026-08-03	not mentioned → named and allowed	2
2026-08-03	partly restricted → not mentioned	1
2026-08-03	named and allowed → not mentioned	1
2026-08-03	named and allowed → blocked outright	1
2026-08-02	not mentioned → partly restricted	2
2026-08-02	not mentioned → named and allowed	2
2026-08-02	named and allowed → not mentioned	2
2026-08-02	blocked outright → not mentioned	1
2026-08-01	not mentioned → partly restricted	1
2026-08-01	blocked outright → not mentioned	1
2026-07-31	not mentioned → partly restricted	24
2026-07-31	not mentioned → blocked outright	4
2026-07-31	not mentioned → named and allowed	3
2026-07-31	blocked outright → not mentioned	1
2026-07-31	named and allowed → not mentioned	1
2026-07-30	not mentioned → blocked outright	5
2026-07-30	not mentioned → partly restricted	4

Read this before quoting a trend. We hold 55 sealed daily snapshots between 2026-06-09 and 2026-08-07, out of 60 calendar days. 5 calendar day(s) inside that span have no collection run at all: 2026-06-11, 2026-06-12, 2026-06-19, 2026-07-04, 2026-07-15. Consecutive rows in every table below are consecutive SEALED dates, not consecutive days — where a gap falls, that row's diff covers more than 24 hours, and the span is printed with it. We do not interpolate across a day we did not collect.

Every sealed date

The denominator column is the number of panel domains that served a parseable robots.txt that day. It moves, so a raw count moves with it — compare the ratio, not the count.

Sealed date	Names it	Blocks outright	Partly restricts	Names & allows	Parsed that day
2026-08-07	1,477	739	344	394	61,552
2026-08-06	1,470	739	339	392	61,421
2026-08-05	1,461	735	338	388	61,527
2026-08-04	1,459	740	331	388	61,620
2026-08-03	1,444	740	320	384	61,533
2026-08-02	1,434	733	318	383	61,559
2026-08-01	1,438	738	316	384	61,326
2026-07-31	1,454	752	316	386	61,595
2026-07-30	1,418	748	290	380	61,444
2026-07-29	1,396	733	283	380	61,492
2026-07-28	1,398	736	282	380	61,562
2026-07-27	1,392	735	280	377	61,440
2026-07-26	1,389	734	281	374	61,573
2026-07-25	1,393	740	280	373	61,584
2026-07-24	1,387	739	278	370	61,576
2026-07-23	1,385	737	276	372	61,758
2026-07-22	1,380	736	271	373	61,744
2026-07-21	1,362	730	266	366	61,565
2026-07-20	1,350	724	265	361	61,665
2026-07-19	1,350	727	260	363	61,451
2026-07-18	1,346	727	260	359	61,782
2026-07-17	1,339	731	256	352	61,659
2026-07-16	1,327	730	250	347	61,526
2026-07-14	1,280	697	240	343	61,542
2026-07-13	1,269	694	240	335	61,448
2026-07-12	1,267	695	238	334	61,518
2026-07-11	1,266	692	238	336	61,526
2026-07-10	1,260	693	236	331	61,425
2026-07-09	1,254	693	233	328	61,495
2026-07-08	1,247	688	233	326	61,364
2026-07-07	1,243	692	225	326	61,491
2026-07-06	1,231	684	223	324	61,455
2026-07-05	1,231	685	223	323	61,562
2026-07-03	1,232	687	223	322	61,535
2026-07-02	1,226	685	219	322	61,553
2026-07-01	1,216	684	214	318	61,599
2026-06-30	1,212	685	214	313	61,590
2026-06-29	1,212	686	213	313	61,814
2026-06-28	1,201	679	212	310	61,835
2026-06-27	1,197	676	207	314	61,848
2026-06-26	1,202	683	209	310	61,851
2026-06-25	1,195	675	210	310	61,867
2026-06-24	1,201	684	210	307	61,660
2026-06-23	1,201	692	205	304	61,877
2026-06-22	1,200	690	205	305	61,911
2026-06-21	1,194	689	203	302	61,905
2026-06-20	1,185	685	201	299	61,754
2026-06-18	1,173	685	194	294	61,805
2026-06-17	1,184	691	199	294	61,952
2026-06-16	1,168	691	187	290	61,645
2026-06-15	1,166	690	187	289	61,715
2026-06-14	1,171	692	192	287	61,697
2026-06-13	1,166	688	190	288	61,648
2026-06-10	1,151	686	183	282	61,489
2026-06-09	1,145	683	184	278	61,599

Why you will not find a robots.txt file here. These pages render mechanical verdicts and aggregate diffs, never a fetched body. Site operators leave contact addresses in robots.txt comments — on the 2026-08-06 snapshot 2,200 of the distinct bodies we fetched contain an email-shaped string — and republishing bodies would republish those. Nothing on this surface identifies an individual site, either: every figure is a count.

Compiled from each site's own published /robots.txt, /ai.txt, /llms.txt and /.well-known/tdmrep.json, fetched daily over a frozen 100,000-domain research panel (source list: Tranco; no Tranco rank is republished here). Verdicts are mechanical readings of what those files say under RFC 9309 grouping with exact product-token matching — they are not legal advice, not a statement about any site's intentions, and not a claim about what any crawler actually did. A robots.txt is a request, not an access control. Figures are provided for informational purposes only and carry no warranty of accuracy or completeness.

AI crawler policy home · What changed · How this is collected · US Tech Automations.