kc-i.jp 73 B
🛡️ SEO 58 🤖 GEO 88 ⚡ Perf 65 🏗️ Arch 69

kc-i.jp — Global SEODiff Score 73/100

kc-i.jp
📊

kc-i.jp demonstrates elite AI-Readiness, achieving an ACRI of 86/100 — placing it in the top 99% of all indexed domains. 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 4.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. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

73
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (58) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 15, 2026 · 📋 API
Does your site score higher than kc-i.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)58 × 0.25 = 14.5
🤖 AI Readiness / GEO (40% weight)88 × 0.40 = 35.2
⚡ Performance (20% weight)65 × 0.20 = 13.0
🏗️ Architecture & Trust (15% weight)69 × 0.15 = 10.3
Weighted sum = 14.5 + 35.2 + 13.0 + 10.3
Global SEODiff Score = 73 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 35
42
Schema
avg 9
50
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%
Rank #499912
-48 pts
Gap
AI (ACRI)
Top 1%
Score 86/100

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

Tech stackCustom / Proprietary
Industry
RenderingSSR
Schema coverage1 blocks
Token bloat4.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

58/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

27 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

274 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✗ Canonical tag present
  • ✓ No noindex directive
  • ✗ Meta viewport set
  • ✓ HTML lang attribute → ja
  • ➖ Hreflang tags — N/A (single language site)
  • ✓ 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

88/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 209 elements (209 lists, 0 rows, 0 headers)
Total Words670
Raw Density31.2%

🏷️ Schema Health Docs

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

Schema Coverage Map

2/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.
💡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.

📐 AI Efficiency Metrics Docs

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

25%
🗑️ 75%
Useful Content (19.1 KB)Bloat (56.7 KB)
Token Bloat Ratio4.0× — Lean

Multimodal Readiness

Visual Context95% Optimized for Vision
Image Alt Coverage98 / 103 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

25 Entropy
Poor Token Bloat: High
Noise Ratio: 74.8% · SNR: 0.34 · Signal: 4881 / Noise: 14515 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

SEODiff AI analyzed the extracted content of kc-i.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
知的創造拠点
Target Audience
创意产业从业者
Pricing Model
⚠ SEMANTIC VOID
Analyzed by SEODiff AI · 2026-02-26

🔧 Tech Stack

AI-Readiness Score50/100
ServerApache
CDN
HTTP Status200
Load Time843 ms
Raw HTML Size75.8 KB
Visible Text Size19.1 KB

Performance & Speed

65/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

843 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1271
DOM nodes
76 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

69/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

Homepage ACRI
76
Single-page score
-19
Moderate hidden bloat
Δ delta
Site-Wide ACRI
58
Avg across 10 pages · Range 57–60
🔍
Hidden Bloat Detected

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

Total Words
3445
Avg Bloat
18.8×
Page Type ACRI Token Bloat Words Status
https://kc-i.jp/about
About Us|ナレッジキャピタル
about 60 24.5× 318
https://kc-i.jp/contact
サイトマップ|ナレッジキャピタル
support 60 23.0× 359
https://kc-i.jp/pricing
ナレッジキャピタル Not Found(404)
pricing 57 17.5× 346
https://kc-i.jp/products
ナレッジキャピタル Not Found(404)
product 57 17.5× 346
https://kc-i.jp/features
ナレッジキャピタル Not Found(404)
product 57 17.5× 346
https://kc-i.jp/blog
ナレッジキャピタル Not Found(404)
blog 57 17.5× 346
https://kc-i.jp/docs
ナレッジキャピタル Not Found(404)
docs 57 17.5× 346
https://kc-i.jp/case-studies
ナレッジキャピタル Not Found(404)
social-proof 57 17.5× 346
https://kc-i.jp/faq
ナレッジキャピタル Not Found(404)
support 57 17.5× 346
https://kc-i.jp/integrations
ナレッジキャピタル Not Found(404)
integrations 57 17.5× 346
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/contact/ 1 60 0% 23.0× High JS Bloat
/about/ 1 60 0% 24.5× High JS Bloat
/products/ 1 57 0% 17.5× High JS Bloat
/blog/ 1 57 0% 17.5× High JS Bloat
/docs/ 1 57 0% 17.5× High JS Bloat
/faq/ 1 57 0% 17.5× High JS Bloat
/integrations/ 1 57 0% 17.5× High JS Bloat
/pricing/ 1 57 0% 17.5× High JS Bloat
/features/ 1 57 0% 17.5× High JS Bloat
/case-studies/ 1 57 0% 17.5× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 10 pages
congre-cc.jp ×10
grandfront-osaka.jp ×10
instagram.com ×10
gfo-sc.jp ×10
kc-space.jp ×10
youtube.com ×10
twitter.com ×10
facebook.com ×10
🔄 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/kc-i.jp

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

🔗 Similar Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
kc-i.jp (this site) 76 86 Custom / Proprietary 4.0× 1
thycotic.com 86 87 Custom / Proprietary 2.0× 3 Compare →
thycotic.net 86 87 Custom / Proprietary 2.0× 3 Compare →
hairdresserfind.com.au 86 87 Custom / Proprietary 4.9× 4 Compare →
kondela.hu 86 93 Custom / Proprietary 3.1× 4 Compare →
melbourneschool.com 86 87 Custom / Proprietary 5.0× 4 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

Projected Impact

ROI EST.

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

Current Score
86
Projected Score
89
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
🔍 Found indexing issues?
Run a free deep audit to diagnose crawled-not-indexed, soft 404s, redirect errors, and more.
Free Deep Audit → GSC Error Guide →