diariocorreo.pe 52 D
🛡️ SEO 30 🤖 GEO 56 ⚡ Perf 42 🏗️ Arch 88

diariocorreo.pe — Global SEODiff Score 52/100

diariocorreo.pe
📊

diariocorreo.pe shows strong AI visibility with an ACRI of 69/100, outperforming 65% of indexed domains. Within the developer vertical, this places diariocorreo.pe above the industry average of 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. The bloated 50.0× token ratio highlights an urgent need to clean up non-content markup, scripts, and navigation clutter. Structured data coverage is solid at 2 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

52
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (30) needs urgent attention.
🎯 Top Fix: Reduce token bloat (81×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than diariocorreo.pe?
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)30 × 0.25 = 7.5
🤖 AI Readiness / GEO (40% weight)56 × 0.40 = 22.4
⚡ Performance (20% weight)42 × 0.20 = 8.4
🏗️ Architecture & Trust (15% weight)88 × 0.15 = 13.2
Weighted sum = 7.5 + 22.4 + 8.4 + 13.2
Global SEODiff Score = 52 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
84
Rendering
avg 93
30
Structure
avg 35
44
Schema
avg 10
50
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 4%
Rank #44432
+31 pts
Gap
AI (ACRI)
Top 35%
Score 69/100

diariocorreo.pe punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →

Why diariocorreo.pe ranks here

Tech stackCustom / Proprietary
Industrydeveloper
RenderingHybrid
Schema coverage2 blocks
Token bloat50×+

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

30/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

127 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

204 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://diariocorreo.pe/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → es
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Noticias del Perú y el mundo | Lima y Regiones del Perú | Dina Boluarte | Congreso de la República | Espectáculos | CORREO
  • ✓ og:description — Últimas noticias del Perú y el mundo en diariocorreo.pe | Noticias de Arequipa, Cusco, Chimbote, Ica. La Libertad, Lambayeque, Lima, Huancayo, Huánuco, Piura, Tacna y Tumbes | Tendencias y espectáculo
  • ✓ 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

56/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 developer sector, hikkoshizamurai.jp (ACRI: 88) 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 →
diariocorreo.pe
48
Your ACRI Score
88
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. hikkoshizamurai.jp has schema coverage of 5 blocks and uses Custom / Proprietary. 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 81.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 30/100 — Low
Structured Elements 36 elements (36 lists, 0 rows, 0 headers)
Total Words1318
Raw Density2.7%
💡Low structure score (30/100). Your content appears as a wall of text with few structured HTML elements. You have 36 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 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

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

Token Bloat Research

1%
🗑️ 99%
Useful Content (9.2 KB)Bloat (743.7 KB)
Token Bloat Ratio50×+ — Bloated

Multimodal Readiness

Visual Context91% Optimized for Vision
Image Alt Coverage61 / 67 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 752.9 KB, but only 9.2 KB is text. 1% useful / 99% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (50×+) 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: 98.8% · SNR: 0.01 · Signal: 2367 / Noise: 190383 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

AI-Readiness Score50/100
Serveropenresty
CDN
HTTP Status200
Load Time1229 ms
Raw HTML Size752.9 KB
Visible Text Size9.2 KB

Performance & Speed

42/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1229 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1317
DOM nodes
753 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → private, max-age=60
  • ✗ 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
doubleclick.net
📐 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

88/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://diariocorreo.pe/sitemap/?outputType=xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
diariocorreo.pe (this site) 48 69 Custom / Proprietary 81.4× 2
porschesouthorlando.com 47 71 Custom / Proprietary 80.6× 0 Compare →
bigotires.com 43 68 Custom / Proprietary 81.9× 1 Compare →
openfoodfacts.org 48 15 Custom / Proprietary 86.6× 2 Compare →
axlabs.com 41 70 Custom / Proprietary 79.4× 2 Compare →
axlabs.net 41 70 Custom / Proprietary 79.4× 2 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

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

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for diariocorreo.pe:

Current Score
69
Projected Score
77
Improvement
+8 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