AI access report
xe.gr
Blocks 10 of 24 answer engines, blocks 17 training crawlers, no structured data.
10 failing
2 partial
15 passing
Scanned 2 hours ago · 1 scan on record
Reach
29.1
/ 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
18.7
/ 25
Whether a fetcher that does not execute JavaScript receives the actual content, in markup an extractor can segment.
Structure
6
/ 20
Machine-readable markup that states the page's type, entities, canonical URL, and discrete facts instead of leaving them to be inferred.
Attribution
1
/ 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 10 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: / |
served 200 |
| OAI-SearchBot Indexes pages so they can be surfaced and cited in ChatGPT search results, not for training. |
OpenAI | Answer index | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
not probed |
| Claude-SearchBot Indexes content to improve the relevance and accuracy of Claude's search results. |
Anthropic | Answer index | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
not probed |
| Meta-WebIndexer Indexes pages so Meta AI can cite and link them in its search answers. |
Meta | Answer index | blocked Disallow: / |
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 | blocked Disallow: / |
not probed |
| TikTokSpider ignores robots Fetches shared URLs for TikTok link previews and feeds; not expected to follow robots.txt. |
ByteDance | Live retrieval | blocked Disallow: / |
not probed |
| Amazonbot Crawls for Amazon product and Alexa answers and may use the content to train Amazon AI models. |
Amazon | Model training | allowed | 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 | blocked Disallow: / |
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 | blocked Disallow: / |
not probed |
| omgilibot Legacy Omgili search crawler token still blocked alongside the current omgili agent. |
Webz.io | Model training | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
not probed |
| PanguBot Collects web content used to train Huawei's PanGu family of large models. |
Huawei | Model training | blocked Disallow: / |
not probed |
| Timpibot Crawls pages for Timpi's decentralized index, which is also used as LLM training data. |
Timpi | Model training | blocked Disallow: / |
not probed |
| ImagesiftBot Downloads public images plus surrounding text to build ImageSift's searchable image index. |
ImageSift (Hive) | Model training | blocked Disallow: / |
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 | blocked Disallow: / |
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 | blocked Disallow: / |
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 29.1 / 40
✗
Answer-engine fetchers are blocked, so you cannot be cited
Blocked from citing you: OAI-SearchBot, ChatGPT-User, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Meta-WebIndexer, TikTokSpider, cohere-ai, YouBot.
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, FacebookBot, Bytespider, Diffbot, omgili, omgilibot, AI2Bot, cohere-training-data-crawler, PanguBot, Timpibot, ImagesiftBot, SemrushBot-OCOB, Scrapy.
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
✓
AI user agents receive the same 200 response as browsers
Live requests as 4 AI user agents were served normally.
6 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, 17194 bytes, 7 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 18.7 / 25
✗
Visible text is a small fraction of the HTML payload
Text is 1.4% of the 332 KB document; 79 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
0 H1 and 12 headings total.
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
322 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 55 characters: "Χρυσή Ευκαιρία: Το #1 site αγγελιών στην Ελλάδα | xe.gr"
3 pt
✓
Meta description provides an author-written summary
Meta description is 171 characters.
2 pt
✓
Document language is declared on the html element
Declared language: el.
1 pt
Structure 6 / 20
✗
No JSON-LD structured data found on the page
No JSON-LD structured data on the homepage.
Why it matters. JSON-LD gives an answer engine typed facts (headline, author, dates, price, publisher) without inferring them from prose, and those fields populate the entity record a citation is attached to. With no structured data every attribute has to be guessed from text, and guesses are dropped when confidence is low.
Fix. Add one `<script type="application/ld+json">` block describing the page's primary entity, using the schema.org type that actually fits: `Article` or `NewsArticle`, `Product`, `Recipe`, `Event`, `FAQPage`, or `SoftwareApplication`. Populate the required properties for that type and make every value match visible page content. Prefer JSON-LD over microdata or RDFa, since it is the format the major crawlers document, and render it server-side so non-JavaScript fetchers see it.
Fix. Add one `<script type="application/ld+json">` block describing the page's primary entity, using the schema.org type that actually fits: `Article` or `NewsArticle`, `Product`, `Recipe`, `Event`, `FAQPage`, or `SoftwareApplication`. Populate the required properties for that type and make every value match visible page content. Prefer JSON-LD over microdata or RDFa, since it is the format the major crawlers document, and render it server-side so non-JavaScript fetchers see it.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Allow AI answer engines in robots.txt",
"description": "How to opt out of model training while staying citable.",
"url": "https://example.com/blog/robots-for-ai",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/robots-for-ai"
},
"image": "https://example.com/images/robots-for-ai.png",
"inLanguage": "en",
"datePublished": "2026-02-11T09:00:00-05:00",
"dateModified": "2026-08-04T14:20:00-04:00",
"author": {
"@type": "Person",
"name": "Dana Reyes",
"url": "https://example.com/authors/dana-reyes"
},
"publisher": {
"@type": "Organization",
"name": "Example",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png",
"width": 512,
"height": 512
}
}
}7 pt
✗
Structured data is too generic for what the page is about
No entity types that answer engines consume.
Why it matters. Answer engines route by entity type: a `Product` node supplies price and availability, an `Article` node supplies author and dates, and a `FAQPage` node supplies question and answer pairs. A generic `WebPage` or `WebSite` node on a product or article page carries none of those fields, so the specific facts stay unavailable.
Fix. Replace bare `WebPage` and `WebSite` nodes with the most specific type that describes the page, and fill the properties that type defines. Use `@graph` to publish several linked nodes on one page, such as an `Article` whose `publisher` points at an `Organization` node by `@id`. Add `BreadcrumbList` for hierarchy and reuse the same `@id` values across pages so the entity resolves to one record.
Fix. Replace bare `WebPage` and `WebSite` nodes with the most specific type that describes the page, and fill the properties that type defines. Use `@graph` to publish several linked nodes on one page, such as an `Article` whose `publisher` points at an `Organization` node by `@id`. Add `BreadcrumbList` for hierarchy and reuse the same `@id` values across pages so the entity resolves to one record.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Product",
"@id": "https://example.com/products/widget#product",
"name": "Widget Pro",
"sku": "WGT-PRO-1",
"brand": { "@type": "Brand", "name": "Example" },
"offers": {
"@type": "Offer",
"url": "https://example.com/products/widget",
"price": "49.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Products", "item": "https://example.com/products" },
{ "@type": "ListItem", "position": 2, "name": "Widget Pro" }
]
}
]
}4 pt
✗
JSON-LD fails to parse or uses invalid schema.org terms
1 JSON-LD block(s) failed to parse and are ignored by every consumer.
Why it matters. A structured data block is parsed as strict JSON in a single pass; one trailing comma, unescaped quote, or unquoted key discards the whole block. Misspelled properties and a missing `@context` or `@type` are silently ignored, so the page scores as having no structured data at all.
Fix. Serialise the block from a real object rather than string concatenation, so quoting and escaping are handled for you. Include `@context: "https://schema.org"` and a `@type` on every node, and check property spelling against the type's page on schema.org, since `datePublished` and `dateModified` are camelCase and `author` is not `authors`. Escape `<` as `\u003c` inside string values to avoid terminating the script element early, and validate the output with the schema.org validator before shipping.
Fix. Serialise the block from a real object rather than string concatenation, so quoting and escaping are handled for you. Include `@context: "https://schema.org"` and a `@type` on every node, and check property spelling against the type's page on schema.org, since `datePublished` and `dateModified` are camelCase and `author` is not `authors`. Escape `<` as `\u003c` inside string values to avoid terminating the script element early, and validate the output with the schema.org validator before shipping.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Valid JSON-LD: no trailing commas, every key quoted",
"datePublished": "2026-08-04",
"author": { "@type": "Person", "name": "Dana Reyes" }
}3 pt
✓
Page declares a self-referential canonical URL
Canonical: https://www.xe.gr/
3 pt
✓
XML sitemap is declared in robots.txt and returns 200
Sitemap found at /sitemap.xml (304 URLs on the first document).
2 pt
✓
Key facts are available in lists or tables
0 tables, 17 lists, 0 code blocks, 0 question headings.
1 pt
Attribution 1 / 15
✗
No /llms.txt index of canonical pages
No /llms.txt.
Why it matters. `/llms.txt` is a markdown file that points an assistant at the canonical pages for a site, so retrieval does not depend on which page a search happened to return. Its format is fixed: one `#` title, a `>` blockquote summary, then `##` sections of markdown links with short notes.
Fix. Publish `/llms.txt` as `text/plain` markdown: an `#` H1 with the project name, a `>` blockquote summary, optional plain paragraphs of context, then `##` sections whose bullets are `[title](absolute-url): note`. Link the pages you want quoted, put lower-priority links under an `## Optional` section, and prefer URLs that also serve clean markdown. Keep it generated from the same source as your sitemap so it does not drift, and remember it is a hint for assistants, not an access control mechanism.
Fix. Publish `/llms.txt` as `text/plain` markdown: an `#` H1 with the project name, a `>` blockquote summary, optional plain paragraphs of context, then `##` sections whose bullets are `[title](absolute-url): note`. Link the pages you want quoted, put lower-priority links under an `## Optional` section, and prefer URLs that also serve clean markdown. Keep it generated from the same source as your sitemap so it does not drift, and remember it is a hint for assistants, not an access control mechanism.
# Example
> Example publishes reference documentation for the Widget API and guides for
> configuring crawler access.
Prefer the pages below over search results; each URL is canonical.
## Docs
- [Widget API reference](https://example.com/docs/api): endpoints, auth, limits.
- [Quickstart](https://example.com/docs/quickstart): first request in five minutes.
## Policies
- [Crawler policy](https://example.com/legal/crawlers): which agents we allow.
## Optional
- [Changelog](https://example.com/changelog): dated release notes.4 pt
✗
No machine-readable author is attached to the page
No author or Person entity, which weakens the authority signals answer engines use.
Why it matters. An `author` property in structured data is what lets an answer engine name a person or organisation as the source and link the byline to a stable profile. A byline that exists only as styled text is not reliably associated with the document during extraction.
Fix. Add an `author` property to the page's `Article`, `BlogPosting`, or `NewsArticle` node, typed as `Person` or `Organization`, with a `name` and a `url` pointing at a real profile page. Give each author a stable `@id` and reuse it across posts so the entity consolidates. Keep the visible byline identical to the structured value, and avoid generic names such as "Admin" or "Staff Writer" where a real author exists.
Fix. Add an `author` property to the page's `Article`, `BlogPosting`, or `NewsArticle` node, typed as `Person` or `Organization`, with a `name` and a `url` pointing at a real profile page. Give each author a stable `@id` and reuse it across posts so the entity consolidates. Keep the visible byline identical to the structured value, and avoid generic names such as "Admin" or "Staff Writer" where a real author exists.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Allow AI answer engines in robots.txt",
"author": {
"@type": "Person",
"@id": "https://example.com/authors/dana-reyes#person",
"name": "Dana Reyes",
"url": "https://example.com/authors/dana-reyes",
"jobTitle": "Infrastructure Engineer",
"sameAs": ["https://github.com/danareyes"]
}
}3 pt
✗
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 Organization entity identifies the publisher
No Organization entity, so the brand is harder to resolve to a known entity.
Why it matters. An `Organization` node with `sameAs` links resolves your site to a single entity across knowledge graphs instead of leaving the publisher name as an ambiguous string. That resolution is what lets an assistant attribute an answer to your brand and reuse your name, logo, and contact details.
Fix. Publish one `Organization` node, usually on the home page, with `name`, `url`, `logo`, and `sameAs` pointing at the profiles that already describe you: Wikipedia or Wikidata, Crunchbase, LinkedIn, and your primary social accounts. Give it a stable `@id` such as `https://example.com/#organization` and reference that `@id` from each page's `publisher` property instead of repeating the block. Add `contactPoint` and `address` when they are public, and keep every value identical to what the site shows.
Fix. Publish one `Organization` node, usually on the home page, with `name`, `url`, `logo`, and `sameAs` pointing at the profiles that already describe you: Wikipedia or Wikidata, Crunchbase, LinkedIn, and your primary social accounts. Give it a stable `@id` such as `https://example.com/#organization` and reference that `@id` from each page's `publisher` property instead of repeating the block. Add `contactPoint` and `address` when they are public, and keep every value identical to what the site shows.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example",
"legalName": "Example Holdings, Inc.",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png",
"width": 512,
"height": 512
},
"sameAs": [
"https://www.wikidata.org/wiki/Q00000000",
"https://www.linkedin.com/company/example",
"https://github.com/example"
],
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer support",
"email": "support@example.com",
"areaServed": "US",
"availableLanguage": ["en"]
}
}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
Evidence raw measurements
robots.txt
- Size
- 17,194 bytes
- Groups
- 7
- Sitemaps
- https://www.xe.gr/sitemap
View the file as our crawler received it
User-agent: Mediapartners-Google
Disallow:
User-agent: *
Allow: */jobs/evresi-prosopikou
Allow: */property/stegastiko-daneio
Allow: */property/times-akiniton
Allow: */property/real-estate-market-trends-in-greece
Allow: */property/immobilienmarkt-trends-in-griechenland
Allow: */property/tendances-du-marche-immobilier-en-grece
Allow: */property/tendencias-inmobiliarias-mercado-griego
Allow: */property/kataxorisi-aggelias-akinitou
Allow: */property/foititika-spitia
Allow: */property/student-accommodation
Allow: */property/studentenwohnungen
Allow: */property/logement-etudiants
Allow: */property/casas-estudiantes
Disallow: /search
Disallow: */automoto/premium
Disallow: */automoto/count
Disallow: */automoto/selected
Disallow: */automoto/recent_classifieds
Disallow: */automoto/result_metrics
Disallow: */automoto/r/*/*?
Disallow: */property/search
Allow: /*/sitemap/property/results
Allow: /sitemap/property/results
Disallow: /*/property/results
Disallow: /property/results
Disallow: */property/evresi
Disallow: */property/result_metrics
Disallow: */property/unique_properties
Disallow: */property/u
Disallow: */property/r/*/*?
Disallow: */account
Disallow: */services
Disallow: */auth
Disallow: */εργασία/θέσεις-εργασίας?*
Disallow: */εργασία/θέση-εργασίας*?*
Allow: */εργασία/θέσεις-εργασίας?page=
Disallow: */εργασία/θέσεις-εργασίας?page=*&
Disallow: /static_html/promo/esales/phones/
Disallow: /*/εργασία
Disallow: /*/professionals
Allow: /*/sitemap/automoto
Allow: /sitemap/automoto
Disallow: /*/automoto
Disallow: */jobs/search
Allow: /*/sitemap/jobs/results
Allow: /sitemap/jobs/results
Disallow: /*/jobs/results
Disallow: /jobs/results
User-agent: Twitterbot
Disallow:
User-agent: proximic
Disallow: */property/d/*
Disallow: */εργασία/θέση-εργασίας/*
Disallow: */%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1/%CE%B8%CE%AD%CF%83%CE%B7-%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1%CF%82/*
Disallow: */professionals/results/*
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Claude-User
User-agent: Claude-SearchBot
User-agent: Bravebot
User-agent: meta-webindexer
Allow: */εργασία/θέση-εργασίας/*
Allow: */%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1/%CE%B8%CE%AD%CF%83%CE%B7-%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1%CF%82/*
Disallow: */εργασία/θέση-εργασίας/*?*
Disallow: */%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1/%CE%B8%CE%AD%CF%83%CE%B7-%CE%B5%CF%81%CE%B3%CE%B1%CF%83%CE%AF%CE%B1%CF%82/*?*
Allow: /sitemap$
Allow: /*/sitemap$
Allow: /sitemap/jobs/listings
Allow: /*/sitemap/jobs/listings
Allow: */jobs/evresi-prosopikou
Allow: */property/stegastiko-daneio
Allow: */property/times-akiniton
Allow: */property/real-estate-market-trends-in-greece
Allow: */property/immobilienmarkt-trends-in-griechenland
Allow: */property/tendances-du-marche-immobilier-en-grece
Allow: */property/tendencias-inmobiliarias-mercado-griego
Allow: */property/kataxorisi-aggelias-akinitou
Allow: */property/foititika-spitia
Allow: */property/student-accommodation
Allow: */property/studentenwohnungen
Allow: */property/logement-etudiants
Allow: */property/casas-estudiantes
Disallow: /
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: Bytespider
User-agent: TikTokSpider
User-agent: meta-externalagent
User-agent: Omgilibot
User-agent: Omgili
User-agent: webzio-extended
User-agent: AI2Bot
User-agent: AI2Bot-Dolma
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: DeepSeekBot
User-agent: PanguBot
User-agent: Cotoyogi
User-agent: SBIntuitionsBot
User-agent: ICC-Crawler
User-agent: Timpibot
User-agent: Youbot
User-agent: img2dataset
User-agent: Diffbot
Disallow: /
User-agent: PiplBot
User-agent: 01h4x.com
User-agent: 360Spider
User-agent: 404checker
User-agent: 404enemy
User-agent: 80legs
User-agent: ADmantX
User-agent: AIBOT
User-agent: ALittle Client
User-agent: ASPSeek
User-agent: Abonti
User-agent: Aboundex
User-agent: Aboundexbot
User-agent: Acunetix
User-agent: AdsTxtCrawlerTP
User-agent: AfD-Verbotsverfahren
User-agent: AhrefsBot
User-agent: AiHitBot
User-agent: Aipbot
User-agent: Alexibot
User-agent: AllSubmitter
User-agent: Alligator
User-agent: AlphaBot
User-agent: Anarchie
User-agent: Anarchy
User-agent: Anarchy99
User-agent: Ankit
User-agent: Anthill
User-agent: Apexoo
User-agent: Aspiegel
User-agent: Asterias
User-agent: Atomseobot
User-agent: Attach
User-agent: AwarioBot
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: BBBike
User-agent: BDCbot
User-agent: BDFetch
User-agent: BLEXBot
User-agent: BackDoorBot
User-agent: BackStreet
User-agent: BackWeb
User-agent: Backlink-Ceck
User-agent: BacklinkCrawler
User-agent: BacklinksExtendedBot
User-agent: Badass
User-agent: Bandit
User-agent: Barkrowler
User-agent: BatchFTP
User-agent: Battleztar Bazinga
User-agent: BetaBot
User-agent: Bigfoot
User-agent: Bitacle
User-agent: Black Hole
User-agent: BlackWidow
User-agent: Blackboard
User-agent: Blow
User-agent: BlowFish
User-agent: Boardreader
User-agent: Bolt
User-agent: BotALot
User-agent: Brandprotect
User-agent: Brandwatch
User-agent: Buck
User-agent: Buddy
User-agent: BuiltBotTough
User-agent: BuiltWith
User-agent: Bullseye
User-agent: BunnySlippers
User-agent: BuzzSumo
User-agent: CATExplorador
User-agent: CODE87
User-agent: CSHttp
User-agent: Calculon
User-agent: CazoodleBot
User-agent: Cegbfeieh
User-agent: CensysInspect
User-agent: CheTeam
User-agent: CheeseBot
User-agent: CherryPicker
User-agent: ChinaClaw
User-agent: Chlooe
User-agent: Citoid
UserMachine-readable extras
- llms.txt
- absent
- ai.txt
- absent
- Sitemap
- /sitemap.xml (304 URLs)
- Feeds
- none
- Schema types
- none
- Edge
- CloudFront
- Final URL
- https://www.xe.gr/
- HTML size
- 332 KB, 322 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/xe.gr"><img src="https://crawlcensus.com/badge/xe.gr.svg" alt="AI access score for xe.gr" 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.