0/100
min 0
AISO SCAN · combined· SCANNED 35D AGO
aiso.tools
How AI sees it: invisible · preview · 10 critical issues blocking AI agents.
AISO SCORE0/100Invisible10 critical
How AI sees it: invisible · preview · 10 critical issues blocking AI agents.
AISO fixSend a Content-Security-Policy response header (or <meta http-equiv> tag) so directive strictness can be scored.
AISO fixBuild cited-by signals: domain authority (OpenPageRank), placements on high-DR publications (TechCrunch, ProductHunt, etc), patent/news mentions. Authority is the #1 driver of LLM citations.
AISO fixMost claims lack inline sources within 200 chars. LLMs heavily discount uncited statistics. Add anchor links to primary sources, "according to" attributions, or numeric footnote refs.
AISO fixAdd a /best-X-alternatives or /you-vs-competitor page
AISO fixAdd an HTML <table> with <th>feature</th>/<th>price</th> columns
AISO fixStructured data (Organization, LocalBusiness, FAQ, Article) is the strongest GEO signal — LLMs prefer schema-typed entities.
AISO fixAdd Pros/Cons sections to comparison and review pages
AISO fixAdd Review and/or AggregateRating JSON-LD with reviewer + ratingValue + datePublished. LLMs cite review summaries when ranking peers in comparison answers.
AISO fixIncrease the sampled-page count to evaluate internal connectivity
AISO fixLow review count is a weak trust signal. AI agents prefer entities with sustained review volume.
AISO fixProfiles linked from your site that don't load fail trust checks.
AISO fixPrioritize: Frequently Asked Questions about AI Agent Tooling.
AISO fixBreak paragraphs above 400 words with subheadings, lists, or bolded facts
AISO fixMissing: content-security-policy, x-xss-protection.
AISO fixAdd a 2–4 sentence paragraph immediately after the H1 summarising what the product is and who it serves.
AISO fixPublish an AGENTS.md at your repo or web root listing the skills, conventions, and tools agents should use when working with your codebase or service.
AISO fixAI agents performing 'delegate' tasks need clear actionable CTAs (book / order / sign up).
AISO fixAdd a TL;DR sentence or '<Brand> is a <category> that …' lead at the top
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
AISO fixAim for 134-167 words per h2-bounded section — zubair's empirical citability optimum. Long sections get truncated; short ones don't carry enough signal.
AISO fixAdd 'according to', 'source:', or numeric footnote references. LLMs cite content that points at primary sources.
AISO fixRestructure paragraphs to 30-120 words each. RAG retrievers favour self-contained spans of this size.
AISO fixRemove agent-hostile signals: prompt-injection patterns, broken links, deceptive cloaking, robots conflicts. Agents discount hosts that look unsafe to act on.
AISO fixAdd explicit entity surfaces: team or founder page, pricing page, docs or API page.
AISO fixAim for 3-11 words of context-bearing description per non-decorative image.
AISO fixAdd an explicit '<h2>FAQ</h2>' or 'Frequently Asked Questions' section with at least 3 items.
AISO fixAdd more question-shaped h2/h3 headings — they map directly to LLM-extracted Q→A pairs.
AISO fixWrap term/definition pairs in <dl><dt>term</dt><dd>def</dd></dl> markup
AISO fixOG image drives social previews and is referenced by some AI image-aware crawlers.
AISO fixSee dimension details for remediation guidance.
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 fixAdd `serviceType` (e.g. 'AI search optimization') or `suitableForBusinessFunction` to your Service/Product node so LLMs categorise the offering correctly.
AISO fixSites without an archive history are weaker citation candidates for LLMs that prefer aged sources.
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 fixConfigure TINYFISH_API_KEY and BRAVE_SEARCH_API_KEY to cross-check rendered fetchability and search-index visibility.
AISO fixWe will retry on the next scan. No action needed on your side.
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 fixRun Template Audit, Full Site, or Deep Investigation mode to compare key templates across the site.
AISO fixPages about prices, versions, launches, or changing data should expose a clear last-updated date and refresh cadence.
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.
# aiso.tools
> Public profile for agent-readable discovery.
Canonical: https://aiso.tools/
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": "aiso.tools",
"url": "https://aiso.tools/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "aiso.tools",
"profile_url": "https://aiso.tools/",
"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.