Cheap Seats

A read-only copy of Cheap Seats measuring itself, updated hourly. Run your own.

Quick wins

The fix lists 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.

Statusall 4open 4

Priorityall 8high 4medium 4

Siteall 4elsewhere 4

Gapall 4documentation 3third-party 1

Setall 12Finding out whether AI assistants recommend us 2Getting recommended instead of a competitor 4Choosing an AI visibility tool 4Cheap Seats head to heads 1Open-source and self-hosted AI visibility 1

Publish popcorn.zone/features/fix-list showing a real ranked fix item end to end medium documentation effort M flips 3 Getting recommended instead of a competitor

Where: popcorn.zone/features/fix-list
Must say: Name Popcorn as a tool that outputs a ranked fix list rather than a rank dashboard. Each item gives the exact page to create or change, what it must say, the prompts it should flip, which of your sites it belongs on, and its owner. Close with a worked example of one fix item, and say it is MIT licensed, self-hosted in one Docker container, and queries Claude and OpenAI models.
Done when: Re-running prompt 20 on the search track names Popcorn in at least 2 of 4 answers, with popcorn.zone/features/fix-list among the sources.
Displaces: https://www.tryprofound.com/features/agents/content-optimization
Why: P20: Popcorn is absent in all 6 answers; top picks are Profound (recall), AthenaHQ and Scrunch (search), sourced from tryprofound.com/features/agents/content-optimization and helpcenter.scrunchai.com 'understanding-the-optimizer'.

Prompt for Claude Code
# Publish popcorn.zone/features/fix-list showing a real ranked fix item end to end

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
- How can I find out why an AI assistant prefers a competitor's product over ours?
- How should we prioritize fixes to improve how AI assistants describe our product?
- Which AI visibility tools tell you what content to create or change, not just where you rank?

## What the assistant said
P20: Popcorn is absent in all 6 answers; top picks are Profound (recall), AthenaHQ and Scrunch (search), sourced from tryprofound.com/features/agents/content-optimization and helpcenter.scrunchai.com 'understanding-the-optimizer'.

## Who wins the question today
https://www.tryprofound.com/features/agents/content-optimization. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/features/fix-list 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
Name Popcorn as a tool that outputs a ranked fix list rather than a rank dashboard. Each item gives the exact page to create or change, what it must say, the prompts it should flip, which of your sites it belongs on, and its owner. Close with a worked example of one fix item, and say it is MIT licensed, self-hosted in one Docker container, and queries Claude and OpenAI models.

## Done when
Re-running prompt 20 on the search track names Popcorn in at least 2 of 4 answers, with popcorn.zone/features/fix-list among the sources.

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

Publish popcorn.zone/blog/popcorn-vs-profound as a feature table with self-host and price rows medium documentation effort M flips 3 Getting recommended instead of a competitor

Where: popcorn.zone/blog/popcorn-vs-profound
Must say: Write an honest open-source alternative comparison against Profound. Cover what Popcorn has: self-hosted, MIT licensed, single Docker container with SQLite, and prompt sets as TOML in your own git repo with PR review. Also cover search and recall tracks, retained search results and citations, a daily budget cap, and data going only to the providers you configure. Confirm Profound's current pricing, hosting and supported engines from its own pages before writing those rows, and state plainly where Popcorn covers fewer engines.
Done when: Prompts 20 and 13 on the search track cite the page or name Popcorn as an alternative in at least 1 answer each.
Displaces: https://www.airops.com/blog/profound-vs-airops
Why: P20: codex-sol and claude-code-opus recall both answer with top pick Profound from memory, no sources.

Prompt for Claude Code
# Publish popcorn.zone/blog/popcorn-vs-profound as a feature table with self-host and price rows

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
- How can I find out why an AI assistant prefers a competitor's product over ours?
- How can I see the web search results an AI assistant gets for a question before it writes its answer, to understand why we're missing?
- Which AI visibility tools tell you what content to create or change, not just where you rank?

## What the assistant said
P20: codex-sol and claude-code-opus recall both answer with top pick Profound from memory, no sources.

