agentic checks passed 57% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
openid.net is live and passes 12 of 30 agentic-readiness checks (57%). It runs on all on Apache over HTTPS.
For AI agents, openid.net's strongest signals are tidy, crawlable markup, fully indexable pages, a visually stable layout, and a clear canonical URL. Approximately 1036 DOM nodes.
Its main gaps are text that is hard for agents to extract, no structured tables or lists, few clear definitions, and no speakable schema for voice agents. An agent can read openid.net's content but has little machine-readable way to discover it - closing the AI discovery gap would be the fastest lift.
Agent interaction
~Semantic HTML5 & AccessibilityMissing lang attribute on <html> tag
✓Clean, Crawlable HTMLPage has title and meta description
✗Extraction Friction ScoreFew pages have voice-friendly lead paragraphs
✓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 1036 DOM nodes
~Page Speed: Load Blockers31 blocking stylesheets in <head>
Machine extraction
✗Table & List ExtractabilityNo HTML tables found across homepage
✓Sentence AtomicityAverage 46% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 55.5% across 1 pages (target >15%)
✗Definition PatternsNo definition patterns found
~Answer Capsule PatternNo H2 headings found across sampled pages
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 CrawlersNo explicit AI crawler rules in robots.txt
~Sitemap CompletenessNo lastmod dates in sitemap
✗RSS/Atom FeedRSS/Atom feed link tag found in homepage <head>
✗Internationalization SignalsNo hreflang alternate links found
✗Content Licensing & AI PermissionsNo ai.txt file found
Trust & transparency
✓Entity Authority & E-E-A-TSocial media / sameAs references found on homepage
~Creator TransparencyVisible authorship is present on some content but inconsistent
~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 SignalOnly machine-readable date signals were found; users still do not see a visible published or updated date
✓Title & Meta QualityTitles are present, unique, and well-sized, and pages carry meta descriptions
~Content Freshness SignalsNo <time> elements found in content areas across homepage
✗Author & Expert SchemaNo Person schema found across homepage
Every check is a verifiable fact about openid.net'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 openid.net more agent-ready, in priority order.
1 Add structured tables and lists critical impactmedium effort
Present openid.net's comparison and spec data as real HTML tables and lists agents can extract.
