logmi.jp achieves a 73/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. Within the infrastructure vertical, this places logmi.jp above the industry average of 57 —, suggesting strong competitive positioning in AI search. A ghost ratio of 15% indicates a mixed rendering strategy where core content loads server-side but interactive sections rely on JavaScript. The 9.7× token bloat ratio falls within the normal range, though there is room to trim navigation, footer, and script overhead. Structured data coverage is solid at 2 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. Some AI crawlers are permitted while others are blocked — a mixed robots.txt policy that limits visibility in certain AI ecosystems.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
logmi.jp punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →
Why logmi.jp ranks here
Fastest improvements
- Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
- Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
- 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
48/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 2
- ✓ Has <h2> headings — found 9
- ✓ <h2> not before <h1>
🔍 Indexability
- ✓ Canonical tag present →
https://logmi.jp/ - ✓ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
ja - ✗ Hreflang tags
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✓ og:title — ログミーBusiness 学び続ける次世代リーダーのためのメディア
- ✓ 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
81/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.👻 Rendering (Ghost Ratio) Docs
📊 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/gemma-3-4b-it-qat-4bit) analyzed the extracted content of logmi.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
65/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=60, stale-while-revalidate=3600 - ✗ 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
86/100 15 % of Global Score 🟢 High Confidence🗺️ Sitemap & Robots
- ✓ Sitemap declared in robots.txt →
https://logmi.jp/sitemap.xml - ✓ 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 60/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/logmi.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=logmi.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 54 pages · Deep-10
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| product | 65 | 91.3× | 301 | ✓ | |
| product | 65 | 87.3× | 317 | ✓ | |
| product | 65 | 84.4× | 337 | ✓ | |
| product | 65 | 90.6× | 304 | ✓ | |
| product | 65 | 86.0× | 314 | ✓ | |
| product | 65 | 87.9× | 315 | ✓ | |
| product | 65 | 86.0× | 322 | ✓ | |
| product | 65 | 85.8× | 332 | ✓ | |
| product | 65 | 92.1× | 297 | ✓ | |
| product | 65 | 84.9× | 326 | ✓ | |
| product | 65 | 88.7× | 306 | ✓ | |
| product | 65 | 87.9× | 314 | ✓ | |
| product | 65 | 87.5× | 316 | ✓ | |
| product | 65 | 85.3× | 325 | ✓ | |
| product | 65 | 89.1× | 319 | ✓ | |
| product | 65 | 89.6× | 304 | ✓ | |
| product | 65 | 90.1× | 308 | ✓ | |
| product | 65 | 91.4× | 307 | ✓ | |
| product | 65 | 85.6× | 318 | ✓ | |
| product | 65 | 85.0× | 332 | ✓ |
| Path | Pages | Avg ACRI | Ghost % | Bloat | Top Issue |
|---|---|---|---|---|---|
| /original/ | 50 | 65 | 0% | 88.2× | High JS Bloat |
| /main/ | 3 | 65 | 0% | 84.6× | High JS Bloat |
| /tag/ | 1 | 47 | 0% | 133.3× | High JS Bloat |
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/logmi.jpGet your free API key — 100 requests/month included.
🔗 Similar infrastructure Sites
Domains with a similar tech stack, industry, and AI readiness profile to logmi.jp. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| logmi.jp (this site) | 60 | 73 | Custom / Proprietary | 9.7× | 2 | — |
| lobbes.nl | 85 | 86 | Custom / Proprietary | 1.5× | 2 | Compare → |
| qtponline.com | 85 | 86 | Custom / Proprietary | 1.3× | 2 | Compare → |
| kondela.cz | 85 | 92 | Custom / Proprietary | 3.1× | 4 | Compare → |
| haoshunjia.com | 85 | 86 | Custom / Proprietary | 1.3× | 1 | Compare → |
| endorphone.com.ua | 85 | 91 | Custom / Proprietary | 2.8× | 4 | Compare → |
📊 Semantic Share of Voice
How often would an AI cite logmi.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-PASTEAuto-generated code fixes tailored to logmi.jp. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
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 Logmi?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Logmi does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Logmi work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Logmi."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for logmi.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 →