SEOBuilder
MENU
PRODUCTFREE TOOLSPRICINGBLOG
RUN LIVE SCAN
← the whole board

ranked.ai

outbid.lol rank #29 · bid $1,025 · checked 2026-08-22

82/100

Mostly ready

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

AI crawler access

1007/7

Discovery

1003/3

Agent interfaces

603/5

Agent-usable responses

250/2

Machine readability

835/6

Identity and trust

1002/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 ranked.ai

5 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 /.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.

  • 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.

  • 0.35% of the homepage is readable text

    Missing

    4,361 characters of text inside 12,42,360 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.

Already passing (20)

  • 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
  • /llms.txt is published
  • llms.txt says what the site is for
  • The homepage serves markdown on request
  • The homepage has a title
  • The homepage has a meta description
  • Valid JSON-LD structured data
  • One clear H1
  • The page reads without JavaScript
  • About, contact and privacy all have real content
  • Organization schema is complete

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.

Check your own siteShare this score

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.