The AI-Readiness profile for paypay.ne.jp is strong: an ACRI of 84/100 places it ahead of 98% of domains in the index. Server-side rendering keeps the ghost ratio near zero, giving AI systems direct access to all visible content. A 5.0× 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. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
paypay.ne.jp has balanced Google and AI visibility — both rank roughly in the same tier. ACRI measures technical crawler readiness. Read the methodology →
Why paypay.ne.jp ranks here
Fastest improvements
- 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
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://paypay.ne.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 — PayPay（ペイペイ）- QRコードで支払うキャッシュレス決済のスマホアプリ
- ✓ og:description — PayPayは、スマホひとつでカンタン・おトクにお支払いができるアプリです。最短1分で登録完了！街のお店をはじめ、ネットサービスや請求書のお支払いなどにもご使用いただけます。
- ✓ 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
78/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
📊 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-VERIFIEDSEODiff AI analyzed the extracted content of paypay.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.
🔧 Tech Stack
Performance & Speed
74/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
- ✗ 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
91/100 15 % of Global Score 🟢 High Confidence🗺️ Sitemap & Robots
- ✓ Sitemap declared in robots.txt →
https://paypay.ne.jp/sitemap_index.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 67/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/paypay.ne.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=paypay.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 103 pages · Deep-10
Homepage scores 67, but internal pages average only 47 — a -21-point gap. Blogs, docs, and legacy content are dragging down AI readability site-wide.
Poorly formatted tables or pricing grids on 9 pages will be split incorrectly during RAG chunking, causing AI models to hallucinate prices and features.
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| blog | 70 | 71.3× | 621 | ✓ | |
| other | 70 | 48.9× | 597 | ✓ | |
| pricing | 60 | 69.8× | 490 | ⚠️ RAG Fracture | |
| blog | 60 | 94.1× | 245 | ✓ | |
| blog | 60 | 120.2× | 220 | ✓ | |
| pricing | 60 | 77.1× | 311 | 💰 Pricing | |
| pricing | 60 | 103.4× | 273 | ⚠️ RAG Fracture | |
| pricing | 60 | 117.8× | 202 | 💰 Pricing | |
| pricing | 60 | 107.9× | 225 | ⚠️ RAG Fracture | |
| blog | 60 | 86.6× | 296 | ✓ | |
| pricing | 60 | 102.5× | 246 | 💰 Pricing | |
| blog | 60 | 112.2× | 251 | ✓ | |
| blog | 60 | 87.1× | 317 | ✓ | |
| pricing | 60 | 80.7× | 380 | 💰 Pricing | |
| blog | 60 | 85.7× | 342 | ✓ | |
| other | 60 | 77.1× | 203 | ✓ | |
| other | 60 | 84.9× | 378 | ✓ | |
| pricing | 60 | 82.0× | 320 | 💰 Pricing | |
| other | 60 | 52.5× | 446 | ✓ | |
| pricing | 60 | 79.0× | 274 | 💰 Pricing |
| Path | Pages | Avg ACRI | Ghost % | Bloat | Top Issue |
|---|---|---|---|---|---|
| /guide/ | 64 | 51 | 0% | 158.1× | High JS Bloat |
| /event/ | 18 | 55 | 0% | 84.0× | High JS Bloat |
| /card-gold/ | 1 | 60 | 0% | 84.9× | High JS Bloat |
| /useful/ | 1 | 37 | 0% | 267.4× | High JS Bloat |
| /features/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /youth-pp-sec/ | 1 | 47 | 0% | 202.9× | High JS Bloat |
| /finance/ | 1 | 47 | 0% | 129.5× | High JS Bloat |
| /case-studies/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /pricing/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /beginner/ | 1 | 60 | 0% | 76.7× | High JS Bloat |
| /faq/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /paytoku/ | 1 | 60 | 0% | 82.0× | High JS Bloat |
| /point/ | 1 | 47 | 0% | 117.8× | High JS Bloat |
| /about/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /contact/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
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/paypay.ne.jpGet your free API key — 100 requests/month included.
🔗 Similar Sites
Domains with a similar tech stack, industry, and AI readiness profile to paypay.ne.jp. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| paypay.ne.jp (this site) | 67 | 84 | WordPress | 5.0× | 1 | — |
| globalinitiative.net | 77 | 86 | WordPress | 2.6× | 1 | Compare → |
| aiaa.org | 77 | 82 | WordPress | 1.9× | 1 | Compare → |
| brilliance.co.jp | 77 | 90 | WordPress | 3.3× | 3 | Compare → |
| hultsfred.se | 77 | 90 | WordPress | 9.2× | 2 | Compare → |
| heathrowtravelcare.co.uk | 77 | 86 | Custom / Proprietary | 3.6× | 1 | Compare → |
📊 Semantic Share of Voice
How often would an AI cite paypay.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-PASTEAuto-generated code fixes tailored to paypay.ne.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": "Ne",
"url": "https://paypay.ne.jp",
"logo": "https://paypay.ne.jp/uploads/2022/03/cropped-cropped-paypay-32x32.png",
"sameAs": []
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Ne?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Ne does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Ne work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Ne."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for paypay.ne.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 →