tractebel-engie.com 62 C
🛡️ SEO 57 🤖 GEO 59 ⚡ Perf 47 🏗️ Arch 97

tractebel-engie.com — Global SEODiff Score 62/100

tractebel-engie.com
📊

tractebel-engie.com shows strong AI visibility with an ACRI of 74/100, outperforming 79% of indexed domains. Compared to other infrastructure sites (avg score: 57), tractebel-engie.com performs above the benchmark, suggesting strong competitive positioning in AI search. The rendering approach is hybrid, with a moderate ghost ratio of 30% — most content is accessible without JS, though some elements are client-rendered. Heavy markup overhead (31.3× bloat) forces AI systems to wade through excess code before finding useful information. Only 1 schema block is present — adding Organization, WebSite, and Breadcrumb schemas would significantly improve structured data coverage. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

62
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (47) is your bottleneck.
🎯 Top Fix: Reduce token bloat (31×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than tractebel-engie.com?
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)57 × 0.25 = 14.2
🤖 AI Readiness / GEO (40% weight)59 × 0.40 = 23.6
⚡ Performance (20% weight)47 × 0.20 = 9.4
🏗️ Architecture & Trust (15% weight)97 × 0.15 = 14.5
Weighted sum = 14.2 + 23.6 + 9.4 + 14.5
Global SEODiff Score = 62 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
84
Rendering
avg 93
58
Structure
avg 35
42
Schema
avg 10
55
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #660261
-45 pts
Gap
AI (ACRI)
Top 21%
Score 74/100

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

Why tractebel-engie.com ranks here

Tech stackVue.js
RenderingHybrid
Schema coverage1 blocks
Token bloat31.3×

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

57/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

47 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

189 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://tractebel-engie.com/en/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en
  • ✓ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Engineering a carbon-neutral future | Tractebel
  • ✓ og:description — Tractebel is a leading global engineering company delivering innovative solutions for energy, water, infrastructure, and sustainable development. Partner with us to shape a better tomorrow.
  • ✓ og:image — preview
  • ✓ 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

59/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 →
tractebel-engie.com
54
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.

👻
Shadow Content Detected: 30% of your page token budget is trapped in non-rendered regions (JavaScript-dependent content invisible to AI crawlers). Combined with 31.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 30%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type Hybrid

📊 Structure & Information Density Docs

Structure Grade 58/100 — Fair
Structured Elements 165 elements (165 lists, 0 rows, 0 headers)
Total Words1619
Raw Density10.2%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks1 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

52
AI Extractability
High
Crawl Cost
None
Blocklist Risk
Extractability52/100 — AI models can partially extract answers from this page
Crawl CostHigh (80/100) — expensive for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

3%
🗑️ 97%
Useful Content (10.3 KB)Bloat (310.8 KB)
Token Bloat Ratio31.3× — Bloated

Multimodal Readiness

Visual Context86% Optimized for Vision
Image Alt Coverage19 / 22 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 321.1 KB, but only 10.3 KB is text. 3% useful / 97% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (31.3×) 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: 96.8% · SNR: 0.03 · Signal: 2628 / Noise: 79571 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
Server
CDN
HTTP Status200
Load Time1352 ms
Raw HTML Size321.1 KB
Visible Text Size10.3 KB

Performance & Speed

47/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1352 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1429
DOM nodes
321 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → private, no-store, no-cache, max-age=0, s-maxage=0
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

1
tracker scripts
1
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
googletagmanager.com
📐 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

97/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://tractebel-engie.com/wp-sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
tractebel-engie.com (this site) 54 74 Vue.js 31.3× 1
unibroue.com 58 80 Vue.js 32.7× 1 Compare →
77577.com 52 71 Vue.js 30.2× 0 Compare →
vidangel.com 48 67 Vue.js 31.3× 0 Compare →
fmcloud.fm 49 72 Vue.js 29.8× 2 Compare →
stadtwerke-konstanz.de 57 76 Vue.js 27.1× 1 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to tractebel-engie.com. 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": "Tractebel-engie",
  "url": "https://tractebel-engie.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://tractebel-engie.com/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 3% 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 Tractebel-engie?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Tractebel-engie does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Tractebel-engie work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Tractebel-engie."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for tractebel-engie.com:

Current Score
74
Projected Score
86
Improvement
+12 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