naritasan.or.jp 69 C
🛡️ SEO 62 🤖 GEO 76 ⚡ Perf 69 🏗️ Arch 65
Radar → Domains → naritasan.or.jp

naritasan.or.jp — Global SEODiff Score 69/100

naritasan.or.jp
📊

With an ACRI of 88/100, naritasan.or.jp stands out as one of the highest-performing sites in AI search visibility, outranking 99% of its peers. Compared to other saas sites (avg score: 57), naritasan.or.jp performs above the benchmark, suggesting strong competitive positioning in AI search. Content is delivered server-side, meaning bots and AI agents can parse the full page without executing JavaScript. Token bloat registers at 10.8× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. 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.

69
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (62) is your bottleneck.
🎯 Top Fix: Monitor weekly to catch regressions early
62
🛡️ Traditional SEO
76
🤖 AI Readiness
69
⚡ Performance
65
🏗️ Architecture
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
Does your site score higher than naritasan.or.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)62 × 0.25 = 15.5
🤖 AI Readiness / GEO (40% weight)76 × 0.40 = 30.4
⚡ Performance (20% weight)69 × 0.20 = 13.8
🏗️ Architecture & Trust (15% weight)65 × 0.15 = 9.8
Weighted sum = 15.5 + 30.4 + 13.8 + 9.8
Global SEODiff Score = 69 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 35
42
Schema
avg 10
70
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 38%
Rank #379027
-36 pts
Gap
AI (ACRI)
Top 1%
Score 88/100

naritasan.or.jp ranks much higher on Google (Tranco Top 38%) than in AI search (Top 1%). This is the 'Invisible Giant' pattern — implement the patches above to close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why naritasan.or.jp ranks here

Tech stackNext.js
Industrysaas
RenderingSSR
Schema coverage1 blocks
Token bloat10.8×

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…
See other Next.js sites → saas industry → Full leaderboard → Domain A–Z →
🛡️

Traditional SEO

62/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

27 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

275 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — 大本山成田山新勝寺
  • ✓ og:description — 成田山新勝寺は真言宗智山派の大本山。不動明王を御本尊に、1080年余の御護摩で心願成就を祈る不動尊信仰の総府。年間1000万人超が参拝し、広大な境内に交通安全祈祷殿や公園・書道美術館も備えます。
  • ✓ og:image — preview
  • ✓ 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

76/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 saas sector, gp-auto.com.ua (ACRI: 84) 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 →
naritasan.or.jp
66
Your ACRI Score
→
gp-auto.com.ua
84
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. gp-auto.com.ua has schema coverage of 2 blocks and uses Cloudflare Pages. 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 157 elements (157 lists, 0 rows, 0 headers)
Total Words493
Raw Density31.9%

🏷️ Schema Health Docs

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

Schema Coverage Map

2/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.
💡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

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

9%
🗑️ 91%
Useful Content (16.2 KB)Bloat (158.7 KB)
Token Bloat Ratio10.8× — Normal

Multimodal Readiness

Visual Context14% Optimized for Vision
Image Alt Coverage3 / 21 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Only 14% 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: 90.7% · SNR: 0.10 · Signal: 4160 / Noise: 40615 tokens
Run Full Entropy Audit →

🔬 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

FrameworkNext.js
AI-Readiness Score70/100
ServerApache
CDN—
HTTP Status200
Load Time411 ms
Raw HTML Size174.9 KB
Visible Text Size16.2 KB
⚡

Performance & Speed

69/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

411 ms
Acceptable — room for improvement

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

📦 Page Weight

934
DOM nodes
175 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → public, max-age=0, s-maxage=3600
  • ✗ 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

65/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

AI-Verified badge for naritasan.or.jp
Pending Audit — score below 80 threshold 
<a href="https://seodiff.io/radar/domains/naritasan.or.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=naritasan.or.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
66
Single-page score
-22
Severe hidden bloat
Δ delta
Site-Wide ACRI
44
Avg across 10 pages · Range 44–44
🔍
Hidden Bloat Detected

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

Total Words
1420
Avg Bloat
252.3×
Ext. Citations
4
Page Type ACRI Token Bloat Words Status
https://naritasan.or.jp/pricing
大本山成田山新勝寺
 pricing 44 252.3× 142 ✓
https://naritasan.or.jp/about
大本山成田山新勝寺
 about 44 252.3× 142 ✓
https://naritasan.or.jp/products
大本山成田山新勝寺
 product 44 252.3× 142 ✓
https://naritasan.or.jp/features
大本山成田山新勝寺
 product 44 252.3× 142 ✓
https://naritasan.or.jp/blog
大本山成田山新勝寺
 blog 44 252.3× 142 ✓
https://naritasan.or.jp/docs
大本山成田山新勝寺
 docs 44 252.3× 142 ✓
https://naritasan.or.jp/case-studies
大本山成田山新勝寺
 social-proof 44 252.3× 142 ✓
https://naritasan.or.jp/contact
大本山成田山新勝寺
 support 44 252.3× 142 ✓
https://naritasan.or.jp/faq
大本山成田山新勝寺
 support 44 252.3× 142 ✓
https://naritasan.or.jp/integrations
大本山成田山新勝寺
 integrations 44 252.3× 142 ✓
🔗
Outbound External Citations
4 unique external domains cited across 10 pages
instagram.com ×10
youtube.com ×10
x.com ×10
naritasan-kyosho.jp ×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/naritasan.or.jp

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

🔗 Similar saas Sites

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
naritasan.or.jp (this site) 66 88 Next.js 10.8× 1 —
officelovin.com 65 78 Next.js 10.8× 1 Compare →
goodpatch.com 67 82 Next.js 11.4× 1 Compare →
hotsymbol.com 63 75 Next.js 10.7× 1 Compare →
ssp.co.jp 62 82 Next.js 10.9× 1 Compare →
sellerspace.com 68 93 Next.js 12.0× 1 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

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

Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 9% of your HTML is useful content. AI crawlers waste context window tokens on bloat.
html 
<!-- Move inline CSS to external stylesheets -->
<link rel="stylesheet" href="/css/main.css">

<!-- Move inline scripts to external files with defer -->
<script src="/js/app.js" defer></script>

<!-- Remove duplicate navigation blocks -->
<!-- Keep only ONE <nav> in the <header> -->

<!-- Ensure <main> wraps your primary content -->
<main>
  <!-- Your content here — this is what AI sees first -->
</main>
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 Or?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Or does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Or work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Or."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
88
Projected Score
96
Improvement
+8 pts
Reduce token bloat +5 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).

📄 Generate llms.txt 📊 Export JSON Data 📸 Download Visual

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
Open My Site report → Open Self-Diffing incidents → Open History timeline →

🕒 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

📚 Research & Documentation

🔬
The Science of ACRI
Methodology behind the AI-Crawler Reality Index scoring model.
🚨
Hallucination Risk Study
How poor crawl access increases AI fabrication rates by 3.5×.
🔥
Structural Entropy Paper
The median web page wastes 55% of tokens on noise. Here's the data.
🧪
Extraction Lab Paper
Causal evidence that semantic HTML structure increases AI extraction accuracy.
📖
Documentation Hub
Metrics definitions, fix guides, and API reference for CI/CD integration.
🛠️
Free Tools
llms.txt generator, hallucination checker, entropy audit, and more.