ecolines.by 55 D
🛡️ SEO 15 🤖 GEO 84 ⚡ Perf 40 🏗️ Arch 61

ecolines.by — Global SEODiff Score 55/100

ecolines.by
📊

At 83/100, the ACRI for ecolines.by indicates strong fundamentals in AI extractability, surpassing the majority of indexed sites. In the infrastructure sector, ecolines.by outperforms the average (57), suggesting strong competitive positioning in AI search. The low ghost ratio (0%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. With a 2.5× bloat ratio, the page delivers its content without excessive boilerplate, giving AI systems a clean extraction path. The site includes 2 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.

55
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (15) needs urgent attention.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than ecolines.by?
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)15 × 0.25 = 3.8
🤖 AI Readiness / GEO (40% weight)84 × 0.40 = 33.6
⚡ Performance (20% weight)40 × 0.20 = 8.0
🏗️ Architecture & Trust (15% weight)61 × 0.15 = 9.2
Weighted sum = 3.8 + 33.6 + 8.0 + 9.2
Global SEODiff Score = 55 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
72
Structure
avg 35
44
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #552146
-52 pts
Gap
AI (ACRI)
Top 3%
Score 83/100

ecolines.by ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 3%). This is the 'Invisible Giant' pattern — implement the patches above to close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why ecolines.by ranks here

Tech stackDrupal
RenderingSSR
Schema coverage2 blocks
Token bloat2.5×

Fastest improvements

  • You’re already in decent shape — the next moat is monitoring drift over time.
  • 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

15/100 25 % of Global Score 🟡 Medium Confidence

📝 Title Tag

95 chars
Too long

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 0
  • ✓ Has <h2> headings — found 19
  • ✗ <h2> not before <h1>

🔍 Indexability

  • ✗ Canonical tag present
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → ru
  • ✗ 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

84/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 →
ecolines.by
65
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)
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 72/100 — Good
Structured Elements 79 elements (79 lists, 0 rows, 0 headers)
Total Words509
Raw Density15.5%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks2 block(s) — Basic (low value for AI)

Schema Coverage Map

1/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.
💡WebSite schema missing. Add WebSite + SearchAction so Google can generate a Sitelinks Search Box for your brand in AI results.

📐 AI Efficiency Metrics Docs

78
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability78/100 — AI models can easily extract answers from this page
Crawl CostLow (30/100) — efficient for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

40%
🗑️ 60%
Useful Content (42.5 KB)Bloat (65.2 KB)
Token Bloat Ratio2.5× — Lean

Multimodal Readiness

Visual Context50% Optimized for Vision
Image Alt Coverage6 / 12 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

62 Entropy
Fair Token Bloat: Medium
Noise Ratio: 60.5% · SNR: 0.65 · Signal: 10881 / Noise: 16688 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

FrameworkDrupal
AI-Readiness Score70/100
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time2455 ms
Raw HTML Size107.7 KB
Visible Text Size42.5 KB

Performance & Speed

40/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2455 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

854
DOM nodes
108 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → public, max-age=0
  • ✓ CDN cache status → DYNAMIC
  • ✓ CDN detected → cloudflare

🔬 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

61/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

  • ✗ Sitemap declared in robots.txt
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

� Deep Crawl Analysis 10 pages · Deep-10

Homepage ACRI
65
Single-page score
-8
Moderate hidden bloat
Δ delta
Site-Wide ACRI
57
Avg across 10 pages · Range 57–57
Total Words
4090
Avg Bloat
53.9×
Ext. Citations
3
Page Type ACRI Token Bloat Words Status
https://ecolines.by/pricing
Автобусные билеты на международные перевозки | ECOLINES
pricing 57 53.9× 409
https://ecolines.by/about
Автобусные билеты на международные перевозки | ECOLINES
about 57 53.9× 409
https://ecolines.by/features
Автобусные билеты на международные перевозки | ECOLINES
product 57 53.9× 409
https://ecolines.by/products
Автобусные билеты на международные перевозки | ECOLINES
product 57 53.9× 409
https://ecolines.by/docs
Автобусные билеты на международные перевозки | ECOLINES
docs 57 53.9× 409
https://ecolines.by/blog
Автобусные билеты на международные перевозки | ECOLINES
blog 57 53.9× 409
https://ecolines.by/case-studies
Автобусные билеты на международные перевозки | ECOLINES
social-proof 57 53.9× 409
https://ecolines.by/integrations
Автобусные билеты на международные перевозки | ECOLINES
integrations 57 53.9× 409
https://ecolines.by/faq
Автобусные билеты на международные перевозки | ECOLINES
support 57 53.9× 409
https://ecolines.by/contact
Автобусные билеты на международные перевозки | ECOLINES
support 57 53.9× 409
🔗
Outbound External Citations
3 unique external domains cited across 10 pages
itunes.apple.com ×10
play.google.com ×10
ecolines.net ×10
🔄 Re-Crawl & Update 📡 Track this Domain

Scores update automatically each month. Create a free account for on-demand re-crawls (3/month free).

🔌 API Access

Pull this data programmatically. All sub-page metrics are available via our public API.

curl https://seodiff.io/api/v1/deep10/domain/ecolines.by

Get your free API key — 100 requests/month included.

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
ecolines.by (this site) 65 83 Drupal 2.5× 2
snowsoftware.com 66 78 Drupal 2.7× 2 Compare →
flexera.com 66 78 Drupal 2.7× 2 Compare →
spot.io 66 78 Drupal 2.7× 2 Compare →
flexera.eu 66 78 Drupal 2.7× 2 Compare →
spotinst.com 66 78 Drupal 2.7× 2 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

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": "Ecolines",
  "url": "https://ecolines.by",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://ecolines.by/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
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 Ecolines?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Ecolines does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Ecolines work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Ecolines."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for ecolines.by:

Current Score
83
Projected Score
90
Improvement
+7 pts
Add WebSite schema +4 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