kappasushi.jp 66 C
🛡️ SEO 71 🤖 GEO 63 ⚡ Perf 55 🏗️ Arch 81

kappasushi.jp — Global SEODiff Score 66/100

kappasushi.jp
📊

kappasushi.jp has earned a 90/100 ACRI — a tier-1 result that puts it ahead of 99% of sites in the SEODiff Radar. Compared to other infrastructure sites (avg score: 57), kappasushi.jp performs above the benchmark, 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. A 9.5× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. Minimal structured data (1 block) limits the site's ability to communicate entity relationships to AI systems. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

66
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (55) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than kappasushi.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)71 × 0.25 = 17.8
🤖 AI Readiness / GEO (40% weight)63 × 0.40 = 25.2
⚡ Performance (20% weight)55 × 0.20 = 11.0
🏗️ Architecture & Trust (15% weight)81 × 0.15 = 12.2
Weighted sum = 17.8 + 25.2 + 11.0 + 12.2
Global SEODiff Score = 66 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
100
Structure
avg 35
42
Schema
avg 10
85
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 8%
Rank #79623
-6 pts
Gap
AI (ACRI)
Top 1%
Score 90/100

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

Tech stackWordPress
RenderingSSR
Schema coverage1 blocks
Token bloat9.5×

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

71/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

30 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

276 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — かっぱ寿司 | 回転寿司
  • ✓ 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

63/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 →
kappasushi.jp
63
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 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 50 elements (50 lists, 0 rows, 0 headers)
Total Words66
Raw Density75.8%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks1 block(s) — Basic (low value for AI)

Schema Coverage Map

3/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.
💡FAQ schema missing. Adding FAQPage schema lets AI models directly extract Q&A pairs for Featured Snippets and chatbot answers.

📐 AI Efficiency Metrics Docs

76
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability76/100 — AI models can easily extract answers from this page
Crawl CostLow (10/100) — efficient for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

10%
🗑️ 90%
Useful Content (4.4 KB)Bloat (37.4 KB)
Token Bloat Ratio9.5× — Normal

Multimodal Readiness

Visual Context89% Optimized for Vision
Image Alt Coverage50 / 56 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 89.5% · SNR: 0.12 · Signal: 1125 / Noise: 9578 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

FrameworkWordPress
AI-Readiness Score85/100
ServerApache
CDN
HTTP Status200
Load Time2841 ms
Raw HTML Size41.8 KB
Visible Text Size4.4 KB

Performance & Speed

55/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2841 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

358
DOM nodes
42 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✗ 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

81/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.kappasushi.jp/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

� Deep Crawl Analysis 1 pages · Deep-10

Homepage ACRI
63
Single-page score
-16
Moderate hidden bloat
Δ delta
Site-Wide ACRI
47
Avg across 1 pages · Range 47–47
🔍
Hidden Bloat Detected

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

Total Words
114
Avg Bloat
56.5×
Ext. Citations
1
Page Type ACRI Token Bloat Words Status
https://kappasushi.jp/contact
ご意見フォーム | かっぱ寿司 | 回転寿司
pricing 47 56.5× 114 💰 Pricing
🔗
Outbound External Citations
1 unique external domains cited across 1 pages
kappa-create.co.jp ×1
🔄 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/kappasushi.jp

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
kappasushi.jp (this site) 63 90 WordPress 9.5× 1
cscmonavenir.ca 63 76 WordPress 9.5× 1 Compare →
crashplan.com 63 76 WordPress 9.5× 1 Compare →
schlagerradio.de 63 81 WordPress 9.5× 1 Compare →
jacboardsolutions.com 63 76 WordPress 9.5× 1 Compare →
torontoguardian.com 63 79 WordPress 9.5× 1 Compare →
Compare All 5 Similar Sites →
📈

Projected Impact

ROI EST.

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

Current Score
90
Projected Score
93
Improvement
+3 pts
Reduce token bloat +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