sapporobeer.jp 71 B
🛡️ SEO 45 🤖 GEO 84 ⚡ Perf 65 🏗️ Arch 87

sapporobeer.jp — Global SEODiff Score 71/100

sapporobeer.jp
📊

sapporobeer.jp shows strong AI visibility with an ACRI of 80/100, outperforming 94% of indexed domains. In the saas sector, sapporobeer.jp outperforms the average (57), 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 3.1×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. Zero schema blocks puts this site at a disadvantage in knowledge graph and AI-answer pipelines that rely on explicit structured data. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

71
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (45) is your bottleneck.
🎯 Top Fix: Add Organization + WebSite JSON-LD → +5–8 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 18, 2026 · 📋 API
Does your site score higher than sapporobeer.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)45 × 0.25 = 11.2
🤖 AI Readiness / GEO (40% weight)84 × 0.40 = 33.6
⚡ Performance (20% weight)65 × 0.20 = 13.0
🏗️ Architecture & Trust (15% weight)87 × 0.15 = 13.0
Weighted sum = 11.2 + 33.6 + 13.0 + 13.0
Global SEODiff Score = 71 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
99
Structure
avg 35
0
Schema
avg 9
50
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 7%
Rank #66184
Aligned
Gap
AI (ACRI)
Top 6%
Score 80/100

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

Why sapporobeer.jp ranks here

Tech stackCustom / Proprietary
Industrysaas
RenderingSSR
Schema coverage0 blocks
Token bloat3.1×

Fastest improvements

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

45/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

21 chars
Too short

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

309 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://www.sapporobeer.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 — 「★乾杯をもっとおいしく。」サッポロビールのウェブサイトです。黒ラベルやヱビスをはじめとした商品情報のほか、レシピやサッポロのお酒が飲めるお店情報、工場見学など、乾杯をもっとおいしくする情報をお届けします。
  • ✓ 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

