latuaspesa.com 44 D
🛡️ SEO 57 🤖 GEO 37 ⚡ Perf 21 🏗️ Arch 70

latuaspesa.com — Global SEODiff Score 44/100

latuaspesa.com
📊

latuaspesa.com achieves a 66/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. Within the infrastructure vertical, this places latuaspesa.com above the industry average of 57 —, suggesting strong competitive positioning in AI search. A ghost ratio of 30% indicates a mixed rendering strategy where core content loads server-side but interactive sections rely on JavaScript. A 26.3× token bloat ratio means crawlers must process significantly more tokens to reach the actual content — a drag on extraction efficiency. Minimal structured data (1 block) limits the site's ability to communicate entity relationships to AI systems. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

44
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Performance (21) has the most room for improvement.
🎯 Top Fix: Reduce token bloat (26×) → +5–10 pts
⚠️ Crawl Blocked: Anti-bot protection detected (WAF/CAPTCHA)
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than latuaspesa.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)37 × 0.40 = 14.8
⚡ Performance (20% weight)21 × 0.20 = 4.2
🏗️ Architecture & Trust (15% weight)70 × 0.15 = 10.5
Weighted sum = 14.2 + 14.8 + 4.2 + 10.5
Global SEODiff Score = 44 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
84
Rendering
avg 93
15
Structure
avg 36
42
Schema
avg 9
55
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #519627
-8 pts
Gap
AI (ACRI)
Top 43%
Score 66/100

latuaspesa.com 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 latuaspesa.com ranks here

Tech stackVue.js
RenderingHybrid
Schema coverage1 blocks
Token bloat26.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…

⚠️ Crawl Failed: Anti-Bot Protection Detected

Anti-bot protection detected (WAF/CAPTCHA)

The scores below may not reflect actual site quality. The crawler received a challenge page instead of real content.

🛡️

Traditional SEO

57/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

50 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

177 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.latuaspesa.com/home-2022
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → it
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — La Tua Spesa.com
  • ✗ og:description
  • ✓ 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

37/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 →
latuaspesa.com
21
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 in non-rendered regions (JavaScript-dependent content that AI crawlers may not process). Combined with 26.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 15/100 — Poor
Structured Elements 16 elements (16 lists, 0 rows, 0 headers)
Total Words2447
Raw Density0.6%
💡Low structure score (15/100). Your content appears as a wall of text with few structured HTML elements. You have 16 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 ✅ 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

40
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability40/100 — AI models can partially extract answers from this page
Crawl CostMedium (60/100) — moderate for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

3%
🗑️ 97%
Useful Content (16.4 KB)Bloat (414.1 KB)
Token Bloat Ratio26.3× — Heavy

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage79 / 79 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 430.5 KB, but only 16.4 KB is text. 3% useful / 97% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (26.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.2% · SNR: 0.04 · Signal: 4194 / Noise: 106019 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
ServerApache/2.4.54 (Ubuntu)
CDN
HTTP Status200
Load Time3071 ms
Raw HTML Size430.5 KB
Visible Text Size16.4 KB

Performance & Speed

21/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

3071 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

3782
DOM nodes
430 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → max-age=7200
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

2
tracker scripts
1
third-party domains
1.9%
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

70/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

165
internal links
30
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 → it
  • ✓ 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 is currently blocking AI crawlers. Unblock them and rescan to earn your AI-Verified badge.

AI-Verified badge for latuaspesa.com
Unverified — crawl access is blocked
<a href="https://seodiff.io/radar/domains/latuaspesa.com" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=latuaspesa.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 latuaspesa.com. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
latuaspesa.com (this site) 21 66 Vue.js 26.3× 1
odrescred.com.br 46 79 WordPress 27.4× 1 Compare →
seisiaholidaypark.com 46 74 WordPress 29.7× 1 Compare →
sunbasedata.com 46 67 Custom / Proprietary 22.5× 0 Compare →
dreamhouse.com.gr 46 15 Cloudflare Pages 28.5× 3 Compare →
timeforit.se 46 72 WordPress 33.4× 1 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite latuaspesa.com when users ask about topics in this domain's niche? We run entity queries through our 188k-page search index and measure citation probability.

Analyzing citation landscape…

🩹

Remediation Patches

COPY-PASTE

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

Projected Impact

ROI EST.

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

Current Score
66
Projected Score
78
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