AI access report
chavesnamao.com.br
Blocks 1 of 24 answer engines, blocks 6 training crawlers, refuses AI user agents at the edge, publishes llms.txt.
3 failing
4 partial
20 passing
Scanned 2 hours ago · 2 scans on record
Reach
35.9
/ 40
Whether AI crawlers and answer-engine fetchers are permitted to request the page at all, in robots.txt, in robots directives, and at the edge.
Readability
20.6
/ 25
Whether a fetcher that does not execute JavaScript receives the actual content, in markup an extractor can segment.
Structure
20
/ 20
Machine-readable markup that states the page's type, entities, canonical URL, and discrete facts instead of leaving them to be inferred.
Attribution
11
/ 15
Signals that let an answer engine name the author, date the content, resolve the publisher, and cite it under known terms.
Who is allowed to read this site 1 of 24 answer engines blocked
| Crawler | Operator | Uses content for | robots.txt | Live request |
|---|---|---|---|---|
| GPTBot Crawls content that may be used to train OpenAI's generative AI foundation models. |
OpenAI | Model training | blocked Disallow: / |
refused 403 |
| OAI-SearchBot Indexes pages so they can be surfaced and cited in ChatGPT search results, not for training. |
OpenAI | Answer index | allowed | served 200 |
| ChatGPT-User Fetches a page when a ChatGPT user or GPT Action asks for it; user-initiated, so robots rules may not apply. |
OpenAI | Live retrieval | allowed | not probed |
| OAI-AdsBot Visits pages submitted as ChatGPT ads to check policy compliance and ad relevance; not used for model training. |
OpenAI | Live retrieval | allowed | not probed |
| ClaudeBot Collects web content that may contribute to training Anthropic's models; honors Crawl-delay. |
Anthropic | Model training | blocked Disallow: / |
served 200 |
| Claude-User Retrieves pages on demand when a Claude user's question needs live web content. |
Anthropic | Live retrieval | allowed | not probed |
| Claude-SearchBot Indexes content to improve the relevance and accuracy of Claude's search results. |
Anthropic | Answer index | allowed | not probed |
| anthropic-ai Legacy token widely blocked for Anthropic training; Anthropic now documents ClaudeBot, Claude-User and Claude-SearchBot. |
Anthropic | Model training | allowed | not probed |
| Google-Extended Control token with no user agent of its own; governs Gemini training and grounding use of Googlebot data. |
Model training | blocked Disallow: / |
not probed | |
| Googlebot Crawls and renders pages for Google Search, Images, Video, News and Discover. |
Answer index | allowed | not probed | |
| Googlebot-News Robots token controlling Google News inclusion; crawling itself uses the Googlebot user agents. |
Answer index | allowed | not probed | |
| Google-CloudVertexBot Crawls sites at a site owner's request to build Vertex AI agents; no effect on Google Search. |
Live retrieval | allowed | not probed | |
| GoogleOther Generic Google crawler used by product teams for one-off fetches such as internal research and development. |
Model training | allowed | not probed | |
| Applebot Crawls for Siri, Spotlight and Safari search; falls back to Googlebot rules and ignores Crawl-delay. |
Apple | Answer index | allowed | not probed |
| Applebot-Extended Control token with no user agent; disallowing it excludes crawled content from Apple foundation model training. |
Apple | Model training | blocked Disallow: / |
not probed |
| Bingbot Indexes pages for Bing search and the Copilot answers that are grounded in the Bing index. |
Microsoft | Answer index | allowed | not probed |
| msnbot Legacy Microsoft search crawler token still honored alongside bingbot. |
Microsoft | Answer index | allowed | not probed |
| PerplexityBot Indexes and links pages in Perplexity search results; not used to collect foundation model training data. |
Perplexity | Answer index | allowed | served 200 |
| Perplexity-User ignores robots Fetches a page for a specific user question; Perplexity documents that it generally ignores robots.txt. |
Perplexity | Live retrieval | allowed | not probed |
| Meta-ExternalAgent Crawls the web to train Meta's foundation AI models and to index content directly into products. |
Meta | Model training | blocked Disallow: / |
not probed |
| Meta-ExternalFetcher ignores robots Fetches individual links for agentic AI tasks; Meta documents that it may bypass robots.txt. |
Meta | Live retrieval | allowed | not probed |
| FacebookBot Crawls public pages to improve language models behind Meta's speech recognition technology. |
Meta | Model training | allowed | not probed |
| Meta-WebIndexer Indexes pages so Meta AI can cite and link them in its search answers. |
Meta | Answer index | allowed | not probed |
| Meta-ExternalAds Crawls the web to improve Meta's advertising and other business products and services. |
Meta | Model training | allowed | not probed |
| facebookexternalhit ignores robots Fetches shared links for Facebook, Instagram and Messenger previews; may bypass robots.txt for integrity checks. |
Meta | Live retrieval | allowed | not probed |
| Bytespider ignores robots Downloads content to train ByteDance LLMs and is widely reported to ignore robots.txt directives. |
ByteDance | Model training | allowed | not probed |
| TikTokSpider ignores robots Fetches shared URLs for TikTok link previews and feeds; not expected to follow robots.txt. |
ByteDance | Live retrieval | allowed | not probed |
| Amazonbot Crawls for Amazon product and Alexa answers and may use the content to train Amazon AI models. |
Amazon | Model training | blocked Disallow: / |
not probed |
| Amzn-SearchBot Indexes content for Amazon search experiences such as Alexa; does not crawl for generative AI training. |
Amazon | Answer index | allowed | not probed |
| Amzn-User ignores robots Fetches live pages to answer a user's Alexa question; Amazon documents it may not follow all robots.txt rules. |
Amazon | Live retrieval | allowed | not probed |
| CCBot Builds the open Common Crawl web archive, a common source of LLM pretraining corpora. |
Common Crawl Foundation | Archive | blocked Disallow: / |
not probed |
| Diffbot Extracts structured page data for Diffbot's knowledge graph, which is licensed to AI customers. |
Diffbot | Model training | allowed | not probed |
| omgili Collects forum, news and blog content that Webz.io sells as web data feeds, including for AI training. |
Webz.io | Model training | allowed | not probed |
| omgilibot Legacy Omgili search crawler token still blocked alongside the current omgili agent. |
Webz.io | Model training | allowed | not probed |
| AI2Bot Collects web text for Ai2's open datasets used to train open language models such as OLMo. |
Allen Institute for AI | Model training | allowed | not probed |
| cohere-ai Retrieves pages to answer user-initiated prompts in Cohere's enterprise AI products. |
Cohere | Live retrieval | blocked Disallow: / |
not probed |
| cohere-training-data-crawler Downloads training data for the large language models behind Cohere's enterprise AI products. |
Cohere | Model training | allowed | not probed |
| MistralAI-User Fetches pages on demand so Mistral's Vibe assistant can answer a question with live, cited web content. |
Mistral AI | Live retrieval | allowed | not probed |
| MistralAI-Index Indexes content for Mistral search behind Vibe answers; not used for generative AI training. |
Mistral AI | Answer index | allowed | not probed |
| MistralAI-Training Crawls web content to build datasets for training Mistral's generative AI models. |
Mistral AI | Model training | allowed | not probed |
| DuckAssistBot Crawls pages in real time for DuckDuckGo's cited AI-assisted answers; not used for model training. |
DuckDuckGo | Live retrieval | allowed | not probed |
| YouBot Indexes pages for You.com search results and the AI answers built on that index. |
You.com | Answer index | allowed | not probed |
| PanguBot Collects web content used to train Huawei's PanGu family of large models. |
Huawei | Model training | allowed | not probed |
| Timpibot Crawls pages for Timpi's decentralized index, which is also used as LLM training data. |
Timpi | Model training | allowed | not probed |
| ImagesiftBot Downloads public images plus surrounding text to build ImageSift's searchable image index. |
ImageSift (Hive) | Model training | allowed | not probed |
| Kangaroo Bot Scrapes site content into datasets used to train the Kangaroo LLM. |
Kangaroo LLM | Model training | allowed | not probed |
| SemrushBot-OCOB Crawls pages to feed Semrush's ContentShake AI writing tool. |
Semrush | Model training | allowed | not probed |
| Scrapy Generic scraping framework often used to build AI training datasets; obeys robots.txt only when ROBOTSTXT_OBEY is on. |
Zyte (open-source framework) | Model training | allowed | not probed |
Two of these columns matter differently. robots.txt is what the site declares. Live request is what actually happened when we sent a real request using that crawler's user agent from a datacentre IP, which is how edge blocking, rate limits and challenge pages show up even when robots.txt looks permissive.
Reach 35.9 / 40
✗
Edge returns 403, 429, or a challenge to AI user agents
Requests identifying as gptbot were refused at the edge (HTTP 403 Forbidden).
Why it matters. A permissive robots.txt is irrelevant if the edge answers an AI user agent with 403, 429, or a JavaScript challenge. Retrieval fetchers do not solve interstitials, so the assistant records a fetch failure and answers from another source.
Fix. Fetch the page with each AI user agent string and compare the status and byte count against a browser request. On Cloudflare, check whether the "Block AI bots" toggle in AI Crawl Control, a Bot Fight Mode rule, or a WAF custom rule on `cf.verified_bot_category` is catching the request, then narrow it: block the training category and add a skip rule for the retrieval agents you want citing you. Verified bots must not be handed Managed Challenge, since a challenge is a hard failure for a non-browser client. Re-test after every WAF or bot-management change, because these toggles are applied zone-wide.
Fix. Fetch the page with each AI user agent string and compare the status and byte count against a browser request. On Cloudflare, check whether the "Block AI bots" toggle in AI Crawl Control, a Bot Fight Mode rule, or a WAF custom rule on `cf.verified_bot_category` is catching the request, then narrow it: block the training category and add a skip rule for the retrieval agents you want citing you. Verified bots must not be handed Managed Challenge, since a challenge is a hard failure for a non-browser client. Re-test after every WAF or bot-management change, because these toggles are applied zone-wide.
for ua in "OAI-SearchBot/1.0" "ChatGPT-User/1.0" "Claude-User/1.0" \
"Claude-SearchBot/1.0" "PerplexityBot/1.0" "Mozilla/5.0"; do
code=$(curl -s -o /dev/null -w '%{http_code}' -A "$ua" https://example.com/)
printf '%s\t%s\n' "$code" "$ua"
done6 pt
!
Answer-engine fetchers are blocked, so you cannot be cited
Blocked from citing you: cohere-ai.
Why it matters. Retrieval fetchers (OAI-SearchBot, ChatGPT-User, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User) load a page at answer time to quote and link it. When robots.txt disallows them the assistant drops the URL from its candidate set, so the citation goes to a competitor while your training exposure stays exactly the same.
Fix. Separate the two crawler classes in robots.txt instead of blocking by vendor. Allow `OAI-SearchBot` and `ChatGPT-User` (OpenAI retrieval and user-initiated fetches), `Claude-SearchBot` and `Claude-User` (Anthropic retrieval), and `PerplexityBot` and `Perplexity-User`; keep any opt-out you want on `GPTBot`, `ClaudeBot`, `CCBot`, `Google-Extended`, and `Applebot-Extended`. Order does not decide precedence in RFC 9309 parsers, the longest matching rule does, so make the allow rules at least as specific as the disallow rules. Blocking retrieval buys nothing on training, because the training crawlers are separate user agents with separate rules.
Fix. Separate the two crawler classes in robots.txt instead of blocking by vendor. Allow `OAI-SearchBot` and `ChatGPT-User` (OpenAI retrieval and user-initiated fetches), `Claude-SearchBot` and `Claude-User` (Anthropic retrieval), and `PerplexityBot` and `Perplexity-User`; keep any opt-out you want on `GPTBot`, `ClaudeBot`, `CCBot`, `Google-Extended`, and `Applebot-Extended`. Order does not decide precedence in RFC 9309 parsers, the longest matching rule does, so make the allow rules at least as specific as the disallow rules. Blocking retrieval buys nothing on training, because the training crawlers are separate user agents with separate rules.
# Retrieval and citation fetchers: allowed.
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
Allow: /
# Training and dataset crawlers: disallowed.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: Google-Extended
User-agent: Applebot-Extended
Disallow: /
User-agent: *
Allow: /
Disallow: /checkout
Sitemap: https://example.com/sitemap.xml12 pt
!
Training crawlers are disallowed for this path
Blocked by robots.txt: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, Amazonbot.
Why it matters. GPTBot, ClaudeBot, and CCBot collect pages into pretraining corpora, and Google-Extended and Applebot-Extended are opt-out tokens that govern whether already-crawled pages may be used for Gemini and Apple Intelligence. Disallowing them removes your text from the corpora models generalise from, which is a policy choice, not a bug.
Fix. Decide this deliberately rather than by inheriting a template. If you want your content in model weights, remove the `Disallow: /` groups for `GPTBot`, `ClaudeBot`, `CCBot`, `Google-Extended`, and `Applebot-Extended`. If you do not, keep those groups but scope them to the paths that matter and leave retrieval fetchers untouched, because `Google-Extended` and `Applebot-Extended` only control training use and never affect search or answer citation. Record the decision somewhere durable so the next robots.txt edit does not silently reverse it.
Fix. Decide this deliberately rather than by inheriting a template. If you want your content in model weights, remove the `Disallow: /` groups for `GPTBot`, `ClaudeBot`, `CCBot`, `Google-Extended`, and `Applebot-Extended`. If you do not, keep those groups but scope them to the paths that matter and leave retrieval fetchers untouched, because `Google-Extended` and `Applebot-Extended` only control training use and never affect search or answer citation. Record the decision somewhere durable so the next robots.txt edit does not silently reverse it.
# Opt out of model training only.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: Google-Extended
User-agent: Applebot-Extended
Disallow: /8 pt
✓
No blanket disallow applies to this path
The wildcard group does not disallow the entire site.
5 pt
✓
robots.txt served as plain text with a 200 response
robots.txt served, 4833 bytes, 42 group(s).
3 pt
✓
No Crawl-delay directive constrains fetchers
No Crawl-delay directive.
2 pt
✓
Page is indexable, with no noindex directive
No noindex directive on the homepage.
2 pt
✓
Full-length snippet extraction is permitted
Snippets are not restricted by meta tags.
1 pt
✓
X-Robots-Tag header is absent or permissive
No restrictive X-Robots-Tag header.
1 pt
Readability 20.6 / 25
✗
Visible text is a small fraction of the HTML payload
Text is 2.3% of the 430 KB document; 285 KB is inline script.
Why it matters. Extractors strip scripts, styles, and wrapper markup before passing text to a model, and a page where content is a small fraction of the payload loses more of it to boilerplate removal. Inline JSON state blobs and deeply nested wrappers also push real text past the truncation limit of a retrieval context.
Fix. Move inline hydration state and large inline scripts out of the document, or fetch them after load instead of embedding them. Flatten wrapper `div` trees and let semantic elements carry the content, and keep utility-class soup out of the article body. Serve the same text without the boilerplate at a stable URL if you need a clean extraction target.
Fix. Move inline hydration state and large inline scripts out of the document, or fetch them after load instead of embedding them. Flatten wrapper `div` trees and let semantic elements carry the content, and keep utility-class soup out of the article body. Serve the same text without the boilerplate at a stable URL if you need a clean extraction target.
4 pt
!
Heading levels are missing, duplicated, or skipped
4 H1 and 49 headings total, 7 phrased as questions.
Why it matters. Chunkers split long pages on heading boundaries and carry the nearest heading into each chunk's metadata. A page with no `h1`, several competing `h1`s, or levels that skip from `h2` to `h4` produces chunks whose topic labels do not match their text, so retrieval matches the wrong passage.
Fix. Give every page one `h1` that names its subject, then nest `h2` and `h3` without skipping levels. Make each heading describe the section beneath it in words a reader would search for, rather than a label like "Overview". Style with CSS instead of choosing heading levels for their font size, and never use a heading tag for a caption or a button.
Fix. Give every page one `h1` that names its subject, then nest `h2` and `h3` without skipping levels. Make each heading describe the section beneath it in words a reader would search for, rather than a label like "Overview". Style with CSS instead of choosing heading levels for their font size, and never use a heading tag for a caption or a button.
<h1>Robots.txt rules for AI crawlers</h1>
<h2>Training crawlers</h2>
<h3>GPTBot</h3>
<h3>ClaudeBot</h3>
<h2>Retrieval and citation fetchers</h2>
<h3>OAI-SearchBot</h3>3 pt
✓
Substantive text is present in the server-rendered HTML
1547 words of text are present in the raw HTML. Most AI fetchers do not run JavaScript.
9 pt
✓
Primary content is wrapped in a semantic landmark
A <main> landmark marks the primary content.
3 pt
✓
Title is unique and describes the page in specific terms
Title is 56 characters: "Classificados de imóveis, carros e motos | Chaves na Mão"
3 pt
✓
Meta description provides an author-written summary
Meta description is 141 characters.
2 pt
✓
Document language is declared on the html element
Declared language: pt-BR.
1 pt
Structure 20 / 20
✓
Page ships JSON-LD structured data
21 JSON-LD node(s): Organization, Person, PostalAddress, ContactPoint, FAQPage, Question.
7 pt
✓
Structured data uses a specific type that matches the page
Recognized types: organization, faqpage, softwareapplication.
4 pt
✓
JSON-LD parses cleanly with recognised schema.org terms
All JSON-LD blocks parse cleanly.
3 pt
✓
Page declares a self-referential canonical URL
Canonical: https://www.chavesnamao.com.br
3 pt
✓
XML sitemap is declared in robots.txt and returns 200
Sitemap found at /sitemap.xml (463 URLs on the first document).
2 pt
✓
Key facts are available in lists or tables
0 tables, 17 lists, 0 code blocks, 7 question headings.
1 pt
Attribution 11 / 15
✗
No machine-readable published or modified date
No publication or modification dates in structured data.
Why it matters. Answer engines prefer recent sources for questions about current state and use `dateModified` to decide whether a cached copy needs refetching. With no machine-readable date the page is treated as undated and loses to competitors that publish one.
Fix. Publish `datePublished` and `dateModified` in the page's structured data as ISO 8601 values with a timezone offset. Update `dateModified` only when the content actually changes, since bumping it on every deploy trains crawlers to ignore it. Mirror the value in a visible `<time datetime>` element so the rendered text and the metadata agree, and keep the sitemap `lastmod` consistent with it.
Fix. Publish `datePublished` and `dateModified` in the page's structured data as ISO 8601 values with a timezone offset. Update `dateModified` only when the content actually changes, since bumping it on every deploy trains crawlers to ignore it. Mirror the value in a visible `<time datetime>` element so the rendered text and the metadata agree, and keep the sitemap `lastmod` consistent with it.
<time datetime="2026-08-04T14:20:00-04:00">Updated August 4, 2026</time>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Allow AI answer engines in robots.txt",
"datePublished": "2026-02-11T09:00:00-05:00",
"dateModified": "2026-08-04T14:20:00-04:00"
}
</script>3 pt
!
No machine-readable license or usage terms for the content
No licence declaration, so reuse terms are ambiguous.
Why it matters. A `license` property, or a linked terms page, states the reuse conditions in a place a crawler can read, rather than leaving them to be inferred. Where terms are unstated, some pipelines default to the more restrictive handling, which reduces how much of the text is quoted.
Fix. Add a `license` property to the page's structured data pointing at a specific license URL, such as a Creative Commons deed or your own terms page, and add `rel="license"` on the visible link. Use `usageInfo` for conditions that are not a standard license, such as attribution wording or an API-only clause. State the terms once, at a stable URL, and reference it from every page rather than restating it per template.
Fix. Add a `license` property to the page's structured data pointing at a specific license URL, such as a Creative Commons deed or your own terms page, and add `rel="license"` on the visible link. Use `usageInfo` for conditions that are not a standard license, such as attribution wording or an API-only clause. State the terms once, at a stable URL, and reference it from every page rather than restating it per template.
<a rel="license" href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Allow AI answer engines in robots.txt",
"license": "https://creativecommons.org/licenses/by/4.0/",
"usageInfo": "https://example.com/legal/content-reuse",
"creditText": "Example, crawlcensus research desk"
}
</script>2 pt
✓
/llms.txt lists canonical pages in the documented format
/llms.txt is present and well formed (5 sections, 16 links).
4 pt
✓
Author is declared in structured data
Authorship is declared in structured data or markup.
3 pt
✓
Organization entity declares the publisher and its identifiers
Organization entity with sameAs links is present.
3 pt
Evidence raw measurements
robots.txt
- Size
- 4,833 bytes
- Groups
- 42
- Sitemaps
- https://www.chavesnamao.com.br/sitemap-index.xml
https://www.chavesnamao.com.br/blog/sitemap.xml
View the file as our crawler received it
# As a condition of accessing this website, you agree to abide by the
# following content signals:
#
# (a) If a content-signal = yes, you may collect content for the corresponding use.
# (b) If a content-signal = no, you may not collect content for the corresponding use.
# (c) If the website operator does not include a content signal for a corresponding
# use, the website operator neither grants nor restricts permission via content
# signal with respect to the corresponding use.
#
# The content signals and their meanings are:
#
# search: building a search index and providing search results (e.g.,
# returning hyperlinks and short excerpts from your website's contents).
# Search does not include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g.,
# retrieval augmented generation, grounding, or other real-time taking
# of content for generative AI search answers).
# ai-train: training or fine-tuning AI models.
#
# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF RIGHTS
# UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT AND RELATED
# RIGHTS IN THE DIGITAL SINGLE MARKET.
# Sitemaps
Sitemap: https://www.chavesnamao.com.br/sitemap-index.xml
Sitemap: https://www.chavesnamao.com.br/blog/sitemap.xml
User-agent: *
Content-Signal: ai-train=no, search=yes, ai-input=yes
# ========================
# PARÂMETROS
# ========================
Allow: /*?pg=2$
Allow: /*?pg=3$
Allow: /*?pg=4$
Allow: /*?pg=5$
Disallow: /*?*
# ========================
# APIs & AGENT DISCOVERY
# ========================
Allow: /api/mcp
Allow: /.well-known/
Disallow: /api/*?pg=
Disallow: /api/
# ========================
# ÁREAS PRIVADAS
# ========================
Disallow: /admin/
Disallow: /minhaconta/
Disallow: /favoritos/
Disallow: /contatados/
Disallow: /historico/
Disallow: /cadastre-se
Disallow: /entrar
Disallow: /pagamento/
Disallow: /public/views_contracts/
# ========================
# ROTAS INTERNAS
# ========================
Disallow: /ws/
Disallow: /servicos/
Disallow: /site/cobranca/
Disallow: /imoveis/integracao/
Disallow: /veiculos/integracao/
Disallow: /cdn-cgi/zaraz
# ========================
# ERROS / DUPLICAÇÕES
# ========================
Disallow: /*/undefined
Disallow: /*/undefined/
# ========================
# BLOG WP
# ========================
Disallow: /noticias/wp-admin/
# ========================
# ESTATÍSTICAS
# ========================
Disallow: /imoveis/estatisticas/
Disallow: /veiculos/estatisticas/
User-agent: GPTBot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: ClaudeBot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: Google-Extended
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: Meta-ExternalAgent
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: Applebot-Extended
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: DeepSeekBot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: Grok
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: GrokBot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: Amazonbot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: CCBot
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: cohere-ai
Content-Signal: ai-train=no, search=yes, ai-input=yes
User-agent: sitebot
Disallow: /
User-agent: Slurp
Disallow: /
User-agent: CazoodleBot
Disallow: /
User-agent: Cazoodlebot
Disallow: /
User-agent: sistrix
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: UbiCrawler
Disallow: /
User-agent: DOC
Disallow: /
User-agent: Zao
Disallow: /
User-agent: sitecheck.internetseer.com
Disallow: /
User-agent: Zealbot
Disallow: /
User-agent: MSIECrawler
Disallow: /
User-agent: SiteSnagger
Disallow: /
User-agent: WebStripper
Disallow: /
User-agent: WebCopier
Disallow: /
User-agent: Fetch
Disallow: /
User-agent: Offline Explorer
Disallow: /
User-agent: Teleport
Disallow: /
User-agent: TeleportPro
Disallow: /
User-agent: WebZIP
Disallow: /
User-agent: linko
Disallow: /
User-agent: HTTrack
Disallow: /
User-agent: Microsoft.URL.Control
Disallow: /
User-agent: Xenu
Disallow: /
User-agent: larbin
Disallow: /
User-agent: libwww
Disallow: /
User-agent: ZyBORG
Disallow: /
User-agent: Download Ninja
Disallow: /
User-agent: wget
Disallow: /
User-agent: grub-client
Disallow: /
User-agent: k2spider
Disallow: /
User-agent: NPBot
Disallow: /
User-agent: WebReaper
Disallow: /
User-agent: psbot
Disallow: /
User-agent: Exabot
Disallow: /
User-agent: Speedy
Disallow: /
User-agent: dotbot
Disallow: /
User-agent: Bloglines/3.1
Disallow: /
User-agent: Jyxobot/1
Disallow: /
User-agent: cityreview
Disallow: /
User-agent: WijuBot
Disallow: /
Machine-readable extras
- llms.txt
- valid, 3,156 bytes, 16 links
- ai.txt
- absent
- Sitemap
- /sitemap.xml (463 URLs)
- Feeds
- none
- Schema types
- Organization, Person, PostalAddress, ContactPoint, FAQPage, Question, Answer, SoftwareApplication
- Edge
- Cloudflare
- Final URL
- https://www.chavesnamao.com.br/
- HTML size
- 430 KB, 1,547 words of text
Publish the score free
Sites that score well embed the badge. It links back to this live report, which re-measures on every scan.
<a href="https://crawlcensus.com/site/chavesnamao.com.br"><img src="https://crawlcensus.com/badge/chavesnamao.com.br.svg" alt="AI access score for chavesnamao.com.br" width="150" height="20"></a>Track changes on this domain pro
Crawler policy is edited quietly. We re-scan monitored domains daily, keep the history, and email you the moment a crawler is blocked or unblocked, an llms.txt appears, or the score moves.
One address, unlimited domains during the beta. No newsletter, only change alerts.