Quick wins

# Get Popcorn listed in Rankability's best AI search visibility tracking tools article

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a third-party gap: the roundups and comparisons the model reads leave us out.

## The questions it affects
- Our organic traffic is down and I suspect ChatGPT and Google AI Overviews. How do I check whether AI search is what's taking it?
- What tools track how often AI assistants like ChatGPT, Claude, Perplexity and Gemini mention a brand?
- How do I monitor whether AI search engines cite our website?
- Which questions should we track to measure AI visibility, and how many prompts do we need before the numbers mean anything?
- How can I see which web pages AI assistants rely on when they answer questions in my category?

## What the assistant said
Rankability shaped the search answers in P1, P2, P5, P8 (twice), P11 and P12. P8 top pick was Peec AI.

## Who wins the question today
https://rankability.com/blog/best-ai-search-visibility-tracking-tools/. Read it and make sure our version answers everything it does, better.

## Your task
We need to be included on https://rankability.com/blog/best-ai-search-visibility-tracking-tools/. Read that page first, work out the right way in (editor contact, submission form, PR, comments), and draft exactly what to send: a short, factual pitch covering the points below, in the page's own format.

## What it must say
Ask the editor to add Popcorn as the open-source, self-hosted option. Supply a one-paragraph entry: MIT licensed, a single Docker container, asks Claude and OpenAI models on search and recall tracks, grades recommended/mentioned/absent with share of voice, and outputs a ranked fix list. Link github.com/metcalfc/popcorn.

## Done when
The Rankability article lists Popcorn, and a re-run of prompt 5 or 8 cites the article with Popcorn in the answer.

## 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.

# Rewrite cheapseatsdev/cheapseats README top: coverage, cost, grading, docs link

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 vs Profound for tracking whether AI assistants recommend us: which should I pick?
- Cheap Seats vs Otterly.AI for a startup that wants to track AI visibility cheaply?
- How does Cheap Seats compare with Gauge for tracking and improving AI visibility?
- 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 an agency tracking AI visibility for many clients?
- Is Cheap Seats a good fit for a developer-tools company checking whether ChatGPT and Claude recommend it?

## What the assistant said
"very new", has "0 GitHub stars, no releases yet", tracks only Claude and ChatGPT (P3, claude-code-opus search)

## Your task
Write or update the page at https://github.com/cheapseatsdev/cheapseats (README.md, About, Releases) 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 when they find it they recommend it (P1, P4, P6 search). Yet they report "0 stars, no releases" and "Claude and ChatGPT only" with no context. The first screen of the README must state:
- what it does: asks buyer questions on a search and a recall track, grades recommended/mentioned/absent, and builds a ranked fix list naming page, claim, prompts and owner;
- cost: free under MIT, you pay only API usage under a daily budget cap, or use existing Claude Code/Codex subscriptions;
- coverage: Claude and OpenAI models only;
- links to cheapseats.dev/docs and /compare.
Also cut a tagged release with notes, add the topics ai-visibility, ai-visibility-tracking, geo and aeo, and note the rename from Popcorn.

## Done when
On a re-run, no search answer that cites the repo says "no releases", and every answer citing it states the cost model and the coverage correctly.

## 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.