MEASURED 11 NOVEMBER 2026

Does lilyray.nyc block ChatGPT?

lilyray.nyc blocks 2 of the 14 crawlers that can cite a source in an AI answer (Google-CloudVertexBot, PetalBot). Content behind those rules is unlikely to appear as a cited source on those surfaces.

57%of 30 tracked AI crawlers can reach lilyray.nyc — 17 allowed, 13 blocked, 0 not listed

That is below the 100% median across the 1671 sites in this dataset. Resolved from https://lilyray.nyc/robots.txt on 11 November 2026.

Does lilyray.nyc block each AI product?

AI productPosition in robots.txtCrawlers checked
ChatGPTBlocks GPTBot; not OAI-SearchBot and ChatGPT-User3
ClaudeBlocks ClaudeBot; not Claude-SearchBot and Claude-User3
PerplexityAllows2
Gemini and Google AIBlocks all3
Microsoft CopilotAllows1
Apple IntelligenceBlocks all1
Meta AIBlocks Meta-ExternalAgent; not Meta-ExternalFetcher2

Has lilyray.nyc changed its AI crawler rules?

We read this file every week. Between 17 August 2026 and 11 November 2026 we recorded no lasting change in which AI crawlers it blocks. See which sites did change their rules.

What lilyray.nyc's robots.txt says about each AI crawler

A crawler named directly in its own group is governed by that group. One not named falls back to the wildcard group. Where neither exists the crawler is reported as not listed — no policy has been expressed, and in practice most crawlers will proceed.

User-agentOperatorPurposeAccessDecided by
OAI-SearchBotOpenAIsearch indexingAllowedwildcard policy
GPTBotOpenAImodel trainingBlockeddirect rule
ChatGPT-UserOpenAIon-demand fetchAllowedwildcard policy
Claude-SearchBotAnthropicsearch indexingAllowedwildcard policy
ClaudeBotAnthropicmodel trainingBlockeddirect rule
Claude-UserAnthropicon-demand fetchAllowedwildcard policy
PerplexityBotPerplexitysearch indexingAllowedwildcard policy
Perplexity-UserPerplexityon-demand fetchAllowedwildcard policy
Google-ExtendedGoogleGemini training controlBlockeddirect rule
BingbotMicrosoftCopilot search indexAllowedwildcard policy
Applebot-ExtendedAppleApple Intelligence controlBlockeddirect rule
Meta-ExternalAgentMetamodel trainingBlockeddirect rule
AmazonbotAmazonmodel trainingBlockeddirect rule
BytespiderByteDancemodel trainingBlockeddirect rule
CCBotCommon Crawltraining datasetBlockeddirect rule
GoogleOtherGoogleresearch and development fetchBlockeddirect rule
Google-CloudVertexBotGoogleVertex AI on-demand fetchBlockeddirect rule
Meta-ExternalFetcherMetaon-demand fetchAllowedwildcard policy
MistralAI-UserMistral AIon-demand fetchAllowedwildcard policy
cohere-aiCoheremodel trainingBlockeddirect rule
DuckAssistBotDuckDuckGoon-demand fetchAllowedwildcard policy
YouBotYou.comsearch indexingAllowedwildcard policy
TimpibotTimpitraining datasetAllowedwildcard policy
AI2BotAllen Institute for AImodel trainingAllowedwildcard policy
DiffbotDiffbotstructured-data extractionBlockeddirect rule
ImagesiftBotImageSifttraining datasetAllowedwildcard policy
PetalBotHuaweisearch indexingBlockeddirect rule
OmgilibotWebz.iotraining datasetAllowedwildcard policy
ElevenlabsCrawlerElevenLabsmodel trainingAllowedwildcard policy
ElevenlabsBotElevenLabson-demand fetchAllowedwildcard policy

Does lilyray.nyc allow AI training?

For each AI company with both kinds of crawler: whether this robots.txt lets its training crawlers in, and whether it lets in the crawlers behind its answers.

AI companyTrainingAnswers
OpenAIRefused GPTBotAllowed OAI-SearchBot, ChatGPT-User
AnthropicRefused ClaudeBotAllowed Claude-SearchBot, Claude-User
MetaRefused Meta-ExternalAgentAllowed Meta-ExternalFetcher
ElevenLabsAllowed ElevenlabsCrawlerAllowed ElevenlabsBot

Google is not in this table: its AI answers read what Googlebot may read, and its training control is Google-Extended, in the full list.

The shared AI-training signal

On 11 November 2026 this file had no group for __usage_ai-training, so it expresses no preference with the shared signal. A rule under User-agent: * is not read as one, and each company's own crawler rules above keep their meaning.

Google announced this signal on 30 October 2026 and plans to support it with other AI companies in 2027. It is a draft standard and no company has confirmed it reads it yet, so this is what the file says, not what happens to the content.

What this does and does not tell you

It tells you what lilyray.nyc states in its robots.txt, which is the file every well-behaved AI crawler consults before fetching. It is a stated preference and a voluntary protocol — not an access control, and not evidence about what any crawler actually did.

It also says nothing about whether the content is useful to an answer engine once fetched. Access is the precondition; extractable passages, visible dates, named authorship and sourced claims decide whether a reachable page is actually cited. Sign up for a free AI visibility report to see the original answers and which pages they cite.

Finally, robots.txt changes. This page reflects lilyray.nyc as it was on 11 November 2026. To see the current position, inspect the domain’s live robots.txt file and its matching rules.

Check your own site

Run the free AI crawler checker on your own site for the same verdict on every crawler, and the robots.txt lines to change if one is blocked by mistake. The ChatGPT citation guide explains the distinction between training and search access.

Browse the full study of 1671 measured domains, or the seo and marketing tools category, to see how this compares.

Embed this result

A live badge for lilyray.nyc, updated whenever this report refreshes. Paste it into a README or site footer:

EMBED HTML
<a href="https://www.indexhalo.com/ai-crawler-report/lilyray.nyc/">
  <img src="https://www.indexhalo.com/badge/ai-crawler-access/lilyray.nyc.svg"
       alt="AI crawler access for lilyray.nyc: 57%" height="20">
</a>
Who started blocking which crawler this week, measured from live robots.txt. Unsubscribe in one click.