How AI sees it: invisible · preview · 7 critical issues blocking AI agents.
AISO fixEnsure the site serves HTML at the root URL without auth.
AISO fixRemove WAF/CDN rules that block OpenAI's GPTBot crawler and similar AI user agents.
AISO fixPublish /llms.txt at the site root with '# <Project>' + a short summary + H2 sections linking to canonical doc URLs.
AISO fixExpose a public API reference or OpenAPI document at /docs/api, /openapi.json, or an equivalent developer URL so agents can understand callable surfaces.
Deterministic extraction from stored page context: identity, offers, actions, files, trust, and evidence.
No grounded description found.
No structured offer or price evidence found.
No booking, buying, contact, quote, or API path found.
No llms.txt, agents.json, mcp.json, x402.json, profile.json, or offers.json found.
Agents need a stable name, category, and short description before they can explain the page.
Agents cannot recommend, compare, or transact without a grounded offer or price.
Agents need explicit next actions instead of guessing how to engage.
Files such as llms.txt, agents.json, mcp.json, profile.json, and offers.json make the site directly readable.
Paste these into the public agent files your site is missing, then rescan.
# npmjs.com
> Public profile for agent-readable discovery.
Canonical: https://www.npmjs.com/package/@firecrawl/pdf-inspector
Agent-readable schema: aios.agent_readable.v1
## Offers
- Add structured offers.
## Actions
- Add book, buy, quote, contact, or API actions.Every check rolls up into covered, not captured, or planned-only. Click-through rows below stay tied to stored signals only.
Web3 surfaces, Solidity and Rust audit, content quality, and site-wide context intelligence ship via the AISO Web Context Engine plus planned TOOLBOX code-audit workers. Cards below show what each module checks; metrics populate once the context-shard dispatch is enabled for your tier.
Wallet-connect, contract addresses, x402 endpoint health, ENS, chain metadata, exposed ABI and token metadata.
Context Engine - scrape regex + actionsAgent readiness is discovery, metadata, proof, offers, actions, protocols, and safe access together.
Sequential. Most of it auto-generates when you install Agent Link; the scanner verifies the result on the next pass.
The preview above stays visible. The detailed scanner rows, provider evidence, PDF export, and long copy-paste repair prompt are behind a one-time Stripe checkout. Referral attribution is preserved through the signed AISO referral cookie when present.
The detail rows, provider evidence, repair prompt and PDF export are behind a one-time unlock. The preview cards above stay visible.
AISO fixEnsure the homepage and at least one sampled page return HTML.
AISO fixPublish a /robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended and other AI crawlers.
AISO fixDrop 'unsafe-eval' from script-src; refactor any eval/new Function callers.
AISO fixPrioritize: Frequently Asked Questions about AI Search Visibility; AI Search Visibility Glossary: Key Terms Explained.
AISO fixbridge returned HTTP 401
AISO fixbridge returned HTTP 401
AISO fixchild-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixIn Cloudflare → Security → Bots, add rules to allow AI crawler user agents.
AISO fixframe-ancestors 'none'; (or 'self' if same-origin embedding is needed)
AISO fixframe-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixMake the homepage reachable over plain HTTP(S) without auth.
AISO fixAdd /.well-known/ai.txt with your AI/agent policy in RFC9116-style key:value lines or short markdown.
AISO fixPublish /ai/summary.json with name, description, founded, services[], contact, and brand_assets so agents skip HTML scraping.
AISO fixDocument the skills, actions, tools, or capabilities agents can use. Include names, input schemas, output shapes, auth requirements, and whether each action is read-only or writes data.
AISO fixPublish an MCP endpoint or setup guide, then link it from the homepage or llms.txt. Agents should be able to discover tool access without reading human-only docs.
AISO fixstyle-src 'self' 'nonce-<random>'; (drop 'unsafe-inline')
AISO fixworker-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixAdd explicit entity surfaces: about or company page, team or founder page, pricing page, docs or API page.
AISO fixOptional: publish /.well-known/agent.json (A2A or MCP manifest) so agent runtimes can discover capabilities.
AISO fixPublish /ai/faq.json as { faqs: [{ question, answer, source_url }] } so agents can cite your answers verbatim.
AISO fixPublish /ai/service.json as a schema.org Service object describing what you sell, area served, and provider.
AISO fixExpose a crawlable sitemap and stable navigation to docs, pricing, support, API references, and key task pages. Agents need predictable links, not only app-shell buttons.
AISO fixAdd CLI install/use docs when your product can be operated from CI, terminals, or coding agents. Include copy-paste commands and JSON output examples.
AISO fixDocument auth, API keys/OAuth, rate limits, webhooks, SDKs, sandbox/test mode, and status-page behavior so agents can call tools safely.
AISO fixIf the service supports temporary agent visits, publish a Portal manifest at /portal with tool metadata and a call endpoint, then link it from docs and llms.txt.
AISO fixIf the site supports browser-native agent access, publish a WebMCP endpoint or discovery document and link it from developer docs and llms.txt.
AISO fixIf paid agent/API access is supported, document x402 payment flow, supported networks/tokens, payment headers, and facilitator behavior.
AISO fixProvide business_name + area in ScanContext.agntBridge so the bridge can call this lane.
AISO fixIf you launch localised variants (e.g. /es, /de, fr.example.com), add `<link rel="alternate" hreflang="...">` tags pointing at each variant plus `x-default`.
AISO fixProvide social_links in ScanContext.agntBridge so the bridge can call this lane.
AISO fixRun Template Audit, Full Site, or Deep Investigation mode to compare key templates across the site.
AISO fixupgrade-insecure-requests;
{
"schema": "aios.agent_readable.v1",
"name": "npmjs.com",
"url": "https://www.npmjs.com/package/@firecrawl/pdf-inspector",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "npmjs.com",
"profile_url": "https://www.npmjs.com/package/@firecrawl/pdf-inspector",
"tools": [
{
"name": "ask_profile",
"description": "Answer questions using grounded public profile context."
},
{
"name": "get_offers",
"description": "Return structured offers with prices, URLs, and evidence."
},
{
"name": "start_action",
"description": "Open the best booking, buying, quote, contact, or API action."
}
]
}AISO maps llms.txt and WebMCP overlap with Chrome Lighthouse's experimental agentic audits. This is an overlap map, not a Lighthouse pass/fail claim.
Flesch-Kincaid readability, AI-readability, thin pages, duplicate content, keyword stuffing and original-research density.
Sitemap coverage %, scrape markdown quality, crawl-discovered pages, entity knowledge-graph presence, research-synthesized authority and wire-extractor results.
Context Engine - scrape + map + crawl + research