Checked 9/24/2026 · https://www.heise.de/
There are 1 critical blockers for AI discoverability — fix these first.
AI crawler matrix
For each bot: what your robots.txt allows — and what your server actually returns to the bot's user agent. Rows highlighted in red: robots allows it, but the server blocks it (usually a WAF or bot-protection rule).
| Bot | Operator | robots.txt | Server response |
|---|---|---|---|
| GPTBot | OpenAI | allowed | 200 + content |
| OAI-SearchBot | OpenAI | allowed | 200 + content |
| ChatGPT-User | OpenAI | allowed | 200 + content |
| ClaudeBot | Anthropic | allowed | 200 + content |
| Claude-SearchBot | Anthropic | allowed | 200 + content |
| Claude-User | Anthropic | allowed | 200 + content |
| PerplexityBot | Perplexity | allowed | 200 + content |
| Perplexity-User | Perplexity | allowed | 200 + content |
| Google-Extended | Google (Gemini-Training) | blocked | — |
| Googlebot | Google (KI-Übersichten) | allowed (via User-agent: *) | 200 + content |
| CCBot | Common Crawl (Trainingsdaten vieler LLMs) | blocked | 200 + content |
| Bytespider | ByteDance (Doubao) | blocked | 200 + content |
| Amazonbot | Amazon (Alexa/Rufus) | blocked | 200 + content |
| Applebot-Extended | Apple (Intelligence-Training) | blocked | — |
| Meta-ExternalAgent | Meta (Llama/Meta AI) | blocked | 200 + content |
How is the score calculated?
| AI search bots are blocked in robots.txt | -8 |
| Page title too short or too long | -6 |
| Not exactly one H1 heading | -5 |
| No llms.txt | -5 |
| No Organization schema | -4 |
| No author or authorship signal | -4 |
| No sameAs links | -3 |
| No FAQ or HowTo markup | -2 |
| Result | 63 / 100 |
Access for AI crawlers
AI search bots are blocked in robots.txt
Your robots.txt blocks 1 bots that fetch content for answers in AI assistants and search engines: Google-Extended. While they are blocked, your site cannot appear there as a source.
This is what you should do: Check for each bot whether the block is intended. If you only want to opt out of AI training, block the training bots (GPTBot, ClaudeBot, Google-Extended) and allow the search bots.
Structure & machine understanding
Page title too short or too long
The <title> is 67 characters long. Around 30–60 characters is sensible: descriptive enough to name the topic, short enough not to be cut off.
This is what you should do: Write a concise title that contains the topic and, if relevant, the brand.
Not exactly one H1 heading
The page has 0 H1 headings. A single, unambiguous H1 tells humans and machines what the page is primarily about.
This is what you should do: Set exactly one H1 that names the page's main topic. Everything below starts at H2.
No llms.txt
There is no file at /llms.txt. llms.txt is a short Markdown overview of your key content that some AI systems use for orientation.
This is what you should do: Create an /llms.txt: an H1 with the name, a short paragraph about the offering, and a link list to the central pages.
# Your company > One-sentence description. ## Key pages - [Product](https://your-domain.com/product): … - [Pricing](https://your-domain.com/pricing): … - [About](https://your-domain.com/about): …
No Organization schema
There is JSON-LD, but no "Organization" entry. AI systems can then place your brand less well as a distinct entity and link it to external sources.
This is what you should do: Add an "Organization" schema with name, url, logo and sameAs (links to your official profiles).
No FAQ or HowTo markup
Question-and-answer and step-by-step content is harder for AI systems to recognise as directly citable answers without FAQPage or HowTo markup.
This is what you should do: Where the page answers real questions or gives instructions, mark it up as FAQPage or HowTo (no markup without visibly matching content).
Trust and entity signals (E-E-A-T)
No author or authorship signal
No author is recognisable (neither meta tag, rel=author nor JSON-LD Person). For "experience" and "expertise" in the E-E-A-T sense, named, traceable authorship matters.
This is what you should do: For editorial content, name an author and link an author page; also mark them up as JSON-LD "Person".
No sameAs links
The JSON-LD is missing "sameAs". It lets AI systems clearly map your brand or person to known entities (Wikidata, LinkedIn, industry directories).
This is what you should do: Add a "sameAs" in Organization or Person with the URLs of your official profiles and directory entries.
OK (6)
- The main content is in the HTML without JavaScript.
- Structured data (JSON-LD) is present. — ItemList, Thing
- A canonical URL is set.
- The sitemap is reachable.
- Fast server response time.
- No noindex — the page may be indexed.
Next steps
- AI search bots are blocked in robots.txt. Check for each bot whether the block is intended. If you only want to opt out of AI training, block the training bots (GPTBot, ClaudeBot, Google-Extended) and allow the search bots.
- Page title too short or too long. Write a concise title that contains the topic and, if relevant, the brand.
- Not exactly one H1 heading. Set exactly one H1 that names the page's main topic. Everything below starts at H2.
Weekly re-scan with an email alert on every change. In preparation — add your address.
Method & limits
Checked 9/24/2026. citeglass fetches heise.de and its related files (robots.txt, llms.txt, sitemap.xml) over HTTP — once as a normal browser, once per AI crawler user agent. No JavaScript is executed. Time to first byte: 65 ms.
What this is not: No rank or citation tracking, no statement about whether a model actually names you, and no check of content loaded via JavaScript. A snapshot from the perspective of one server IP.