AX Rush

Prontezza IA di spacex.com

Misurato sulla home page. Valutazione complessiva: Scarso.

spacex.com

Scarso · 17 controlli superati, 21 avvisi, 11 controlli non superati · 2,3s

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.

Robots.txt

  • /robots.txt not found

    Create a /robots.txt file at your site root. Add User-agent entries for AI crawlers (GPTBot, ClaudeBot, etc.) with Allow: / to grant access.

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.

Sitemap

  • No sitemap found

    Publish an XML sitemap at /sitemap.xml and reference it from robots.txt with: Sitemap: https://your-site.com/sitemap.xml

AI Well-Known

  • 0/5 emerging AI discovery files published

  • ai.txt not found

    Publish /.well-known/ai.txt declaring opt-in/opt-out signals for AI training. See https://site.spawning.ai/spawning-ai-txt for the format.

  • genai.txt not found

    Publish /.well-known/genai.txt declaring your generative-AI usage policy.

  • 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.

Content NegotiationInformativo

  • 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 LicenseInformativo

  • 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.

HTML Rendering

  • Sparse server-rendered content (1 words, 6 chars)

    Render at least the main page content server-side. Many AI crawlers (GPTBot, ClaudeBot, CCBot) do not execute JavaScript and will see only the static HTML.

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

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

  • No semantic HTML landmarks found

    Replace generic <div> structures with semantic tags: <main>, <article>, <header>, <nav>, <footer>. Agents use these to identify the primary content region.

  • No <h1> heading found

    Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.

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">.

  • OpenGraph required tags present (og:title, og:description, og:url, og:type)

  • 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.

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.

  • Only 2/7 security headers present

    Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.

  • No Link header for AI discovery (llms.txt, agent.json)

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

Security.txt

  • /.well-known/security.txt exists

  • Required field "Contact" present

  • 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

  • 2/5 optional fields present

SEO Basics

  • <title> is too short (6 chars): "SpaceX"

    Lengthen the title to 20-70 characters with a clear topic indicator.

  • Meta description is long (209 chars)

    Trim to 70-160 characters; longer descriptions get truncated.

  • No <link rel="canonical"> found

    Add <link rel="canonical" href="https://your-site.com/page"> so agents have an unambiguous URL to cite even when crawled via a redirect or query-string variant.

  • <html lang="en">

  • UTF-8 charset declared

  • Viewport meta present: "width=device-width, user-scalable=1"

TLS / HTTPS

  • Site is served over HTTPS

  • HTTP requests redirect to HTTPS

  • HSTS max-age=63072000

  • HSTS includes subdomains

  • HSTS preload-eligible

Agent AccessInformativo

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

Crawl EfficiencyInformativo

  • Response compressed with gzip

  • Cache validator present (Last-Modified)

  • Conditional request returns 304 Not Modified

  • Homepage size is reasonable (3.4 KB decompressed)