SEOBuilder
MENU
PRODUCTFREE TOOLSPRICINGBLOG
RUN LIVE SCAN
← the whole board

limestonedigital.com

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

72/100

Partly ready

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

AI crawler access

1007/7

Discovery

672/3

Agent interfaces

402/5

Agent-usable responses

00/2

Machine readability

1006/6

Identity and trust

501/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 limestonedigital.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.

  • No usable sitemap

    Missing

    Nothing usable at https://limestonedigital.com/wp-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.

  • 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 did not answer at all, so an agent cannot tell a missing route from an outage.

    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 answer nothing

    Missing

    /seobuilder-agent-readiness-probe-404 answered nothing. A page that does not exist must not answer 200, or every typo becomes a page an agent believes in.

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

  • No about, contact or privacy page found

    Missing

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

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
  • 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 has a title
  • The homepage has a meta description
  • Valid JSON-LD structured data
  • One clear H1
  • The page reads without JavaScript
  • 14.34% of the homepage is readable text
  • 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.