fuellog.ai

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 Link response headers

  Missing

  RFC 8288 Link headers let an agent find related resources without parsing the HTML.

  Send a Link header for the things an agent should find without parsing HTML: canonical, alternate, and your llms.txt.

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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

  Copy prompt

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
• The homepage has a title
• The homepage has a meta description
• One clear H1
• The page reads without JavaScript
• 6.60% of the homepage is readable text

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.