party-calendar.net 68 C
🛡️ SEO 55 🤖 GEO 88 ⚡ Perf 39 🏗️ Arch 78

party-calendar.net — Global SEODiff Score 68/100

party-calendar.net
📊

party-calendar.net demonstrates elite AI-Readiness, achieving an ACRI of 86/100 — placing it in the top 99% of all indexed domains. Compared to other infrastructure sites (avg score: 57), party-calendar.net performs above the benchmark, suggesting strong competitive positioning in AI search. Server-side rendering keeps the ghost ratio near zero, giving AI systems direct access to all visible content. The token bloat ratio sits at a lean 4.6×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. The site includes 2 schema blocks, providing adequate structured data for basic entity recognition. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

68
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (39) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 26, 2026 · 📋 API
📈 ACRI Trend 3 snapshots
Feb 23 Feb 26
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than party-calendar.net?
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)55 × 0.25 = 13.8
🤖 AI Readiness / GEO (40% weight)88 × 0.40 = 35.2
⚡ Performance (20% weight)39 × 0.20 = 7.8
🏗️ Architecture & Trust (15% weight)78 × 0.15 = 11.7
Weighted sum = 13.8 + 35.2 + 7.8 + 11.7
Global SEODiff Score = 68 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 36
44
Schema
avg 9
50
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 8%
Rank #81914
-7 pts
Gap
AI (ACRI)
Top 1%
Score 86/100

party-calendar.net 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 party-calendar.net ranks here

Tech stackCustom / Proprietary
RenderingSSR
Schema coverage2 blocks
Token bloat4.6×

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

55/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

84 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

237 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://party-calendar.net/
  • ✓ 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
  • ✗ 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

88/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 →
party-calendar.net
76
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 352 elements (337 lists, 13 rows, 2 headers)
Total Words690
Raw Density51.0%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks2 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

86
AI Extractability
Medium
Crawl Cost
None
Blocklist Risk
Extractability86/100 — AI models can easily extract answers from this page
Crawl CostMedium (50/100) — moderate for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

21%
🗑️ 79%
Useful Content (63.1 KB)Bloat (227.0 KB)
Token Bloat Ratio4.6× — Lean

Multimodal Readiness

Visual Context73% Optimized for Vision
Image Alt Coverage29 / 40 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

10 Entropy
Poor Token Bloat: High
Noise Ratio: 78.3% · SNR: 0.28 · Signal: 16146 / Noise: 58101 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

A local LLM (mlx-community/gemma-3-4b-it-qat-4bit) analyzed the extracted content of party-calendar.net 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 curated content and rankings of marriage support events and parties organized by local governments and event organizers,
Target Audience
Singles seeking romantic partners, particularly those interested in local marriage support initiatives and organized events; individuals looking for dating opportunities and connection.
Pricing Model
⚠ SEMANTIC VOID
🏆 Competitive Moat
Dominant market position in Japan for providing event rankings and curated content for the dating and marriage support market, leveraging a large user base and extensive event coverage.
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
Frequent use of ‘婚活パーティー’ (dating party), ‘街コン’ (speed dating), and ‘自治体婚活支援’ (local government marriage support) keywords.Regularly updated event rankings and lists.‘オミカレ公式インタビュー’ (Omikare Official Interview) – a key content format showcasing event organizers and their strategies.
⚡ Key Pain Points
• Limited information on event details beyond rankings (requires further research on the Omikare website).
• Lack of direct product offering – the website acts as a directory and content aggregator.
Model: mlx-community/gemma-3-4b-it-qat-4bit · Analyzed: 2026-02-28 · Data extracted from the site’s main content via strict JSON prompting.

🔧 Tech Stack

AI-Readiness Score50/100
ServerApache
CDN
HTTP Status200
Load Time1145 ms
Raw HTML Size290.0 KB
Visible Text Size63.1 KB

Performance & Speed

39/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1145 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1941
DOM nodes
290 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✓ Cache-Control header → public; max-age=600
  • ✗ 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

78/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://cdn.party-calendar.net/sitemap/sitemap_index.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

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

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

Homepage ACRI
76
Single-page score
-7
Moderate hidden bloat
Δ delta
Site-Wide ACRI
69
Avg across 44 pages · Range 34–75
Total Words
39711
Avg Bloat
225.7×
RAG Fractures [?]
40
⚠️
40 RAG-Chunking Fractures Detected

Poorly formatted tables or pricing grids on 40 pages will be split incorrectly during RAG chunking, causing AI models to hallucinate prices and features.

