charge-spot.tw 59 D
🛡️ SEO 56 🤖 GEO 58 ⚡ Perf 47 🏗️ Arch 84

charge-spot.tw — Global SEODiff Score 59/100

charge-spot.tw
📊

Among all indexed domains, charge-spot.tw ranks in the top echelon with an ACRI of 86, demonstrating that its content is highly visible to AI systems. In the infrastructure sector, charge-spot.tw 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. A 50.0× token bloat ratio means crawlers must process significantly more tokens to reach the actual content — a drag on extraction efficiency. The site includes 2 schema blocks, providing adequate structured data for basic entity recognition. Robots.txt grants unrestricted access to the key AI user-agents, which is the strongest starting position for AI visibility.

59
D — Global SEODiff Score
Comprehensive search visibility assessment
Below average — Performance (47) has the most room for improvement.
🎯 Top Fix: Reduce token bloat (211×) → +5–10 pts
🔬 Automated SEODiff Assessment · Snapshot: Mar 20, 2026 · 📋 API
📈 ACRI Trend 3 snapshots
Mar 6 Mar 20
🔔 Recent AI Indexing Activity
No recent changes detected by adaptive crawler.
Does your site score higher than charge-spot.tw?
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)56 × 0.25 = 14.0
🤖 AI Readiness / GEO (40% weight)58 × 0.40 = 23.2
⚡ Performance (20% weight)47 × 0.20 = 9.4
🏗️ Architecture & Trust (15% weight)84 × 0.15 = 12.6
Weighted sum = 14.0 + 23.2 + 9.4 + 12.6
Global SEODiff Score = 59 (D)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
97
Rendering
avg 93
100
Structure
avg 35
44
Schema
avg 9
55
Tech Stack
avg 63

Why charge-spot.tw ranks here

Tech stackWix
RenderingHybrid
Schema coverage2 blocks
Token bloat50×+

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

56/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

47 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

746 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://www.charge-spot.tw
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → zh
  • ✅ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — 首頁 | CHARGESPOT 共享行動電源租借站
  • ✓ og:description — ChargeSPOT TW 是全球首家提供「跨國行動電源租借服務」的共享品牌,自2017年創立以來,已於台灣、日本、香港、澳洲、新加坡與泰國等地設點,打造最完整的國際充電網絡。 用戶可透過 ChargeSPOT App 即時查找附近據點,支援「甲地租借、乙地歸還」,更可進行跨國借還行動電源,解決通勤、外出與旅遊時的臨時充電需求。服務遍布超商、百貨、餐飲與車站等熱門場域,操作快速便利。 我們秉持「以租代買、綠色永續」理念,致力提升電池使用效率、減少電子廢棄物。母公司 INFORICH 已於東京證交所上市,ChargeSPOT 台灣持續推動智慧生活與共享充電的全新體驗。
  • ✓ 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

58/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 →
charge-spot.tw
56
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 10%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type Hybrid

📊 Structure & Information Density Docs

Structure Grade 100/100 — Excellent
Structured Elements 95 elements (34 lists, 17 rows, 44 headers)
Total Words222
Raw Density42.8%

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

66
AI Extractability
High
Crawl Cost
None
Blocklist Risk
Extractability66/100 — AI models can partially extract answers from this page
Crawl CostHigh (100/100) — expensive for AI crawlers to process
Blocklist RiskNone — 0 of 5 AI crawlers blocked

Token Bloat Research

1%
🗑️ 99%
Useful Content (6.8 KB)Bloat (1429.8 KB)
Token Bloat Ratio50×+ — Bloated

Multimodal Readiness

Visual Context46% Optimized for Vision
Image Alt Coverage41 / 89 images have alt text

TDM Rights

TDM-Reservation HeaderNot set
X-Robots-Tag: noaiNot set
💡Your HTML is 1436.6 KB, but only 6.8 KB is text. 1% useful / 99% bloat. AI crawlers have limited context windows (e.g. 128k tokens). This level of bloat (50×+) risks context-window truncation by ChatGPT, Claude, and Gemini. Reduce inline scripts, CSS, hydration payloads, and tracking code.
💡Only 46% of images have alt text. Add descriptive alt attributes so multimodal AI (ChatGPT Vision) can understand your images.

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 99.5% · SNR: 0.00 · Signal: 1740 / Noise: 366018 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…

🔧 Tech Stack

FrameworkWix
AI-Readiness Score55/100
ServerPepyaka
CDN
HTTP Status200
Load Time687 ms
Raw HTML Size1436.6 KB
Visible Text Size6.8 KB

Performance & Speed

47/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

687 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

1710
DOM nodes
1437 KB
HTML payload
Heavy page — consider reducing DOM complexity

🗄️ Cache & CDN

  • ✓ Cache-Control header → private,max-age=0,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
googlesyndication.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

84/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.charge-spot.tw/en_en-sitemap.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

46
internal links
16
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 → zh
  • ✓ 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 56/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

AI-Verified badge for charge-spot.tw
Pending Audit — score below 80 threshold
<a href="https://seodiff.io/radar/domains/charge-spot.tw" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=charge-spot.tw" 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.

🔗 Similar infrastructure Sites

Domains with a similar tech stack, industry, and AI readiness profile to charge-spot.tw. Compare side-by-side.

Domain ACRI AI Score Tech Stack Token Bloat Schema
charge-spot.tw (this site) 56 86 Wix 211.3× 2
puuilo.fi 81 87 Express 4.1× 2 Compare →
stamp-marche.com 81 86 Custom / Proprietary 2.1× 2 Compare →
drifthq.com 81 88 Next.js 3.8× 2 Compare →
pacificpeche.com 81 86 Custom / Proprietary 3.8× 2 Compare →
platinumshop.hu 81 87 Express 2.8× 2 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

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

Reduce Token Bloat
Medium Impact ⏱ 1–2 hrs
Only 0% of your HTML is useful content. AI crawlers waste context window tokens on bloat.
html
<!-- Move inline CSS to external stylesheets -->
<link rel="stylesheet" href="/css/main.css">

<!-- Move inline scripts to external files with defer -->
<script src="/js/app.js" defer></script>

<!-- Remove duplicate navigation blocks -->
<!-- Keep only ONE <nav> in the <header> -->

<!-- Ensure <main> wraps your primary content -->
<main>
  <!-- Your content here — this is what AI sees first -->
</main>
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 Charge-spot?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Charge-spot does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Charge-spot work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Charge-spot."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for charge-spot.tw:

Current Score
86
Projected Score
94
Improvement
+8 pts
Reduce token bloat +5 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 →