stadtausstellung.at 25 F
🛡️ SEO 32 🤖 GEO 3 ⚡ Perf 55 🏗️ Arch 60

stadtausstellung.at — Global SEODiff Score 25/100

stadtausstellung.at
📊

stadtausstellung.at struggles with AI visibility, recording a critical ACRI of 10/100 — AI crawlers face significant hurdles extracting its content. Within the saas vertical, this places stadtausstellung.at below the industry average of 57 —, indicating room for competitive improvement. Heavy client-side rendering (80% ghost ratio) makes content extraction nearly impossible for static AI crawlers. A 50.0× token bloat ratio means crawlers must process significantly more tokens to reach the actual content — a drag on extraction efficiency. The complete absence of JSON-LD schema is a missed opportunity: even basic Organization markup would improve how AI crawlers understand this domain. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

25
F — Global SEODiff Score
Comprehensive search visibility assessment
Critical gaps across the board. Start with AI Readiness (3).
🎯 Top Fix: Enable server-side rendering (ghost ratio 80%) → +8–15 pts
⚠️ Crawl Blocked: Suspected anti-bot protection (minimal content)
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than stadtausstellung.at?
Run the same 40-signal audit on your own domain — free, instant results.
Scan Your Site Free →
🧮 Score Transparency — How is this calculated?
🛡️ Traditional SEO (25% weight)32 × 0.25 = 8.0
🤖 AI Readiness / GEO (40% weight)3 × 0.40 = 1.2
⚡ Performance (20% weight)55 × 0.20 = 11.0
🏗️ Architecture & Trust (15% weight)60 × 0.15 = 9.0
Weighted sum = 8.0 + 1.2 + 11.0 + 9.0
Global SEODiff Score = 25 (F)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
28
Rendering
avg 93
0
Structure
avg 35
0
Schema
avg 10
55
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 21%
Rank #210214
+52 pts
Gap
AI (ACRI)
Top 73%
Score 10/100

stadtausstellung.at punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →

Why stadtausstellung.at ranks here

Tech stackVue.js
Industrysaas
RenderingCSR
Schema coverage0 blocks
Token bloat50×+

Fastest improvements

  • Add basic Organization and WebSite JSON-LD to fix “0 schema blocks” (see Schema Coverage).
  • Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
  • Create an llms.txt file so AI crawlers can discover your content structure without heavy crawling. Generate llms.txt →
  • Run a full entropy audit to find which DOM regions waste the most tokens. Run Entropy Audit →
🧪

JavaScript Rendering Check

We check what AI crawlers miss when they skip JavaScript execution.

Running headless browser to simulate AI extraction…

⚠️ Crawl Failed: Anti-Bot Protection Detected

Suspected anti-bot protection (minimal content)

The scores below may not reflect actual site quality. The crawler received a challenge page instead of real content.

🛡️

Traditional SEO

32/100 25 % of Global Score 🟡 Medium Confidence

📝 Title Tag

11 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

0 chars
Missing

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

  • ✓ Exactly 1 <h1> tag — found 1
  • ✗ Has <h2> headings — found 0
  • ✓ <h2> not before <h1>

🔍 Indexability

  • ✗ Canonical tag present
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → de
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✗ og:title
  • ✗ og:description
  • ✗ og:image
  • ✗ twitter:card
📐 How the SEO Pillar score is calculated

SEO Pillar = Title (20 pts) + Meta Desc (20 pts) + Heading Hierarchy (20 pts) + Indexability (20 pts) + Social/OG (20 pts)

Each sub-score is derived from the checks above. Canonical tag, lang attribute, og:image, and a single H1 are the highest-impact items.

🤖

AI Readiness / GEO

3/100 40 % of Global Score 🟢 High Confidence

This pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.

🔗

Citation Alternatives

Research
💡
Insight: In the saas sector, gp-auto.com.ua (ACRI: 84) currently has stronger AI extractability. AI models tend to prefer sources with higher semantic structure and schema coverage. Domains with ACRI < 40 see 3.5× more hallucinations. Read the research →
stadtausstellung.at
7
Your ACRI Score
84
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. gp-auto.com.ua has schema coverage of 2 blocks and uses Cloudflare Pages. Improve your score by implementing the remediation patches below.
📊 Side-by-Side Comparison →
🚨

Hallucination Risk

Research

Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.

