finans.dk 43 D
🛡️ SEO 25 🤖 GEO 47 ⚡ Perf 34 🏗️ Arch 71

finans.dk — Global SEODiff Score 43/100

finans.dk
📊

At 46/100, finans.dk falls in the moderate bracket of AI-Readiness, suggesting its content is partially accessible to AI systems but not fully optimized. Within the infrastructure vertical, this places finans.dk below the industry average of 57 —, indicating room for competitive improvement. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. Heavy markup overhead (50.0× bloat) forces AI systems to wade through excess code before finding useful information. The complete absence of JSON-LD schema is a missed opportunity: even basic Organization markup would improve how AI crawlers understand this domain. Most AI crawlers are blocked by robots.txt, severely restricting how AI-powered search engines can index and surface this content.

43
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (25) needs urgent attention.
🎯 Top Fix: Reduce token bloat (97×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than finans.dk?
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)25 × 0.25 = 6.2
🤖 AI Readiness / GEO (40% weight)47 × 0.40 = 18.8
⚡ Performance (20% weight)34 × 0.20 = 6.8
🏗️ Architecture & Trust (15% weight)71 × 0.15 = 10.7
Weighted sum = 6.2 + 18.8 + 6.8 + 10.7
Global SEODiff Score = 43 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
40
Bot Access
avg 92
99
Rendering
avg 93
13
Structure
avg 35
0
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 10%
Rank #98900
+46 pts
Gap
AI (ACRI)
Top 55%
Score 46/100

finans.dk 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 finans.dk ranks here

Tech stackNext.js
RenderingSSR
Schema coverage0 blocks
Token bloat50×+

Fastest improvements

  • Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
  • 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…
🛡️

Traditional SEO

25/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

65 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

159 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://finans.dk
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → da
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Finans - Seneste nyheder - Nyt fra erhvervslivet - Nyhedsoverblik
  • ✓ og:description — Danmarks største digitale erhvervsmedie. Seneste overblik over dagens mest aktuelle danske og internationale nyheder om erhverv, finans samt aktier og kurser.
  • ✓ og:image — preview
  • ✓ twitter:card — summary_large_image
📐 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

47/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 infrastructure sector, safely.co.jp (ACRI: 90) 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 →
finans.dk
26
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. safely.co.jp has schema coverage of 3 blocks and uses WordPress. 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.

Analyzing hallucination risk…

🤖 Bot Access Matrix

GPTBot (OpenAI)
Blocked
ClaudeBot (Anthropic)
Allowed
CCBot (Common Crawl)
Blocked
Google-Extended
Blocked
Googlebot
Allowed
💡GPTBot is blocked. To appear in ChatGPT citations, add Allow: / under User-agent: GPTBot in your robots.txt.

👻 Rendering (Ghost Ratio) Docs

Ghost Ratio 5%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 13/100 — Poor
Structured Elements 4 elements (4 lists, 0 rows, 0 headers)
Total Words779
Raw Density0.5%
💡Low structure score (13/100). Your content appears as a wall of text with few structured HTML elements. You have 4 list items, 0 table rows, 0 table headers. Convert features into <ul> lists and data into <table> elements to help AI models extract structured information.

🏷️ 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

30
AI Extractability
High
Crawl Cost
High
Blocklist Risk
Extractability30/100 — AI models can barely extract answers from this page
Crawl CostHigh (100/100) — expensive for AI crawlers to process
Blocklist RiskHigh — 3 of 5 AI crawlers blocked

Token Bloat Research

1%
🗑️ 99%
Useful Content (5.5 KB)Bloat (529.6 KB)
Token Bloat Ratio50×+ — Bloated

Multimodal Readiness

Visual Context28% Optimized for Vision
Image Alt Coverage9 / 32 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 535.1 KB, but only 5.5 KB 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.
💡Only 28% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 99.0% · SNR: 0.01 · Signal: 1407 / Noise: 135579 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

FrameworkNext.js
AI-Readiness Score70/100
Server
CDN
HTTP Status200
Load Time1865 ms
Raw HTML Size535.1 KB
Visible Text Size5.5 KB

Performance & Speed

34/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1865 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1514
DOM nodes
535 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → notset
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

0
tracker scripts
0
third-party domains
0.0%
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

71/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://finans.dk/sitemapindex.xml
  • ✓ Googlebot allowed
  • ✗ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

148
internal links
18
external links
Good internal linking — helps crawlers discover content

🔒 Security & Trust

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

♿ Accessibility Signals

  • ✓ HTML lang attribute → da
  • ✓ 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 scores 26/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for finans.dk
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/finans.dk" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=finans.dk" 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 infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
finans.dk (this site) 26 46 Next.js 97.3× 0
backyard.ai 27 62 Next.js 97.3× 0 Compare →
mailim.com 28 62 Next.js 97.6× 0 Compare →
getiago.com 24 62 Next.js 96.5× 0 Compare →
vibecity.com 24 62 Next.js 96.0× 0 Compare →
vibecity.in 24 62 Next.js 96.0× 0 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to finans.dk. 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": "Finans",
  "url": "https://finans.dk",
  "logo": "https://finans.dk/static/finans.dk/favicon/apple-touch-icon.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": "Finans",
  "url": "https://finans.dk",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://finans.dk/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Allow GPTBot in robots.txt
High Impact ⏱ 2 min
GPTBot is blocked — your content cannot appear in ChatGPT citations. Add this to your robots.txt:
text
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 1% 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>
Add FAQ Schema
Medium Impact ⏱ 10 min
FAQ schema lets AI models directly extract Q&A pairs. This is the easiest way to get featured in AI responses.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Finans?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Finans does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Finans work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Finans."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for finans.dk:

Current Score
46
Projected Score
72
Improvement
+26 pts
Allow GPTBot +8 pts
Add Organization schema +6 pts
Add WebSite schema +4 pts
Reduce token bloat +5 pts
Add FAQ schema +3 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