0/100
min 0
AISO SCAN · combined· SCANNED 50D AGO
cameronamer.com
How AI sees it: invisible · preview · 31 critical issues blocking AI agents.
AISO SCORE0/100Invisible31 critical
How AI sees it: invisible · preview · 31 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 fixYour domain is not being cited by any configured AI search platform. Add structured data, publish authoritative content, get listed in roundups + comparison pages.
AISO fixMention the brand at least once like "Cameronamer is a [category] for [audience]" for clean LLM resolution.
AISO fix3 queries return zero domain placement in top 10. Audit content gaps for those query intents and ensure each has a dedicated landing page.
AISO fixCite at least one .edu/.gov, Wikipedia, IETF/W3C spec, or tier-1 publication near your flagship claims.
AISO fixAdd H2/H3 section breaks every ~500 words to scaffold the content
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 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 h2-headed sections with 134-167 words of factual content each. Empty marketing pages give LLMs nothing to cite.
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 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 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 fixAdd a Person JSON-LD entry for founder/principal author with sameAs links.
AISO fixAdd a glossary page with 5+ defined terms
AISO fixDefine key terms explicitly: '**AI Agent** is a software program that...'
AISO fixPublish JSON-LD with Organization/Service nodes including `audience` and `aggregateRating` properties so LLMs can extract market-fit signals.
AISO fixPublish JSON-LD blocks (`<script type="application/ld+json">`) describing your offer/service, address, and contact methods. Without structured data, delegate agents can't transact on your behalf.
AISO fixPublish Organization JSON-LD with name + url + sameAs for entity association.
AISO fixAdd Pros/Cons sections to comparison and review pages
AISO fixRAG retrievers index paragraph spans. A landing page with only headings + buttons gives nothing for an LLM to cite — add 2-4 short paragraphs explaining what you do.
AISO fixAdd an explicit '<h2>FAQ</h2>' or 'Frequently Asked Questions' section with at least 3 items.
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 fixDomain has no indexed mentions on any of the high-authority publications tracked. This is the single biggest lever for AI-search citation rates — pursue PR + roundup placements + founder content.
AISO fixAim for 5-10 explicit brand mentions in body copy. Helps LLMs build a clean entity-page association during indexing.
AISO fixPrioritize: Frequently Asked Questions about Developer Tooling; Developer Tooling Glossary: Key Terms Explained.
AISO fixReach out to the listed pages and ask for a link to your apex. Unlinked mentions are the highest-conversion link-building lane.
AISO fixbridge returned HTTP 401
AISO fixbridge returned HTTP 401
AISO fixReturns HTTP 999. Update or remove this link.
AISO fixRefresh the homepage copy and bump the dateModified / visible timestamp.
AISO fixUse exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
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 a 2–4 sentence paragraph immediately after the H1 summarising what the product is and who it serves.
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 fixOpen with 'We are ...' / 'Our mission is ...' / 'This is ...' — AI models need explicit entity framing.
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 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 fixLaunch on ProductHunt — even a low-effort listing gets indexed and helps LLMs answer 'is X legit?' questions.
AISO fixAdd statistical claims to drive AI-citation rate +30-40% (Aggarwal Princeton GEO 2024).
AISO fixAdd explicit entity surfaces: team or founder page, pricing page, docs or API page.
AISO fixAdd a unique <title>, meta description, and canonical URL. Add Open Graph/Twitter tags for share and citation previews.
AISO fixAdd ItemList JSON-LD schema to comparison pages
AISO fixAdopt and reuse a small vocabulary of capitalised brand terms
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 fixDocument auth, API keys/OAuth, rate limits, webhooks, SDKs, sandbox/test mode, and status-page behavior so agents can call tools safely.
AISO fixIf the homepage surfaces editorial content, include an author byline (Person JSON-LD or 'By <Name>').
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 links to Wikipedia, LinkedIn company page, YouTube channel, or GitHub org so AI engines can cross-reference authority.
AISO fixClaim a Trustpilot profile + invite a few customers to leave verified reviews. Trustpilot pages are heavily indexed for trust signals.
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 fixProvide business_name + area in ScanContext.agntBridge so the bridge can call this lane.
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 fixProvide social_links in ScanContext.agntBridge so the bridge can call this lane.
AISO fixExpand thin pages with direct answers, evidence, FAQs, and specific facts before expecting AI engines to cite them.
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.
# cameronamer.com
> Public profile for agent-readable discovery.
Canonical: https://www.cameronamer.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": "cameronamer.com",
"url": "https://www.cameronamer.com/",
"description": "Public profile for agent-readable discovery.",
"offers": [],
"actions": [],
"evidence": []
}{
"schema": "aios.mcp_manifest.v1",
"name": "cameronamer.com",
"profile_url": "https://www.cameronamer.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.