0/100
min 0
AISO SCAN · combined· SCANNED 46D AGO
bugzmanov.github.io
How AI sees it: invisible · preview · 30 critical issues blocking AI agents.
AISO SCORE0/100Invisible30 critical
How AI sees it: invisible · preview · 30 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 fixPublish Organization JSON-LD with name + url + sameAs for entity association.
AISO fixCite at least one .edu/.gov, Wikipedia, IETF/W3C spec, or tier-1 publication near your flagship claims.
AISO fixWrap the FAQ with a FAQPage JSON-LD block so AI engines can lift the Q/A pairs verbatim.
AISO fixMake WHO you are unambiguous: Organization JSON-LD with sameAs links, agent-discovery files (llms.txt + .well-known manifests), structured contact + offer data so delegate agents can transact.
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 fixDeclare a PotentialAction (e.g., BuyAction, BookAction, OrderAction) with target endpoint + input schema so delegate agents know how to invoke the transaction.
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 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 fixOpen the homepage with '<Brand> is a <category> that <differentiator>' — this is the single biggest lever for AI citability.
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 fixMention the brand at least once like "Bugzmanov is a [category] for [audience]" for clean LLM resolution.
AISO fixAdd a glossary page with 5+ defined terms
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
AISO fixBuild at least a basic navigation menu linking the homepage to product, pricing, and content pages. Without internal links, AI crawlers can't traverse the site.
AISO fixPublish Organization JSON-LD with name + url + sameAs for entity association.
AISO fixAdd Pros/Cons sections to comparison and review pages
AISO fixAdd FAQPage schema with 5-10 high-frequency questions for AI-search retrieval.
AISO fixAdd Review and/or AggregateRating JSON-LD with reviewer + ratingValue + datePublished. LLMs cite review summaries when ranking peers in comparison answers.
AISO fixPublish a /robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended and other AI crawlers.
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 fixBold key statistics, definitions, and claims so AI can cite them
AISO fixUse numbered and bullet lists to expose key facts
AISO fixRemove agent-hostile signals: prompt-injection patterns, broken links, deceptive cloaking, robots conflicts. Agents discount hosts that look unsafe to act on.
AISO fixFix crawl access first: ensure 200 OK on homepage + sitemap, valid JSON-LD, llms.txt published, SSR-rendered content, and a non-blocking CSP. Without this layer agents can't read the site.
AISO fixComparative pages can over-index on the competitor name. Rebalance copy so your own brand is the dominant entity per section.
AISO fixPrioritize: Frequently Asked Questions about Developer Tooling; Developer Tooling Glossary: Key Terms Explained.
AISO fixAdd /.well-known/ai.txt with your AI/agent policy in RFC9116-style key:value lines or short markdown.
AISO fixPublish an About page listing founders, team, and credentials. AI engines heavily weight provenance.
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 /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 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 fixOpen with 'We are ...' / 'Our mission is ...' / 'This is ...' — AI models need explicit entity framing.
AISO fixAdd a ContactPoint node with telephone or email, ideally including contactType. Agents fall back to noisy prose extraction without this.
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 fixConcrete claims (percentages, customer counts, dates, comparative superlatives) drive trust + LLM citation likelihood. Add specific stats with sources.
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 fixUse exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
AISO fixAdd statistical claims to drive AI-citation rate +30-40% (Aggarwal Princeton GEO 2024).
AISO fixAdd page-family schema for Organization, WebSite, FAQPage. Strong JSON-LD should match the page type, not just include generic Organization markup.
AISO fixAdd explicit entity surfaces: about or company page, team or founder page, pricing page, docs or API page.
AISO fixImprove the underlying dimensions that drive chatgpt citations: crawlability, structure, schema, freshness, entity clarity, and trust.
AISO fixImprove the underlying dimensions that drive claude citations: crawlability, structure, schema, freshness, entity clarity, and trust.
AISO fixImprove the underlying dimensions that drive google_ai citations: crawlability, structure, schema, freshness, entity clarity, and trust.
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 fixExpose a crawlable sitemap (sitemap.xml or sitemap.md) and stable navigation to docs, pricing, support, API references, and key task pages. Agents need predictable links, not only app-shell buttons.
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 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 fixAdd `serviceType` (e.g. 'AI search optimization') or `suitableForBusinessFunction` to your Service/Product node so LLMs categorise the offering correctly.
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 fixImprove the underlying dimensions that drive perplexity citations: crawlability, structure, schema, freshness, entity clarity, and trust.
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 fixAdd concrete numbers, dates, and named entities. LLMs cite specifics — '47% of teams use X' beats 'many teams use X'.
AISO fixRun Template Audit, Full Site, or Deep Investigation mode to compare key templates across the site.
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.
# bugzmanov.github.io
> Public profile for agent-readable discovery.
Canonical: https://bugzmanov.github.io/bookokrat/index.html
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": "bugzmanov.github.io",
"url": "https://bugzmanov.github.io/bookokrat/index.html",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "bugzmanov.github.io",
"profile_url": "https://bugzmanov.github.io/bookokrat/index.html",
"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.