Picturesque AI

My website aipicturesque.com scored 80/100 on Good for Bots (Good). 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://aipicturesque.com/: Asking the homepage for markdown still returns text/html.
- https://aipicturesque.com/blog/agentic-ai-director-picturesque-guide: Asking the page at /blog/agentic-ai-director-picturesque-guide for markdown still returns text/html.
- https://aipicturesque.com/billing: Asking the page at /billing for markdown still returns text/html.
- https://aipicturesque.com/blog: Asking the page at /blog 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/aipicturesque.com.md?scan=cmusihkxg01pd01o0vxw4eupf. 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 aipicturesque.com scored 80/100 on Good for Bots (Good). 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 6.52 points of it still on the table. What the scanner saw: None of the 4 pages read pass fully; 3 partly. The homepage is barely structured: No <main> element and nothing carrying role="main".

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://aipicturesque.com/: The homepage is barely structured: No <main> element and nothing carrying role="main".
- https://aipicturesque.com/blog/agentic-ai-director-picturesque-guide: The page at /blog/agentic-ai-director-picturesque-guide is partly structured: No <main> element and nothing carrying role="main".
- https://aipicturesque.com/billing: The page at /billing is partly structured: No <main> element and nothing carrying role="main".
- https://aipicturesque.com/blog: The page at /blog is partly 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/aipicturesque.com.md?scan=cmusihkxg01pd01o0vxw4eupf. 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 aipicturesque.com scored 80/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: declare the site's AI usage preferences in robots.txt or HTTP headers.

The check it fails is "Declares AI usage preferences", worth 2.5 points. What the scanner saw: No usage declaration found in robots.txt or the final successful homepage response header.

Blocking a crawler says who may fetch a page. This says what may be done with the
content afterwards (trained on, indexed, quoted in an answer), which is a different
question, and one a site can answer without blocking anybody.

There are two vocabularies for it and either is fine. Cloudflare's `Content-Signal` is
deployed at scale; the IETF AIPREF working group's `Content-Usage` is the standards-track
version. Pick one.

Cloudflare's, placed inside a user-agent group:

```
User-agent: *
Content-Signal: ai-train=no, search=yes, ai-input=yes
Allow: /
```

The three categories are `ai-train` (training or fine-tuning models), `search` (building
a search index that links back here) and `ai-input` (feeding the content to a model at
answer time, such as retrieval-augmented generation). Each takes `yes` or `no`.

The IETF version, with reversed naming for the training category and single-letter
values:

```
User-agent: *
Content-Usage: train-ai=n, search=y, ai-use=y
Allow: /
```

Alternatively, send the same IETF preference as an HTTP response header:

```http
Content-Usage: train-ai=n, search=y, ai-use=y
```

Configure it on the content responses it is meant to cover, including the final
homepage response after redirects. A header applies only to that response's content;
it is not a site-wide declaration. Do not put a robots.txt path prefix in it.
The scanner samples the final successful homepage response and awards this check
once even when both robots.txt and the header declare preferences.

Use lowercase category labels and the unquoted tokens `y` or `n`. Parameters are
ignored. Repeated HTTP fields form one dictionary: a duplicate category keeps its
last value. Keep that distinct from conflicts between separate applicable AIPREF
statements, where disallow takes precedence over allow by default. Keep the
carriers consistent with the intended policy; a header does not automatically
override robots.txt.

Decide what this project wants. A common position is to refuse training while
allowing search and grounding, so the site stays citable without feeding a model.
Omitting a category is allowed and means "unstated", not "allowed".

One caution: nothing compels a crawler to honour either directive. This is a stated
preference, not an enforcement mechanism. The standards-track vocabulary is also a draft
that can still change under you.

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