smahospital.jp 68 C
🛡️ SEO 63 🤖 GEO 91 ⚡ Perf 33 🏗️ Arch 61

smahospital.jp — Global SEODiff Score 68/100

smahospital.jp
📊

Among all indexed domains, smahospital.jp ranks in the top echelon with an ACRI of 88, demonstrating that its content is highly visible to AI systems. In the saas sector, smahospital.jp outperforms the average (57), suggesting strong competitive positioning in AI search. The low ghost ratio (5%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. The token bloat ratio sits at a lean 2.0×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. Minimal structured data (1 block) limits the site's ability to communicate entity relationships to AI systems. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

68
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (33) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 27, 2026 · 📋 API
Does your site score higher than smahospital.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)63 × 0.25 = 15.8
🤖 AI Readiness / GEO (40% weight)91 × 0.40 = 36.4
⚡ Performance (20% weight)33 × 0.20 = 6.6
🏗️ Architecture & Trust (15% weight)61 × 0.15 = 9.2
Weighted sum = 15.8 + 36.4 + 6.6 + 9.2
Global SEODiff Score = 68 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 36
42
Schema
avg 9
70
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 46%
Rank #455560
-44 pts
Gap
AI (ACRI)
Top 1%
Score 88/100

smahospital.jp ranks much higher on Google (Tranco Top 46%) than in AI search (Top 1%). This is the 'Visibility Gap' pattern — implementing the recommendations above can help close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why smahospital.jp ranks here

Tech stackNext.js
Industrysaas
RenderingSSR
Schema coverage1 blocks
Token bloat2.0×

Fastest improvements

  • You’re already in decent shape — the next moat is monitoring drift over time.
  • 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

63/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

104 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

259 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — スマホ・iPhone修理は「デジホ」ブランドのスマホスピタル【総務省登録修理業者】
  • ✓ og:description — iPhone修理・スマホ修理に関するご相談ならスマホスピタルにお任せ!即日修理最短15分。安心の保証付。画面割れやバッテリー交換、水没復旧修理など何でもご相談ください。
  • ✓ 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

91/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.

🚨

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 100/100 — Excellent
Structured Elements 361 elements (361 lists, 0 rows, 0 headers)
Total Words1143
Raw Density31.6%

🏷️ 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

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

50%
🗑️ 50%
Useful Content (240.2 KB)Bloat (241.1 KB)
Token Bloat Ratio2.0× — Lean

Multimodal Readiness

Visual Context49% Optimized for Vision
Image Alt Coverage35 / 71 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Only 49% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

75 Entropy
Good Token Bloat: Low
Noise Ratio: 50.1% · SNR: 1.00 · Signal: 61490 / Noise: 61732 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 smahospital.jp 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
Smartphone repair and replacement for iPhone and Android
Target Audience
Smartphone users needing repairs or replacements
Pricing Model
Not explicitly mentioned
🛡️ Compliance Standards
登録修理業者
Model: mlx-community/Qwen2.5-7B-Instruct-4bit · Analyzed: 2026-02-25 · Data extracted from the site’s main content via strict JSON prompting.

🔧 Tech Stack

FrameworkNext.js
AI-Readiness Score70/100
Servernginx
CDN
HTTP Status200
Load Time1025 ms
Raw HTML Size481.3 KB
Visible Text Size240.2 KB

Performance & Speed

33/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1025 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

3309
DOM nodes
481 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

61/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

  • ✗ Sitemap declared in robots.txt
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

474
internal links
87
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.

✓ TOP 15% AI-READY

🏆 You Are AI-Verified — Claim Your Badge

Your site scores 84/100 on the AI-Crawler Reality Index. Embed this trust badge on your site — every click sends visitors to your verified report and builds backlinks to your domain.

AI-Verified badge for smahospital.jp
Verified — updates automatically every 24h
<a href="https://seodiff.io/radar/domains/smahospital.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=smahospital.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.

How it works: The badge queries your ACRI score daily. If your score drops below 80 or your site hasn't been scanned in 30 days, the badge changes to "Pending Audit" (yellow) — prompting you to fix issues and rescan. Learn about ACRI methodology →

� Deep Crawl Analysis 2 pages · Deep-10

Homepage ACRI
84
Single-page score
-29
Severe hidden bloat
Δ delta
Site-Wide ACRI
56
Avg across 2 pages · Range 54–57
🔍
Hidden Bloat Detected

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

Total Words
610
Avg Bloat
177.9×
Page Type ACRI Token Bloat Words Status
https://smahospital.jp/faq
FAQ | スマホスピタル
support 57 148.0× 372
https://smahospital.jp/contact
お問い合わせ | スマホスピタル
support 54 207.9× 238
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/faq/ 1 57 0% 148.0× High JS Bloat
/contact/ 1 54 0% 207.9× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 2 pages
smahospital.co.jp ×2
4900.co.jp ×2
smahospital.xyz ×2
en-gage.net ×2
gamehospital.jp ×2
j-pcs.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/smahospital.jp

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

🔗 Similar saas Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
smahospital.jp (this site) 84 88 Next.js 2.0× 1
ma-cp.com 82 88 Next.js 4.1× 1 Compare →
golmicio.asahi.co.jp 79 88 Next.js 2.7× 2 Compare →
binder-connector.com 79 88 Next.js 3.1× 2 Compare →
bmbf.de 79 88 Next.js 5.1× 2 Compare →
haisha.kurumaerabi.com 78 89 Next.js 4.8× 3 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

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

Projected Impact

ROI EST.

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

Current Score
88
Projected Score
91
Improvement
+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