tickety.jp 66 C
🛡️ SEO 63 🤖 GEO 86 ⚡ Perf 16 🏗️ Arch 83

tickety.jp — Global SEODiff Score 66/100

tickety.jp
📊

Registering an exceptional 87/100 on the AI-Crawler Reality Index, tickety.jp sits in the highest tier of AI extractability among indexed domains. The low ghost ratio (5%) confirms that what crawlers see matches what users see — a hallmark of strong SSR implementation. With a 2.3× bloat ratio, the page delivers its content without excessive boilerplate, giving AI systems a clean extraction path. Structured data coverage is solid at 3 blocks, covering core entities — expanding to include FAQ or Breadcrumb schemas could strengthen the profile further. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

66
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Performance (16) is your bottleneck.
🎯 Top Fix: Fix title tag length → +3 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than tickety.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)63 × 0.25 = 15.8
🤖 AI Readiness / GEO (40% weight)86 × 0.40 = 34.4
⚡ Performance (20% weight)16 × 0.20 = 3.2
🏗️ Architecture & Trust (15% weight)83 × 0.15 = 12.4
Weighted sum = 15.8 + 34.4 + 3.2 + 12.4
Global SEODiff Score = 66 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
99
Rendering
avg 93
100
Structure
avg 35
46
Schema
avg 10
55
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #820354
-81 pts
Gap
AI (ACRI)
Top 1%
Score 87/100

tickety.jp ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 1%). This is the 'Invisible Giant' pattern — implement the patches above to close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why tickety.jp ranks here

Tech stackExpress
Industry
RenderingSSR
Schema coverage3 blocks
Token bloat2.3×

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

63/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

74 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

461 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.tickety.jp
  • ✓ 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 — 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

86/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.

🚨

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 2151 elements (2151 lists, 0 rows, 0 headers)
Total Words3173
Raw Density67.8%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks3 blocks

Schema Coverage Map

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

📐 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

43%
🗑️ 57%
Useful Content (188.3 KB)Bloat (248.0 KB)
Token Bloat Ratio2.3× — Lean

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage57 / 57 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

68 Entropy
Fair Token Bloat: Medium
Noise Ratio: 56.9% · SNR: 0.76 · Signal: 48193 / Noise: 63500 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/Qwen2.5-7B-Instruct-4bit) analyzed the extracted content of tickety.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
高価買取・格安販売の金券ショップ
Target Audience
金券を処分したい個人・企業
Pricing Model
高価買取・格安販売
🛡️ Compliance Standards
適切な個人情報管理
Model: mlx-community/Qwen2.5-7B-Instruct-4bit · Analyzed: 2026-02-25 · Data extracted from the site’s main content via strict JSON prompting.

🔧 Tech Stack

FrameworkExpress
AI-Readiness Score55/100
ServerApache/2.4.54 (Debian)
CDN
HTTP Status200
Load Time2060 ms
Raw HTML Size436.3 KB
Visible Text Size188.3 KB

Performance & Speed

16/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

2060 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

5999
DOM nodes
436 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → no-store, no-cache, must-revalidate
  • ✗ 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

83/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

2188
internal links
7
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.

✓ TOP 15% AI-READY

🏆 You Are AI-Verified — Claim Your Badge

Your site scores 86/100 on the AI-Crawler Reality Index. Embed this trust badge on your site — every click sends visitors to your verified report and builds backlinks to your domain.

AI-Verified badge for tickety.jp
Verified — updates automatically every 24h
<a href="https://seodiff.io/radar/domains/tickety.jp" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=tickety.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.

How it works: The badge queries your ACRI score daily. If your score drops below 80 or your site hasn't been scanned in 30 days, the badge changes to "Pending Audit" (yellow) — prompting you to fix issues and rescan. Learn about ACRI methodology →

🔗 Similar Sites

Domains with a similar tech stack, industry, and AI readiness profile to tickety.jp. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
tickety.jp (this site) 86 87 Express 2.3× 3
tilibraexpress.com.br 87 87 Express 1.9× 3 Compare →
corso101.com 85 87 Express 1.8× 3 Compare →
mecshopping.it 84 87 Express 2.2× 3 Compare →
onlinepets.com 84 86 Express 2.4× 3 Compare →
medpets.nl 84 86 Express 2.4× 3 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to tickety.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": "Tickety",
  "url": "https://tickety.jp",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://tickety.jp/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
87
Projected Score
91
Improvement
+4 pts
Add WebSite schema +4 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