Agents are likely to struggle

• Content without JavaScriptFailed

  Could not fetch homepage

  Recommendation

  Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

• Not blocked by bot detectionFailed

  Could not test bot user agents

  Recommendation

  Allowlist known AI agent User-Agents (ChatGPT-User, ClaudeBot, Google-Extended, DeepSeekBot) in your WAF or bot-detection rules.

• Markdown content negotiation (acceptmarkdown.com)Failed

  Could not probe both Accept: text/markdown and Accept: text/html on canonical URL

  Recommendation

  On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.

• Agent crawler reachabilityFailed

  No major AI crawler can reach the homepage - ChatGPT-User: unknown, ClaudeBot: unknown, Google-Extended: unknown, ora-agent: unknown, DeepSeekBot: unknown

  Recommendation

  Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.

• Agent-friendly 404sFailed

  Could not probe a nonexistent path - both fetches failed

  Recommendation

  Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist - it must print 404.

• Developer resource discoverabilityFailed

  Agent searched for "mikeldev" developer resources but found nothing relevant

  Recommendation

  Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.

• Brand name discoverabilityPartial (33%)

  mikeldev.com appears once in brand-name search results for "mikeldev" (position #9 out of 9)

  Recommendation

  Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.

• Sitemap existsFailed

  No sitemap found

  Recommendation

  Add a valid XML sitemap at /sitemap.xml listing all indexable URLs. Include lastmod dates and keep it under 50MB.

• Content efficiencyFailed

  Insufficient context: no homepage HTML available - agents have nothing to consume

  Recommendation

  Reduce markup overhead so readable text is at least 5% of your HTML. Strip unused inline scripts/styles, server-render content instead of shipping large JSON hydration blobs, and keep wrapper nesting shallow.

• Content crawl depth signalsFailed

  Could not fetch homepage

  Recommendation

  Add and tags on paginated pages (blog archives, product listings, docs) so AI crawlers can traverse beyond the first page.

• JSON-LD structured dataFailed

  Could not fetch homepage

  Recommendation

  Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.

• Agent instruction / when-to-useFailed

  No agent instruction file with when-to-use guidance found

  Recommendation

  Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.

• Metadata completenessFailed

  Could not fetch homepage

  Recommendation

  Add all four signals to your homepage: , , , and . Agents use these for entity resolution and attribution.

• Organization schema completenessFailed

  Could not fetch homepage

  Recommendation

  Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.

• Trust anchor pagesFailed

  No trust anchor pages found with sufficient content (About, Contact, Privacy)

  Recommendation

  Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.

No positive signals in this group.