Skip to main content

Brand profile

heise online

How often AI names heise online and where the brand ranks in web search. Aggregated across 3 Achtung.app industry reports.

heise.de DACH dataset (DE/AT/CH), as of 1. Aug 2026

heise online was named in 2 analysed AI answers across 3 industry reports. Its strongest placement is the Media & Publishing report: rank 151 of 475 by AI prominence. ChatGPT names the brand most often, on average at position 9,0 of the answer. In classic web search heise online holds 2 results, at an average rank of 5,0.

At a glance

AI citations
2
Summed across reports
Avg AI position
8,50
Weighted across reports
Web-search hits
2
Brave Search, aggregated
Verticals
3
AI models: 2

Verticals heise online appears in

Sorted by rank. Click to open the full vertical report.

Vertical Rank AI citations
Media & Publishing #151/475 2 View report
SaaS & Software #311/325 0 View report
Health & Wellness #374/433 0 View report

AI prominence over time

How the AI prominence of heise online has moved across the collections so far. One point per report collection.

heise online in Media & Publishing

heise online 38.6 Top 10 in the report 64.3
0 25 50 75 100 May 26 Jun 26 Jul 26
heise online in Media & Publishing
Collection heise online Top 10 in the report
May 26 27.8 66.7
Jun 26 20.0 67.4
Jul 26 38.6 64.3

AI prominence is a 0 to 100 score combining citation frequency, position and model coverage. The dashed line is the average of the ten strongest brands in the same collection, which shows whether a movement came from the brand or from the whole market. The series only covers verticals with at least two collections. Definitions in the glossary.

Competitive context

The brands placed directly above and below heise online in the Media & Publishing report, by AI prominence.

Rank Brand AI prominence
#149 Outseta 39,0
#150 Wishlistmember 39,0
#151 heise online 38,6
#152 Streambuzzer 38,2
#153 Pressebund 38,2

Full ranking in the report →

Which AI models name heise online?

Distribution of citations across the AI models we query. Longer bars mean the model named heise online more often in its answers.

n = 2 citations total

  • ChatGPT
    1 (50%)
  • Perplexity
    1 (50%)

Discoverability for AI platforms

Weekly audit of the technical prerequisites that search-grounded AI platforms (live web search per query) need to find and render this site.

Last checked: 2. Aug 2026

AI-ready 5 of 5 critical checks passing · 4 of 5 important checks passing

Two crawler categories: AI live-retrieval crawlers fetch pages on demand to answer questions in ChatGPT, Perplexity or Claude; training crawlers feed model pre-training. Only the live-retrieval layer is graded here; the training tier is an editorial choice.

Critical: blocks AI visibility

  • AI live-retrieval crawlers allowed in robots.txt Your robots.txt must allow OAI-SearchBot, ChatGPT-User, PerplexityBot, Perplexity-User, Claude-User, and Claude-SearchBot. These fetch pages on demand to answer questions in ChatGPT, Perplexity, and Claude. Blocking any of them removes the brand from those answers.
  • No silent edge block on AI live-retrieval crawlers Even with robots.txt allowing them, the edge (Cloudflare, WAF, server) can still 403/429/503 AI bot user-agents. Most common culprit: Cloudflare's "Block AI Scrapers and Crawlers" managed rule, or Bot Fight Mode. Allow these UAs at a level above the WAF challenge rules.
  • HTTPS reachable on the homepage The homepage must be reachable over HTTPS without a redirect chain that fails. AI crawlers do not retry on TLS errors.
  • Sitemap reachable A reachable sitemap helps AI crawlers discover internal pages beyond the homepage. We try /sitemap.xml, /sitemap_index.xml (Yoast), /wp-sitemap.xml (WordPress 5.5+), and any Sitemap: URL in robots.txt.
  • Homepage renders content without JavaScript AI retrieval crawlers do not execute JavaScript. If your homepage is a SPA shell that renders client-side, bots see an empty div and have nothing to cite. The page must produce at least 100 words and 1 heading without JS; typically requires server-side rendering or pre-rendering.

Important: improves capture

  • Organization or WebSite JSON-LD on the homepage Organization or WebSite JSON-LD on the homepage helps search engines recognize the brand as an entity (Knowledge Graph, rich results). Current evidence shows no direct effect on grounded-LLM citations; those models read the visible page text, not the JSON-LD. Still useful SERP hygiene; add via schema.org markup in the head.
  • Canonical URL declared A canonical link tag tells crawlers which URL is the definitive version. Avoids citation fragmentation across www / non-www / trailing-slash variants.
  • Open Graph title and image set Open Graph title and image are used by AI assistants in answer cards and preview tiles. Missing either degrades how the citation renders.
  • HSTS header advertised The Strict-Transport-Security header tells browsers to enforce HTTPS for future visits. Set in your web server config or via Plesk's HTTPS Strict Transport Security toggle.
  • SPA detected and a meaningful noscript fallback exists When the homepage is a SPA, a noscript block with real fallback content (not just "please enable JavaScript") gives AI crawlers at least something to read. Best is server-side rendering; this is the half-measure.

Training-crawler status (informational, not graded): 0 / 5 blockiert.

Diagnostics

JSON-LD types
ItemList, Thing

SEO hygiene; per Google not a direct lever for AI citations.

Sitemap
10.000 URLs
llms.txt (informational)
absent

Per Google, no effect on AI visibility; tracked here for information only.

Encryption
HTTPS ✓ · HSTS ✓

Track your own brand over time?

Achtung.app monitors how often a brand is named in AI answers and classic web search, which verticals it appears in, and how that changes over time.

Check your brand

All figures come from Achtung.app's published vertical reports. Achtung.app runs standardized, brand-free queries against AI models and classic web search, extracts named brands, and consolidates them on their canonical domain. Details in the methodology document.