cocoromi-mental.jp 73 B
🛡️ SEO 57 🤖 GEO 86 ⚡ Perf 62 🏗️ Arch 80

cocoromi-mental.jp — Global SEODiff Score 73/100

cocoromi-mental.jp
📊

Among all indexed domains, cocoromi-mental.jp ranks in the top echelon with an ACRI of 90, demonstrating that its content is highly visible to AI systems. Within the infrastructure vertical, this places cocoromi-mental.jp above the industry average of 57 —, 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 5.6× token bloat ratio falls within the normal range, though there is room to trim navigation, footer, and script overhead. 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.

73
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (57) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 1, 2026 · 📋 API
📈 ACRI Trend 3 snapshots
Feb 23 Mar 1
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than cocoromi-mental.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)57 × 0.25 = 14.2
🤖 AI Readiness / GEO (40% weight)86 × 0.40 = 34.4
⚡ Performance (20% weight)62 × 0.20 = 12.4
🏗️ Architecture & Trust (15% weight)80 × 0.15 = 12.0
Weighted sum = 14.2 + 34.4 + 12.4 + 12.0
Global SEODiff Score = 73 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
100
Structure
avg 36
42
Schema
avg 9
85
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #761851
-75 pts
Gap
AI (ACRI)
Top 1%
Score 90/100

cocoromi-mental.jp ranks much higher on Google (Tranco Top 50%+) 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 cocoromi-mental.jp ranks here

Tech stackWordPress
RenderingSSR
Schema coverage1 blocks
Token bloat5.6×

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

57/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

158 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

356 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — 田町三田こころみクリニック 内科・心療内科・糖尿病内科・精神科【初診予約◎】|田町駅徒歩3分の駅近クリニック
  • ✓ og:description — 【内科・心療内科】芝浦方面、田町駅3分三田駅5分。内科は「血液」「糖尿病」に、心療内科・精神科は「豊富な治療選択肢」が強みのクリニック。地域医療連携◎→済生会中央病院・NTT東日本病院・慈恵医大・東邦大学大森病院と提携。お気軽にご相談ください。
  • ✗ og:image
  • ✓ 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

86/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, plodopitomnik-sad.ru (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 →
cocoromi-mental.jp
71
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. plodopitomnik-sad.ru has schema coverage of 12 blocks and uses Express. 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 102 elements (102 lists, 0 rows, 0 headers)
Total Words323
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

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

Token Bloat Research

17%
🗑️ 83%
Useful Content (9.9 KB)Bloat (45.1 KB)
Token Bloat Ratio5.6× — Normal

Multimodal Readiness

Visual Context82% Optimized for Vision
Image Alt Coverage32 / 39 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: 82.0% · SNR: 0.22 · Signal: 2538 / Noise: 11551 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
Servernginx
CDN
HTTP Status200
Load Time1252 ms
Raw HTML Size55.0 KB
Visible Text Size9.9 KB

Performance & Speed

62/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1252 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

660
DOM nodes
55 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

80/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://cocoromi-mental.jp/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

Homepage ACRI
71
Single-page score
-12
Moderate hidden bloat
Δ delta
Site-Wide ACRI
59
Avg across 3 pages · Range 57–60
🔍
Hidden Bloat Detected

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

Total Words
666
Avg Bloat
47.3×
Page Type ACRI Token Bloat Words Status
https://cocoromi-mental.jp/blog
ブログ - 田町三田こころみクリニック 内科・心療内科・糖尿病内科・精神科
blog 60 46.4× 215
https://cocoromi-mental.jp/contact
企業・法人・メディアの方へ - 田町三田こころみクリニック 内科・心療内科・糖尿病内科・精神科
support 60 47.7× 226
https://cocoromi-mental.jp/about
当院について - 田町三田こころみクリニック 内科・心療内科・糖尿病内科・精神科
about 57 47.7× 225
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/blog/ 1 60 0% 46.4× High JS Bloat
/contact/ 1 60 0% 47.7× High JS Bloat
/about/ 1 57 0% 47.7× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 3 pages
musashikosugi-cocoromi-cl.jp ×3
ipt-clinic.com ×3
ueno-okachimachi-cocoromi-cl.jp ×3
cocoromi-cl.jp ×3
island-cocoromi-cl.jp ×3
bellsleep.jp ×3
ebisukodomo.jp ×3
tokyo-yokohama-tms-cl.jp ×3
🔄 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/cocoromi-mental.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 cocoromi-mental.jp. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
cocoromi-mental.jp (this site) 71 90 WordPress 5.6× 1
profitserver.ru 86 90 WordPress 3.8× 2 Compare →
profitserver.net 86 90 WordPress 3.7× 2 Compare →
safely.co.jp 90 90 WordPress 1.9× 3 Compare →
hi-ad.jp 86 89 WordPress 3.0× 5 Compare →
meriambet.us.com 87 95 WordPress 4.1× 6 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

Projected Impact

ROI EST.

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

Current Score
90
Projected Score
96
Improvement
+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