linkbiz.tw 65 C
🛡️ SEO 71 🤖 GEO 69 ⚡ Perf 62 🏗️ Arch 50

linkbiz.tw — Global SEODiff Score 65/100

linkbiz.tw
📊

Among all indexed domains, linkbiz.tw ranks in the top echelon with an ACRI of 90, demonstrating that its content is highly visible to AI systems. Compared to other infrastructure sites (avg score: 57), linkbiz.tw 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. Token bloat registers at 11.6× — acceptable, but reducing inline scripts and redundant markup could yield measurable gains. The site includes 2 schema blocks, providing adequate structured data for basic entity recognition. All major AI bot user-agents (GPTBot, ClaudeBot, CCBot, Google-Extended) are permitted by robots.txt, ensuring broad AI crawler access.

65
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Architecture (50) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 pts
🔬 Automated SEODiff Assessment · Snapshot: Feb 27, 2026 · 📋 API
Does your site score higher than linkbiz.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)71 × 0.25 = 17.8
🤖 AI Readiness / GEO (40% weight)69 × 0.40 = 27.6
⚡ Performance (20% weight)62 × 0.20 = 12.4
🏗️ Architecture & Trust (15% weight)50 × 0.15 = 7.5
Weighted sum = 17.8 + 27.6 + 12.4 + 7.5
Global SEODiff Score = 65 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
100
Structure
avg 36
44
Schema
avg 9
85
Tech Stack
avg 63
🔀
Visibility Delta: Google vs AI
Google (Tranco)
Top 50%+
Rank #700712
-69 pts
Gap
AI (ACRI)
Top 1%
Score 90/100

linkbiz.tw ranks much higher on Google (Tranco Top 50%+) than in AI search (Top 1%). This is the 'Visibility Gap' pattern — implementing the recommendations above can help close the AI gap. ACRI measures technical crawler readiness. Read the methodology →

Why linkbiz.tw ranks here

Tech stackWordPress
RenderingSSR
Schema coverage2 blocks
Token bloat11.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

71/100 25 % of Global Score 🟢 High Confidence

📝 Title Tag

47 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

935 chars
Too long

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://linkbiz-tw.com/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → ja
  • ✗ Hreflang tags
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — LinkBiz 台湾進出会社設立専門サイト
  • ✓ og:description — 台湾(台北、台中、高雄)での会社・法人設立、銀行口座開設、登記住所、資本金送金、国税局面談、ビザ申請、労務、会計、輸出事務など台湾進出に関わる情報を提供しています。 法人設立価格は、日本語サポートを提供している進出支援業界では最低価格で提供しています。(2024年自社調べ) 現地法人と支店と代表者事務所/駐在員事務所の形態の違い、設立の基本的な流れやスケジュール、必要書類、手続き費用、資本金額の決め方、登記住所の決め方、人材の集め方、日本と台湾の労基法の違い、雇用契約や就業規則の作成、法人税、営業税、所得税などの税務で注意すべき点、台湾の領収書(発票)についてなど、進出後気になる点などがありましたらLinkBiz台湾にお任せください。
  • ✗ og:image
  • ✓ 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

69/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 →
linkbiz.tw
65
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 100/100 — Excellent
Structured Elements 68 elements (68 lists, 0 rows, 0 headers)
Total Words155
Raw Density43.9%

🏷️ Schema Health Docs

Organization Schema ✅ Present
Product / Service Schema ⚠️ Not Found
Total Schema Blocks2 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

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

8%
🗑️ 92%
Useful Content (5.0 KB)Bloat (52.5 KB)
Token Bloat Ratio11.6× — Normal

Multimodal Readiness

Visual Context63% Optimized for Vision
Image Alt Coverage19 / 30 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: 91.4% · SNR: 0.09 · Signal: 1267 / Noise: 13431 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
ServerLiteSpeed
CDN
HTTP Status200
Load Time1353 ms
Raw HTML Size57.4 KB
Visible Text Size5.0 KB

Performance & Speed

62/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

1353 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

508
DOM nodes
57 KB
HTML payload
Lean page — fast for bots and users

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✗ CDN cache status
  • ✗ CDN detected

🔬 Tracker Tax

2
tracker scripts
2
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
googletagmanager.comfacebook.net
📐 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

50/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

1
internal links
101
external links
Very few internal links — crawlers may miss important pages

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
linkbiz.tw (this site) 65 90 WordPress 11.6× 2
grupocasalima.com 87 96 WordPress 11.4× 5 Compare →
profitserver.ru 86 90 WordPress 3.8× 2 Compare →
profitserver.net 86 90 WordPress 3.7× 2 Compare →
driphydration.com 86 95 WordPress 1.9× 2 Compare →
safely.co.jp 90 90 WordPress 1.9× 3 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite linkbiz.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 linkbiz.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 8% 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>
📈

Projected Impact

ROI EST.

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

Current Score
90
Projected Score
95
Improvement
+5 pts
Reduce token bloat +5 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