SpeeJax

My website speejax.online scored 30/100 on Good for Bots (Poor). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: serve the content as markdown at its own URLs.

The check it fails is "Serves markdown at its own URL", worth 12.5 points. What the scanner saw: No /llms-full.txt and no markdown versions linked from llms.txt.

A model that can only reach this site's content through HTML pays to parse markup and
loses structure doing it: navigation, cookie banners and script tags arrive alongside
the prose, and headings, tables and code blocks come out flattened. Markdown at its own
address removes HTML from the path entirely: what is fetched is the content and nothing
else.

Two routes satisfy this, and it is worth being clear about which one the specification
asks for. llmstxt.org asks for a markdown version of each page **at the same URL as the
original**, either with `.md` appended (`page.html.md`) or with the extension replaced
(`page.md`). `llms-full.txt`, the single bundle holding everything, does not appear in
the specification at all. It is a community convention that grew up around it and is
now widespread. Both are accepted here. The per-page form is the one the document
asks for.

Either of these passes:

- **The bundle.** `/llms-full.txt`, one document, real markdown rather than HTML,
  carrying the site's actual content rather than a placeholder.
- **Per-page mirrors.** A markdown twin for each page at `page.md` or `page.html.md`,
  **and linked from `/llms.txt`**. That second half is load-bearing: mirrors are counted
  from the links in the index, so twins that nothing points at are invisible to this scan
  and, more to the point, to anything crawling the site.

For the mirror route, the index carries them as ordinary link lines:

```markdown
## Docs

- [Quickstart](/docs/quickstart.md): create an account and take a first payment
- [Concepts](/docs/concepts.md): customers, subscriptions, invoices and proration
- [Webhooks](/docs/webhooks.md): events, signature verification, retry schedule
```

Both `/docs/quickstart` and `/docs/quickstart.md` have to answer 200: the HTML for
people, the markdown for everything else.

Serving markdown through content negotiation does **not** satisfy this, and that is
deliberate rather than an oversight. A negotiated response only exists for a client that
knows to send `Accept: text/markdown`, and most crawlers send no preference at all. A
`.md` address sits in the open: it is found by ordinary crawling, it can be linked to,
and it can be cited. If this site already negotiates markdown, the report says so in
these words: *"Markdown is served on request, but not at any URL a crawler would find on
its own"*. That is a different check passing on its own terms, not a contradiction.

Four things about how this is measured. The bundle is judged by size, by being markdown
rather than a page or JSON, and by not merely repeating `llms.txt`; its content is never
sampled beyond that, so a couple of kilobytes of boilerplate would pass. Do not take that
as permission, since the point of the file is the content in it. `.mdx` counts as markdown
although the specification names only `.md`, because excluding it would punish a large
part of the documentation ecosystem for its toolchain. The number of mirrors we want
before calling it a convention on this site is our judgement, not the specification's.
And the mirror URLs listed in the index are counted, never fetched, so a list of `.md`
addresses that 404 passes this check and helps nobody at all.

The whole report, as markdown, is at https://goodforbots.com/r/speejax.online.md?scan=cmuthqdqu00h901p3k6gyfmye. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

My website speejax.online scored 30/100 on Good for Bots (Poor). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: publish an llms.txt at the site root.

The check it fails is "llms.txt is present and well formed", worth 11.25 points. What the scanner saw: No /llms.txt on this site.

A model that arrives at a site with no `llms.txt` has to work out what is here from
whatever the navigation happens to expose. A sitemap does not help it. That file was
written for a search engine and lists addresses without saying what any of them are
for. `llms.txt` is the one file written for the other kind of reader: a short, curated
index that says what this project is and which pages are worth fetching.

The format is defined at llmstxt.org, currently at version 2. It is a convention with a
written specification and real adoption, not a standards-body document: there is no RFC
behind it and no working group. Worth knowing before treating any corner of it as
settled.

The file must:

- be served at `/llms.txt`, at the site root, answering 200 as text rather than HTML;
- open with an H1 naming the project (a `#`, a space, then the name). The specification
  makes this the one required element, so a file without it is not llms.txt at all;
- carry a blockquote directly under that title saying what the project is, in the terms
  someone who has never seen it would need;
- list the pages worth fetching as bullet links, `- [Name](url)`, each followed by `:`
  and a note saying what is behind it;
- group those links under `##` headings that mean something (`Docs`, `API`, `Optional`)
  rather than one undifferentiated pile.

