Blog Tool, Publishing Platform, and CMS – WordPress.org
AI Agentic Readiness
15 / 30
agentic checks passed 64% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
wordpress.org is live and passes 15 of 30 agentic-readiness checks (64%). It runs on wordpress on nginx over HTTPS.
For AI agents, wordpress.org's strongest signals are clean semantic HTML, tidy, crawlable markup, fully indexable pages, and a visually stable layout. Average entity density 27.0% across 1 pages (target >15%).
Its main gaps are no structured tables or lists, few clear definitions, no speakable schema for voice agents, and no content feed. The weakest area is Trust & transparency; addressing it first would raise this score the most.
Agent interaction
✓Semantic HTML5 & AccessibilityARIA attributes found for accessibility
✓Clean, Crawlable HTMLPage has title and meta description
~Extraction Friction ScoreHigh jargon density in opening content
✓Indexability & Snippet EligibilityPages are indexable and snippet-eligible - the precondition for Google AI features is met
✓Layout Stability & ResponsivenessViewport is configured and media declares dimensions - static layout-stability signals look good
✓Canonical URL StrategySingle canonical tag present (no duplicates)
~Page Speed: Page SizeApproximately 649 DOM nodes
~Page Speed: Load Blockers8 blocking stylesheets in <head>
Machine extraction
✗Table & List ExtractabilityNo HTML tables found across homepage
~Sentence AtomicityAverage 32% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 27.0% across 1 pages (target >15%)
✗Definition PatternsOnly 2 definition pattern(s) found
✓Answer Capsule Pattern6/9 H2 sections have 15-30 word self-contained capsules (67%)
Structured data
✓Schema.org Structured DataOrganization or LocalBusiness schema found on homepage
✗Speakable SchemaNo SpeakableSpecification schema found across homepage
AI discovery
✓llms.txt FileNote: Google does not read llms.txt (its AI features rely on normal indexing); this signal serves other AI assistants and carries reduced weight
✓robots.txt for AI CrawlersSitemap URL referenced in robots.txt
✓Sitemap CompletenessSitemap index found, indicating organized sitemap structure
✗RSS/Atom FeedRSS/Atom feed link tag found in homepage <head>
✓Internationalization SignalsSelf-referencing hreflang present on homepage
✗Content Licensing & AI PermissionsNo ai.txt file found
Trust & transparency
✓Entity Authority & E-E-A-TSocial media / sameAs references found on homepage
✗Creator TransparencyCreator visibility is weak on content-like pages
~Methodology TransparencyLittle content-production or review transparency is visible
~AI Assistance DisclosureNo AI-assistance disclosure found on sampled pages (neutral - the engine cannot tell whether AI was used)
~Visible Date Signal3 visible <time> element(s) with datetime attribute found across homepage
✓Title & Meta QualityTitles are present, unique, and well-sized, and pages carry meta descriptions
~Content Freshness SignalsNo JSON-LD date properties (datePublished/dateModified) found across homepage
✗Author & Expert SchemaNo Person schema found across homepage
Every check is a verifiable fact about wordpress.org's live pages. Scoring follows Google Lighthouse agentic-browsing: a fraction of concrete checks, not an invented 0-100.
How to improve for AI agents
The highest-impact changes to make wordpress.org more agent-ready, in priority order.
1 Add structured tables and lists critical impactmedium effort
Present wordpress.org's comparison and spec data as real HTML tables and lists agents can extract.
2 Add content freshness signals high impactlow effort
Refresh and re-date wordpress.org's key pages so agents see it as maintained.