👻
Shadow Content Detected: 80% of your page token budget is trapped in non-rendered regions (JavaScript-dependent content invisible to AI crawlers). Combined with 1530.3x token bloat, AI models are using most of their context window on noise instead of your real content. This dramatically increases hallucination probability — models fill the gap with made-up facts.
Analyzing hallucination risk…

🤖 Bot Access Matrix

GPTBot (OpenAI)
Allowed
ClaudeBot (Anthropic)
Allowed
CCBot (Common Crawl)
Allowed
Google-Extended
Allowed
Googlebot
Allowed

👻 Rendering (Ghost Ratio) Docs

Ghost Ratio 80%
0% — Safe 50% 100% — Risk
Status Heavily JS-Dependent (High Risk)
Rendering Type CSR
💡High ghost ratio means AI crawlers may miss content. Consider server-side rendering (SSR) or pre-rendering for critical pages.

📊 Structure & Information Density Docs

Structure Grade 0/100 — Poor
Structured Elements 0 elements (0 lists, 0 rows, 0 headers)
Total Words2
Raw Density0.0%
💡Low structure score (0/100). Very little extractable text detected (2 words). AI crawlers may be blocked from accessing the real page content — check the Ghost Ratio and Bot Access sections.

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks0 — No JSON-LD detected

Schema Coverage Map

0/7 schema types detected
❌ Organization
❌ Product/Service
❌ Breadcrumb
❌ FAQ
❌ Article
❌ WebSite
💡Organization schema missing. AI models cannot identify your brand entity. Without it, your brand won't appear in Knowledge Panels or be associated with your content.
💡Product / Service schema missing. AI models don't know this is a SaaS product. Add Product or SoftwareApplication schema so AI understands what you offer and can surface pricing/features.
💡BreadcrumbList schema missing. AI cannot understand your site hierarchy or how pages relate to each other.
💡FAQ schema missing. Adding FAQPage schema lets AI models directly extract Q&A pairs for Featured Snippets and chatbot answers.
💡WebSite schema missing. Add WebSite + SearchAction so Google can generate a Sitelinks Search Box for your brand in AI results.

📐 AI Efficiency Metrics Docs

7
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability7/100 — AI models can barely extract answers from this page
Crawl CostLow (25/100) — efficient for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

1%
🗑️ 99%
Useful Content (24 B)Bloat (35.8 KB)
Token Bloat Ratio50×+ — Bloated

Multimodal Readiness

Visual ContextNo images detected
Image Alt Coverage0 / 0 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 35.9 KB, but only 24 B is text. 1% useful / 99% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (50×+) risks context-window truncation by ChatGPT, Claude, and Gemini. Reduce inline scripts, CSS, hydration payloads, and tracking code.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 99.9% · SNR: 0.00 · Signal: 6 / Noise: 9175 tokens

🔬 AI-Crawler Simulation

See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.

🌐
This is what humans see — styled, branded, visual.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
🤖

AI Answer Preview

NEW

See how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.

Simulating AI extraction…

🔧 Tech Stack

FrameworkVue.js
AI-Readiness Score55/100
Servernginx/1.18.0 (Ubuntu)
CDN
HTTP Status200
Load Time2661 ms
Raw HTML Size35.9 KB
Visible Text Size24 B

Performance & Speed

55/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2661 ms
Slow — bots may time out or deprioritise

Google considers <200 ms "good". AI crawlers may have even shorter timeouts.

📦 Page Weight

235
DOM nodes
36 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

0
tracker scripts
0
third-party domains
1.1%
token overhead
Minimal tracker load — clean signal for bots
📐 How the Performance Pillar score is calculated

Perf Pillar = TTFB (35 pts) + Page Weight (25 pts) + Cache/CDN (20 pts) + Tracker Tax (20 pts)

TTFB <200 ms = full marks. DOM >3000 or payload >300 KB incurs heavy penalties. Tracker scripts beyond 5 reduce score.

🏗️

Architecture & Trust

60/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → http://www.stadtausstellung.at/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

0
internal links
0
external links
Very few internal links — crawlers may miss important pages

🔒 Security & Trust

  • ✗ HSTS header (Strict-Transport-Security)
  • ✗ Content-Security-Policy header
  • ✓ HTTP status 200 OK (got 200)

♿ Accessibility Signals

  • ✓ HTML lang attribute → de
  • ✓ Meta viewport for mobile
  • ✓ Single H1 for screen readers
📐 How the Architecture Pillar score is calculated