By convention the section named `Optional` holds secondary information: links an agent
can skip when it needs a shorter context. It is the only place in the format where a
site can say "this matters less", so use it rather than leaving everything equally
weighted.

A minimal, valid example:

```markdown
# Acme

> Acme is a hosted billing API for subscription businesses. These pages cover the
> concepts, the REST endpoints, and the migration path from the v1 API.

Start with the quickstart. The API reference is generated from the OpenAPI document
linked below, so it is always current.

## Docs

- [Quickstart](/docs/quickstart.md): create an account and take a first payment
- [Concepts](/docs/concepts.md): customers, subscriptions and invoices, and how they relate
- [Migrating from v1](/docs/migrate-v1.md): what changed, and the cut-off date

## API

- [REST reference](/api/reference.md): every endpoint, with request and response shapes
- [OpenAPI document](/api/openapi.json): the machine-readable schema

## Optional

- [Changelog](/changelog.md): release notes, most recent first
```

Two things get this wrong more often than anything else.

**A catch-all route answering for the file.** A framework that serves its application
shell for every unknown path returns 200 and a page of HTML at `/llms.txt`, which is
worse than a plain 404 because nothing signals that the file is absent. Verify from
outside the application: `curl -s https://speejax.online/llms.txt | head -5` must print markdown,
not `<!doctype html>`. On most stacks the answer is to put the file in the directory
that is served verbatim (`public/`, `static/`, `www/`) rather than in the router.

**Generating it from the sitemap.** A dump of every URL the site has is a sitemap with
different punctuation. This file is a curated index: a few dozen entries a person chose,
each carrying a note. A generated wall of bare links satisfies the format and helps
nobody, and it fails the companion check that asks whether the index describes anything.

Two limits of this scan are worth knowing, because neither is a reading of the
specification. The specification allows the file at any subpath (`/docs/llms.txt`
covers the URLs beneath `/docs/`), but this scan requests the site root and nothing
else, so a file that exists only under a subpath is reported as absent. And the URLs
inside the file are never fetched, so an index pointing at pages that have moved still
reads as well formed here.

The whole report, as markdown, is at https://goodforbots.com/r/speejax.online.md?scan=cmuthqdqu00h901p3k6gyfmye. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

My website speejax.online scored 30/100 on Good for Bots (Poor). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: serve markdown through content negotiation on all public HTML routes.

The check it fails is "Serves markdown when asked for it", worth 10 points. What the scanner saw: None of the 3 pages read pass. Asking the homepage for markdown still returns text/html.

The scan checked a sample of 3 pages. It does not establish which other pages have the same issues. Use the findings below to locate the responsible templates, components or configuration, and apply the fix wherever the same issue occurs. Pages in the sample with findings:
- https://speejax.online/: Asking the homepage for markdown still returns text/html.
- https://speejax.online/blogs/: Asking the page at /blogs/ for markdown still returns text/html.
- https://speejax.online/write-for-us/: Asking the page at /write-for-us/ for markdown still returns text/html.

Implement content negotiation across all public HTML routes, including page types
outside the scan's sample. Put it in the shared response handling or the handlers
for each page type, so new pages receive it too. Agents need the content of any
page they follow, including pages the report did not name.

When a request arrives with `text/markdown` in its `Accept` header, the same URL that
serves HTML to a browser should return a markdown rendering of that page's content.
Requests without that header must keep getting the HTML exactly as they do now.

The response must:

- set `Content-Type: text/markdown; charset=utf-8`;
- include `Accept` in the `Vary` header, so shared caches never serve the markdown to a
  browser or the HTML to an agent (RFC 9110 says a server SHOULD send `Vary` whenever
  the representation depends on a request header);
- contain real markdown, not HTML with a different header on it;
- drop `ETag` and `Last-Modified` for the converted response, since a conditional request
  cannot be honoured against a body generated on the fly.

Work out how to do this in whatever stack this project uses. If the site is behind
Cloudflare on a paid plan, the "Markdown for Agents" zone setting does all of the above
and is the least invasive option. Otherwise implement it in the framework: middleware
inspecting the `Accept` header, a route handler that returns the markdown source, or
whatever fits the architecture here.

Strip navigation, headers, footers and cookie banners from the markdown. The point is the
content, without the page furniture around it.

Verify HTML and Markdown responses for each public page type, including URLs
outside the reported sample. Check that each Markdown response contains that
page's content and that ordinary browser requests still receive HTML.

The whole report, as markdown, is at https://goodforbots.com/r/speejax.online.md?scan=cmuthqdqu00h901p3k6gyfmye. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.