nextage.jp 71 B
🛡️ SEO 54 🤖 GEO 86 ⚡ Perf 53 🏗️ Arch 83

nextage.jp — Global SEODiff Score 71/100

nextage.jp
📊

The AI-Readiness profile for nextage.jp is strong: an ACRI of 80/100 places it ahead of 94% of domains in the index. Compared to other infrastructure sites (avg score: 57), nextage.jp performs above the benchmark, 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. Token bloat registers at 6.3× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. 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.

71
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (53) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than nextage.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)54 × 0.25 = 13.5
🤖 AI Readiness / GEO (40% weight)86 × 0.40 = 34.4
⚡ Performance (20% weight)53 × 0.20 = 10.6
🏗️ Architecture & Trust (15% weight)83 × 0.15 = 12.4
Weighted sum = 13.5 + 34.4 + 10.6 + 12.4
Global SEODiff Score = 71 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 35
2
Schema
avg 10
50
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 6%
Rank #62013
Aligned
Gap
AI (ACRI)
Top 6%
Score 80/100

nextage.jp has balanced Google and AI visibility — both rank roughly in the same tier. ACRI measures technical crawler readiness. Read the methodology →

Why nextage.jp ranks here

Tech stackCustom / Proprietary
RenderingSSR
Schema coverage1 blocks
Token bloat6.3×

Fastest improvements

  • 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

54/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

30 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

232 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.nextage.jp
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → ja
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — 中古車のネクステージ
  • ✓ og:description — 中古車販売・買取査定・車検のネクステージ サイト。新車・中古車販売、中古車検索、買取査定、車検、整備、鈑金、修理、保険など、おクルマの事ならネクステージで!
  • ✓ 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

86/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 →
nextage.jp
70
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 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 344 elements (344 lists, 0 rows, 0 headers)
Total Words594
Raw Density57.9%

🏷️ Schema Health Docs

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

Schema Coverage Map

1/7 schema types detected
❌ Organization
❌ Product/Service
❌ Breadcrumb
❌ FAQ
❌ Article
✅ WebSite
💡Organization schema missing. AI models cannot identify your brand entity. Without it, your brand won't appear in Knowledge Panels or be associated with your content.
💡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

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

15%
🗑️ 85%
Useful Content (14.0 KB)Bloat (74.8 KB)
Token Bloat Ratio6.3× — Normal

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage61 / 61 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 84.2% · SNR: 0.19 · Signal: 3593 / Noise: 19142 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

AI-Readiness Score50/100
Servernginx
CDN
HTTP Status200
Load Time1894 ms
Raw HTML Size88.8 KB
Visible Text Size14.0 KB

Performance & Speed

53/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1894 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1198
DOM nodes
89 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

83/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.nextage.jp/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

Homepage ACRI
70
Single-page score
-24
Severe hidden bloat
Δ delta
Site-Wide ACRI
47
Avg across 3 pages · Range 40–50
🔍
Hidden Bloat Detected

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

Total Words
212
Avg Bloat
181.8×
Ext. Citations
20
Page Type ACRI Token Bloat Words Status
https://nextage.jp/contact
お問い合わせ|中古車の【ネクステージ】
support 50 74.6× 130
https://nextage.jp/faq
よくある質問|中古車の【ネクステージ】
support 50 99.3× 66
https://nextage.jp/about
会社概要|中古車の【ネクステージ】
about 40 371.6× 16
🔗
Outbound External Citations
20 unique external domains cited across 3 pages
ja-jp.facebook.com ×3
sweden-cars.jp ×3
recruit.nextage.jp ×3
universe-cars.jp ×3
youtube.com ×3
alc-mg.com ×3
instagram.com ×3
suv-land.jp ×3
🔄 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/nextage.jp

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

🔗 Similar infrastructure Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
nextage.jp (this site) 70 80 Custom / Proprietary 6.3× 1
startbase.com 70 78 Custom / Proprietary 6.3× 1 Compare →
hanadonya.com 70 80 Custom / Proprietary 6.3× 1 Compare →
b2online.com.br 70 76 Custom / Proprietary 6.3× 1 Compare →
nonnon.jp 70 80 Custom / Proprietary 6.4× 1 Compare →
drukbedrijf.nl 70 83 Custom / Proprietary 6.1× 1 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to nextage.jp. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

Add Organization JSON-LD
High Impact ⏱ 5 min
AI models cannot identify your brand entity without Organization schema. This is the #1 fix for AI visibility.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Nextage",
  "url": "https://nextage.jp",
  "logo": "https://nextage.jp/images/global/favicon_pwa_mask_512.png",
  "sameAs": []
}
</script>
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 Nextage?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Nextage does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Nextage work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Nextage."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
80
Projected Score
92
Improvement
+12 pts
Add Organization schema +6 pts
Reduce token bloat +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