happymail.co.jp 65 C
🛡️ SEO 48 🤖 GEO 81 ⚡ Perf 53 🏗️ Arch 69

happymail.co.jp — Global SEODiff Score 65/100

happymail.co.jp
📊

happymail.co.jp achieves a 76/100 on the AI-Crawler Reality Index, reflecting above-average readiness for AI-driven discovery. In the infrastructure sector, happymail.co.jp outperforms the average (57), 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. The token bloat ratio sits at a lean 2.0×, 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. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

65
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (48) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 15, 2026 · 📋 API
📈 ACRI Trend 30 snapshots
Feb 22 Mar 15
🔔 Recent AI Indexing Activity
🔄 Mar 10 Content change detected
Does your site score higher than happymail.co.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)48 × 0.25 = 12.0
🤖 AI Readiness / GEO (40% weight)81 × 0.40 = 32.4
⚡ Performance (20% weight)53 × 0.20 = 10.6
🏗️ Architecture & Trust (15% weight)69 × 0.15 = 10.3
Weighted sum = 12.0 + 32.4 + 10.6 + 10.3
Global SEODiff Score = 65 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
46
Structure
avg 35
44
Schema
avg 9
50
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 0.9%
Rank #8891
+17 pts
Gap
AI (ACRI)
Top 17%
Score 76/100

happymail.co.jp punches above its weight in AI — AI visibility exceeds Google ranking. This is a competitive moat worth protecting. ACRI measures technical crawler readiness. Read the methodology →

Why happymail.co.jp ranks here

Tech stackCustom / Proprietary
RenderingSSR
Schema coverage2 blocks
Token bloat2.0×

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

48/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

168 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

456 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://happymail.co.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 — 出会い・恋愛のハッピーメール【公式】|彼氏・彼女がほしい貴方に贈る日本最大級のマッチングアプリ・マッチングサイト
  • ✓ og:description — ハッピーメール(ハピメ)は登録無料の優良出会いマッチングアプリ・マッチングサイトです。趣味友から恋活・婚活まで幅広い出会いを提供。スマホ・アプリにも対応しているから初めての方でも安心してご利用頂けます。25年の運営実績で累計会員数3,500万以上、全国47都道府県のどこからでも素敵な出会いを見つけることができます。
  • ✓ 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

81/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 →
happymail.co.jp
60
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 46/100 — Fair
Structured Elements 26 elements (26 lists, 0 rows, 0 headers)
Total Words411
Raw Density6.3%

🏷️ 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.
💡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

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

50%
🗑️ 50%
Useful Content (44.6 KB)Bloat (46.5 KB)
Token Bloat Ratio2.0× — Lean

Multimodal Readiness

Visual Context94% Optimized for Vision
Image Alt Coverage72 / 77 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

75 Entropy
Good Token Bloat: Low
Noise Ratio: 51.0% · SNR: 0.96 · Signal: 11413 / Noise: 11898 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 happymail.co.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.

Core Offering
Hapmail is a long-standing (20+ years) dating site and app offering a free, ad-free alternative to monthly subscription dating apps.
Target Audience
Singles seeking romantic relationships, particularly those frustrated with the high costs of traditional dating apps; users seeking a more affordable and ad-free dating experience.
Pricing Model
Free to use (with a small cost per message), with optional premium features (not explicitly detailed).
🏆 Competitive Moat
Long-standing reputation and user base (35 million members), combined with a low-cost, ad-free model and a focus on direct messaging, differentiating it from subscription-based apps.
📊 Content Depth
7/10
🔄 Programmatic SEO Signals
Template comparison pages (e.g., ‘Hapmail vs. other dating apps’)Integration directory pages (implicitly, through mentions of profile image search)SEO-optimized landing pages for key features (e.g., ‘Profile Image Search’, ‘Browse’, ‘Diary’)
⚡ Key Pain Points
• Lack of structured FAQ schema
• Thin landing pages for features (some pages are short and lack detailed information)
• Potential concerns about safety and spam (addressed with 24/7 monitoring and user reporting)
Analyzed by SEODiff AI · 2026-02-28

🔧 Tech Stack

AI-Readiness Score50/100
Servernginx
CDN
HTTP Status200
Load Time1389 ms
Raw HTML Size91.1 KB
Visible Text Size44.6 KB

Performance & Speed

53/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1389 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

889
DOM nodes
91 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

69/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

Homepage ACRI
60
Single-page score
-14
Moderate hidden bloat
Δ delta
Site-Wide ACRI
47
Avg across 117 pages · Range 0–64
🔍
Hidden Bloat Detected

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

