kaishi-pu.ac.jp 69 C
🛡️ SEO 59 🤖 GEO 84 ⚡ Perf 47 🏗️ Arch 75

kaishi-pu.ac.jp — Global SEODiff Score 69/100

kaishi-pu.ac.jp
📊

At 80/100, the ACRI for kaishi-pu.ac.jp indicates strong fundamentals in AI extractability, surpassing the majority of indexed sites. In the infrastructure sector, kaishi-pu.ac.jp outperforms the average (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. The token bloat ratio sits at a lean 2.3×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. Only 1 schema block is present — adding Organization, WebSite, and Breadcrumb schemas would significantly improve structured data coverage. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

69
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (47) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 21, 2026 · 📋 API
📈 ACRI Trend 7 snapshots
Feb 27 Mar 21
🔔 Recent AI Indexing Activity
🔄 Mar 21 Content change detected
📈 Mar 18 ACRI +2 (65→67)
🔄 Mar 15 Content change detected
📉 Mar 10 ACRI -1 (66→65)
🔄 Feb 27 Content change detected
Does your site score higher than kaishi-pu.ac.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)59 × 0.25 = 14.8
🤖 AI Readiness / GEO (40% weight)84 × 0.40 = 33.6
⚡ Performance (20% weight)47 × 0.20 = 9.4
🏗️ Architecture & Trust (15% weight)75 × 0.15 = 11.2
Weighted sum = 14.8 + 33.6 + 9.4 + 11.2
Global SEODiff Score = 69 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
49
Structure
avg 35
42
Schema
avg 9
85
Tech Stack
avg 63

Why kaishi-pu.ac.jp ranks here

Tech stackWordPress
RenderingSSR
Schema coverage1 blocks
Token bloat2.3×

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

59/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

135 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

0 chars
Missing

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://kaishi-pu.ac.jp/
  • ✓ 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 — 【公式】開志専門職大学|ビジネス・起業・IoT・データサイエンス・アニメ・マンガのプロになる。【公式】開志専門職大学|ビジネス・起業・IoT・データサイエンス・アニメ・マンガのプロになる。
  • ✓ og:description — 成長分野のプロフェッショナル人材を育成する総合専門職大学。経営・経済・マーケティング・商品開発の最先端ビジネスを学ぶ事業創造学部、AI・IoT・データサイエンス・ゲーム開発の最先端技術を学ぶ情報学部、アニメ・マンガ・キャラクターデザインを制作・研究し、ビジネスへの展開を学ぶアニメ・マンガ学部の3学部を設置。
  • ✓ og:image — preview
  • ✗ twitter:card
📐 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

84/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 →
kaishi-pu.ac.jp
67
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 49/100 — Fair
Structured Elements 170 elements (170 lists, 0 rows, 0 headers)
Total Words2333
Raw Density7.3%

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

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

43%
🗑️ 57%
Useful Content (74.2 KB)Bloat (96.2 KB)
Token Bloat Ratio2.3× — Lean

Multimodal Readiness

Visual Context51% Optimized for Vision
Image Alt Coverage36 / 70 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

68 Entropy
Fair Token Bloat: Medium
Noise Ratio: 56.4% · SNR: 0.77 · Signal: 18995 / Noise: 24619 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 Time1510 ms
Raw HTML Size170.4 KB
Visible Text Size74.2 KB

Performance & Speed

47/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1510 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1102
DOM nodes
170 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

3
tracker scripts
1
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
googletagmanager.com
📐 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

75/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
kaishi-pu.ac.jp (this site) 67 80 WordPress 2.3× 1
driphydration.com 86 95 WordPress 1.9× 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 90 WordPress 3.1× 5 Compare →
hupishop.com.br 87 92 WordPress 2.4× 23 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for kaishi-pu.ac.jp:

Current Score
80
Projected Score
83
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 →