SEOBuilder
MENU
PRODUCTFREE TOOLSPRICINGBLOG
RUN LIVE SCAN
← the whole board

orynth.dev

outbid.lol rank #4 · bid $12,716 · checked 2026-08-22

34/100

Not ready yet

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

AI crawler access

866/7

Discovery

331/3

Agent interfaces

00/5

Agent-usable responses

250/2

Machine readability

171/6

Identity and trust

00/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 orynth.dev

17 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 robots.txt

    Missing

    Nothing is blocked, but you also have no way to say which agents may read you.

    Publish a robots.txt at the root, even if it allows everything. Silence is not a policy an agent can read.

  • No usable sitemap

    Missing

    Nothing usable at https://www.orynth.dev/sitemap.xml. Agents have to discover pages by following links, which misses whatever is not linked.

    Publish a sitemap.xml listing every page you want read, and check it answers with XML rather than an HTML error page.

  • robots.txt does not name a sitemap

    Missing

    A Sitemap line in robots.txt is how an agent finds a sitemap that is not at the default path.

    Add one line to robots.txt: Sitemap: https://www.orynth.dev/sitemap.xml

  • 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 page title

    Missing

    Agents have nothing to name this page with.

    Give the homepage a title that names what you do, not just the company name.

  • No valid JSON-LD

    Missing

    Without structured data an agent has to infer what you are from prose.

    Add JSON-LD to the homepage. Start with Organization and WebSite, and validate it before you ship.

  • 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

    Missing

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

  • 0.04% of the homepage is readable text

    Missing

    35 characters of text inside 91,357 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.

  • No about, contact or privacy page found

    Missing

    About: 404 at /about. Contact: 404 at /contact. Privacy: 404 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.

  • No Organization schema

    Missing

    Nothing on the homepage states, in machine-readable form, which organisation this site belongs to.

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

Already passing (8)

  • 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
  • Link response headers are set
  • The homepage has a meta description

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.