0/100
min 0avg 2-max 15
AISO SCAN · combined· SCANNED 51D AGO
binance.com
How AI sees it: invisible · preview · 6 critical issues blocking AI agents.
AISO SCORE0/100Invisible6 critical
0/100
invisible
$0
$0/yr-recoverable
29
6 H13 M10 L
25
10 pass-15 fail
Provider citation crawl rows were not captured for this scan. AISO is showing the real stored TOOLBOX signals across the enabled scanner modules instead of inventing AI-engine counts.
Top findings - fix first
What to fix first.
Add a Content-Security-Policy to enable directive-level audit
AISO fixSend a Content-Security-Policy response header (or <meta http-equiv> tag) so directive strictness can be scored.
csp-auditimpact not pricedagent fix
Homepage has zero external citations
AISO fixAdd 2–3 outbound links to .edu/.gov, Wikipedia, or major publications to back your strongest claims.
citationsimpact not pricedmanual
llms.txt missing H1 title
AISO fixStart llms.txt with '# <Project name>' as the H1 — per llmstxt.org this is the only required field.
llmstxtimpact not pricedagent fix
No definition-lead opener in the first 150 tokens
AISO fixOpen the homepage with '<Brand> is a <category> that <differentiator>' — this is the single biggest lever for AI citability.
structureimpact not pricedmanual
Agent extraction - what agents can read
binance.com is 0% grounded.
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.
Fix nextidentityoffersactionsagent filestrustgrounding
Recommended repairscriticalAdd a clear identity summary criticalPublish structured offers or pricing criticalAdd booking, contact, buy, or quote paths importantPublish agent discovery files
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.
Copy-ready agent files
Paste these into the public agent files your site is missing, then rescan.
# binance.com
> Public profile for agent-readable discovery.
Canonical: https://www.binance.com/en/trade
Agent-readable schema: aios.agent_readable.v1
## Offers
- Add structured offers.
## Actions
- Add book, buy, quote, contact, or API actions.Signal matrix - all checks
138 checks, 19 systems.
Every check rolls up into covered, not captured, or planned-only. Click-through rows below stay tied to stored signals only.
Coverage upgrade - Wave A
Five new capability tiers landing on this report.
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.
Web3 / On-Chain Surfaces
Wallet-connect, contract addresses, x402 endpoint health, ENS, chain metadata, exposed ABI and token metadata.
Context Engine - scrape regex + actions- wallet-connect detection (RainbowKit / WalletConnect / Privy)
- contract addresses present on page (EVM / Solana)
- x402 endpoint health and challenge shape
- ENS / handle resolution to on-chain identity
- chain metadata declared (chainId, RPC hints)
- exposed ABI or method-list reachable to agents
- token metadata (name / symbol / decimals / logoURI)
Content Quality & Readability
Pre-flight - agent readiness
Can agents use this business?
Agent readiness is discovery, metadata, proof, offers, actions, protocols, and safe access together.
- robots.txt is reachable
- GPTBot access
- ChatGPT-User access
- ClaudeBot access
- PerplexityBot access
- Google-Extended access
- clear entity name
- clear category
- clear offer
- pricing path
- agent-readable profile
- structured services and offers
- MCP endpoint exists
- MCP tools/list works
- MCP resources/list works
Recovery plan - five steps
Fix first.
Sequential. Most of it auto-generates when you install Agent Link; the scanner verifies the result on the next pass.
- profile.json
- llms.txt
- agents.json
- public profile
- AI-readable summary
- offers.json
- booking actions
- contact actions
- CTA routes
- action metadata
- reviews
- citations
- testimonials
- credentials
- authority links
- robots guidance
- sitemap
- schema
- OpenAPI
- MCP-ready surfaces
- weekly scans
- engine checks
- citation tracking
- agent reads
- score history
Today
Built for humans.
- Template coverage is limited in homepage-only scans
- 2 high-impact content gaps detected
- 4 entity page gaps detected
- No definition-lead opener in the first 150 tokens
Unlock the full scan, PDF, and repair prompt for $19.
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.
138 scanner checks, 25 stored signals, 29 findings.
- Scanner modules19 modules - 0/138 covered - 0 planned-only
- Retrieval scanPaid provider citation crawl not stored - no fake cited-source count
- Trust stackFive layers, weakest first - per-layer score and weak-signal drilldown
- Dimensions grid25 weighted signals - per-dimension score, weight, and status
- Findings29 total - 6 critical - 13 medium - severity, dimension, monthly impact, and fix path
- Repair promptCopy-paste prompt in four variants (full, dev, content, schema) - PDF export
The detail rows, provider evidence, repair prompt and PDF export are behind a one-time unlock. The preview cards above stay visible.