alaskapublic.org 68 C
🛡️ SEO 50 🤖 GEO 87 ⚡ Perf 39 🏗️ Arch 85

alaskapublic.org — Global SEODiff Score 68/100

alaskapublic.org
📊

alaskapublic.org achieves a 78/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. Within the infrastructure vertical, this places alaskapublic.org above the industry average of 58 —, suggesting strong competitive positioning in AI search. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. The token bloat ratio sits at a lean 4.3×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual 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.

68
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (39) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
📈 ACRI Trend 3 snapshots
Feb 23 Feb 26
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than alaskapublic.org?
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)50 × 0.25 = 12.5
🤖 AI Readiness / GEO (40% weight)87 × 0.40 = 34.8
⚡ Performance (20% weight)39 × 0.20 = 7.8
🏗️ Architecture & Trust (15% weight)85 × 0.15 = 12.8
Weighted sum = 12.5 + 34.8 + 7.8 + 12.8
Global SEODiff Score = 68 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
89
Structure
avg 36
2
Schema
avg 9
55
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 5%
Rank #49803
+8 pts
Gap
AI (ACRI)
Top 12%
Score 78/100

alaskapublic.org shows stronger AI visibility than traditional SEO ranking. Great AI foundation to build on. ACRI measures technical crawler readiness. Read the methodology →

Why alaskapublic.org ranks here

Tech stackExpress
RenderingSSR
Schema coverage1 blocks
Token bloat4.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

50/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

19 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

137 chars
Good length

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://alaskapublic.org/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en
  • ✗ 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

87/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 →
alaskapublic.org
73
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 5%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 89/100 — Excellent
Structured Elements 318 elements (318 lists, 0 rows, 0 headers)
Total Words1325
Raw Density24.0%

🏷️ Schema Health Docs

Organization Schema ❌ Missing
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
💡Organization schema missing. AI models cannot identify your brand entity. Without it, your brand won't appear in Knowledge Panels or be associated with your content.
💡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

72
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability72/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

23%
🗑️ 77%
Useful Content (47.9 KB)Bloat (156.0 KB)
Token Bloat Ratio4.3× — Lean

Multimodal Readiness

Visual Context71% Optimized for Vision
Image Alt Coverage17 / 24 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

17 Entropy
Poor Token Bloat: High
Noise Ratio: 76.5% · SNR: 0.31 · Signal: 12264 / Noise: 39940 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…
🧠

The LLM Interpretation

AI-VERIFIED

A local LLM (mlx-community/Qwen2.5-7B-Instruct-4bit) analyzed the extracted content of alaskapublic.org and produced this structured business intelligence. Fields marked SEMANTIC VOID indicate information the AI could not find — a critical gap in your site’s machine-readability.

Core Offering
Provides radio, TV, and digital content to inform, educate, and connect Alaskans.
Target Audience
Alaskans, community organizations, PBS viewers, radio listeners, TV viewers
Pricing Model
Membership-based, with various support options
🏆 Competitive Moat
Unique role in informing and connecting a geographically diverse, remote population
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
Ways to WatchWays to ListenON DEMAND
⚡ Key Pain Points
• Limited technical SEO signals, no clear directory or location pages, no API documentation, no comparison pages, no glossary/dictionary pages
Model: mlx-community/Qwen2.5-7B-Instruct-4bit · Analyzed: 2026-02-27 · Data extracted from the site’s main content via strict JSON prompting.

🔧 Tech Stack

FrameworkExpress
AI-Readiness Score55/100
ServerN/A
CDN
HTTP Status200
Load Time1045 ms
Raw HTML Size203.9 KB
Visible Text Size47.9 KB

Performance & Speed

39/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1045 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1610
DOM nodes
204 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → max-age=300
  • ✗ 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

85/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://alaskapublic.org/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

344
internal links
29
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 73/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Homepage ACRI
73
Single-page score
-20
Moderate hidden bloat
Δ delta
Site-Wide ACRI
53
Avg across 70 pages · Range 44–72
🔍
Hidden Bloat Detected

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

