mjh.nz 56 D
🛡️ SEO 43 🤖 GEO 60 ⚡ Perf 62 🏗️ Arch 60

mjh.nz — Global SEODiff Score 56/100

mjh.nz
📊

With a solid 84/100 ACRI, mjh.nz is well-positioned for AI search — better than 98% of sites in the Radar. Compared to other developer sites (avg score: 57), mjh.nz performs above the benchmark, suggesting strong competitive positioning in AI search. Its server-rendered architecture ensures AI crawlers receive complete HTML on first request, a key advantage for extractability. The bloated 32.8× token ratio highlights an urgent need to clean up non-content markup, scripts, and navigation clutter. The presence of 7 structured data blocks ensures search engines and AI agents can accurately classify and extract entities from the page. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

56
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (43) needs urgent attention.
🎯 Top Fix: Reduce token bloat (33×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than mjh.nz?
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)43 × 0.25 = 10.8
🤖 AI Readiness / GEO (40% weight)60 × 0.40 = 24.0
⚡ Performance (20% weight)62 × 0.20 = 12.4
🏗️ Architecture & Trust (15% weight)60 × 0.15 = 9.0
Weighted sum = 10.8 + 24.0 + 12.4 + 9.0
Global SEODiff Score = 56 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
100
Structure
avg 35
14
Schema
avg 10
65
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 23%
Rank #227425
-20 pts
Gap
AI (ACRI)
Top 2%
Score 84/100

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

Why mjh.nz ranks here

Tech stackBlogger
Industrydeveloper
RenderingSSR
Schema coverage7 blocks
Token bloat32.8×

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

43/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

12 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

0 chars
Missing

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — Matt Huisman
  • ✓ og:description — { created with code &amp; coffee }
  • ✓ og:image — preview
  • ✗ 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

60/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 →
mjh.nz
61
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.

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 0%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 100/100 — Excellent
Structured Elements 84 elements (84 lists, 0 rows, 0 headers)
Total Words266
Raw Density31.6%

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks7 blocks

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.
💡WebSite schema missing. Add WebSite + SearchAction so Google can generate a Sitelinks Search Box for your brand in AI results.

📐 AI Efficiency Metrics Docs

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

Token Bloat Research

3%
🗑️ 97%
Useful Content (3.4 KB)Bloat (109.7 KB)
Token Bloat Ratio32.8× — Bloated

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage7 / 7 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 113.1 KB, but only 3.4 KB is text. 3% useful / 97% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (32.8×) 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: 97.0% · SNR: 0.03 · Signal: 882 / Noise: 28077 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

FrameworkBlogger
AI-Readiness Score65/100
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time1232 ms
Raw HTML Size113.1 KB
Visible Text Size3.4 KB

Performance & Speed

62/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1232 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

661
DOM nodes
113 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → private, max-age=0
  • ✓ CDN cache status → DYNAMIC
  • ✓ 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

60/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → http://www.matthuisman.nz/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

0
internal links
108
external links
Very few internal links — crawlers may miss important pages

🔒 Security & Trust

  • ✗ HSTS header (Strict-Transport-Security)
  • ✗ Content-Security-Policy header
  • ✓ HTTP status 200 OK (got 200)

♿ Accessibility Signals

  • ✗ HTML lang attribute
  • ✓ 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 61/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
mjh.nz (this site) 61 84 Blogger 32.8× 7
car.blog.br 66 81 Blogger 30.7× 8 Compare →
ilmuguru.org 61 73 Blogger 29.5× 9 Compare →
pkgway.in 63 83 Blogger 26.7× 7 Compare →
educationblog24.com 63 75 Blogger 26.7× 7 Compare →
freefirenamestyle.com 68 76 Blogger 27.3× 6 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for mjh.nz:

Current Score
84
Projected Score
100
Improvement
+16 pts
Add Organization schema +6 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