batonz.jp 53 D
🛡️ SEO 35 🤖 GEO 61 ⚡ Perf 29 🏗️ Arch 91

batonz.jp — Global SEODiff Score 53/100

batonz.jp
📊

At 69/100, the ACRI for batonz.jp indicates strong fundamentals in AI extractability, surpassing the majority of indexed sites. Within the developer vertical, this places batonz.jp above the industry average of 57 —, 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. A 50.0× token bloat ratio means crawlers must process significantly more tokens to reach the actual content — a drag on extraction efficiency. Zero schema blocks puts this site at a disadvantage in knowledge graph and AI-answer pipelines that rely on explicit structured data. Some AI crawlers are permitted while others are blocked — a mixed robots.txt policy that limits visibility in certain AI ecosystems.

53
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Performance (29) needs urgent attention.
🎯 Top Fix: Reduce token bloat (65×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than batonz.jp?
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)35 × 0.25 = 8.8
🤖 AI Readiness / GEO (40% weight)61 × 0.40 = 24.4
⚡ Performance (20% weight)29 × 0.20 = 5.8
🏗️ Architecture & Trust (15% weight)91 × 0.15 = 13.7
Weighted sum = 8.8 + 24.4 + 5.8 + 13.7
Global SEODiff Score = 53 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
80
Bot Access
avg 92
99
Rendering
avg 93
65
Structure
avg 35
0
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 42%
Rank #416573
-7 pts
Gap
AI (ACRI)
Top 34%
Score 69/100

batonz.jp 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 batonz.jp ranks here

Tech stackNext.js
Industrydeveloper
RenderingSSR
Schema coverage0 blocks
Token bloat50×+

Fastest improvements

  • Allow ClaudeBot (many assistants rely on it) — blocking it often correlates with “AI invisibility.”
  • Add basic Organization and WebSite JSON-LD to fix “0 schema blocks” (see Schema Coverage).
  • 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

35/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

86 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

305 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✗ Canonical tag present
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → ja
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — M&AならBATONZ(バトンズ)| 国内最大級の成約支援実績|事業承継・M&AならBATONZ(バトンズ)
  • ✓ og:description — バトンズは、成約実績No.1の事業承継支援・M&Aマッチングプラットフォームです。累計4.1万件以上のM&A案件を掲載し、毎月約800件の新着M&A案件が登録されます。28万以上の買い手候補から平均10件以上のオファーを受けられます。
  • ✓ 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

61/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 →
batonz.jp
49
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)
Blocked
CCBot (Common Crawl)
Allowed
Google-Extended
Allowed
Googlebot
Allowed
💡ClaudeBot is blocked. To be cited by Claude, allow ClaudeBot in robots.txt.

👻 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 65/100 — Good
Structured Elements 79 elements (61 lists, 13 rows, 5 headers)
Total Words615
Raw Density12.9%

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks0 — No JSON-LD detected

Schema Coverage Map

0/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

46
AI Extractability
High
Crawl Cost
Low
Blocklist Risk
Extractability46/100 — AI models can partially extract answers from this page
Crawl CostHigh (95/100) — expensive for AI crawlers to process
Blocklist RiskLow — 1 of 5 AI crawlers blocked

Token Bloat Research

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

Multimodal Readiness

Visual Context89% Optimized for Vision
Image Alt Coverage135 / 152 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 1208.6 KB, but only 18.6 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.5% · SNR: 0.02 · Signal: 4774 / Noise: 304627 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

FrameworkNext.js
AI-Readiness Score70/100
Servernginx
CDN
HTTP Status200
Load Time3002 ms
Raw HTML Size1208.6 KB
Visible Text Size18.6 KB

Performance & Speed

29/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

3002 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1283
DOM nodes
1209 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → no-cache
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

0
tracker scripts
0
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
📐 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://batonz.jp/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✗ ClaudeBot allowed

🔗 Linking

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
batonz.jp (this site) 49 69 Next.js 64.8× 0
render.com 49 73 Next.js 64.9× 0 Compare →
onrender.com 49 73 Next.js 64.9× 0 Compare →
eurosportplayer.com 48 71 Next.js 64.9× 0 Compare →
tina.io 48 73 Next.js 65.4× 0 Compare →
meilisearch.com 47 71 Next.js 65.0× 0 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to batonz.jp. 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": "Batonz",
  "url": "https://batonz.jp",
  "logo": "https://batonz.jp/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": "Batonz",
  "url": "https://batonz.jp",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://batonz.jp/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Allow ClaudeBot in robots.txt
Medium Impact ⏱ 2 min
ClaudeBot is blocked — Claude cannot cite your content. Many AI assistants rely on it.
text
User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /
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 Batonz?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Batonz does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Batonz work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Batonz."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for batonz.jp:

Current Score
69
Projected Score
92
Improvement
+23 pts
Allow ClaudeBot +5 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