Skip to main content

Brand profile

spar viel.

How often AI names spar viel. and where the brand ranks in web search. From one Achtung.app industry report.

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

spar viel. was named in 2 analysed AI answers in the Insurance industry report. That places the brand 82 of 129 there by AI prominence. Every citation comes from ChatGPT, on average at position 6,0 of the answer. The same queries returned no classic web-search result for the brand.

At a glance

AI citations
2
Summed across reports
Avg AI position
6,00
Weighted across reports
Web-search hits
0
Brave Search, aggregated
Verticals
1
AI models: 1

Verticals spar viel. appears in

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

Vertical Rank AI citations
Insurance #82/129 2 View report

Competitive context

The brands placed directly above and below spar viel. in the Insurance report, by AI prominence.

Rank Brand AI prominence
#80 LV 1871 31,1
#81 Continentale Versicherung 29,5
#82 spar viel. 29,0
#83 PREISVERGLEICH.de 29,0
#84 SIGNAL IDUNA 28,3

Full ranking in the report →

Which AI models name spar viel.?

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

n = 2 citations total

  • ChatGPT
    2 (100%)

Sample queries where spar viel. was named

A cross-section of the automated queries where AI models included spar viel. in their answer.

Query Model
versicherung vergleichen sparen ChatGPT

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 · 3 of 4 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 takes the brand's own pages out of the source pool for those answers; the brand can still be described from third-party pages.
  • 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. A TLS error is the one failure no crawler can work around, and retry behaviour is not documented for any of them.
  • 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 Crawlers differ in whether they render JavaScript: OpenAI documents its fetchers as reading raw HTML, while Google-grounded answers ride a search index that does render. If the homepage is a SPA shell, the non-rendering crawlers see an empty div and have nothing to cite. Server-side rendering or pre-rendering makes the page readable to all of them; the check looks for at least 100 words and 1 heading without JS.

Important: improves capture

  • 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 what link-preview cards are built from across the web. Which AI surfaces use them, and where, is not documented per assistant; the cost of setting them is low enough that the check grades it anyway.
  • 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.
  • No SPA, or a SPA with a meaningful noscript fallback 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.

Agent readiness: makes facts machine-readable

This check does not count towards AI visibility. It answers a different question: could software verify a fact about this brand without reading prose? On current evidence, structured markup does not make a brand cited more often in AI answers.

  • 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.

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

Diagnostics

JSON-LD types
WebSite, Organization, FAQPage

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

Sitemap
306 URLs
llms.txt (informational)
absent

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

Encryption
HTTPS ✓ · HSTS ✓
SPA
Detected client framework: angular

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.