kamigamojinja.jp 52 D
🛡️ SEO 28 🤖 GEO 65 ⚡ Perf 49 🏗️ Arch 64

kamigamojinja.jp — Global SEODiff Score 52/100

kamigamojinja.jp
📊

The AI-Readiness profile for kamigamojinja.jp is strong: an ACRI of 84/100 places it ahead of 98% of domains in the index. Compared to other infrastructure sites (avg score: 57), kamigamojinja.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 11.9× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. Zero schema blocks puts this site at a disadvantage in knowledge graph and AI-answer pipelines that rely on explicit structured data. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

52
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Traditional SEO (28) has the most room for improvement.
🎯 Top Fix: Add Organization + WebSite JSON-LD → +5–8 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 3, 2026 · 📋 API
📈 ACRI Trend 4 snapshots
Feb 23 Mar 3
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than kamigamojinja.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)28 × 0.25 = 7.0
🤖 AI Readiness / GEO (40% weight)65 × 0.40 = 26.0
⚡ Performance (20% weight)49 × 0.20 = 9.8
🏗️ Architecture & Trust (15% weight)64 × 0.15 = 9.6
Weighted sum = 7.0 + 26.0 + 9.8 + 9.6
Global SEODiff Score = 52 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
100
Structure
avg 36
0
Schema
avg 9
85
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #565545
-54 pts
Gap
AI (ACRI)
Top 2%
Score 84/100

kamigamojinja.jp ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 2%). This is the 'Visibility Gap' pattern — implementing the recommendations above can help close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why kamigamojinja.jp ranks here

Tech stackWordPress
RenderingSSR
Schema coverage0 blocks
Token bloat11.9×

Fastest improvements

  • Add basic Organization and WebSite JSON-LD to fix “0 schema blocks” (see Schema Coverage).
  • 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

28/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

84 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

264 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — 賀茂別雷神社(上賀茂神社:かみがもじんじゃ)公式Webサイト
  • ✓ 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

65/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, plodopitomnik-sad.ru (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 →
kamigamojinja.jp
56
Your ACRI Score
90
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. plodopitomnik-sad.ru has schema coverage of 12 blocks and uses Express. 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 0%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 100/100 — Excellent
Structured Elements 84 elements (84 lists, 0 rows, 0 headers)
Total Words232
Raw Density36.2%

🏷️ Schema Health Docs

Organization Schema ❌ Missing
Product / Service Schema ⚠️ Not Found
Total Schema Blocks0 — No JSON-LD detected

Schema Coverage Map

0/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.
💡WebSite schema missing. Add WebSite + SearchAction so Google can generate a Sitelinks Search Box for your brand in AI results.

📐 AI Efficiency Metrics Docs

63
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability63/100 — AI models can partially 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

8%
🗑️ 92%
Useful Content (5.9 KB)Bloat (64.7 KB)
Token Bloat Ratio11.9× — Normal

Multimodal Readiness

Visual Context64% Optimized for Vision
Image Alt Coverage25 / 39 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: 91.6% · SNR: 0.09 · Signal: 1515 / Noise: 16565 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

FrameworkWordPress
AI-Readiness Score85/100
Servernginx
CDN
HTTP Status200
Load Time2142 ms
Raw HTML Size70.6 KB
Visible Text Size5.9 KB

Performance & Speed

49/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2142 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

512
DOM nodes
71 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

64/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

Homepage ACRI
56
Single-page score
-17
Moderate hidden bloat
Δ delta
Site-Wide ACRI
39
Avg across 1 pages · Range 39–39
🔍
Hidden Bloat Detected

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

Total Words
60
Avg Bloat
128.0×
Page Type ACRI Token Bloat Words Status
https://kamigamojinja.jp/about
上賀茂神社について | 賀茂別雷神社(上賀茂神社:かみがもじんじゃ)公式Webサイト
about 39 128.0× 60
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/about/ 1 39 0% 128.0× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 1 pages
instagram.com ×1
youtube.com ×1
kamigamojinja-wedding.info ×1
facebook.com ×1
tiktok.com ×1
🔄 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/kamigamojinja.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 kamigamojinja.jp. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
kamigamojinja.jp (this site) 56 84 WordPress 11.9× 0
arzancell.com 81 90 WordPress 8.1× 2 Compare →
swistakpakuje.pl 81 89 WordPress 7.7× 3 Compare →
princeclassified.com 81 94 WordPress 5.6× 5 Compare →
gastronet24.pl 81 90 WordPress 2.2× 3 Compare →
reddress.com 81 89 Shopify 7.3× 3 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite kamigamojinja.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 kamigamojinja.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": "Kamigamojinja",
  "url": "https://kamigamojinja.jp",
  "logo": "https://www.kamigamojinja.jp/favicon.ico",
  "sameAs": []
}
</script>
Add WebSite + SearchAction JSON-LD
High Impact ⏱ 5 min
Enables the Sitelinks Search Box in Google and allows AI to understand your site structure.
html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Kamigamojinja",
  "url": "https://kamigamojinja.jp",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://kamigamojinja.jp/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 8% 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 Kamigamojinja?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Kamigamojinja does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Kamigamojinja work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Kamigamojinja."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
84
Projected Score
100
Improvement
+16 pts
Add Organization schema +6 pts
Add WebSite schema +4 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).

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