wemoscooter.com 71 B
🛡️ SEO 60 🤖 GEO 80 ⚡ Perf 62 🏗️ Arch 76

wemoscooter.com — Global SEODiff Score 71/100

wemoscooter.com
📊

With a solid 80/100 ACRI, wemoscooter.com is well-positioned for AI search — better than 94% of sites in the Radar. Compared to other infrastructure sites (avg score: 57), wemoscooter.com performs above the benchmark, suggesting strong competitive positioning in AI search. Its server-rendered architecture ensures AI crawlers receive complete HTML on first request, a key advantage for extractability. A 9.6× bloat ratio is typical for sites in this tech tier — not wasteful, but streamlining could further boost extractability. Only 1 schema block is present — adding Organization, WebSite, and Breadcrumb schemas would significantly improve structured data coverage. The site maintains an open-door policy for AI crawlers — GPTBot, ClaudeBot, and other major agents are all allowed.

71
B — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (60) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 25, 2026 · 📋 API
Does your site score higher than wemoscooter.com?
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)60 × 0.25 = 15.0
🤖 AI Readiness / GEO (40% weight)80 × 0.40 = 32.0
⚡ Performance (20% weight)62 × 0.20 = 12.4
🏗️ Architecture & Trust (15% weight)76 × 0.15 = 11.4
Weighted sum = 15.0 + 32.0 + 12.4 + 11.4
Global SEODiff Score = 71 (B)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
50
Structure
avg 35
42
Schema
avg 10
85
Tech Stack
avg 64
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #961720
-90 pts
Gap
AI (ACRI)
Top 6%
Score 80/100

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

Why wemoscooter.com ranks here

Tech stackWordPress
RenderingSSR
Schema coverage1 blocks
Token bloat9.6×

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

60/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

63 chars
Too long

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

305 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

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

🌐 Social / OpenGraph

  • ✓ og:title — WeMo Scooter 24H 共享機車
  • ✓ og:description — 手機 App 即可一鍵騎乘共享電動機車,全新二代車款 WeMo Fly 與環島縱貫線同站租還站點新上線,自由選擇「隨租隨還模式」或升級為「包車方案」,日租包車全台最低價 $349!日常通勤、旅遊、商務出差皆可快速租車、抵達目的地!
  • ✓ 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

80/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 →
wemoscooter.com
57
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 0%
0% — Safe 50% 100% — Risk
Status Server-Side Rendered (Safe)
Rendering Type SSR

📊 Structure & Information Density Docs

Structure Grade 50/100 — Fair
Structured Elements 28 elements (28 lists, 0 rows, 0 headers)
Total Words369
Raw Density7.6%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks1 block(s) — Basic (low value for AI)

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.
💡FAQ schema missing. Adding FAQPage schema lets AI models directly extract Q&A pairs for Featured Snippets and chatbot answers.

📐 AI Efficiency Metrics Docs

61
AI Extractability
Low
Crawl Cost
None
Blocklist Risk
Extractability61/100 — AI models can partially 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

10%
🗑️ 90%
Useful Content (9.9 KB)Bloat (85.2 KB)
Token Bloat Ratio9.6× — Normal

Multimodal Readiness

Visual Context75% Optimized for Vision
Image Alt Coverage12 / 16 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

0 Entropy
Poor Token Bloat: High
Noise Ratio: 89.6% · SNR: 0.12 · Signal: 2521 / Noise: 21801 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

FrameworkWordPress
AI-Readiness Score85/100
ServerApache
CDN
HTTP Status200
Load Time1577 ms
Raw HTML Size95.0 KB
Visible Text Size9.9 KB

Performance & Speed

62/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1577 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

458
DOM nodes
95 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

  • ✓ Cache-Control header → max-age=0, no-cache, no-store, must-revalidate
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

2
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

76/100 15 % of Global Score 🟢 High Confidence

🗺️ Sitemap & Robots

  • ✓ Sitemap declared in robots.txt → https://www.wemoscooter.com/sitemap_index.xml
  • ✓ Googlebot allowed
  • ✓ GPTBot allowed
  • ✓ ClaudeBot allowed

🔗 Linking

24
internal links
19
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-hant
  • ✓ 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 57/100. Reach 80+ to unlock the green "AI-Verified" badge. Fix the issues below to improve your score.

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
wemoscooter.com (this site) 57 80 WordPress 9.6× 1
vatabai.ro 57 72 WordPress 9.6× 1 Compare →
pianetadesign.it 57 79 WordPress 9.6× 1 Compare →
increasily.com 57 76 WordPress 9.6× 1 Compare →
1win-skachat-apk.com 57 79 WordPress 9.6× 1 Compare →
artplacer.com 57 77 WordPress 9.6× 1 Compare →
Compare All 5 Similar Sites →
🩹

Remediation Patches

COPY-PASTE

Auto-generated code fixes tailored to wemoscooter.com. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →

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 Wemoscooter?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Wemoscooter does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Wemoscooter work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Wemoscooter."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

If you apply the patches above, here's the estimated improvement for wemoscooter.com:

Current Score
80
Projected Score
86
Improvement
+6 pts
Reduce token bloat +3 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