one.ne.jp 23 F
🛡️ SEO 0 🤖 GEO 71 ⚡ Perf 49 🏗️ Arch 47

one.ne.jp — Global SEODiff Score 23/100

one.ne.jp
📊

one.ne.jp registers just 15/100 on the ACRI scale — a bottom-tier result indicating systemic AI visibility problems. In the social sector, one.ne.jp underperforms relative to the average (57), indicating room for competitive improvement. Its server-rendered architecture ensures AI crawlers receive complete HTML on first request, a key advantage for extractability. A 7.7× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. Minimal structured data (1 block) limits the site's ability to communicate entity relationships to AI systems. A full AI bot restriction means AI-powered search and answer engines cannot currently crawl and index this domain's content.

23
F — Global SEODiff Score
Comprehensive search visibility assessment
Significant improvement opportunities. Start with Traditional SEO (0).
🎯 Top Fix: Allow GPTBot + ClaudeBot in robots.txt → lift the score cap
🔬 Automated SEODiff Assessment · Snapshot: Mar 21, 2026 · 📋 API
📈 ACRI Trend 4 snapshots
Mar 1 Mar 21
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than one.ne.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)0 × 0.25 = 0.0
🤖 AI Readiness / GEO (40% weight)71 × 0.40 = 28.4
⚡ Performance (20% weight)49 × 0.20 = 9.8
🏗️ Architecture & Trust (15% weight)47 × 0.15 = 7.0
Weighted sum = 0.0 + 28.4 + 9.8 + 7.0
⚠️ Fatal multiplier: All major AI bots blocked → ×0.5
Global SEODiff Score = 23 (F)
🚫
Gatekeeper Rule: Score cannot exceed 15. Both GPTBot and ClaudeBot are blocked in robots.txt. No major AI assistant can cite this site. Allow at least one major AI crawler to lift the cap. See Bot Access →
📊 ACRI Sub-Scores (AI Readiness Detail)
0
Bot Access
avg 92
100
Rendering
avg 93
89
Structure
avg 35
42
Schema
avg 9
85
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #740782
-7 pts
Gap
AI (ACRI)
Top 67%
Score 15/100

one.ne.jp is more visible to Google than to AI models. There's room to improve AI discoverability to match your search reputation. ACRI measures technical crawler readiness. Read the methodology →

Why one.ne.jp ranks here

Tech stackWordPress
Industrysocial
RenderingSSR
Schema coverage1 blocks
Token bloat7.7×

Fastest improvements

  • Allow GPTBot in robots.txt so AI crawlers can access your pages (see Crawl Access).
  • Allow ClaudeBot (many assistants rely on it) — blocking it often correlates with “AI invisibility.”
  • 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

0/100 25 % of Global Score 🟡 Medium Confidence

📝 Title Tag

18 chars
Too short

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 0
  • ✓ Has <h2> headings — found 16
  • ✗ <h2> not before <h1>

🔍 Indexability

  • ✓ Canonical tag present → https://www.one.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 — one 株式会社 -
  • ✗ og:description
  • ✗ og:image
  • ✓ twitter:card — summary
📐 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

71/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 social sector, martin-sad.ru (ACRI: 87) 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 →
one.ne.jp
52
Your ACRI Score
87
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. martin-sad.ru has schema coverage of 63 blocks and uses Custom / Proprietary. 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)
Blocked
ClaudeBot (Anthropic)
Blocked
CCBot (Common Crawl)
Blocked
Google-Extended
Blocked
Googlebot
Blocked
💡GPTBot is blocked. To appear in ChatGPT citations, add Allow: / under User-agent: GPTBot in your robots.txt.
💡ClaudeBot is blocked. To be cited by Claude, allow ClaudeBot in robots.txt.

👻 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 89/100 — Excellent
Structured Elements 40 elements (39 lists, 1 rows, 0 headers)
Total Words170
Raw Density23.5%

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

75
AI Extractability
Low
Crawl Cost
Critical
Blocklist Risk
Extractability75/100 — AI models can easily extract answers from this page
Crawl CostLow (30/100) — efficient for AI crawlers to process
Blocklist RiskCritical — 5 of 5 AI crawlers blocked

