The AI-Readiness profile for minkabu.jp is strong: an ACRI of 78/100 places it ahead of 88% of domains in the index. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. The token bloat ratio sits at a lean 3.5×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. The site includes 2 schema blocks, providing adequate structured data for basic entity recognition. The site allows access to some AI bots but restricts others, creating an uneven visibility profile across AI-powered services.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
minkabu.jp shows stronger AI visibility than traditional SEO ranking. Great AI foundation to build on. ACRI measures technical crawler readiness. Read the methodology →
Why minkabu.jp ranks here
Fastest improvements
- Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
- Create an
llms.txtfile 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 →
Traditional SEO
55/100 25 % of Global Score 🟢 High Confidence📝 Title Tag
Optimal range: 30–60 characters for SERP display.
📋 Meta Description
Optimal range: 120–160 characters for snippet control.
🔤 Heading Hierarchy
- ✓ Exactly 1 <h1> tag — found 1
- ✓ Has <h2> headings — found 11
- ✓ <h2> not before <h1>
🔍 Indexability
- ✓ Canonical tag present →
https://minkabu.jp/ - ✓ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
ja - ✗ Hreflang tags
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✓ og:title — みんかぶ - 資産形成のための情報メディア・株価予想・ニュース・SNS
- ✓ og:description — みんなの売買予想、予想株価がわかる資産形成のための情報メディアです。株価・チャート・ニュース・株主優待・IPO情報等の企業情報に加えSNS機能も提供しています。『証券アナリストの予想』『株価診断』『個人投資家の株価予想』これらを総合的に算出した目標株価を掲載。『ブログ』で個人投資家同士の意見交換や情報収集をしたり、売買シミュレーションができる『株価予想』機能も、無料でご利用いただけます。
- ✓ 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
88/100 40 % of Global Score 🟢 High ConfidenceThis pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.
Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.
🤖 Bot Access Matrix
Allow: / under User-agent: GPTBot in your robots.txt.📊 Structure & Information Density Docs
🏷️ Schema Health Docs
Schema Coverage Map
📐 AI Efficiency Metrics Docs
Token Bloat Research
Multimodal Readiness
TDM Rights
🔥 Structural Entropy Check Research
🔬 AI-Crawler Simulation
See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
AI Answer Preview
NEWSee how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.
The LLM Interpretation
AI-VERIFIEDA local LLM (mlx-community/Qwen2.5-7B-Instruct-4bit) analyzed the extracted content of minkabu.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.
🔧 Tech Stack
Performance & Speed
39/100 20 % of Global Score 🟢 High Confidence⏱️ Time to First Byte
Google considers <200 ms "good". AI crawlers may have even shorter timeouts.
📦 Page Weight
DOM nodes
HTML payload
🗄️ Cache & CDN
- ✓ Cache-Control header →
max-age=0, private, must-revalidate - ✗ CDN cache status
- ✗ CDN detected
🔬 Tracker Tax
tracker scripts
third-party domains
token overhead
📐 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
87/100 15 % of Global Score 🟢 High Confidence🗺️ Sitemap & Robots
- ✓ Sitemap declared in robots.txt →
https://assets.minkabu.jp/concerns/sitemap/sitemap.xml.gz - ✓ Googlebot allowed
- ✗ GPTBot allowed
- ✓ ClaudeBot allowed
🔗 Linking
internal links
external links
🔒 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.
<a href="https://seodiff.io/radar/domains/minkabu.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=minkabu.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 Sites
Domains with a similar tech stack, industry, and AI readiness profile to minkabu.jp. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| minkabu.jp (this site) | 76 | 78 | WordPress | 3.5× | 2 | — |
| lnews.jp | 76 | 84 | WordPress | 3.5× | 2 | Compare → |
| at-bay.com | 76 | 88 | WordPress | 3.6× | 2 | Compare → |
| aossms.com | 76 | 83 | WordPress | 3.3× | 2 | Compare → |
| bythim.ru | 76 | 86 | WordPress | 3.3× | 2 | Compare → |
| grantthornton.pl | 76 | 85 | WordPress | 3.2× | 2 | Compare → |
Remediation Patches
COPY-PASTEAuto-generated code fixes tailored to minkabu.jp. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Minkabu",
"url": "https://minkabu.jp",
"logo": "https://minkabu.jp/favicon.ico",
"sameAs": []
}
</script>
User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: /
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Minkabu?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Minkabu does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Minkabu work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Minkabu."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for minkabu.jp:
*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 →