Arch Pillar = Sitemap & Robots (30 pts) + Linking (25 pts) + Security (25 pts) + Accessibility (20 pts)

Having a valid sitemap, allowing AI bots, HSTS, and a good internal link count are the highest-impact items.

🏅 AI-Verified Trust Badge

Your site is currently blocking AI crawlers. Unblock them and rescan to earn your AI-Verified badge.

AI-Verified badge for stadtausstellung.at
Unverified — crawl access is blocked
<a href="https://seodiff.io/radar/domains/stadtausstellung.at" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=stadtausstellung.at" alt="AI-Verified by SEODiff" width="280" height="52"></a>

💡 Paste in your site footer, GitHub README, or email signature. Badge updates automatically as your score changes.

🔗 Similar saas Sites

Domains with a similar tech stack, industry, and AI readiness profile to stadtausstellung.at. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
stadtausstellung.at (this site) 7 10 Vue.js 1530.3× 0
k74app.com 21 15 Vue.js 91.8× 0 Compare →
365aceapp.com 21 15 Vue.js 123.0× 0 Compare →
cartx.cloud 26 57 Vue.js 6.8× 0 Compare →
hihonorcloud.com 27 15 Vue.js 12.6× 0 Compare →
gbetmax.app 27 62 Vue.js 79.6× 0 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to stadtausstellung.at. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Add Organization JSON-LD
High Impact ⏱ 5 min
AI models cannot identify your brand entity without Organization schema. This is the #1 fix for AI visibility.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Stadtausstellung",
  "url": "https://stadtausstellung.at",
  "logo": "https://assets.sta.io/site_media/f:fixed=ffffff,32x32/u/si/2020/05/06/android-chrome-512x512.png",
  "sameAs": []
}
</script>
Add WebSite + SearchAction JSON-LD
High Impact ⏱ 5 min
Enables the Sitelinks Search Box in Google and allows AI to understand your site structure.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Stadtausstellung",
  "url": "https://stadtausstellung.at",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://stadtausstellung.at/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Fix Client-Side Rendering
High Impact ⏱ 2–4 hrs
80% of your content is invisible to AI crawlers. Wrap critical content in server-rendered HTML using Vue.js (switch to Nuxt.js or use vue-server-renderer).
html
<!-- Ensure main content is in the initial HTML response -->
<main id="content">
  <!-- Server-rendered content goes here -->
  <h1>Stadtausstellung</h1>
  <p>Your key content should render without JavaScript.</p>
  <!-- Move <script> tags to the bottom of <body> -->
</main>

<!-- In your framework config, enable SSR/prerendering: -->
<!-- Vue.js (switch to Nuxt.js or use vue-server-renderer) -->
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 0% of your HTML is useful content. AI crawlers waste context window tokens on bloat.
html
<!-- Move inline CSS to external stylesheets -->
<link rel="stylesheet" href="/css/main.css">

<!-- Move inline scripts to external files with defer -->
<script src="/js/app.js" defer></script>

<!-- Remove duplicate navigation blocks -->
<!-- Keep only ONE <nav> in the <header> -->

<!-- Ensure <main> wraps your primary content -->
<main>
  <!-- Your content here — this is what AI sees first -->
</main>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for stadtausstellung.at:

Current Score
10
Projected Score
35
Improvement
+25 pts
Add Organization schema +6 pts
Add WebSite schema +4 pts
Fix client-side rendering +10 pts
Reduce token bloat +5 pts

*Estimates based on SEODiff's scoring model. Actual results depend on implementation quality.

📋 Data Export

Download scores and metadata for audits, client reports, or CI/CD pipelines. Exports contain computed metrics only (no copyrighted content).

All data is generated automatically and updated with each crawl. JSON exports contain scores and metadata only (no copyrighted content).

Is this your company?

Monitor your AI visibility score weekly and get alerted when changes happen.

Start Free →

🧭 Self-Diffing (Private Layer)

For owned domains, combine this world snapshot with private drift + regression history.
Template Drift
Track in My Site
Drift → Traffic Impact
In development coming soon
Regression Incidents
Track in My Site
Internal Linking
Deep Audit graph
Semantic Structure
GEO view in Deep Audit
Content Quality
Thin/duplicate tracking

🕒 History

Score over timeAvailable in My Site history
Drift eventsTemplate timeline + incidents
Drift → Revenue AttributionComing soon
Schema/rendering/extractability changesTracked per scan in project history