AX Rush

AI readiness of chase.com

Measured on the home page. Overall grade: Poor.

chase.com

Poor · 27 passing checks, 19 warnings, 12 failures · 3.7s

ax-audit@3.6.0

LLMs.txt

  • /llms.txt not found

    Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.

Agent Card (A2A)

  • /.well-known/agent.json not found

    Create a /.well-known/agent.json file following the A2A (Agent-to-Agent) protocol. It should include name, description, url, and skills fields describing your site's capabilities.

OpenAPI Spec

  • /.well-known/openapi.json not found

    Create a /.well-known/openapi.json file with your API specification following the OpenAPI 3.x standard. See https://swagger.io/specification/ for the spec.

MCP (Model Context Protocol)

  • /.well-known/mcp.json not found

    Create a /.well-known/mcp.json file describing your MCP server configuration. Include name, description, tools, and version fields. See https://modelcontextprotocol.io for the spec.

Content NegotiationInformational

  • Homepage does not serve Markdown via content negotiation

    Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by ~80% vs HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.

  • No <link rel="alternate" type="text/markdown"> fallback found on the homepage

    If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.

RSL LicenseInformational

  • No RSL license discovery found

    Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.

Structured Data

  • No JSON-LD structured data found

    Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.

Meta Tags

  • No AI meta tags (ai:*) found

    Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.

  • No rel="alternate" link to llms.txt in HTML

    Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">

  • No rel="alternate" link to agent.json in HTML

    Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent.json" title="Agent Card">

  • No rel="me" identity links found

    Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.

  • No OpenGraph meta tags found

    Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.

  • No Twitter Card meta tags found

    Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.

AI Well-Known

  • 2/5 emerging AI discovery files published

  • ai.txt present at /.well-known/ai.txt

  • genai.txt present at /.well-known/genai.txt

  • ai-plugin.json not found

    Publish /ai-plugin.json (legacy ChatGPT plugin manifest). Schema: name_for_model, description_for_model, api.url. Still consumed by some agents.

  • agents.json not found

    Publish /agents.json describing your site as a callable agent (OpenAgents / Wildcard emerging spec). Includes name, description, and operations[].

  • nlweb.json not found

    Publish /.well-known/nlweb.json (Microsoft NLWeb) so agents can interact with the site through a natural-language interface.

Security.txt

  • /.well-known/security.txt exists

  • Required field "Contact" missing (RFC 9116)

    Add "Contact:" to your security.txt. Use a mailto: or https: URI, e.g., Contact: mailto:security@example.com

  • Required field "Expires" missing (RFC 9116)

    Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z

  • No optional fields (Canonical, Preferred-Languages, Policy, etc.)

    Consider adding Canonical: (canonical URL), Preferred-Languages: (e.g., en), and Policy: (link to your security policy).

Robots.txt

  • /robots.txt exists

  • No core AI crawlers explicitly configured

    Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.

  • Sitemap directive present

  • No Content-Signal directive found (optional)

    Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train. Generate yours at contentsignals.org.

  • 0/48 known AI crawlers have explicit rules

    Add explicit User-agent entries for more AI crawlers to maximize discoverability.

HTML Rendering

  • Server-rendered content detected (963 words, 6064 chars of visible text)

  • Low text-to-markup ratio (1.9%)

    A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.

  • Empty SPA mount point detected: #root

    The static HTML contains an empty SPA mount node, which means content is rendered only client-side. Enable SSR/SSG so the initial HTML response includes meaningful content.

  • Semantic landmarks present (main, header, footer, nav)

  • Single <h1> heading: "Chase home page"

  • 2/2 <img> tags have alt attributes

HTTP Headers

  • Missing critical header: X-Content-Type-Options

    Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.

  • 5/7 security headers present

  • Link header present but does not reference AI discovery files

    Add AI discovery entries to your Link header: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent.json>; rel="alternate"; type="application/json"

TLS / HTTPS

  • Site is served over HTTPS

  • HTTP requests redirect to HTTPS

  • HSTS max-age=31536000

  • HSTS does not include subdomains

    Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.

  • HSTS lacks the preload directive

    Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.

Sitemap

  • Sitemap located: https://www.chase.com/video/sitemap.xml

  • Content-Type is XML (text/xml)

  • 321 URL(s) declared

  • Only 0% of URLs have <lastmod>

    Add a <lastmod>YYYY-MM-DD</lastmod> child to each <url>. AI agents use lastmod to prioritize re-fetching.

SEO Basics

  • <title> length 63 chars: "Credit Card, Mortgage, Banking, Auto | Chase Online | Chase.com"

  • Meta description length 134 chars

  • 3 <link rel="canonical"> tags (must be exactly 1)

    Keep a single canonical link per page. Multiple canonical hints are ignored by agents and search engines.

  • <html lang="en-US">

  • UTF-8 charset declared

  • Viewport meta present: "width=device-width, initial-scale=1"

Agent AccessInformational

  • All 8 core AI crawler user-agents receive equivalent responses

Crawl EfficiencyInformational

  • Response compressed with gzip

  • Cache validator present (ETag)

  • Conditional request returns 304 Not Modified

  • Homepage size is reasonable (306.8 KB decompressed)