lorealparis.cz 66 C
🛡️ SEO 44 🤖 GEO 79 ⚡ Perf 47 🏗️ Arch 91

lorealparis.cz — Global SEODiff Score 66/100

lorealparis.cz
📊

The AI-Readiness profile for lorealparis.cz is strong: an ACRI of 77/100 places it ahead of 86% of domains in the index. In the infrastructure sector, lorealparis.cz outperforms the average (57), suggesting strong competitive positioning in AI search. While the majority of content is server-rendered, the 30% ghost ratio suggests some content remains invisible to static crawlers. A 5.4× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. Structured data coverage is solid at 2 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

66
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (44) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than lorealparis.cz?
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)44 × 0.25 = 11.0
🤖 AI Readiness / GEO (40% weight)79 × 0.40 = 31.6
⚡ Performance (20% weight)47 × 0.20 = 9.4
🏗️ Architecture & Trust (15% weight)91 × 0.15 = 13.7
Weighted sum = 11.0 + 31.6 + 9.4 + 13.7
Global SEODiff Score = 66 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
84
Rendering
avg 93
69
Structure
avg 35
44
Schema
avg 10
55
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #702541
-56 pts
Gap
AI (ACRI)
Top 14%
Score 77/100

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

Why lorealparis.cz ranks here

Tech stackVue.js
RenderingHybrid
Schema coverage2 blocks
Token bloat5.4×

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

44/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

91 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

180 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.lorealparis.cz
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → cs-CZ
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Dekorativní kosmetika, péče o pleť, péče pro muže a vlasová péče - L'Oréal Paris
  • ✓ og:description — Objevte na stránkách L'Oréal Paris dekorativní kosmetiku, péči o pleť, péči pro muže a vlasovou péči a prohlédněte si náš exkluzivní obsah v sekci Beauty Magazine.
  • ✗ og:image
  • ✓ 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

79/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 →
lorealparis.cz
67
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 5.4x 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 69/100 — Good
Structured Elements 146 elements (146 lists, 0 rows, 0 headers)
Total Words1012
Raw Density14.4%

🏷️ Schema Health Docs

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

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

71
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability71/100 — AI models can easily extract answers from this page
Crawl CostMedium (50/100) — moderate for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

18%
🗑️ 82%
Useful Content (46.0 KB)Bloat (200.5 KB)
Token Bloat Ratio5.4× — Normal

Multimodal Readiness

Visual Context91% Optimized for Vision
Image Alt Coverage29 / 32 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: 81.3% · SNR: 0.23 · Signal: 11783 / Noise: 51326 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
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time1092 ms
Raw HTML Size246.5 KB
Visible Text Size46.0 KB

Performance & Speed

47/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1092 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1104
DOM nodes
246 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → public, must-revalidate, max-age=600
  • ✓ CDN cache status → HIT
  • ✓ CDN detected → cloudflare

🔬 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

91/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

136
internal links
5
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 → cs-CZ
  • ✓ 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 67/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Homepage ACRI
67
Single-page score
-33
Severe hidden bloat
Δ delta
Site-Wide ACRI
34
Avg across 1 pages · Range 34–34
🔍
Hidden Bloat Detected

Homepage scores 67, but internal pages average only 34 — a -33-point gap. Blogs, docs, and legacy content are dragging down AI readability site-wide.

Total Words
3
Avg Bloat
24862.7×
RAG Fractures
1
Ext. Citations
4
⚠️
1 RAG-Chunking Fracture Detected

Poorly formatted tables or pricing grids on 1 page will be split incorrectly during RAG chunking, causing AI models to hallucinate prices and features.

Page Type ACRI Token Bloat Words Status
https://lorealparis.cz/products pricing 34 24862.7× 3 ⚠️ RAG Fracture
🔗
Outbound External Citations
4 unique external domains cited across 1 pages
loreal.com ×1
instagram.com ×1
youtube.com ×1
facebook.com ×1
🔄 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/lorealparis.cz

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
lorealparis.cz (this site) 67 77 Vue.js 5.4× 2
lorealparis.ro 68 78 Vue.js 5.2× 2 Compare →
lorealparis.gr 67 77 Vue.js 4.7× 2 Compare →
newtalk.tw 66 79 Vue.js 5.0× 2 Compare →
loreal-paris.hr 68 80 Vue.js 4.8× 2 Compare →
loreal-paris.nl 68 78 Vue.js 4.6× 2 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for lorealparis.cz:

Current Score
77
Projected Score
83
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