Check
- What we found
- Why it matters
- What to change
- How to check it
Evidence
Nothing to show: the finding rests on what is absent from the page.
One offer, delivered by three disciplines.
Search Presence Engineering Found, understood, trusted, chosen: the method, and the three ways to work with usWhich AI crawlers may fetch this page under its robots.txt, and what is each of them for?
Progress
Time so far:
Surface:
How the address answers, and where it leads.
Structure:
The tags and headers a crawler reads.
Presence:
Permission to crawl and index, and the sitemap.
Each piece of a ring is one check.
No check found an error or a warning.
robots.txt
| Crawler | robots.txt says | The lines that decide | |
|---|---|---|---|
What the page itself tells AI features
How the address answers, and where it leads.
The tags and headers a crawler reads.
Permission to crawl and index, and the sitemap.
Changed something?
Keep this report
Nothing to show: the finding rests on what is absent from the page.
| robots.txt says: | The lines that decide: |
The checker reads the site’s robots.txt for every AI crawler on its list, each as its operator documents it, then the page’s own robots meta tags and headers: 13 checks in three groups. The report names each one with what it found, why it matters and how to check it yourself.
How the address answers, and where it leads.
The tags and headers a crawler reads.
Permission to crawl and index, and the sitemap.
A real check of tulus.studio, made on 16 October 2026.
1 page inspected, with its site’s robots.txt. 9 applicable checks ran.
Nothing to fix.
Surface:
2 passed
How the address answers, and where it leads.
Structure:
No check applied
The tags and headers a crawler reads.
Presence:
7 passed
Permission to crawl and index, and the sitemap.
Each piece of a ring is one check.
No check found an error or a warning.
robots.txt https://
Found, with 1 group of rules.
| Crawler | robots.txt says | The lines that decide | |
|---|---|---|---|
| Search and answers None kept out Crawlers for search results and answers that show or link the pages they come from. | |||
| Claude- | Crawls the web to improve the quality, relevance and accuracy of search results for users. Anthropic’s page on Claude-SearchBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Applebot Apple | Crawls for search in Spotlight, Siri and Safari, and what it crawls may also help train Apple’s AI models. Apple’s page on Applebot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| DuckAssistBot DuckDuckGo | Crawls pages in real time for DuckDuckGo’s AI-assisted answers, which cite their sources. DuckDuckGo’s page on DuckAssistBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Meta- | Crawls the web to improve the quality of Meta AI’s search results. Meta’s page on Meta-WebIndexer | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| MistralAI- | Crawls the web to index content for Mistral’s search, which helps answer people’s questions in Vibe. Mistral AI’s page on MistralAI-Index | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| OAI- | Used to show websites in the search results of ChatGPT’s search features. OpenAI’s page on OAI-SearchBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| PerplexityBot Perplexity | Used to show and link websites in Perplexity’s search results. Perplexity’s page on PerplexityBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Googlebot Google | Crawls for Google Search and all its features, AI Overviews and AI Mode among them. Google’s page on Googlebot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Bingbot Microsoft | Bing’s standard crawler, whose crawling and indexing Microsoft says Copilot also relies on. Microsoft’s page on Bingbot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Model training None kept out Crawlers that collect content to train AI models, and tokens that say whether pages another crawler fetched may be used for it. | |||
| Amazonbot Amazon | Used to improve Amazon’s products and services, and may be used to train Amazon’s AI models. Amazon’s page on Amazonbot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| ClaudeBot Anthropic | Collects web content that could help train Anthropic’s generative AI models. Anthropic’s page on ClaudeBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| CCBot Common Crawl | Builds Common Crawl’s open repository of web data, a primary source of training data for many large language models. Common Crawl’s page on CCBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Meta- | Crawls the web for uses such as training AI models or improving products by indexing content directly. Meta’s page on Meta-ExternalAgent | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| MistralAI- | Crawls web content to help build datasets for training Mistral’s generative AI models. Mistral AI’s page on MistralAI-Training | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| GPTBot OpenAI | Crawls content that may be used to train OpenAI’s generative AI models. OpenAI’s page on GPTBot | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Applebot- | Tells Apple whether content Applebot crawled may be used to train Apple’s foundation models. Apple’s page on Applebot-Extended Fetches nothing: its rules govern the use of pages another crawler fetched. | robots.txt says: May be used | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Google- | Tells Google whether content it crawls may train Gemini models and ground answers in Gemini Apps and Vertex AI. Google’s page on Google-Extended Fetches nothing: its rules govern the use of pages another crawler fetched. | robots.txt says: May be used | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Fetches a person asked for None kept out Fetches made because a person asked an AI assistant to open a page. | |||
| Amzn- | May fetch up-to-date information from the web when a person asks Alexa a question that needs it. Amazon’s page on Amzn-User Amazon says robots.txt may not apply to it. | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Claude- | May access a website when a person asks Claude a question. Anthropic’s page on Claude-User | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Meta- | Fetches individual links at a person’s request, including to help AI navigate websites and complete tasks. Meta’s page on Meta-ExternalFetcher Meta says robots.txt may not apply to it. | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| MistralAI- | May visit a web page to help answer a person’s question in Mistral’s Vibe. Mistral AI’s page on MistralAI-User | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| ChatGPT- | May visit a web page when a person asks ChatGPT or a custom GPT a question. OpenAI’s page on ChatGPT-User OpenAI says robots.txt may not apply to it. | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
| Perplexity- | May visit a web page to help answer a person’s question in Perplexity. Perplexity’s page on Perplexity-User Perplexity says it generally ignores robots.txt. | robots.txt says: May fetch | The lines that decide: line 1 User-agent: * line 2 Allow: / |
What the page itself tells AI features
Each crawler as its operator describes it, read on 15 October 2026.
2 of 2 applicable checks passed
How the address answers, and where it leads.
The address, after any redirects, answered with a success status (2xx).
Official documentation: How HTTP status codes affect Google’s crawlers
Evidence
Nothing to show: the finding rests on what is absent from the page.
Answer https://tulus.studio/
200 OK The address led to the page directly or through no more than three redirects.
Official documentation: Redirects and Google Search
Evidence
Nothing to show: the finding rests on what is absent from the page.
Answer https://tulus.studio/
200 OK No check of this kind was performed by this tool on this page.
The tags and headers a crawler reads.
The page’s robots meta tags and X-Robots-Tag headers carry none of the directives Google or Microsoft document for the AI features of their search.
Official documentation: AI features and your website
Evidence
Nothing to show: the finding rests on what is absent from the page.
7 of 7 applicable checks passed
Permission to crawl and index, and the sitemap.
robots.txt was checked for 8 AI training crawlers and control tokens, to see which may fetch or use this address and which it keeps out.
Official documentation: RFC 9309: Robots Exclusion Protocol
Evidence
Nothing to show: the finding rests on what is absent from the page.
robots.txt https://tulus.studio/robots.txt line 1
User-agent: * robots.txt https://tulus.studio/robots.txt line 2
Allow: / robots.txt was checked for 6 agents that fetch a page when a person asks an AI assistant to. For these, their operators say robots.txt may not apply: Amzn-User, Meta-ExternalFetcher, ChatGPT-User, Perplexity-User.
Official documentation: RFC 9309: Robots Exclusion Protocol
Evidence
Nothing to show: the finding rests on what is absent from the page.
robots.txt https://tulus.studio/robots.txt line 1
User-agent: * robots.txt https://tulus.studio/robots.txt line 2
Allow: / Nothing in robots.txt forbids Googlebot to fetch this address.
Official documentation: How Google interprets the robots.txt specification
Evidence
Nothing to show: the finding rests on what is absent from the page.
robots.txt https://tulus.studio/robots.txt line 1
User-agent: * robots.txt https://tulus.studio/robots.txt line 2
Allow: / No robots or googlebot meta tag in the page carries noindex or none.
Official documentation: Block Search indexing with noindex
Evidence
Nothing to show: the finding rests on what is absent from the page.
HTML https://tulus.studio/ line 1, column 538
<meta name="robots" content="index, follow, max-image-preview:large"> No X-Robots-Tag header in the answer carries noindex or none for all crawlers or for Googlebot.
Official documentation: Robots meta tag, data-nosnippet, and X-Robots-Tag specifications
Evidence
Nothing to show: the finding rests on what is absent from the page.
The site serves a robots.txt file, and this scan read it.
Official documentation: How Google interprets the robots.txt specification
Evidence
Nothing to show: the finding rests on what is absent from the page.
Answer https://tulus.studio/robots.txt
200 OK, 88 bytes, 1 group Nothing in robots.txt forbids Bingbot to fetch this address.
Official documentation: RFC 9309: Robots Exclusion Protocol
Evidence
Nothing to show: the finding rests on what is absent from the page.
robots.txt https://tulus.studio/robots.txt line 1
User-agent: * robots.txt https://tulus.studio/robots.txt line 2
Allow: / Nothing in robots.txt keeps any of the 7 AI search and answer crawlers checked from fetching this address.
Official documentation: RFC 9309: Robots Exclusion Protocol
Evidence
Nothing to show: the finding rests on what is absent from the page.
robots.txt https://tulus.studio/robots.txt line 1
User-agent: * robots.txt https://tulus.studio/robots.txt line 2
Allow: / robots.txt is within Google’s limit of 500 KiB.
Official documentation: How Google interprets the robots.txt specification
Evidence
Nothing to show: the finding rests on what is absent from the page.
Answer https://tulus.studio/robots.txt
88 bytes robots.txt names no AI crawler, or there is no robots.txt, so there is no name to check.
Official documentation: RFC 9309: Robots Exclusion Protocol
Evidence
Nothing to show: the finding rests on what is absent from the page.
Checked in 0.7 s with 2 requests, 18 kB received.
Two things about this page stay out of a public check’s reach:
The pages each check is based on.