Page Type ACRI Token Bloat Words Status
https://party-calendar.net/area/hokkaido/genre-15
北海道の婚活セミナ一覧│オミカレ
pricing 75 88.6× 1508 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-4/genre-2
旭川市(北海道)の20代が参加する婚活パーティー・街コン一覧│オミカレ
pricing 75 98.8× 1168 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-18
札幌の食事あり婚活パーティー・街コン一覧│オミカレ
pricing 75 92.8× 1412 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-18
北海道の食事あり婚活パーティー・街コンでの出会い一覧│オミカレ
pricing 75 93.4× 1428 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-7
札幌の婚活ツアー・街コン一覧│オミカレ
pricing 75 91.3× 1438 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-4/genre-18
旭川市(北海道)の食事あり婚活パーティー・街コン一覧│オミカレ
pricing 75 102.2× 1021 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-8
北海道の趣味コンパーティー・街コン一覧│オミカレ
pricing 72 105.1× 1048 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-13
北海道の個室の婚活パーティー・街コンでの出会い一覧│オミカレ
pricing 72 148.1× 812 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-4
札幌の40代(アラフォー)が参加する婚活パーティー・街コン一覧│オミカレ
pricing 72 111.1× 1103 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-1
札幌のハイステータスが参加する婚活パーティー・街コン一覧│オミカレ
pricing 72 122.0× 958 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-2
札幌の20代が参加する婚活パーティー・街コン一覧│オミカレ
pricing 72 112.8× 1078 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-3
札幌の30代(アラサー)が参加する婚活パーティー・街コン一覧│オミカレ
pricing 72 114.6× 1057 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-11
札幌の50代以上(アラフィフ)が参加する婚活パーティー・街コン一覧│オミカレ
pricing 72 101.5× 1220 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-8
札幌の趣味コンパーティー・街コン一覧│オミカレ
pricing 72 107.6× 925 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-12
札幌の女性無料で参加できる婚活パーティー・街コン一覧│オミカレ
pricing 72 112.2× 1093 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-13
札幌の個室の婚活パーティー・街コン一覧│オミカレ
pricing 72 146.1× 818 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/unit-1834/genre-16
札幌の一人参加限定婚活パーティー・街コン一覧│オミカレ
pricing 72 127.5× 817 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-2
北海道の20代が参加する婚活パーティー・街コンでの出会い一覧│オミカレ
pricing 72 114.7× 1083 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-4
北海道の40代(アラフォー)が参加する婚活パーティー・街コンでの出会い一覧│オミカレ
pricing 72 107.8× 1182 ⚠️ RAG Fracture
https://party-calendar.net/area/hokkaido/genre-3
北海道の30代(アラサー)が参加する婚活パーティー・街コンでの出会い一覧│オミカレ
pricing 72 107.1× 1183 ⚠️ RAG Fracture
Showing 20 of 44 pages. Unlock full subpage table →
📂
Health by Sub-Directory
Average ACRI and top issues aggregated by URL path prefix
Path Pages Avg ACRI Ghost % Bloat Top Issue
/area/ 40 72 0% 123.3× High JS Bloat
/contact/ 1 34 0% 1532.6× High JS Bloat
/blog/ 1 59 0% 207.6× High JS Bloat
/features/ 1 47 0% 241.8× High JS Bloat
/faq/ 1 37 0% 3018.0× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 44 pages
omicale.co.jp ×44
instagram.com ×43
party-calendar.onelink.me ×43
lin.ee ×43
x.com ×43
facebook.com ×43
play.google.com ×40
itunes.apple.com ×40
🔄 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/party-calendar.net

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

🔗 Similar infrastructure Sites

Domains with a similar tech stack, industry, and AI readiness profile to party-calendar.net. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
party-calendar.net (this site) 76 86 Custom / Proprietary 4.6× 2
pubsandclubs.com.au 86 87 Custom / Proprietary 4.9× 4 Compare →
insuranceyet.com 86 87 Custom / Proprietary 4.9× 4 Compare →
violinsetc.com 89 86 Custom / Proprietary 2.2× 1 Compare →
kruizinga.nl 87 93 Custom / Proprietary 3.0× 5 Compare →
safescan.com 86 87 Custom / Proprietary 1.9× 5 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

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 Party-calendar?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Party-calendar does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Party-calendar work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Party-calendar."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for party-calendar.net:

Current Score
86
Projected Score
92
Improvement
+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