Act on your results

Quick wins

The pages to improve first, ranked by the buyer questions they could help you win.

1 of 40 fixes

How fixes are ranked

The fix lists come from the latest run of every prompt set, core sets first, then fastest expected ranking gain: prompts a fix could flip per working day, each weighted by what it has left to win (one minus its recommended rate over the last two weeks; named, for an info prompt). Mark a fix with the commit or pull request you submitted for it; open leaves out the ones you have. A later fix for the same page stays open, with what was tried before.

Cut a tagged v0.1 GitHub release and rewrite the README top section with fit and linkshttps://github.com/cheapseatsdev/cheapseatsdocumentation · Cheap Seats head to heads · github.com/cheapseatsdev/cheapseatsurgentEffort SCould flip 4 prompts

Where: https://github.com/cheapseatsdev/cheapseats
Must say: The repo is the only Cheap Seats page assistants find, and every time Claude found it, Claude recommended Cheap Seats. It still drew '0 stars, no releases, very new' objections. Tag a v0.x release with a changelog and a Docker image tag, and open the README with a one-line category statement, the engines covered, a quickstart (single Docker container, SQLite, Helm, exe.dev), the daily budget cap, a 'who it fits' list (dev-tools teams: TOML prompt sets in git reviewed by PR, CLI, MCP server), and links to cheapseats.dev docs and compare pages.
Done when: Re-running prompts 5, 6, 7 and 10, no answer cites 'no releases' as an objection, and the Claude search answers still pick Cheap Seats first.
Why: P5 claude search objections: "very new project; 0 GitHub stars and no releases; grading accuracy undocumented".

Prompt for Claude Code

# Cut a tagged v0.1 GitHub release and rewrite the README top section with fit and links

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Cheap Seats or Semrush AI Toolkit for tracking our brand in ChatGPT and Claude?
- Is Cheap Seats a good open-source alternative to paid AI visibility tools?
- What are the downsides of self-hosting Cheap Seats to measure AI search visibility?
- Is Cheap Seats a good fit for a developer-tools company checking whether ChatGPT and Claude recommend it?

## What the assistant said
P5 claude search objections: "very new project; 0 GitHub stars and no releases; grading accuracy undocumented".

## Your task
Write or update the page at https://github.com/cheapseatsdev/cheapseats so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
The repo is the only Cheap Seats page assistants find, and every time Claude found it, Claude recommended Cheap Seats. It still drew '0 stars, no releases, very new' objections. Tag a v0.x release with a changelog and a Docker image tag, and open the README with a one-line category statement, the engines covered, a quickstart (single Docker container, SQLite, Helm, exe.dev), the daily budget cap, a 'who it fits' list (dev-tools teams: TOML prompt sets in git reviewed by PR, CLI, MCP server), and links to cheapseats.dev docs and compare pages.

## Done when
Re-running prompts 5, 6, 7 and 10, no answer cites 'no releases' as an objection, and the Claude search answers still pick Cheap Seats first.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

From this run →