agentic checks passed 44% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
iowarn.org is live and passes 9 of 30 agentic-readiness checks (44%). It runs on cloudflare over HTTPS.
For AI agents, iowarn.org's strongest signals are tidy, crawlable markup, fully indexable pages, a lightweight page, and an efficient render path. Average 43% atomic sentences across 1 pages (target 40%+).
Its main gaps are text that is hard for agents to extract, no canonical URL, no structured tables or lists, and no speakable schema for voice agents. An agent can read iowarn.org'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 & Responsiveness13/13 images lack explicit width/height - the most common cause of layout shift (CLS)
✗Table & List ExtractabilityNo HTML tables found across homepage
✓Sentence AtomicityAverage 43% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 32.5% across 1 pages (target >15%)
~Definition PatternsOnly 1 definition pattern(s) found
~Answer Capsule PatternNo H2 headings found across sampled pages
Structured data
✓Schema.org Structured DataOrganization or LocalBusiness schema found on homepage
✓Schema Coverage & Depth@id linking found - schema types are connected in a graph
✗Speakable SchemaNo SpeakableSpecification schema found across homepage
AI discovery
✗llms.txt FileNo llms.txt file found at https://iowarn.org/llms.txt (HTML page served (not a valid text file))
✗robots.txt for AI CrawlersNo robots.txt file found
✗Sitemap Completenesssitemap.xml does not contain valid XML structure
✗RSS/Atom FeedHomepage does not link to an RSS/Atom feed in <head>
✗Internationalization SignalsNo hreflang alternate links found
✗Content Licensing & AI PermissionsNo ai.txt file found
Trust & transparency
~Entity Authority & E-E-A-TNo phone number 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 SignalNo visible date signals found across homepage (no <time> elements, no JSON-LD dates, no article meta dates)
✓Title & Meta Quality1/1 titles are shorter than 10 or longer than 70 characters
✗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 iowarn.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 iowarn.org more agent-ready, in priority order.
1 Add structured tables and lists critical impactmedium effort
Present iowarn.org's comparison and spec data as real HTML tables and lists agents can extract.
2 Strengthen entity authority (NAP) high impactlow effort
Make iowarn.org's name, address and phone consistent and add Organization schema to anchor its identity.