Token Bloat Research

12%
🗑️ 88%
Useful Content (10.1 KB)Bloat (67.9 KB)
Token Bloat Ratio7.7× — Normal

Multimodal Readiness

Visual Context45% Optimized for Vision
Image Alt Coverage10 / 22 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Only 45% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 87.1% · SNR: 0.15 · Signal: 2580 / Noise: 17395 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 one.ne.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
The company provides a comprehensive suite of cloud services focused on cybersecurity and risk management for healthcare and medical organizations,
Target Audience
Healthcare administrators, medical directors, IT managers, cybersecurity professionals, and medical professionals in the healthcare and medical fields.
Pricing Model
Not specified - services are offered on a project and custom basis.
🛡️ Compliance Standards
個人情報保護法GDPR
🏆 Competitive Moat
Expertise in cybersecurity and risk management for the healthcare industry combined with a comprehensive service offering.
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
【オンラインセミナー】【学会発表】
⚡ Key Pain Points
• Cybersecurity threats to medical organizations
• Risk management and communication
• Compliance with privacy regulations (個人情報保護法, GDPR)
• Lack of easy and secure ways to manage patient inquiries
Analyzed by SEODiff AI · 2026-04-03

🔧 Tech Stack

FrameworkWordPress
AI-Readiness Score85/100
Servernginx
CDN
HTTP Status200
Load Time2949 ms
Raw HTML Size78.0 KB
Visible Text Size10.1 KB

Performance & Speed

49/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2949 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

588
DOM nodes
78 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

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

🔬 Tracker Tax

1
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

47/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

2
internal links
67
external links
Limited internal links — consider adding contextual cross-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 52/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for one.ne.jp
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/one.ne.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=one.ne.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
52
Single-page score
-5
Consistent readability
Δ delta
Site-Wide ACRI
47
Avg across 10 pages · Range 47–47
Total Words
960
Avg Bloat
166.5×
Page Type ACRI Token Bloat Words Status
https://one.ne.jp/pricing
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/about
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/products
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/features
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/docs
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/blog
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/case-studies
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/faq
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/contact
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
https://one.ne.jp/integrations
one 株式会社 -
pricing 47 166.5× 96 💰 Pricing
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/case-studies/ 1 47 0% 166.5× High JS Bloat
/contact/ 1 47 0% 166.5× High JS Bloat
/integrations/ 1 47 0% 166.5× High JS Bloat
/products/ 1 47 0% 166.5× High JS Bloat
/features/ 1 47 0% 166.5× High JS Bloat
/faq/ 1 47 0% 166.5× High JS Bloat
/pricing/ 1 47 0% 166.5× High JS Bloat
/about/ 1 47 0% 166.5× High JS Bloat
/blog/ 1 47 0% 166.5× High JS Bloat
/docs/ 1 47 0% 166.5× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 10 pages
one.jp ×10
shop.nikkeibp.co.jp ×10
sphere.ne.jp ×10
youtube.com ×10
medical.nikkeibp.co.jp ×10
twitter.com ×10
slideshare.net ×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/one.ne.jp

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

🔗 Similar social Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
one.ne.jp (this site) 52 15 WordPress 7.7× 1
substreammagazine.com 77 90 WordPress 7.9× 1 Compare →
vgleaks.com 77 87 WordPress 7.0× 1 Compare →
playdesi.info 77 88 WordPress 6.2× 1 Compare →
dmit.co.th 77 89 WordPress 9.6× 1 Compare →
sustainability.taylorguitars.com 77 87 WordPress 5.2× 1 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite one.ne.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 one.ne.jp. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Allow GPTBot in robots.txt
High Impact ⏱ 2 min
GPTBot is blocked — your content cannot appear in ChatGPT citations. Add this to your robots.txt:
text
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /
Allow ClaudeBot in robots.txt
Medium Impact ⏱ 2 min
ClaudeBot is restricted — Claude may not be able to cite your content. Many AI assistants rely on it.
text
User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for one.ne.jp:

Current Score
15
Projected Score
31
Improvement
+16 pts
Allow GPTBot +8 pts
Allow ClaudeBot +5 pts
Reduce token bloat +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 →