agentic checks passed 55% readiness - how well this site can be read, trusted and transacted with by AI agents
Last checked
zacks.com is live and passes 14 of 30 agentic-readiness checks (55%). It runs on webgenerator on Apache over HTTPS.
For AI agents, zacks.com's strongest signals are tidy, crawlable markup, fully indexable pages, a visually stable layout, and a clear canonical URL. Approximately 2477 DOM nodes - consider simplifying.
Its main gaps are no speakable schema for voice agents, no llms.txt for agent discovery, no sitemap, and no content feed. An agent can read zacks.com'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 & AccessibilityOnly 67% 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 & 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 2477 DOM nodes - consider simplifying
✓Table & List Extractability28 definition list(s) found
✓Sentence AtomicityAverage 58% atomic sentences across 1 pages (target 40%+)
✓Entity DensityAverage entity density 47.9% across 1 pages (target >15%)
✓Definition PatternsGlossary or definition list structure detected
~Answer Capsule Pattern5/20 H2 sections have 15-30 word self-contained capsules (25%)
Structured data
✓Schema.org Structured DataOrganization or LocalBusiness schema found on homepage
~Schema Coverage & DepthArticle schema missing or has fewer than 2 key properties
✗Speakable SchemaNo SpeakableSpecification schema found across homepage
AI discovery
✗llms.txt FileNo llms.txt file found at https://zacks.com/llms.txt (connection failed)
~robots.txt for AI CrawlersNo explicit AI crawler rules in robots.txt
✗Sitemap CompletenessNo sitemap.xml found
✗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 Transparency1/1 sampled pages provide clear visible creator attribution
✗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 zacks.com'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 zacks.com more agent-ready, in priority order.
1 Add content freshness signals high impactlow effort
Refresh and re-date zacks.com's key pages so agents see it as maintained.
2 Enhance author and expert schema critical impactmedium effort
Add Person/author schema with credentials on zacks.com to strengthen expertise signals.
