zexy.net 64 C
🛡️ SEO 41 🤖 GEO 87 ⚡ Perf 39 🏗️ Arch 77

zexy.net — Global SEODiff Score 64/100

zexy.net
📊

With a solid 80/100 ACRI, zexy.net is well-positioned for AI search — better than 94% of sites in the Radar. Within the infrastructure vertical, this places zexy.net above the industry average of 57 —, suggesting strong competitive positioning in AI search. The low ghost ratio (5%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. With a 3.7× bloat ratio, the page delivers its content without excessive boilerplate, giving AI systems a clean extraction path. Structured data coverage is solid at 2 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

64
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (39) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 21, 2026 · 📋 API
📈 ACRI Trend 19 snapshots
Feb 22 Mar 21
🔔 Recent AI Indexing Activity
📉 Mar 21 ACRI -1 (73→72)
📈 Mar 15 ACRI +1 (72→73)
Does your site score higher than zexy.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)41 × 0.25 = 10.2
🤖 AI Readiness / GEO (40% weight)87 × 0.40 = 34.8
⚡ Performance (20% weight)39 × 0.20 = 7.8
🏗️ Architecture & Trust (15% weight)77 × 0.15 = 11.5
Weighted sum = 10.2 + 34.8 + 7.8 + 11.5
Global SEODiff Score = 64 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 35
4
Schema
avg 9
50
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 5%
Rank #47681
Aligned
Gap
AI (ACRI)
Top 6%
Score 80/100

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

Why zexy.net ranks here

Tech stackCustom / Proprietary
RenderingSSR
Schema coverage2 blocks
Token bloat3.7×

Fastest improvements

  • You’re already in decent shape — the next moat is monitoring drift over time.
  • 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

41/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

69 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

330 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://zexy.net/
  • ✓ No noindex directive
  • ✗ Meta viewport set
  • ✓ HTML lang attribute → ja-JP
  • ➖ Hreflang tags — N/A (single language site)
  • ✓ 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

87/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 →
zexy.net
72
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 467 elements (467 lists, 0 rows, 0 headers)
Total Words562
Raw Density83.1%

🏷️ Schema Health Docs

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

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

27%
🗑️ 73%
Useful Content (50.1 KB)Bloat (133.8 KB)
Token Bloat Ratio3.7× — Lean

Multimodal Readiness

Visual Context66% Optimized for Vision
Image Alt Coverage40 / 61 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

32 Entropy
Poor Token Bloat: High
Noise Ratio: 72.8% · SNR: 0.37 · Signal: 12823 / Noise: 34244 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

SEODiff AI analyzed the extracted content of zexy.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
This website is a wedding venue directory and information platform for Gunma Prefecture, Japan, offering details on various venues, including
Target Audience
Engaged couples, wedding planners, and families planning weddings in Gunma Prefecture, Japan.
Pricing Model
Venue rental prices vary significantly, ranging from ¥2,413,290 to ¥2,914,340 for a 90-person event, with additional costs for catering, decorations, and other services.
🏆 Competitive Moat
Extensive venue database for Gunma Prefecture with detailed information and user-friendly search filters, combined with a strong local SEO presence and a focus on providing a comprehensive resource for wedding planning.
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
Integration directory pagesTemplate comparison pagesNumerous venue listings with detailed descriptions and imagesRegularly updated new information
⚡ Key Pain Points
• Limited SEO depth for individual venue pages
• Lack of a centralized system for comparing venues
• Potential difficulty for users to find the perfect venue based on specific needs
Analyzed by SEODiff AI · 2026-03-02

🔧 Tech Stack

AI-Readiness Score50/100
ServerApache
CDN
HTTP Status200
Load Time1405 ms
Raw HTML Size183.9 KB
Visible Text Size50.1 KB

Performance & Speed

39/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1405 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1784
DOM nodes
184 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ 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

77/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://zexy.net/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

276
internal links
40
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-JP
  • ✗ 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 72/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Homepage ACRI
72
Single-page score
-16
Moderate hidden bloat
Δ delta
Site-Wide ACRI
56
Avg across 82 pages · Range 0–72
🔍
Hidden Bloat Detected

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

Total Words
53567
Avg Bloat
57.3×
RAG Fractures [?]
17
⚠️
17 RAG-Chunking Fractures Detected

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