Total Words
15032
Avg Bloat
172.4×
Page Type ACRI Token Bloat Words Status
https://alaskapublic.org/alaska-news-nightly/2007-06-27/alaska-news-nightly-june-26-2007
Alaska News Nightly: June 26, 2007
other 72 57.2× 511
https://alaskapublic.org/alaska-news-nightly/2007-06-26/alaska-news-nightly-2007-06-25
Alaska News Nightly: June 25, 2007
pricing 72 57.7× 508 💰 Pricing
https://alaskapublic.org/alaska-news-nightly/2007-06-05/alaska-news-nightly-june-5-2007
Alaska News Nightly: June 5, 2007
pricing 72 56.1× 533 💰 Pricing
https://alaskapublic.org/alaska-news-nightly/2007-06-23/alaska-news-nightly-2007-06-22
Alaska News Nightly: June 22, 2007
other 72 43.1× 684
https://alaskapublic.org/alaska-news-nightly/2007-06-09/alaska-news-nightly-2007-06-08
Alaska News Nightly: June 8, 2007
pricing 72 37.3× 795 💰 Pricing
https://alaskapublic.org/alaska-news-nightly/2007-06-21/alaska-news-nightly-2007-06-20
Alaska News Nightly: June 20, 2007
pricing 72 58.2× 503 💰 Pricing
https://alaskapublic.org/about
pricing 67 57.8× 512 💰 Pricing
https://alaskapublic.org/talk-of-alaska/2007-06-26/talk-of-alaska-national-parks-in-the-21st-century
Talk of Alaska: National Parks in the 21st Century
other 59 119.7× 248
https://alaskapublic.org/line-one/2007-05-21/line-one-pop-psychology
Line One: Pop Psychology
other 59 136.2× 217
https://alaskapublic.org/line-one/2007-05-07/line-one-adult-add-adhd
Line One: Adult ADD / ADHD
other 59 140.1× 211
https://alaskapublic.org/uncategorized/2007-05-09/community-forum-wev-shea
Community Forum: Wev Shea
other 59 122.8× 239
https://alaskapublic.org/uncategorized/2007-05-16/community-forum-ray-metcalfe
Community Forum: Ray Metcalfe
other 59 127.1× 231
https://alaskapublic.org/uncategorized/2007-05-31/community-forum-mike-doogan
Community Forum: Mike Doogan
other 59 113.6× 261
https://alaskapublic.org/uncategorized/2007-05-02/community-forum-gardening
Community Forum: Gardening
other 59 143.7× 204
https://alaskapublic.org/programs/2007-06-01/stage-talk-three-barons-faire
Stage Talk: Three Barons Fair
other 59 140.5× 207
https://alaskapublic.org/uncategorized/2007-06-06/community-forum-les-gara
Community Forum: Les Gara
other 59 143.0× 205
https://alaskapublic.org/programs/2007-06-08/stage-talk-atz-kilcher-jason-martin
Stage Talk: Atz Kilcher and Jason Martin
other 59 139.9× 208
https://alaskapublic.org/uncategorized/2007-06-20/community-forum-building-neighborhoods
Community Forum: Building Neighborhoods
other 59 113.0× 261
https://alaskapublic.org/programs/2007-06-22/stage-talk-hullabaloo-adored-you
Stage Talk: Hullabaloo, Adored You
other 59 130.5× 223
https://alaskapublic.org/line-one/2007-06-25/line-one-child-athletes
Line One: Senior and Disabilities Services
other 59 123.1× 241
Showing 20 of 70 pages. Unlock full subpage table →
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/news/ 34 49 0% 211.3× High JS Bloat
/programs/ 10 52 0% 163.4× High JS Bloat
/alaska-news-nightly/ 8 69 0% 55.7× High JS Bloat
/uncategorized/ 7 58 0% 130.7× High JS Bloat
/line-one/ 6 56 0% 162.2× High JS Bloat
/talk-of-alaska/ 2 54 0% 230.6× High JS Bloat
/2007-06-19/ 1 44 0% 186.4× High JS Bloat
/about/ 1 67 0% 57.8× High JS Bloat
/2007-06-21/ 1 44 0% 211.8× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 70 pages
bsky.app ×70
youtube.com ×70
pbskids.org ×70
lp.constantcontactpages.com ×70
alaskapublic.wedid.it ×70
video.alaskapublic.org ×70
instagram.com ×70
ktoo.org ×70
🔄 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/alaskapublic.org

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
alaskapublic.org (this site) 73 78 Express 4.3× 1
sigmaflows.com 88 93 Express 2.3× 1 Compare →
photopoint.ee 86 87 Express 1.1× 2 Compare →
tilibraexpress.com.br 87 87 Express 1.9× 3 Compare →
sos-ricambi.it 86 94 Express 2.6× 13 Compare →
sos-accessoire.com 86 93 Express 2.5× 13 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite alaskapublic.org 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 alaskapublic.org. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Add Organization JSON-LD
High Impact ⏱ 5 min
AI models cannot identify your brand entity without Organization schema. This is the #1 fix for AI visibility.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Alaskapublic",
  "url": "https://alaskapublic.org",
  "logo": "https://alaskapublic.org/apple-touch-icon.png",
  "sameAs": []
}
</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 Alaskapublic?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Alaskapublic does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Alaskapublic work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Alaskapublic."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for alaskapublic.org:

Current Score
78
Projected Score
90
Improvement
+12 pts
Add Organization schema +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