SEOBuilder
MENU
PRODUCTFREE TOOLSPRICINGBLOG
RUN LIVE SCAN
← the whole board

peptiprices.com

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

78/100

Mostly ready

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

AI crawler access

1007/7

Discovery

1003/3

Agent interfaces

804/5

Agent-usable responses

250/2

Machine readability

674/6

Identity and trust

500/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 peptiprices.com

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

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

  • 2 H1 headings

    Missing

    More than one H1 splits what the page claims to be about.

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

  • 0.86% of the homepage is readable text

    Missing

    5,851 characters of text inside 6,80,098 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.

  • 2 of 3 trust pages have real content

    Partial

    About: 1,880 characters at /about. Contact: 404 at /contact. Privacy: 3,000 characters at /privacy.

    Publish about, contact and privacy pages with at least 500 characters each. They are where an agent checks you are a real company before it recommends you.

  • 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 (18)

  • 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
  • /.well-known/api-catalog is published
  • An MCP server card is published
  • The homepage has a title
  • The homepage has a meta description
  • Valid JSON-LD structured data
  • The page reads without JavaScript

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.