tw.creativecommons.net 66 C
🛡️ SEO 37 🤖 GEO 79 ⚡ Perf 74 🏗️ Arch 70

tw.creativecommons.net — Global SEODiff Score 66/100

tw.creativecommons.net
📊

The AI-Readiness profile for tw.creativecommons.net is strong: an ACRI of 70/100 places it ahead of 67% of domains in the index. Within the developer vertical, this places tw.creativecommons.net above the industry average of 57 —, 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. The token bloat ratio sits at a lean 2.5×, meaning the ratio of code to visible content is efficient — crawlers spend their token budget on actual information. 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.

66
C — Global SEODiff Score
Comprehensive search visibility assessment
Strong foundations, but Traditional SEO (37) is your bottleneck.
🎯 Top Fix: Add HSTS header → +2 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 tw.creativecommons.net?
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)37 × 0.25 = 9.2
🤖 AI Readiness / GEO (40% weight)79 × 0.40 = 31.6
⚡ Performance (20% weight)74 × 0.20 = 14.8
🏗️ Architecture & Trust (15% weight)70 × 0.15 = 10.5
Weighted sum = 9.2 + 31.6 + 14.8 + 10.5
Global SEODiff Score = 66 (C)
📊 ACRI Sub-Scores (AI Readiness Detail)
100
Bot Access
avg 92
100
Rendering
avg 93
32
Structure
avg 35
2
Schema
avg 9
85
Tech Stack
avg 63

Why tw.creativecommons.net ranks here

Tech stackWordPress
Industrydeveloper
RenderingSSR
Schema coverage1 blocks
Token bloat2.5×

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

37/100 25 % of Global Score 🟡 Medium Confidence

📝 Title Tag

35 chars
Good length

Optimal range: 30–60 characters for SERP display.

📋 Meta Description

0 chars
Missing

Optimal range: 120–160 characters for snippet control.

🔤 Heading Hierarchy

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

🔍 Indexability

  • ✓ Canonical tag present → https://tw.creativecommons.net/
  • ✓ No noindex directive
  • ✓ Meta viewport set
  • ✓ HTML lang attribute → en-US
  • ➖ Hreflang tags — N/A (single language site)
  • ✓ Googlebot allowed by robots.txt

🌐 Social / OpenGraph

  • ✓ og:title — Creative Commons 台灣 - CC Taiwan
  • ✓ og:description — 什麼是 CC 授權? 其全名為 “Creative Commons”,呈現創作與使用兩者一體的概念。透過眾人自願共享智慧成果,讓文化資源自由流通、累積,並且激激盪出更多的創作。更用創作激盪更多的創作,以發揮創作更大價值的流通。CC 授權採「部分權利保留」,由著作人設計授權條件,將著作開放公眾使用,不限制人、時、地,對所有人有效的開放授權。 四個授權要素     六種授權條款 以四個授權要素,組成六種授權條款,以下為各條款之使用條件簡述:   姓名標示 本授權條款允許使用者重製、散布、傳輸以及修改著作(包括商業性利用),惟使用時必須按照著作人或授權人所指定的方式,表彰其姓名。 姓名標示-相同方式分享 授權條款允許使用者對授權者的著作進行重製、散佈、傳輸及修改著作(包括商業與非商業性利用),唯使用時必須按照授權者指定的方式表彰其姓名,並且產出之新創著作也必須採用相同的授權條款釋出。   姓名標示-禁止改作 本授權條款允許使用者重製、散布、傳輸著作(包括商業與非商業性利用),但不得修改該著作。使用時必須按照授權者指定的方式表彰其姓名。 姓名標示-非商業性 本授權條款允許使用者重製、散布、傳輸以及修改著作,但不得為商業目的之使用。使用時必須按照授權者指定的方式表彰其姓名。 姓名標示-非商業性-相同方式分享 本授權條款允許使用者重製、散布、傳輸以及修改著作,但不得為商業目的之使用。若使用者修改該著作時,必須按照授權者所指定的方式來散布該衍生作品,並且將產出之新創著作採用相同的授權條款釋出。 姓名標示-非商業性-禁止改作 本授權條款為六個主要授權條款中限制最多者。僅允許使用者在下載授權者的著作之後,依原狀態分享出去。使用者必須按照授權者指定的方式表彰其姓名,但不得對著作進行任何方式的改變,或為商業目的之使用。 創作自己的 CC 授權 您可以根據需求自行挑選適合的授權條款釋出你的作品。點選 「 CC 你的作品」,即可以透過 Creative Commons 的授權精靈來選擇適合的授權條款哦!     使用創用 CC 授權的素材   作為一個使用者,透過清楚標示於作品上的創用 CC 授權標章,您可以知道創作者對該作品的使用要求與限制,以合法且合於創作者意思的方式適當地使用該作品。 點選「馬上搜尋 CC 」,即可以直接選擇使用 CC 授權的素材網站唷!   原中央研究院「台灣創用 CC 計畫」 「台灣創用 … Read More "Creative Commons 台灣"
  • ✓ 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

