IdeaHunter

My website ideahunter.today scored 58/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 fails is "Content is marked up so a reader can find it", worth 15.79 points. What the scanner saw: None of the 4 pages read pass. The homepage's markup carries no content, so a reader that does not run JavaScript sees an empty page.

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://ideahunter.today/: The homepage's markup carries no content, so a reader that does not run JavaScript sees an empty page.
- https://ideahunter.today/blog/add-guardrails-to-ai-generated-code-checklist: The page at /blog/add-guardrails-to-ai-generated-code-checklist's markup carries no content, so a reader that does not run JavaScript sees an empty page.
- https://ideahunter.today/blog: The page at /blog's markup carries no content, so a reader that does not run JavaScript sees an empty page.
- https://ideahunter.today/alternatives: The page at /alternatives is barely structured: No <main> element and nothing carrying role="main".

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/ideahunter.today.md?scan=cmusib7og017h01o0dyvz3g2c. 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 ideahunter.today scored 58/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: make the homepage's content available in the server response.

The check it only partly passes is "Serves its content without JavaScript", a penalty taking 12.5 points off the score. What the scanner saw: The complete homepage HTML has no readable body text and contains executable scripts. A Markdown alternative was found; its equivalence is not verified.

Inspect the homepage response for https://ideahunter.today using the scanner's declared
User-Agent, GoodForBotsBot/1.0 (+https://goodforbots.com/bot). Save the response headers and HTML, then parse the
body without running scripts. Do not remove whole lines containing `<script>`:
minified pages can put their entire document on one line.

The scanner observed an empty script-bearing HTML response. Confirm whether it
is an application shell, an unintended empty response or a deployment problem
before changing the rendering strategy. Check redirects, status codes and the
content served at the final URL. If the HTML only redirects through
JavaScript, use an HTTP redirect to the intended page so a reader can follow it
without executing code.

If scripts populate the page, make its useful content available through server
rendering or static generation. Keep interactive controls where needed, but
include the headings, descriptions and navigation destinations in the initial
HTML. In Next.js, Client Components can also be pre-rendered: `"use client"`
alone is not the cause. Check client-only data fetching, browser-only rendering
and disabled SSR instead.

If the page intentionally has no textual content, inspect whether meaningful
text alternatives or ordinary links would help readers. Do not add filler just
to reach a word count. A short page is not a failure of this check.

A negotiated `text/markdown` response or a real `/llms-full.txt` can provide an
alternative. Verify that it contains useful, current content: discovery alone
does not prove equivalence. `/llms.txt` by itself is an index of links, not the
content of those pages. Keep the underlying content consistent for people and
agents, and do not weaken bot admission or serve a special score-only page.

Verify the resulting HTTP response without executing JavaScript. Useful text
should be present in the parsed body or in a deliberate static alternative,
rather than existing only in script data or appearing after a client-side fetch.

The whole report, as markdown, is at https://goodforbots.com/r/ideahunter.today.md?scan=cmusib7og017h01o0dyvz3g2c. 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 ideahunter.today scored 58/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://ideahunter.today/: Asking the homepage for markdown still returns text/html.
- https://ideahunter.today/blog/add-guardrails-to-ai-generated-code-checklist: Asking the page at /blog/add-guardrails-to-ai-generated-code-checklist for markdown still returns text/html.
- https://ideahunter.today/blog: Asking the page at /blog for markdown still returns text/html.
- https://ideahunter.today/alternatives: Asking the page at /alternatives 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/ideahunter.today.md?scan=cmusib7og017h01o0dyvz3g2c. 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.