0/100
min 0
AISO SCAN · combined· SCANNED 44D AGO
dflash.z-lab.ai
How AI sees it: invisible · preview · 25 critical issues blocking AI agents.
AISO SCORE0/100Invisible25 critical
How AI sees it: invisible · preview · 25 critical issues blocking AI agents.
AISO fixMake /.well-known/agent.json valid JSON. Validate locally with `jq . < agent.json` and ensure your CDN serves it as application/json.
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 fixMaintain readable structure + recency: clear headings/lists for chunkability, recent updated-at dates, no stale fact decay, answer-extractable formatting (Q→A, def→explanation).
AISO fixStart llms.txt with '# <Project name>' as the H1 — per llmstxt.org this is the only required field.
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 fixDeclare a PotentialAction (e.g., BuyAction, BookAction, OrderAction) with target endpoint + input schema so delegate agents know how to invoke the transaction.
AISO fixWrap term/definition pairs in <dl><dt>term</dt><dd>def</dd></dl> markup
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 a FAQ block with ≥5 question/answer pairs using <details>/<summary> or <h3>+<p> patterns. Also mark it up with FAQPage JSON-LD.
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 fixPopulate `sameAs: [LinkedIn, Crunchbase, Wikipedia, ...]` on your Organization JSON-LD.
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 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 fixPopulate `sameAs: [LinkedIn, Crunchbase, Wikipedia, ...]` on your Organization JSON-LD.
AISO fixValidate the response from your manifest URL. The body must parse as JSON. Re-serve with `Content-Type: application/json`.
AISO fixReturn valid JSON at /.well-known/agent.json describing your agent or MCP capabilities.
AISO fixReturn valid JSON at /ai/faq.json with a faqs array of {question, answer, source_url} objects.
AISO fixReturn valid JSON at /ai/service.json shaped like a schema.org Service (@type, name, provider).
AISO fixReturn valid JSON at /ai/summary.json with at least name and description fields. Validate with a JSON linter.
AISO fixBreak paragraphs above 400 words with subheadings, lists, or bolded facts
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 fixRefresh the homepage copy and bump the dateModified / visible timestamp.
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 fixPopulate <meta name='description'> and <meta property='og:image'> in the server response. If your framework injects them client-side via react-helmet or similar, switch to a server-side metadata API (Next.js generateMetadata, Nuxt useHead with server: true).
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 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 fixHub pages — typically the homepage, blog index, and product index — anchor the site's link graph. Strengthen at least one navigation surface to act as a hub.
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 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 fixImprove indexability with crawlable internal links, sitemap coverage, canonical URLs, page titles, and public references that search engines can discover.
AISO fixUse exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
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 fixAdd page-family schema for Organization, FAQPage. Strong JSON-LD should match the page type, not just include generic Organization markup.
AISO fixReplace generic alt with descriptive text — what's IN the image, what role does it play in the page?
AISO fixTrim verbose alt text. Long alt reads like SEO spam to ranking models and screen readers alike.
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 fixAdopt and reuse a small vocabulary of capitalised brand terms
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 fixAdd links to Wikipedia, LinkedIn company page, YouTube channel, or GitHub org so AI engines can cross-reference authority.
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 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.
# dflash.z-lab.ai
> Public profile for agent-readable discovery.
Canonical: https://dflash.z-lab.ai/
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": "dflash.z-lab.ai",
"url": "https://dflash.z-lab.ai/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "dflash.z-lab.ai",
"profile_url": "https://dflash.z-lab.ai/",
"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.