StackLedge

My website stackledge.com scored 69/100 on Good for Bots (Fair). 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/stackledge.com.md?scan=cmusu3f5s00hg01ozlq6hlmfi. 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 stackledge.com scored 69/100 on Good for Bots (Fair). 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 4 pages read pass. Asking the homepage for markdown still returns text/html.

The scan checked a sample of 4 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://www.stackledge.com/: Asking the homepage for markdown still returns text/html.
- https://www.stackledge.com/blog/how-to-build-an-ai-agent-in-n8n: Asking the page at /blog/how-to-build-an-ai-agent-in-n8n for markdown still returns text/html.
- https://www.stackledge.com/blog: Asking the page at /blog for markdown still returns text/html.
- https://www.stackledge.com/about: Asking the page at /about 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/stackledge.com.md?scan=cmusu3f5s00hg01ozlq6hlmfi. 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 stackledge.com scored 69/100 on Good for Bots (Fair). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: mark the content up so a parser can find it.

The check it only partly passes is "Content is marked up so a reader can find it", with 5 points of it still on the table. What the scanner saw: 1 of 4 pages read pass; 3 partly. The homepage is partly structured: The outline jumps from h2 to h4, which the standard forbids.

The scan checked a sample of 4 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://www.stackledge.com/: The homepage is partly structured: The outline jumps from h2 to h4, which the standard forbids.
- https://www.stackledge.com/blog: The page at /blog is partly structured: The outline jumps from h2 to h4, which the standard forbids.
- https://www.stackledge.com/about: The page at /about is partly structured: The outline jumps from h2 to h4, which the standard forbids.

Review the site's public page templates and shared layout components. Fix missing
content roots, heading structure and landmarks wherever they occur, including
templates outside the reported sample. Check the server's HTML response from each
page type: a shared layout fix can introduce a second `<main>` on pages that
already have one.

Semantic elements help a reader of raw HTML find the page's content and distinguish
it from navigation and other surrounding material.

Three things, all from the HTML standard. Change the markup; do not change what the page
looks like.

**1. One content root.** Wrap the page's dominant content in a single `<main>`.

```html
<body>
  <header>…site header…</header>
  <main>…the article, the docs page, the product copy…</main>
  <footer>…site footer…</footer>
</body>
```

The standard allows exactly one `<main>` per document that is not marked `hidden`, and
its ancestors may only be `<html>`, `<body>`, `<div>`, an unnamed `<form>` or a custom
element, which makes a `<main>` inside `<section>` or `<article>` invalid. Put the real
content inside it: a `<main>` that holds a sliver of the page while the article sits in a
sibling `<div>` marks nothing. If a framework template makes the element impossible,
`role="main"` on the wrapper is an acceptable substitute.

**2. A heading outline that holds together.** Exactly one idea per level, starting at
`<h1>`, and never skipping a level on the way down.

```html
<h1>What this page is about</h1>
  <h2>First section</h2>
    <h3>A detail</h3>
  <h2>Second section</h2>
```

`<h1>` → `<h3>` is invalid; `<h3>` → `<h2>` on the way back up is fine. Use heading
elements for headings and CSS for size: a `<div class="text-2xl">` is invisible to the
outline. If a heading is an image or an icon, give it real text and hide it visually
rather than leaving the element empty.

**3. Landmarks around the content.** At least two of these, outside `<main>`:

```html
<header>   <!-- the site header: becomes the banner landmark -->
<nav>      <!-- navigation -->
<footer>   <!-- the site footer: becomes contentinfo -->
<aside>    <!-- related content -->
<search>   <!-- a search form -->
```

Two rules that surprise people. `<header>` and `<footer>` only count as the page's banner
and contentinfo when they are children of `<body>`; inside `<article>` or `<section>` they
are that section's own header and footer and are not landmarks at all. And a `<form>` is
only a landmark when it has an accessible name, so give a search form
`aria-label="Search"`.

Do not add landmarks that describe nothing: five unlabelled `<nav>` elements are worse
than one. And do not wrap the whole body in `<main>`: that puts the header and footer
inside the content root, which removes the landmarks this asks for.

The report's content and navigation breakdown is diagnostic. It measures extracted
text in marked regions, not content quality. Keep useful navigation; do not remove
links or add filler to change a percentage. If much of the text is labelled "other",
check whether the real main content has a meaningful wrapper. The reported start of
main text follows HTML order, which can differ from the visual layout.

The whole report, as markdown, is at https://goodforbots.com/r/stackledge.com.md?scan=cmusu3f5s00hg01ozlq6hlmfi. 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.