Saltar al contenido principal

Back to AX Tools

Remediation Guides

Step-by-step instructions for fixing every finding ax-audit reports. Each guide covers one of the 14 weighted checks and explains exactly what to do — with code examples, configuration snippets, and context on why it matters for AI agents.

Create a spec-compliant /llms.txt file with proper headings, blockquotes, sections, links, Content-Type, and an optional /llms-full.txt.

Configure robots.txt for 47+ AI crawlers — explicit User-agent entries, Sitemap directives, and avoiding wildcard blocks.

HTML Rendering9%

Server-render content for AI crawlers that don’t execute JavaScript. Detect SPA shells, semantic landmarks, single H1, alt coverage.

Structured Data9%

Add JSON-LD structured data with schema.org context, @graph arrays, key entity types, and BreadcrumbList navigation.

Set security headers, AI discovery Link headers, and CORS for .well-known resources.

Agent Card (A2A)7%

Create /.well-known/agent.json with required fields, same-origin url, complete skills, protocol version, and optional capabilities.

MCP (Model Context Protocol)7%

Create /.well-known/mcp.json with server metadata, tools with descriptions, resources, Content-Type, and CORS.

Title, meta description, canonical, html lang, charset, viewport, hreflang — the head-tag fundamentals every AI agent uses.

Create /.well-known/security.txt per RFC 9116 with Contact, Expires, and optional fields.

AI meta tags, rel="alternate" / rel="me" links, plus full OpenGraph and Twitter Card completeness.

Create /.well-known/openapi.json with version, info, paths, servers, and proper Content-Type.

Serve over HTTPS, redirect HTTP to HTTPS, configure HSTS with preload + includeSubDomains.

Validate sitemap.xml — XML shape, urlset / sitemapindex, lastmod coverage and freshness, 50k URL limit.

AI Well-Known3%

Emerging AI discovery files: ai.txt (Spawning), genai.txt, ai-plugin.json, agents.json (Wildcard), nlweb.json (Microsoft).