79/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 developer sector, hikkoshizamurai.jp (ACRI: 88) 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 →
tw.creativecommons.net
55
Your ACRI Score
88
Industry Peer ACRI
AI models prioritize pages with strong semantic structure and schema coverage. hikkoshizamurai.jp has schema coverage of 5 blocks and uses Custom / Proprietary. 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 32/100 — Low
Structured Elements 33 elements (33 lists, 0 rows, 0 headers)
Total Words1096
Raw Density3.0%
💡Low structure score (32/100). Your content appears as a wall of text with few structured HTML elements. You have 33 list items, 0 table rows, 0 table headers. Convert features into <ul> lists and data into <table> elements to help AI models extract structured information.

🏷️ Schema Health Docs

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

Schema Coverage Map

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

📐 AI Efficiency Metrics Docs

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

40%
🗑️ 60%
Useful Content (40.8 KB)Bloat (60.9 KB)
Token Bloat Ratio2.5× — Lean

Multimodal Readiness

Visual Context100% Optimized for Vision
Image Alt Coverage11 / 11 images have alt text

TDM Rights

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

🔥 Structural Entropy Check Research

62 Entropy
Fair Token Bloat: Medium
Noise Ratio: 59.9% · SNR: 0.67 · Signal: 10434 / Noise: 15599 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
Servercloudflare
CDNcloudflare
HTTP Status200
Load Time949 ms
Raw HTML Size101.7 KB
Visible Text Size40.8 KB

Performance & Speed

74/100 20 % of Global Score 🟢 High Confidence

⏱️ Time to First Byte

949 ms
Slow — bots may time out or deprioritise

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

📦 Page Weight

397
DOM nodes
102 KB
HTML payload
Moderate weight — acceptable for most scenarios

🗄️ Cache & CDN

  • ✗ Cache-Control header
  • ✓ CDN cache status → DYNAMIC
  • ✓ CDN detected → cloudflare

🔬 Tracker Tax

1
tracker scripts
1
third-party domains
0.0%
token overhead
Minimal tracker load — clean signal for bots
google-analytics
📐 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

70/100 15 % of Global Score 🟡 Medium Confidence

🗺️ Sitemap & Robots

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

🔗 Linking

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

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

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

Domain ACRI AI Score Tech Stack Token Bloat Schema
tw.creativecommons.net (this site) 55 70 WordPress 2.5× 1
biltmore.com 80 90 WordPress 4.3× 1 Compare →
aronia-charlottenburg.ro 80 90 WordPress 7.6× 1 Compare →
randstad.es 80 88 WordPress 4.9× 4 Compare →
coveti.com 80 88 WordPress 9.6× 2 Compare →
kombuchakamp.com 80 87 WordPress 5.1× 6 Compare →
Compare All 5 Similar Sites →

📊 Semantic Share of Voice

How often would an AI cite tw.creativecommons.net 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 tw.creativecommons.net. 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": "Creativecommons",
  "url": "https://tw.creativecommons.net",
  "logo": "https://tw.creativecommons.net/wp-content/themes/cc-chapter/images/favicon/apple-icon-57x57.png",
  "sameAs": []
}
</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 Creativecommons?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add your answer here — describe what Creativecommons does in 1-2 sentences."
      }
    },
    {
      "@type": "Question",
      "name": "How does Creativecommons work?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Explain the key features and how users interact with Creativecommons."
      }
    }
  ]
}
</script>
📈

Projected Impact

ROI EST.

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

Current Score
70
Projected Score
79
Improvement
+9 pts
Add Organization schema +6 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 →