WordPress.org holds a Global SEODiff Score of 69, placing it in the upper-middle tier of technical SEO performance, though its ACRI Grade of D (54) indicates significant room for improvement in content quality and user intent alignment. As a leading open-source content management system (CMS) and developer platform, the site serves a global technical audience, yet its low Content Integrity Score (35) and Retrieval Robustness (47) suggest that core content—particularly around documentation, developer resources, and cookie policies—is not effectively structured or surfaced for search engines or users. Despite strong architectural foundations, including a well-linked internal structure and declared sitemap, the site struggles with semantic clarity and content relevance.
The site demonstrates strong technical readiness: it scores 84 in Architecture, with 59 internal links, 18 external references, and full HSTS/CSP support. It allows access to key AI crawlers (GPTbot, Claudebot, CCBot, Google Extended), and has no `noai` meta tag, indicating openness to AI indexing. However, technical efficiency is hampered by a high token bloat ratio (32.0x) and low useful text density (5418 bytes out of 173KB HTML), suggesting excessive non-semantic markup and boilerplate code. While TTFB is acceptable at 832ms, the large HTML payload and minimal word count (563) undermine content depth and search visibility.
Architecturally, WordPress.org leverages a robust internal link structure and has declared a sitemap, but structured data is underutilized, with only minimal schema (Organization, Website) and no Article, FAQ, or Breadcrumb markup. This limits rich snippet opportunities and semantic enrichment. The low Semantic Structure Score (61) and AI Trust Score (53.5) reflect weak entity coherence and inconsistent content-to-intent mapping. To elevate visibility, the site should prioritize reducing token bloat, enriching core content with structured data, and improving content integrity through clearer topic modeling and entity coverage.
🧮 Score Transparency — How is this calculated?
📊 ACRI Sub-Scores (AI Readiness Detail)
wordpress.org has balanced Google and AI visibility — both rank roughly in the same tier. ACRI measures technical crawler readiness. Read the methodology →
Why wordpress.org ranks here
Fastest improvements
- Reduce token bloat (navigation/footer/code) so agents reach your main content faster (see Token Bloat).
- Create an
llms.txtfile 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 →
⚠️ Crawl Failed: Anti-Bot Protection Detected
infrastructure_rate_limit
The scores below may not reflect actual site quality. The crawler received a challenge page instead of real content.
Traditional SEO
67/100 25 % of Global Score 🟢 High Confidence📝 Title Tag
Optimal range: 30–60 characters for SERP display.
📋 Meta Description
Optimal range: 120–160 characters for snippet control.
🔤 Heading Hierarchy
- ✓ Exactly 1 <h1> tag — found 1
- ✓ Has <h2> headings — found 9
- ✓ <h2> not before <h1>
🔍 Indexability
- ✓ Canonical tag present →
https://wordpress.org/ - ✓ No noindex directive
- ✓ Meta viewport set
- ✓ HTML lang attribute →
en-US - ✅ Hreflang tags
- ✓ Googlebot allowed by robots.txt
🌐 Social / OpenGraph
- ✓ og:title — Blog Tool, Publishing Platform, and CMS - WordPress.org
- ✓ og:description — Open source software which you can use to easily create a beautiful website, blog, or app.
- ✓ 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
50/100 40 % of Global Score 🟢 High ConfidenceThis pillar aggregates citation share, hallucination risk, bot access, schema health, and content extractability. The individual diagnostic sections below contribute to this score.
Is AI lying about your brand? This panel measures how likely LLMs are to hallucinate facts when extracting information from your page.
🤖 Bot Access Matrix
📊 Structure & Information Density Docs
🏷️ Schema Health Docs
Schema Coverage Map
📐 AI Efficiency Metrics Docs
Token Bloat Research
Multimodal Readiness
TDM Rights
🔥 Structural Entropy Check Research
🔬 AI-Crawler Simulation
See your website the way AI crawlers do. CSS stripped, structure labeled, content chunked.
Toggle to "AI Agent View" to see what GPTBot, ClaudeBot, and other AI crawlers actually extract from this page.
AI Answer Preview
NEWSee how AI models summarize your site. Left: your actual content. Right: what the LLM extracts and says about you.
The LLM Interpretation
AI-VERIFIEDSEODiff AI analyzed the extracted content of wordpress.org 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.
🔧 Tech Stack
Performance & Speed
68/100 20 % of Global Score 🟢 High Confidence⏱️ Time to First Byte
Google considers <200 ms "good". AI crawlers may have even shorter timeouts.
📦 Page Weight
DOM nodes
HTML payload
🗄️ Cache & CDN
- ✗ Cache-Control header
- ✗ CDN cache status
- ✗ CDN detected
🔬 Tracker Tax
tracker scripts
third-party domains
token overhead
📐 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
85/100 15 % of Global Score 🟢 High Confidence🗺️ Sitemap & Robots
- ✓ Sitemap declared in robots.txt →
https://wordpress.org/sitemap.xml - ✓ Googlebot allowed
- ✓ GPTBot allowed
- ✓ ClaudeBot allowed
🔗 Linking
internal links
external links
🔒 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 is currently blocking AI crawlers. Unblock them and rescan to earn your AI-Verified badge.
<a href="https://seodiff.io/radar/domains/wordpress.org" rel="noopener"><img src="https://seodiff.io/api/v1/badge?domain=wordpress.org" 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.
� Deep Crawl Analysis 129 pages · Deep-10
| Page | Type | ACRI | Token Bloat | Words | Status |
|---|---|---|---|---|---|
| other | 76 | 9.0× | 693 | ✓ | |
| other | 76 | 7.4× | 861 | ✓ | |
| pricing | 67 | 10.3× | 3632 | 💰 Pricing | |
| other | 66 | 15.7× | 8523 | ✓ | |
| other | 66 | 13.2× | 3948 | ✓ | |
| other | 66 | 15.6× | 2571 | ✓ | |
| other | 66 | 13.5× | 6910 | ✓ | |
| other | 66 | 14.4× | 4466 | ✓ | |
| other | 66 | 15.8× | 615 | ✓ | |
| product | 66 | 13.4× | 6998 | ✓ | |
| other | 66 | 14.4× | 808 | ✓ | |
| other | 66 | 15.4× | 8300 | ✓ | |
| other | 66 | 9.8× | 222 | ✓ | |
| other | 66 | 13.9× | 8797 | ✓ | |
| other | 66 | 13.4× | 9143 | ✓ | |
| other | 66 | 14.2× | 7757 | ✓ | |
| other | 66 | 13.9× | 6988 | ✓ | |
| other | 66 | 15.5× | 1272 | ✓ | |
| other | 66 | 13.3× | 5193 | ✓ | |
| other | 66 | 13.7× | 4876 | ✓ |
| Path | Pages | Avg ACRI | Ghost % | Bloat | Top Issue |
|---|---|---|---|---|---|
| /about/ | 14 | 46 | 0% | 161.0× | High JS Bloat |
| /download/ | 8 | 50 | 0% | 350.7× | High JS Bloat |
| /enterprise/ | 4 | 51 | 0% | 69.7× | High JS Bloat |
| /education/ | 3 | 49 | 0% | 85.9× | High JS Bloat |
| /data-liberation/ | 2 | 41 | 0% | 143.1× | High JS Bloat |
| /variety-3/ | 1 | 37 | 0% | 14.5× | High JS Bloat |
| /careers/ | 1 | 0 | 0% | 0.0× | Low AI Readiness |
| /cnn/ | 1 | 47 | 0% | 9.4× | High JS Bloat |
| /sun/ | 1 | 47 | 0% | 9.5× | High JS Bloat |
| /ted/ | 1 | 37 | 0% | 11.4× | High JS Bloat |
| /cnn-2/ | 1 | 37 | 0% | 14.4× | High JS Bloat |
| /community-photo-2/ | 1 | 66 | 0% | 13.4× | High JS Bloat |
| /showcase_thumb_b/ | 1 | 66 | 0% | 15.5× | High JS Bloat |
| /b-2/ | 1 | 66 | 0% | 12.8× | High JS Bloat |
| /logo-people/ | 1 | 47 | 0% | 9.8× | High JS Bloat |
Scores update automatically each month. Create a free account for on-demand re-crawls (3/month free).
🔌 API Access
Pull this data programmatically. All sub-page metrics are available via our public API.
curl https://seodiff.io/api/v1/deep10/domain/wordpress.orgGet your free API key — 100 requests/month included.
🔗 Similar developer Sites
Domains with a similar tech stack, industry, and AI readiness profile to wordpress.org. Compare side-by-side.
| Domain | ACRI | AI Score | Tech Stack | Token Bloat | Schema | |
|---|---|---|---|---|---|---|
| wordpress.org (this site) | 31 | 82 | WordPress | 32.3× | 1 | — |
| corazonxltallasgrandes.es | 56 | 79 | WordPress | 27.0× | 1 | Compare → |
| blog.prezzoforte.it | 56 | 85 | WordPress | 38.6× | 1 | Compare → |
| saveti.bg | 56 | 80 | WordPress | 23.9× | 1 | Compare → |
| irapture.net | 56 | 81 | WordPress | 20.8× | 1 | Compare → |
| perio.org | 56 | 81 | WordPress | 44.1× | 1 | Compare → |
📊 Semantic Share of Voice
How often would an AI cite wordpress.org 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-PASTEAuto-generated code fixes tailored to wordpress.org. Copy and paste these into your codebase to improve AI visibility. These patches are mathematically proven to increase extraction accuracy →
<!-- 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>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Wordpress?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Add your answer here — describe what Wordpress does in 1-2 sentences."
}
},
{
"@type": "Question",
"name": "How does Wordpress work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Explain the key features and how users interact with Wordpress."
}
}
]
}
</script>
Projected Impact
ROI EST.If you apply the patches above, here's the estimated improvement for wordpress.org:
*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 →