VibeCodingList

My website vibecodinglist.com scored 70/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 13.04 points. What the scanner saw: None of the 4 pages read pass. The homepage is unstructured markup: no content root, no usable heading outline and no landmarks.

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://vibecodinglist.com/: The homepage is unstructured markup: no content root, no usable heading outline and no landmarks.
- https://vibecodinglist.com/ai-review: The page at /ai-review is unstructured markup: no content root, no usable heading outline and no landmarks.
- https://vibecodinglist.com/free-tools/ab-test-calculator: The page at /free-tools/ab-test-calculator is unstructured markup: no content root, no usable heading outline and no landmarks.
- https://vibecodinglist.com/free-tools: The page at /free-tools is unstructured markup: no content root, no usable heading outline and no landmarks.

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/vibecodinglist.com.md?scan=cmussbz7b000h01p0fdta0wd3. 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 vibecodinglist.com scored 70/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: describe the pages with schema.org JSON-LD.

The check it fails is "Describes itself to machines with schema.org JSON-LD", worth 10.87 points. What the scanner saw: 1 of 4 pages read pass. The page at /ai-review publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

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://vibecodinglist.com/ai-review: The page at /ai-review publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
- https://vibecodinglist.com/free-tools/ab-test-calculator: The page at /free-tools/ab-test-calculator publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
- https://vibecodinglist.com/free-tools: The page at /free-tools publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

The pages identified as having no structured data need markup added through their
templates. Review the other public page types for the same gap. Use the homepage
example below where it fits, and describe each content page with types that match
its visible content. A passing homepage does not need its markup replaced.

Review structured data across the site's public page types, including those
outside the reported sample. Add or repair it in the templates that generate
each type, using that page's content. Verify a page from each template and keep
existing valid markup. Structured data gives a reader explicit names, types and
relationships for the entities the page describes.

Put a `<script type="application/ld+json">` block in the HTML the server returns. On the
home page describe the organisation and the site; on a content page describe the content
itself: an `Article` for a post, a `Product` for a product, a `BreadcrumbList` for the
trail above it.

Every entity must:

- declare `"@context": "https://schema.org"`;
- declare a `@type` that schema.org defines;
- carry a name: `name`, or `headline` for an article. A type with no name asserts that
  something exists without saying what, which is worth nothing to a reader;
- describe what is on the page. Structured data that disagrees with the visible content
  is worse than none.

A minimal, correct home page block:

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://vibecodinglist.com/#organization",
      "name": "Example Corp",
      "url": "https://vibecodinglist.com",
      "logo": "https://vibecodinglist.com/logo.png"
    },
    {
      "@type": "WebSite",
      "@id": "https://vibecodinglist.com/#website",
      "name": "Example Corp",
      "url": "https://vibecodinglist.com",
      "publisher": { "@id": "https://vibecodinglist.com/#organization" }
    }
  ]
}
</script>
```

The addresses in that example are this site's. The names are not. Replace `Example Corp`
with the organisation's real name, which is the one thing here that cannot be filled in
from the outside.

Work out how to generate this in whatever stack this project uses, from the same data
that renders the page, so the two cannot drift apart.

Two mistakes account for most broken structured data in the wild. Avoid both:

1. **Do not let the template escape the JSON.** A templating engine that escapes variables
   by default will turn every `"` into `&quot;`, and the block will look perfectly correct
   in the page source while no consumer on earth can parse it, because HTML entities
   inside a `<script>` are never decoded. Use the raw output form the templating engine
   provides:
   `dangerouslySetInnerHTML` in React, `{{{ }}}` in Handlebars, `| safe` in Jinja or
   Nunjucks, `@Html.Raw` in Razor.

2. **Do not inject the block with JavaScript.** Tag managers and client-side SEO plugins
   add it after the page loads, so a crawler that does not run scripts, which is most of
   them, sees nothing at all. The block belongs in the HTML the server sends.

Several separate blocks on one page are fine; the specification requires consumers to
merge them all. A single `@graph`, as above, is just tidier.

The whole report, as markdown, is at https://goodforbots.com/r/vibecodinglist.com.md?scan=cmussbz7b000h01p0fdta0wd3. 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 vibecodinglist.com scored 70/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: state a position on AI crawlers in robots.txt.

The check it fails is "States a position on AI crawlers", worth 5 points. What the scanner saw: robots.txt states AI usage preferences, but names no AI crawler individually.

A `robots.txt` that says nothing about AI crawlers leaves every operator to guess what
this site wants, and they guess differently. The point of this task is to state a
position, whichever position that is.

The thing most people get wrong: the major operators run **separate crawlers for
separate purposes**, and blocking one does not block the others. OpenAI runs GPTBot for
training, OAI-SearchBot for search indexing, and ChatGPT-User for pages a user asks
about. Anthropic runs ClaudeBot, Claude-SearchBot and Claude-User for the same three
jobs. Decide about each job, not about the vendor.

A common and reasonable position is to refuse training while staying visible in AI
answers:

```
# Training: no
User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: CCBot
Disallow: /

# Search and user-requested fetches: yes
User-agent: OAI-SearchBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Claude-User
Allow: /
```

Work out what this project wants before copying that. Allowing everything is
equally valid and earns exactly as much here; what is being measured is whether there is
an explicit answer, not which answer it is.

Blocking a documented search or user-fetch control declares a refusal of that route.
Some user-triggered fetchers may still retrieve a page; do not promise complete invisibility.
Google-Extended also controls grounding, while CCBot publishes a reusable dataset.
Their training opt-outs remain neutral in our score.

Two things about how this is judged. The list of crawler tokens we recognise is a
snapshot of a moving target: operators add crawlers faster than any scanner tracks them.
A rule for a token we have not seen yet is a good rule that earns nothing here until we
catch up. And a position stated in a vocabulary rather than in rules, such as
`Content-Signal`, is a different check; this one is about the `User-agent` groups.

Use the operator sources in the report's crawler catalogue. Unconfirmed or retired names
do not count; aliases for one control count once. One mixed-use control still
counts as one engagement group.

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