Agent Web Index › wir-machen-druck.de

Can AI assistants read wir-machen-druck.de?

Measured on 2026-09-19 by asking the site 9 times — once as a browser, once as each of the 8 crawlers that feed ChatGPT, Claude, Perplexity, Gemini, Meta AI, Apple Intelligence and Doubao — and comparing what came back. The AI-training opt-out tokens that never crawl are read from robots.txt instead.

A87 / 100
7 of 8 crawlers can read this page.
More readable than 77% of the 47,315 sites measured so far. Structured data: Organization, WebSite, Offer.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)200 can read it allowed-by-star
GPTBot (ChatGPT)200 can read it allowed-by-star
OAI-SearchBot (ChatGPT Search)200 can read it allowed-by-star
PerplexityBot (Perplexity)200 can read it allowed-by-star
Google-Extended (Gemini, AI Overviews)
a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own
not opted out allowed-by-star
Meta-ExternalAgent (Meta AI)200 can read it allowed-by-star
Amazonbot (Alexa, Rufus)200 can read it allowed-by-star
Bytespider (Doubao, Lark)403 challenged allowed-by-star
Applebot (Siri, Apple Intelligence)200 can read it allowed-by-star
Applebot-Extended (Apple Intelligence training)
a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own
not opted out allowed-by-star

AWS CloudFront answers for this domain. Where a crawler above is refused while robots.txt allows it, the rule is applied by that edge, not written by the site — see how often each edge does this.

What to change, in order

  1. Let in the 1 crawler your own robots.txt already allows+1 crawler
    Bytespider is turned away before reading the page (served a bot challenge instead of the page), while robots.txt permits it — so this block is not written in your site. AWS CloudFront answers for this domain. AWS WAF Bot Control has an AI-crawler category that CloudFront enforces ahead of your origin. https://docs.aws.amazon.com/waf/latest/developerguide/waf-bot-control.html Fixing it takes this domain from 7 to 8 of 8 crawlers.
  2. Publish llms.txt
    llms.txt is missing, so an assistant has to discover the site by following links. llms.txt is the emerging convention for telling an assistant which pages actually matter.

The checks

Re-run this audit live → Full AI-visibility report for wir-machen-druck.de →

Sites with a similar score

a1-systems.comA 88cenforce.onlineA 88rubyonrails.orgA 88wintage.inA 87wisc.eduA 87wimp.comA 87wissenschaft.deA 87webnode.czA 87wuerth.deA 87uraib.inA 87shopalso.inA 87cabaia.frA 87

Browse the whole index →

Embed this score

Put the badge on wir-machen-druck.de — it links back here, and re-measures every time this index re-crawls.

wir-machen-druck.de AI readability: A 87/100
<a href="https://shop.lumnika.com/ai-readiness/wir-machen-druck.de"><img src="https://shop.lumnika.com/ai-readiness/wir-machen-druck.de/badge.svg" alt="AI readability"></a>
Method. 9 live HTTP requests (one per crawler, one as a browser) plus robots.txt, llms.txt, sitemap.xml and security.txt, 12-second timeout each, from a single vantage point. Blocking AI crawlers is a legitimate choice, not a failure: this page records what is true, not what should be. Domain comes from a shop-platform seed (Shopify/WooCommerce/Magento/BigCommerce/Shopline fingerprint or JSON-LD price), not the Tranco traffic ranking. One page per domain — the homepage — is audited.

Part of the Agent Web Index, 47,315 domains measured, updated continuously.