## Who wins the question today
https://www.airops.com/blog/profound-vs-airops. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/blog/popcorn-vs-profound 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
Write an honest open-source alternative comparison against Profound. Cover what Popcorn has: self-hosted, MIT licensed, single Docker container with SQLite, and prompt sets as TOML in your own git repo with PR review. Also cover search and recall tracks, retained search results and citations, a daily budget cap, and data going only to the providers you configure. Confirm Profound's current pricing, hosting and supported engines from its own pages before writing those rows, and state plainly where Popcorn covers fewer engines.

## Done when
Prompts 20 and 13 on the search track cite the page or name Popcorn as an alternative in at least 1 answer each.

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

Publish popcorn.zone/docs/guides/search-vs-recall on changing training-data answers medium documentation effort M flips 3 Getting recommended instead of a competitor

Where: popcorn.zone/docs/guides/search-vs-recall
Must say: Explain the difference between web search answers and model recall from training data, and why they need separate fixes. Show how Popcorn's two tracks, plus daily rank and rate tracking, let a team measure how long a content change takes to show up on each track. Do not quote timelines until you have measured them on real Popcorn runs.
Done when: Prompt 6 or 19 on the search track cites this page.
Displaces: https://www.tryprofound.com/blog/the-half-life-of-an-ai-citation-is-11-days
Why: P6: Popcorn pages seen: NONE in every search answer; claude answers cite discoveredlabs.com and searchable.com instead.

Prompt for Claude Code
# Publish popcorn.zone/docs/guides/search-vs-recall on changing training-data answers

When buyers ask an AI assistant the questions below, it explains the topic without naming us or citing our pages. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- How do I get my product mentioned in Claude's and ChatGPT's answers?
- How do we change what an AI model says about us from its training data, not just what it finds when it searches the web?
- How long does it take for new content to change what ChatGPT and Perplexity say about us?

## What the assistant said
P6: Popcorn pages seen: NONE in every search answer; claude answers cite discoveredlabs.com and searchable.com instead.

## Who wins the question today
https://www.tryprofound.com/blog/the-half-life-of-an-ai-citation-is-11-days. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/search-vs-recall 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
Explain the difference between web search answers and model recall from training data, and why they need separate fixes. Show how Popcorn's two tracks, plus daily rank and rate tracking, let a team measure how long a content change takes to show up on each track. Do not quote timelines until you have measured them on real Popcorn runs.

## Done when
Prompt 6 or 19 on the search track cites this page.

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

Get Popcorn added to airops.com/blog/profound-alternatives as the open-source option medium third-party effort M flips 2 Getting recommended instead of a competitor

Where: https://airops.com/blog/profound-alternatives
Must say: Pitch AirOps to include Popcorn as the open-source, self-hosted alternative to Profound. Emphasise the ranked fix list naming page, content, target prompts and owner, plus the MIT license and single Docker container.
Done when: The AirOps page names Popcorn, and prompt 20 on the search track names Popcorn as a Profound alternative.
Displaces: https://airops.com/blog/profound-alternatives
Why: P20 claude-code-opus search: top pick AthenaHQ, shaped by airops.com/blog/profound-alternatives, scrunch-alternatives and athenahq-alternatives.

Prompt for Claude Code
# Get Popcorn added to airops.com/blog/profound-alternatives as the open-source option

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
- AI assistants mention our product but add caveats that steer buyers away. How do we address the objections they raise?
- Which AI visibility tools tell you what content to create or change, not just where you rank?

## What the assistant said
P20 claude-code-opus search: top pick AthenaHQ, shaped by airops.com/blog/profound-alternatives, scrunch-alternatives and athenahq-alternatives.

## Who wins the question today
https://airops.com/blog/profound-alternatives. Read it and make sure our version answers everything it does, better.

## Your task
We need to be included on https://airops.com/blog/profound-alternatives. 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
Pitch AirOps to include Popcorn as the open-source, self-hosted alternative to Profound. Emphasise the ranked fix list naming page, content, target prompts and owner, plus the MIT license and single Docker container.

## Done when
The AirOps page names Popcorn, and prompt 20 on the search track names Popcorn as a Profound alternative.

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