84/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, smahospital.jp (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 →
sapporobeer.jp
66
Your ACRI Score
84
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. smahospital.jp has schema coverage of 1 blocks and uses Next.js. 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 99/100 — Excellent
Structured Elements 114 elements (114 lists, 0 rows, 0 headers)
Total Words385
Raw Density29.6%

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

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

32%
🗑️ 68%
Useful Content (24.5 KB)Bloat (51.4 KB)
Token Bloat Ratio3.1× — Lean

Multimodal Readiness

Visual Context81% Optimized for Vision
Image Alt Coverage82 / 101 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

48 Entropy
Fair Token Bloat: Medium
Noise Ratio: 67.7% · SNR: 0.48 · Signal: 6267 / Noise: 13147 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 sapporobeer.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
This document chronicles the history of Sapporo Beer, tracing its origins from a small government brewery in Hokkaido to a
Target Audience
Brewery historians, beer enthusiasts, marketing professionals, and those interested in Japanese business history.
Pricing Model
⚠ SEMANTIC VOID
🏆 Competitive Moat
Strong brand recognition, a legacy of cold brewing techniques, and a deep connection to its regional roots.
📊 Content Depth
8/10
🔄 Programmatic SEO Signals
Brand history pagesTimeline of beer productionRegional beer market analysis
⚡ Key Pain Points
• Limited SEO schema for historical content
• Lack of structured data for product timelines
Analyzed by SEODiff AI · 2026-03-03

🔧 Tech Stack

AI-Readiness Score50/100
Servernginx
CDN
HTTP Status200
Load Time530 ms
Raw HTML Size75.8 KB
Visible Text Size24.5 KB

Performance & Speed

65/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

530 ms
Acceptable — room for improvement

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

📦 Page Weight

970
DOM nodes
76 KB
HTML payload
Lean page — fast for bots and users

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

87/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.sapporobeer.jp/sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

158
internal links
11
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 sapporobeer.jp
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/sapporobeer.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=sapporobeer.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 67 pages · Deep-10

Homepage ACRI
66
Single-page score
-35
Severe hidden bloat
Δ delta
Site-Wide ACRI
32
Avg across 67 pages · Range 0–90
🔍
Hidden Bloat Detected

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

Topical Cohesion
1%
Topical Drift
TF-IDF cosine similarity
Total Words
7608
Avg Bloat
180.6×
Page Type ACRI Token Bloat Words Status
https://www.sapporobeer.jp/english/company/history/roots.html
History introduction | SAPPORO BREWERIES
about 90 3.3× 2449
https://www.sapporobeer.jp/english/company/history/1977.html
1977 Sapporo bottled draft beer goes on sale | History | SAPPORO BREWERIES
about 85 9.1× 538
https://www.sapporobeer.jp/english/company/history/1876.html
1876 Kaitakushi Brewery opens | History | SAPPORO BREWERIES
about 85 7.2× 756
https://www.sapporobeer.jp/english/company/history/1959.html
1959 Canned beer emerges | History | SAPPORO BREWERIES
about 75 9.4× 498
https://www.sapporobeer.jp/english/company/history/2000.html
2000 The Kyushu Hita Brewery is completed | History | SAPPORO BREWERIES
about 65 14.8× 276
https://www.sapporobeer.jp/english/company/history/1916.html
1916 Acquisition of The Anglo-German Brewery | History | SAPPORO BREWERIES
about 65 14.4× 284
https://www.sapporobeer.jp/english/company/history/1906.html
1906 The Dainippon Beer Company is established | History | SAPPORO BREWERIES
about 65 10.6× 424
https://www.sapporobeer.jp/english/company/history/
History | Corporate Profile | SAPPORO BREWERIES
about 62 18.2× 390
https://www.sapporobeer.jp/english/company/history/1869.html
1869 Installation of the new administrative system | History | SAPPORO BREWERIES
about 50 31.9× 119
https://www.sapporobeer.jp/english/company/history/1994.html
1994 Yebisu Garden Place opens | History | SAPPORO BREWERIES
about 50 20.1× 198
https://www.sapporobeer.jp/english/company/history/1934.html
1934 Completion of Ginza Beer and opening of a beer hall | History | SAPPORO BREWERIES
about 50 20.1× 194
https://www.sapporobeer.jp/company/quality/detail001.html
おいしいビールの原料 | サッポロビールのこだわり | サッポロビール
about 50 92.8× 82
https://www.sapporobeer.jp/english/company/history/1887.html
1887 Establishment of the Sapporo Beer Brewery | History | SAPPORO BREWERIES
about 50 25.2× 156
https://www.sapporobeer.jp/english/company/history/1970.html
1970 A silent commercial that became the talk of the town | History | SAPPORO BREWERIES
about 50 24.1× 156
https://www.sapporobeer.jp/company/quality/detail004.html
さらにおいしく味わうための基礎知識 | サッポロビールのこだわり | サッポロビール
about 50 99.2× 139
https://www.sapporobeer.jp/company/overview/
会社概要 | 企業情報 | サッポロビール
about 50 61.7× 74
https://www.sapporobeer.jp/english/company/history/1987.html
1987 The Sapporo Beer Museum opens | History | SAPPORO BREWERIES
about 50 23.9× 158
https://www.sapporobeer.jp/english/company/history/1984.html
1984 The Okayama Winery is completed | History | SAPPORO BREWERIES
about 47 41.7× 88
https://www.sapporobeer.jp/english/company/history/1910.html
1910 Development of Shinshu Wase hops | History | SAPPORO BREWERIES
about 47 35.5× 101
https://www.sapporobeer.jp/hanjo/drink-pickup/backnumber/article/drink002.html
定番ドリンクをブラッシュアップ レモンサワー│rise web│繁盛店の扉│サッポロビール
blog 42 148.1× 54
Showing 20 of 67 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
/company/ 17 42 0% 266.6× High JS Bloat
/english/ 17 60 0% 24.7× High JS Bloat
/hanjo/ 12 33 0% 595.6× High JS Bloat
/recruit/ 10 0 0% 0.0× Low AI Readiness
/blog/ 1 0 0% 0.0× Low AI Readiness
/contact/ 1 0 0% 0.0× Low AI Readiness
/docs/ 1 0 0% 0.0× Low AI Readiness
/about/ 1 0 0% 0.0× Low AI Readiness
/features/ 1 0 0% 0.0× Low AI Readiness
/hakone/ 1 0 0% 0.0× Low AI Readiness
/pricing/ 1 0 0% 0.0× Low AI Readiness
/integrations/ 1 0 0% 0.0× Low AI Readiness
/products/ 1 0 0% 0.0× Low AI Readiness
/case-studies/ 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 67 pages
sapporoholdings.jp ×46
youtube.com ×29
instagram.com ×29
myaccount.sapporobeer.jp ×29
facebook.com ×29
twitter.com ×29
sleeman.ca ×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/sapporobeer.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 sapporobeer.jp. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
sapporobeer.jp (this site) 66 80 Custom / Proprietary 3.1× 0
app-liv.jp 80 80 Custom / Proprietary 1.6× 2 Compare →
aklagare.se 78 82 Cloudflare Pages 1.9× 0 Compare →
videoxxx.org 78 82 Cloudflare Pages 1.8× 0 Compare →
sapporochuo.goguynet.jp 77 84 WordPress 3.3× 1 Compare →
dutchgymnastics.nl 79 82 Cloudflare Pages 1.3× 0 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite sapporobeer.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 sapporobeer.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": "Sapporobeer",
  "url": "https://sapporobeer.jp",
  "logo": "https://sapporobeer.jp/icon/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": "Sapporobeer",
  "url": "https://sapporobeer.jp",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://sapporobeer.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 Sapporobeer?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Sapporobeer does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Sapporobeer work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Sapporobeer."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
80
Projected Score
93
Improvement
+13 pts
Add Organization schema +6 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 →