Page Type ACRI Token Bloat Words Status
https://zexy.net/wedding/kagawa/clientList/
【ゼクシィ】香川県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 77.8× 544 💰 Pricing
https://zexy.net/wedding/ehime/clientList/
【ゼクシィ】愛媛県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 81.1× 588 💰 Pricing
https://zexy.net/wedding/iwate/clientList/
【ゼクシィ】岩手県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 80.6× 511 💰 Pricing
https://zexy.net/wedding/niigata/clientList/
【ゼクシィ】新潟県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 87.9× 995 💰 Pricing
https://zexy.net/wedding/kanagawa/clientList/
【ゼクシィ】神奈川県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 96.0× 1664 💰 Pricing
https://zexy.net/wedding/yamaguchi/clientList/
【ゼクシィ】山口県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 84.7× 587 💰 Pricing
https://zexy.net/wedding/fukushima/clientList/
【ゼクシィ】福島県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 89.1× 685 💰 Pricing
https://zexy.net/wedding/yamanashi/clientList/
【ゼクシィ】山梨県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 82.5× 540 💰 Pricing
https://zexy.net/wedding/toyama/clientList/
【ゼクシィ】富山県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 84.1× 530 💰 Pricing
https://zexy.net/wedding/tokyo/clientList/
【ゼクシィ】東京都の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 99.8× 1645 💰 Pricing
https://zexy.net/wedding/gifu/clientList/
【ゼクシィ】岐阜県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 82.5× 687 💰 Pricing
https://zexy.net/wedding/nagasaki/clientList/
【ゼクシィ】長崎県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 79.9× 645 💰 Pricing
https://zexy.net/wedding/kagoshima/clientList/
【ゼクシィ】鹿児島県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 85.3× 763 💰 Pricing
https://zexy.net/wedding/kumamoto/clientList/
【ゼクシィ】熊本県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 88.2× 852 💰 Pricing
https://zexy.net/wedding/oita/clientList/
【ゼクシィ】大分県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 83.7× 727 💰 Pricing
https://zexy.net/wedding/shiga/clientList/
【ゼクシィ】滋賀県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 85.4× 712 💰 Pricing
https://zexy.net/wedding/miyagi/clientList/
【ゼクシィ】宮城県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 89.0× 775 💰 Pricing
https://zexy.net/wedding/nagano/clientList/
【ゼクシィ】長野県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 87.0× 1055 💰 Pricing
https://zexy.net/wedding/aichi/clientList/
【ゼクシィ】愛知県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 96.1× 1652 💰 Pricing
https://zexy.net/wedding/fukuoka/clientList/
【ゼクシィ】福岡県の披露宴・ウェディング会場を探そう!挙式情報満載
pricing 72 93.0× 1658 💰 Pricing
Showing 20 of 82 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
/wedding/ 65 70 0% 71.1× High JS Bloat
/navi/ 7 7 0% 5.5× High JS Bloat
/pricing/ 1 0 0% 0.0× Low AI Readiness
/case-studies/ 1 0 0% 0.0× Low AI Readiness
/integrations/ 1 0 0% 0.0× Low AI Readiness
/contents/ 1 42 0% 35.7× High JS Bloat
/about/ 1 0 0% 0.0× Low AI Readiness
/features/ 1 0 0% 0.0× Low AI Readiness
/docs/ 1 0 0% 0.0× Low AI Readiness
/products/ 1 0 0% 0.0× Low AI Readiness
/contact/ 1 0 0% 0.0× Low AI Readiness
/faq/ 1 0 0% 0.0× Low AI Readiness
🔗
Outbound External Citations
0 unique external domains cited across 82 pages
help.zexy.net ×67
cdn.p.recruit.co.jp ×67
recruit.co.jp ×67
twitter.com ×5
facebook.com ×5
cafe.zexy.net ×5
instagram.com ×5
youtube.com ×5
🔄 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/zexy.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 zexy.net. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
zexy.net (this site) 72 80 Custom / Proprietary 3.7× 2
kondela.hu 86 93 Custom / Proprietary 3.1× 4 Compare →
insuranceyet.com 86 87 Custom / Proprietary 4.9× 4 Compare →
melbourneschool.com 86 87 Custom / Proprietary 5.0× 4 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 zexy.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 zexy.net. 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": "Zexy",
  "url": "https://zexy.net",
  "logo": "https://zexy.net/favicon.ico",
  "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 Zexy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Zexy does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Zexy work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Zexy."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
80
Projected Score
89
Improvement
+9 pts
Add Organization schema +6 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
🔍 Found indexing issues?
Run a free deep audit to diagnose crawled-not-indexed, soft 404s, redirect errors, and more.
Free Deep Audit → GSC Error Guide →