Topical Cohesion
18%
Topical Drift
TF-IDF cosine similarity
Total Words
13975
Avg Bloat
58.4×
Page Type ACRI Token Bloat Words Status
https://happymail.co.jp/happylife/
恋愛ノウハウを配信する 恋活・婚活トレンド情報サイト|ハッピーメールライフ
other 64 159.6× 555
https://happymail.co.jp/transmissionGuideline/
利用者情報の外部送信に関するガイドライン|出会い・恋愛のハッピーメール【公式】
blog 60 36.2× 411
https://happymail.co.jp/rules/
会員規約|出会い・恋愛のハッピーメール【公式】
other 60 42.3× 300
https://happymail.co.jp/topics/
新着トピックス|出会い・恋愛のハッピーメール【公式】
other 60 57.7× 235
https://happymail.co.jp/drama/
ハッピーメールがドラマ化|出会い・恋愛のハッピーメール【公式】
other 60 41.8× 254
https://happymail.co.jp/diary/success/
出会い成功談|出会い・恋愛のハッピーメール【公式】
social-proof 60 27.8× 276
https://happymail.co.jp/party/lst/
ハッピーパーティー|婚活,お見合いパーティーで結婚相手,恋人探しをしよう!|出会い・恋愛のハッピーメール【公式】
other 60 37.8× 208
https://happymail.co.jp/onlineparty/lst/
オンラインパーティー|婚活,お見合いパーティーで結婚相手,恋人探しをしよう!|出会い・恋愛のハッピーメール【公式】
other 60 33.7× 206
https://happymail.co.jp/aff/
ハッピーメールでアフィリエイト|出会い・恋愛のハッピーメール【公式】
other 60 39.1× 253
https://happymail.co.jp/privacy/
プライバシーポリシー|出会い・恋愛のハッピーメール【公式】
legal 60 50.8× 204
https://happymail.co.jp/happylife/column/noro-kayo-part1/
『ハッピーメール』のイメージモデル 野呂佳代さんのマル秘『恋バナ』を深堀インタビュー【Part1】│恋愛ノウハウを配信する 恋活・婚活トレンド情報サイト|ハッピーライフ
other 57 153.6× 493
https://happymail.co.jp/faq/personal/
個人情報の取り扱いについて|出会い・恋愛のハッピーメール【公式】
support 55 65.2× 103
https://happymail.co.jp/faq/point/
料金システム・ポイントについて|出会い・恋愛のハッピーメール【公式】
support 55 59.5× 101
https://happymail.co.jp/faq/age_cert/
本人の年齢確認について|出会い・恋愛のハッピーメール【公式】
support 55 63.6× 116
https://happymail.co.jp/faq/affiliate/
よくある質問のアフィリエイトの項目について|出会い・恋愛のハッピーメール【公式】
support 55 54.5× 149
https://happymail.co.jp/faq/register/
登録 ・ 退会 ・ 変更について|出会い・恋愛のハッピーメール【公式】
support 55 60.7× 113
https://happymail.co.jp/happylife/column/happy-mail-web-drama-5/
現代に蘇る恋の和歌「金木犀と私」ハッピーメールWebドラマ@第5話│恋愛ノウハウを配信する 恋活・婚活トレンド情報サイト|ハッピーライフ
other 54 198.8× 373
https://happymail.co.jp/happylife/manual/japans-largest-matching-service-happymail/
ハッピーメールはなぜ全国で愛用されて日本最大級の出会い・マッチングサービスになれたのか?│恋愛ノウハウを配信する 恋活・婚活トレンド情報サイト|ハッピーライフ
product 54 265.5× 267
https://happymail.co.jp/happylife/authors/
ライター一覧│恋愛ノウハウを配信する 恋活・婚活トレンド情報サイト|ハッピーライフ
auth 54 298.1× 240
https://happymail.co.jp/company/
会社概要/特定商取引法に基づく表記|出会い・恋愛のハッピーメール【公式】
about 50 44.9× 139
Showing 20 of 100 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
/topics/ 34 50 0% 57.5× High JS Bloat
/cooperation/ 11 50 0% 57.5× High JS Bloat
/drama/ 11 51 0% 50.1× High JS Bloat
/faq/ 10 48 0% 55.9× High JS Bloat
/safety/ 9 50 0% 66.3× High JS Bloat
/happylife/ 5 57 0% 215.1× High JS Bloat
/aff/ 3 53 0% 54.8× High JS Bloat
/diary/ 3 53 0% 41.6× High JS Bloat
/about/ 2 25 0% 22.1× High JS Bloat
/price/ 2 50 0% 52.4× High JS Bloat
/beginner/ 1 50 0% 58.8× High JS Bloat
/promotion/ 1 50 0% 63.7× High JS Bloat
/case-studies/ 1 0 0% 0.0× Low AI Readiness
/mediaPublication/ 1 50 0% 62.6× High JS Bloat
/tagline/ 1 50 0% 67.7× High JS Bloat
🔗
Outbound External Citations
0 unique external domains cited across 117 pages
happymail.net ×107
youtube.com ×105
x.com ×105
instagram.com ×105
google.co.jp ×101
twitter.com ×13
support.happymail.co.jp ×10
humax-cinema.co.jp ×6
🔄 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/happymail.co.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 happymail.co.jp. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
happymail.co.jp (this site) 60 76 Custom / Proprietary 2.0× 2
lobbes.nl 85 86 Custom / Proprietary 1.5× 2 Compare →
gurapan.jp 85 80 Custom / Proprietary 1.5× 2 Compare →
qtponline.com 85 86 Custom / Proprietary 1.3× 2 Compare →
haoshunjia.com 85 86 Custom / Proprietary 1.3× 1 Compare →
paradigit.nl 85 95 Custom / Proprietary 4.0× 15 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

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": "Co",
  "url": "https://happymail.co.jp",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://happymail.co.jp/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</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 Co?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Co does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Co work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Co."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
76
Projected Score
83
Improvement
+7 pts
Add WebSite schema +4 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 →