Is wellsfargo.com agent ready?
wellsfargo.com is not yet agent ready: it scores 38/100 (grade D) on the w2agent rubric.
Changed since last check
+6 points since the previous check (2026-09-15)
Fixed: Lists and tables for structured info
Category scores
Category breakdown not recorded for this audit.
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✗XML sitemap existsfail
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ✓JSON-LD validpass
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ~Schema.org completenesspartial
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ~Content lengthpartial
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ~Citation readinesspartial
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ✓Structured formspass
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ~Developer portalpartial
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✗UTF-8 charsetfail
- ~Canonical URLspartial
- ✗Mobile viewportfail
- ~Content accessible without JSpartial
- ✓Security headerspass
Score history
- 38/100 · rubric v3.0
- 32/100 · rubric v3.0
- 52/100 · rubric v2.0
- 52/100 · rubric v2.0
- 45/100 · rubric v2.0
- 46/100 · rubric v2.0
- 38/100 · rubric v2.0