0/100
min 0
AISO SCAN · combined· SCANNED 45D AGO
agntdot.com
How AI sees it: invisible · preview · 16 critical issues blocking AI agents.
AISO SCORE0/100Invisible16 critical
How AI sees it: invisible · preview · 16 critical issues blocking AI agents.
AISO fixBreak paragraphs above 400 words with subheadings, lists, or bolded facts
AISO fixAllowlist these UAs at your CDN (Cloudflare WAF rules / Akamai Bot Manager / fastly). Cloudflare's 'Verified Bots' toggle covers most of these but ChatGPT-User and PerplexityBot frequently need explicit rules. Check robots.txt too.
AISO fixSend a Content-Security-Policy response header (or <meta http-equiv> tag) so directive strictness can be scored.
AISO fixAdd headings like '<Product> vs <Competitor>' to comparison content
AISO fixDeclare a PotentialAction (e.g., BuyAction, BookAction, OrderAction) with target endpoint + input schema so delegate agents know how to invoke the transaction.
AISO fixAdd a /best-X-alternatives or /you-vs-competitor page
AISO fixAdd a TL;DR sentence or '<Brand> is a <category> that …' lead at the top
AISO fixAdd an HTML <table> with <th>feature</th>/<th>price</th> columns
AISO fixAdd a glossary page with 5+ defined terms
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
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 fixSet `price` (or `priceSpecification`/`lowPrice`) on your Offer/Product/Service node. Agents need numeric pricing to compare and quote.
AISO fixBold key statistics, definitions, and claims so AI can cite them
AISO fixValidate the response from your manifest URL. The body must parse as JSON. Re-serve with `Content-Type: application/json`.
AISO fixPrioritize: Frequently Asked Questions about AI Agent Tooling; AI Agent Tooling Glossary: Key Terms Explained.
AISO fixAllowlist these UAs at your CDN (Cloudflare WAF rules / Akamai Bot Manager / fastly). Cloudflare's 'Verified Bots' toggle covers most of these but ChatGPT-User and PerplexityBot frequently need explicit rules. Check robots.txt too.
AISO fixMention the brand at least once like "Agntdot is a [category] for [audience]" for clean LLM resolution.
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 an `audience` property (or Audience node) to your Organization/Service JSON-LD with `audienceType` (e.g. 'Developers', 'Marketers'). LLMs answering 'who is X for?' use this directly.
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 fixMention the brand at least once like "Agntdot is a [category] for [audience]" for clean LLM resolution.
AISO fixAdd a PostalAddress node (or address property on Organization) with addressLocality + addressRegion/Country so delegate agents can geo-resolve the business.
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 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 fixRemove agent-hostile signals: prompt-injection patterns, broken links, deceptive cloaking, robots conflicts. Agents discount hosts that look unsafe to act on.
AISO fixAim for 3-11 words of context-bearing description per non-decorative image.
AISO fixAllowlist these UAs at your CDN (Cloudflare WAF rules / Akamai Bot Manager / fastly). Cloudflare's 'Verified Bots' toggle covers most of these but ChatGPT-User and PerplexityBot frequently need explicit rules. Check robots.txt too.
AISO fixAdd explicit entity surfaces: about or company page, team or founder page, pricing page, docs or API page.
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 your business has operating hours, declare openingHoursSpecification so agents only attempt transactions during open windows.
AISO fixDeclare paymentAccepted on your Offer/Service so payment-capable agents can confirm method compatibility before initiating a transaction.
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 fixSee dimension details for remediation guidance.
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 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 fixAdd page-family schema for Product, Offer. Strong JSON-LD should match the page type, not just include generic Organization markup.
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.
# agntdot.com
> Public profile for agent-readable discovery.
Canonical: https://agntdot.com/
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": "agntdot.com",
"url": "https://agntdot.com/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "agntdot.com",
"profile_url": "https://agntdot.com/",
"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.