mo.gov

Home | MO.gov

AI Agentic Readiness

9 / 30

agentic checks passed
44% readiness - how well this site can be read, trusted and transacted with by AI agents

Last checked
7 Jul 2026

mo.gov is live and passes 9 of 30 agentic-readiness checks (44%). It runs on drupal on nginx over HTTPS.

For AI agents, mo.gov's strongest signals are clean semantic HTML, tidy, crawlable markup, fully indexable pages, and a visually stable layout. Average entity density 38.0% across 1 pages (target >15%).

Its main gaps are text that is hard for agents to extract, no structured tables or lists, no self-contained answer passages, and no Schema.org structured data. The weakest area is Structured data; addressing it first would raise this score the most.

Agent interaction

✓Semantic HTML5 & AccessibilityARIA attributes found for accessibility

✓Clean, Crawlable HTMLPage has substantial text content accessible without JavaScript

✗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 & Responsiveness5/22 images lack explicit width/height

✓Canonical URL StrategySingle canonical tag present (no duplicates)

✓Page Speed: Page SizeLightweight document structure

~Page Speed: Load Blockers6 blocking stylesheets in <head>

Machine extraction

✗Table & List ExtractabilityNo HTML tables found across homepage

~Sentence AtomicityAverage 35% atomic sentences across 1 pages (target 40%+)

✓Entity DensityAverage entity density 38.0% across 1 pages (target >15%)

~Definition PatternsNo definition patterns in the first 2000 characters of content

✗Answer Capsule Pattern0/12 H2 sections have 15-30 word self-contained capsules (0%)

Structured data

✗Schema.org Structured DataNo JSON-LD structured data found across homepage

✗Schema Coverage & DepthNo JSON-LD found - cannot assess schema coverage

✗Speakable SchemaNo JSON-LD found across homepage - cannot assess speakable schema

AI discovery

✗llms.txt FileNo llms.txt file found at https://mo.gov/llms.txt (connection failed)

✗robots.txt for AI CrawlersNo explicit AI crawler rules in robots.txt

✓Sitemap Completeness16 URLs have lastmod dates

✗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 pages lack a usable meta description

✗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 mo.gov'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 mo.gov more agent-ready, in priority order.

1 Add structured tables and lists critical impact medium effort

Present mo.gov's comparison and spec data as real HTML tables and lists agents can extract.

2 Add content freshness signals critical impact medium effort

Refresh and re-date mo.gov's key pages so agents see it as maintained.

3 Add JSON-LD structured data critical impact medium effort

Mark up mo.gov's homepage with Schema.org JSON-LD (Organization, WebSite) an agent can read as facts.

4 Strengthen entity authority (NAP) medium impact low effort

Make mo.gov's name, address and phone consistent and add Organization schema to anchor its identity.

Trust & legitimacy signals

✓Currently activeyes (HTTP 200)

✓Secure (HTTPS)yes

✓Identifiable technologydrupal on nginx

Show your score

Embed this badge on mo.gov - it links to this audit and always shows the latest score.

<a href="https://www.markosweb.com/www/mo.gov/"><img src="https://www.markosweb.com/badge/mo.gov.svg" alt="mo.gov is 44% AI-Ready - MarkosWeb" height="28"></a>

Agentic readiness for mo.gov last checked 7 Jul 2026. Machine-readable: JSON. Method: methodology.