Online College for Working Adults | University of Phoenix
AI Agentic Readiness
9 / 30
agentic checks passed 53% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
phoenix.edu is live and passes 9 of 30 agentic-readiness checks (53%). It runs on Apache over HTTPS.
For AI agents, phoenix.edu's strongest signals are tidy, crawlable markup, fully indexable pages, a clear canonical URL, and an efficient render path. 5 critical third-party domains in startup path.
Its main gaps are no speakable schema for voice agents, no content feed, no language/locale signals, and no stated AI-use permissions. The weakest area is Structured data; addressing it first would raise this score the most.
Agent interaction
~Semantic HTML5 & AccessibilityOnly 79% of images have alt text
✓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 & Responsiveness49/84 images lack explicit width/height - the most common cause of layout shift (CLS)
✓Canonical URL StrategySingle canonical tag present (no duplicates)
~Page Speed: Page SizeApproximately 2788 DOM nodes - consider simplifying
✓Page Speed: Load Blockers5 critical third-party domains in startup path
Machine extraction
~Table & List ExtractabilityNo HTML tables found across homepage
✓Sentence AtomicityAverage 45% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 36.4% across 1 pages (target >15%)
~Definition PatternsNo definition patterns in the first 2000 characters of content
~Answer Capsule Pattern6/16 H2 sections have 15-30 word self-contained capsules (38%)
Structured data
~Schema.org Structured DataMissing Organization or LocalBusiness schema across homepage
~Schema Coverage & DepthArticle schema missing or has fewer than 2 key properties
✗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 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-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 SignalNo visible date signals found across homepage (no <time> elements, no JSON-LD dates, no article meta dates)
✓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 phoenix.edu'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 phoenix.edu more agent-ready, in priority order.
1 Add structured tables and lists high impactlow effort
Present phoenix.edu's comparison and spec data as real HTML tables and lists agents can extract.
