How AI sees it: invisible · preview · 26 critical issues blocking AI agents.
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 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 fixUse a BCP-47 code: 2-3 lowercase letters, optional region as `-XX` uppercase (e.g. `en`, `en-US`, `pt-BR`), or `x-default`.
AISO fixUse a BCP-47 code: 2-3 lowercase letters, optional region as `-XX` uppercase (e.g. `en`, `en-US`, `pt-BR`), or `x-default`.
AISO fixAdd headings like '<Product> vs <Competitor>' to comparison content
AISO fixPublish a /faq page or link a help center from the homepage navigation.
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 fixAdd a /best-X-alternatives or /you-vs-competitor page
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 fixAdd a glossary page with 5+ defined terms
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
AISO fixAdd an Offer, Product, or Service JSON-LD node with `price` and `availability` so agents can quote and check stock without scraping prose.
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 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 fixRemove agent-hostile signals: prompt-injection patterns, broken links, deceptive cloaking, robots conflicts. Agents discount hosts that look unsafe to act on.
AISO fixDrop 'unsafe-eval' from script-src; refactor any eval/new Function callers.
AISO fixscript-src 'self' 'strict-dynamic' 'nonce-<random>'; (drop 'unsafe-inline')
AISO fixscript-src 'self' https://trusted.cdn.example; (replace wildcard with explicit hosts)
AISO fixEvery % / 'X customers' / stat deserves an inline citation link to the origin study or publication.
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 fixLift the lowest-scoring dimensions in `composite_inputs` first; citation-crawl and agent-readiness move the headline metric the most.
AISO fixEmit Article JSON-LD with headline, author, datePublished, dateModified.
AISO fixbase-uri 'none'; (or 'self' if relative URL rewriting is required)
AISO fixchild-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixconnect-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixfont-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixUse exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
AISO fixframe-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixAdd a single h1 that summarises the page topic. Heading hierarchy gives RAG chunkers clean labels and lets retrievers scope queries.
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 fiximg-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixmedia-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixAdd `<link rel="alternate" hreflang="x-default" href="...">` so search engines and AI agents have an unambiguous fallback when the visitor's locale doesn't match any variant.
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 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 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 fixAdd a TL;DR sentence or '<Brand> is a <category> that …' lead at the top
AISO fixAdd a PostalAddress node (or address property on Organization) with addressLocality + addressRegion/Country so delegate agents can geo-resolve the business.
AISO fixobject-src 'none';
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 fixRestructure paragraphs to 30-120 words each. RAG retrievers favour self-contained spans of this size.
AISO fixAdd 'according to', 'source:', or numeric footnote references. LLMs cite content that points at primary sources.
AISO fixstyle-src 'self' 'nonce-<random>'; (drop 'unsafe-inline')
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 fixworker-src 'self' https://trusted.example; (replace wildcards with explicit hosts)
AISO fixAim for 3-11 words of context-bearing description per non-decorative image.
AISO fixAdd explicit entity surfaces: about or company page, team or founder page, pricing page, docs or API page.
AISO fixTrim verbose alt text. Long alt reads like SEO spam to ranking models and screen readers alike.
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 fixUse sequential heading levels (h1→h2→h3). Skipped levels confuse chunkers and accessibility tools alike.
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 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 fixSee dimension details for remediation guidance.
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 fixAdd `serviceType` (e.g. 'AI search optimization') or `suitableForBusinessFunction` to your Service/Product node so LLMs categorise the offering correctly.
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 fixImprove the underlying dimensions that drive perplexity citations: crawlability, structure, schema, freshness, entity clarity, and trust.
AISO fixSet SHERLOCK_SERVICE_URL and SHERLOCK_API_KEY in the AISO server env to enable account-discovery probes.
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.
AISO fixPages about prices, versions, launches, or changing data should expose a clear last-updated date and refresh cadence.
AISO fixAdd page-family schema for Article/BlogPosting/TechArticle, BreadcrumbList, Person. 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.
# aman.com
> Public profile for agent-readable discovery.
Canonical: https://www.aman.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": "aman.com",
"url": "https://www.aman.com/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "aman.com",
"profile_url": "https://www.aman.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.