← the whole board

capitalgurus.com

outbid.lol rank #33 · bid $1,021 · checked 2026-08-22

62/100

Partly ready

14 of 25 checks pass · board median 70 · 3 of 91 scored 90+

AI crawler access

1007/7

Discovery

1003/3

Agent interfaces

00/5

Agent-usable responses

250/2

Machine readability

583/6

Identity and trust

751/2

Is this your site? This score is from 2026-08-22 and does not update when you ship. Run it live and you get today’s answer in a few seconds.

Re-check capitalgurus.com

11 things to fix

Each one has a prompt written for a coding agent. Paste it into Claude Code, Cursor or whatever you build with. Or take all of them in one go.

  • No /llms.txt

    Missing

    llms.txt is the emerging way to tell a model which of your pages matter and what they cover.

    Publish /llms.txt: a title, one sentence on what the site is for, then your pages as markdown links with a line each.

  • Nothing tells an agent what this site is for

    Missing

    Without llms.txt an agent works out your purpose from your navigation, which is a guess.

    Put a blockquote summary under the title of llms.txt: one sentence on who the site is for and which questions it answers.

  • No /.well-known/api-catalog

    Missing

    RFC 9727 defines this path as where an agent looks for the APIs a site offers.

    If you have a public API, list it at /.well-known/api-catalog. If you do not, this one is fair to ignore.

  • No MCP server card

    Missing

    If you run an MCP server, this file is how an agent finds it without being told the URL.

    Running an MCP server? Publish the card at /.well-known/mcp/server-card.json so an agent finds it on its own.

  • Accept: text/markdown returns HTML

    Missing

    Agents that ask for markdown get HTML they have to strip, which loses structure.

    Serve a markdown twin of each page when the request asks for text/markdown, or publish page.md beside page.

  • API errors come back as HTML

    Missing

    /api/seobuilder-agent-readiness-probe-404 answered 404 as text/html. An agent calling your API gets a page where it expected an error object.

    Make every /api/ route answer with JSON on failure too: a real status, and a body with a message field. An HTML error page is a parse error to a caller.

  • Missing pages 404 but do not say so

    Partial

    /seobuilder-agent-readiness-probe-404 answered 404, but the body never says the page is missing. An agent reading the text alone cannot tell.

    Return 404 or 410 for paths that do not exist, and put "404" or "Not found" in the title and the H1.

  • No H1 heading

    Missing

    Nothing states what this page is about at the top level.

    Leave exactly one H1 on the page, and make it the sentence you would want quoted back.

  • The raw HTML is thin without JavaScript

    Partial

    6,030 characters of visible text and 0 H1 in the HTML as sent. Most crawlers never run your JavaScript, so this is the page they read.

    Server-render the copy and the H1. Anything only a browser assembles is invisible to most of the crawlers you want.

  • 1.40% of the homepage is readable text

    Missing

    6,030 characters of text inside 4,30,120 bytes of HTML. Everything else is markup an agent pays for and cannot use.

    Cut inlined state, framework payloads and repeated markup out of the HTML, or serve a markdown twin for agents that ask.

  • Organization schema is missing contactPoint and address

    Partial

    An agent can see who you are but not how to reach you, which is the half that decides whether it recommends you.

    Add Organization JSON-LD with name, url, logo, contactPoint and address. The contact fields are the ones agents quote.

Already passing (14)

  • robots.txt is published
  • OAI-SearchBot can read the site
  • Claude-SearchBot can read the site
  • PerplexityBot can read the site
  • GPTBot can read the site
  • ClaudeBot can read the site
  • Google-Extended can read the site
  • The sitemap is valid XML
  • robots.txt points at your sitemap
  • Link response headers are set
  • The homepage has a title
  • The homepage has a meta description
  • Valid JSON-LD structured data
  • About, contact and privacy all have real content

Not your site?

The same check runs on anything. It fetches the page once and reads what an assistant would read, which is the server’s HTML, with no JavaScript and no scrolling.

Rank and bid from outbid.lol on 2026-08-22. Not affiliated with them. Want this page taken down? Ask us and it goes, no argument.