0/100
min 0
AISO SCAN · combined· SCANNED 50D AGO
warp.dev
How AI sees it: invisible · preview · 23 critical issues blocking AI agents.
AISO SCORE0/100Invisible23 critical
How AI sees it: invisible · preview · 23 critical issues blocking AI agents.
AISO fixYour domain is not being cited by any configured AI search platform. Add structured data, publish authoritative content, get listed in roundups + comparison pages.
AISO fixMention the brand at least once like "Warp is a [category] for [audience]" for clean LLM resolution.
AISO fixCite at least one .edu/.gov, Wikipedia, IETF/W3C spec, or tier-1 publication near your flagship claims.
AISO fixAdd headings like '<Product> vs <Competitor>' to comparison content
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.
AISO fixAdd h2-headed sections with 134-167 words of factual content each. Empty marketing pages give LLMs nothing to cite.
AISO fixAdd a /best-X-alternatives or /you-vs-competitor page
AISO fixAdd a FAQ block with ≥5 question/answer pairs using <details>/<summary> or <h3>+<p> patterns. Also mark it up with FAQPage JSON-LD.
AISO fixAdd FAQPage schema with 5-10 high-frequency questions for AI-search retrieval.
AISO fixAdd an HTML <table> with <th>feature</th>/<th>price</th> columns
AISO fixAdd a Person JSON-LD entry for founder/principal author with sameAs links.
AISO fixAdd a glossary page with 5+ defined terms
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
AISO fixPublish JSON-LD with Organization/Service nodes including `audience` and `aggregateRating` properties so LLMs can extract market-fit signals.
AISO fixPublish JSON-LD blocks (`<script type="application/ld+json">`) describing your offer/service, address, and contact methods. Without structured data, delegate agents can't transact on your behalf.
AISO fixPublish Organization JSON-LD with name + url + sameAs for entity association.
AISO fixAdd Pros/Cons sections to comparison and review pages
AISO fixAdd an explicit '<h2>FAQ</h2>' or 'Frequently Asked Questions' section with at least 3 items.
AISO fixscript-src 'self'; default-src 'self';
AISO fixAdd <script type='application/ld+json'> with @type:Organization including name, url, logo, and sameAs (≥3 social profiles).
AISO fixIncrease the sampled-page count to evaluate internal connectivity
AISO fixEvery % / 'X customers' / stat deserves an inline citation link to the origin study or publication.
AISO fixComparative pages can over-index on the competitor name. Rebalance copy so your own brand is the dominant entity per section.
AISO fixBreak paragraphs above 400 words with subheadings, lists, or bolded facts
AISO fixLift on-page signals + internal links for these specific URLs; lower-half SERP positions get fewer clicks AND fewer LLM citations.
AISO fixPrioritize: Frequently Asked Questions about AI Agent Tooling; AI Agent Tooling Glossary: Key Terms Explained.
AISO fixReach out to the listed pages and ask for a link to your apex. Unlinked mentions are the highest-conversion link-building lane.
AISO fixbridge returned HTTP 401
AISO fixbridge returned HTTP 401
AISO fixbase-uri 'none'; (or 'self' if relative URL rewriting is required)
AISO fixAudit reddit.com for the topical/structural signals they have that you don't.
AISO fixUse exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
AISO fixDR 4.0-5.4 means partial AI-search visibility. Focus on high-quality backlinks from DR 50+ sites in your niche, original research, and PR placements.
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 fixAdd a 2–4 sentence paragraph immediately after the H1 summarising what the product is and who it serves.
AISO fixPublish /llms.txt and, when relevant, a .well-known agent/plugin manifest that points agents at docs, APIs, MCP endpoints, and support policies.
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 fixOpen with 'We are ...' / 'Our mission is ...' / 'This is ...' — AI models need explicit entity framing.
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 fixobject-src 'none';
AISO fixBold key statistics, definitions, and claims so AI can cite them
AISO fixUse numbered and bullet lists to expose key facts
AISO fixRestructure paragraphs to 30-120 words each. RAG retrievers favour self-contained spans of this size.
AISO fixMid-tier coverage. Add inline links, "according to X" attributions, or footnote references next to your stats so LLMs can verify and cite the source.
AISO fixAdd explicit entity surfaces: about or company page, team or founder page, pricing page, docs or API page.
AISO fixLong sentences degrade embedding quality. Tighten sentences to ≤ 25 words for clean chunk embeddings.
AISO fixdefault-src 'self';
AISO fixAdd ItemList JSON-LD schema to comparison pages
AISO fixWrap term/definition pairs in <dl><dt>term</dt><dd>def</dd></dl> markup
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 fixIf the homepage surfaces editorial content, include an author byline (Person JSON-LD or 'By <Name>').
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 you intend to expose agentic surfaces, publish a WebMCP manifest at `/.well-known/webmcp.json` with version + entrypoint + tools list.
AISO fixIf paid agent/API access is supported, document x402 payment flow, supported networks/tokens, payment headers, and facilitator behavior.
AISO fixAdd 'founder': [{ @type: Person, name: ... }] to the Organization schema.
AISO fixWe will retry on the next scan. No action needed on your side.
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;
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.
# warp.dev
> Public profile for agent-readable discovery.
Canonical: https://warp.dev/
Agent-readable schema: aios.agent_readable.v1
## Offers
- Add structured offers.
## Actions
- Add book, buy, quote, contact, or API actions.{
"schema": "aios.agent_readable.v1",
"name": "warp.dev",
"url": "https://warp.dev/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "warp.dev",
"profile_url": "https://warp.dev/",
"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."
}
]
}Every check rolls up into covered, not captured, or planned-only. Click-through rows below stay tied to stored signals only.
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.
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 + actionsFlesch-Kincaid readability, AI-readability, thin pages, duplicate content, keyword stuffing and original-research density.
Context Engine - scrape + researchSitemap coverage %, scrape markdown quality, crawl-discovered pages, entity knowledge-graph presence, research-synthesized authority and wire-extractor results.
Context Engine - scrape + map + crawl + researchAgent 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.