pbz.hr 67 C
🛡️ SEO 58 🤖 GEO 82 ⚡ Perf 24 🏗️ Arch 96

pbz.hr — Global SEODiff Score 67/100

pbz.hr
📊

With a solid 84/100 ACRI, pbz.hr is well-positioned for AI search — better than 98% of sites in the Radar. Within the infrastructure vertical, this places pbz.hr above the industry average of 57 —, suggesting strong competitive positioning in AI search. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. A 6.1× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. The site includes 3 schema blocks, providing adequate structured data for basic entity recognition. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

67
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (24) is your bottleneck.
🎯 Top Fix: Monitor weekly to catch regressions early
🔬 Automated SEODiff Assessment · Snapshot: Feb 24, 2026 · 📋 API
Does your site score higher than pbz.hr?
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)58 × 0.25 = 14.5
🤖 AI Readiness / GEO (40% weight)82 × 0.40 = 32.8
⚡ Performance (20% weight)24 × 0.20 = 4.8
🏗️ Architecture & Trust (15% weight)96 × 0.15 = 14.4
Weighted sum = 14.5 + 32.8 + 4.8 + 14.4
Global SEODiff Score = 67 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
75
Structure
avg 35
46
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 12%
Rank #124009
-10 pts
Gap
AI (ACRI)
Top 2%
Score 84/100

pbz.hr is more visible to Google than to AI models. There's room to improve AI discoverability to match your search reputation. ACRI measures technical crawler readiness. Read the methodology →

Why pbz.hr ranks here

Tech stackRuby on Rails
RenderingSSR
Schema coverage3 blocks
Token bloat6.1×

Fastest improvements

  • 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

58/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

14 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

125 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.pbz.hr/gradjani
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → hr
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✗ og:title
  • ✗ og:description
  • ✗ og:image
  • ✓ twitter:card — summary
📐 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

82/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, plodopitomnik-sad.ru (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 →
pbz.hr
73
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. plodopitomnik-sad.ru has schema coverage of 12 blocks and uses Express. 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)
Allowed
ClaudeBot (Anthropic)
Allowed
CCBot (Common Crawl)
Allowed
Google-Extended
Allowed
Googlebot
Allowed

👻 Rendering (Ghost Ratio) Docs

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

📊 Structure & Information Density Docs

Structure Grade 75/100 — Good
Structured Elements 953 elements (948 lists, 5 rows, 0 headers)
Total Words5586
Raw Density17.1%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks3 blocks

Schema Coverage Map

2/7 schema types detected
✅ Organization
❌ Product/Service
❌ Breadcrumb
❌ FAQ
❌ Article
✅ WebSite
💡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.

📐 AI Efficiency Metrics Docs

75
AI Extractability
High
Crawl Cost
None
Blocklist Risk
Extractability75/100 — AI models can easily extract answers from this page
Crawl CostHigh (70/100) — expensive for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

16%
🗑️ 84%
Useful Content (117.9 KB)Bloat (604.4 KB)
Token Bloat Ratio6.1× — Normal

Multimodal Readiness

Visual Context75% Optimized for Vision
Image Alt Coverage61 / 81 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 83.7% · SNR: 0.20 · Signal: 30194 / Noise: 154716 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

FrameworkRuby on Rails
AI-Readiness Score70/100
Server
CDN
HTTP Status200
Load Time1237 ms
Raw HTML Size722.3 KB
Visible Text Size117.9 KB

Performance & Speed

24/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1237 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

5361
DOM nodes
722 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → no-cache, no-store, must-revalidate, max-age=0
  • ✗ 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

96/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.pbz.hr/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

1030
internal links
15
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 → hr
  • ✓ 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 73/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
pbz.hr (this site) 73 84 Ruby on Rails 6.1× 3
intesasanpaolobank.si 73 85 Ruby on Rails 6.4× 3 Compare →
intesasanpaolobank.ro 72 84 Ruby on Rails 6.9× 3 Compare →
vub.sk 75 87 Ruby on Rails 6.6× 3 Compare →
cib.hu 77 87 Ruby on Rails 6.4× 3 Compare →
adameve.com 74 85 Ruby on Rails 6.3× 2 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

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 Pbz?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Pbz does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Pbz work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Pbz."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for pbz.hr:

Current Score
84
Projected Score
90
Improvement
+6 pts
Reduce token bloat +3 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