Quick wins

# Publish popcorn.zone/docs/guides/benchmark-against-competitors on share-of-voice rank

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
- Is there a way to measure our share of voice in AI chatbot answers?
- What's the best way to benchmark my brand's visibility in LLM answers against competitors?
- What metrics should a marketing team use to measure presence in AI assistant answers?

## What the assistant said
P9: top picks were Profound, Peec AI, Scrunch and Peec AI across the search answers.

## Who wins the question today
https://help.peec.ai/article/decision-lab-what-is-share-of-voice-and-how-is-it-calculated-23. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/benchmark-against-competitors 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 how to benchmark against competitors. Popcorn records every product named in each answer, computes each prompt set's share-of-voice rank and recommended/mentioned rates day by day, and keeps the answers and citations behind each number. Include a worked example showing the competitor table and the rank trend, and explain why comparing top-pick counts on the same prompt set is the fair benchmark.

## Done when
A re-run of prompt 9 or 6 names Popcorn or 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.

# Publish popcorn.zone/blog/prioritize-ai-visibility-fixes with an owner-by-fix-type table

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 should we prioritize fixes to improve how AI assistants describe our product?
- What are the quickest wins for improving our brand's visibility in AI search?
- Who should own AI visibility work: SEO, content, product marketing or the docs team?

## What the assistant said
P18 claude-code-opus search: top pick SEO, shaped by guptadeepak.com/the-geo-org-chart-who-actually-owns-ai-visibility-in-2026.

## Who wins the question today
https://guptadeepak.com/the-geo-org-chart-who-actually-owns-ai-visibility-in-2026/. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/blog/prioritize-ai-visibility-fixes 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
Give a prioritisation method: rank fixes by prompts they could flip times how directly they address the stated reason for losing. Assign each fix to a site and an owner (docs, product marketing, SEO). Show that Popcorn's fix list carries exactly these fields, including owner.

## Done when
Prompt 16 or 18 on the search track cites this post.

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

# Publish popcorn.zone/docs/guides/check-if-chatgpt-recommends-you with a 15-minute walkthrough

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 whether ChatGPT recommends my product when people ask about my category?
- What tools track how often AI assistants like ChatGPT, Claude, Perplexity and Gemini mention a brand?

## What the assistant said
P3 recall: top pick Peec AI. Search: top pick Otterly.AI. Codex cited help.openai.com/en/articles/8590148-memory-in-chatgpt.

## Who wins the question today
https://www.superlines.io/articles/best-chatgpt-tracking-tools. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/check-if-chatgpt-recommends-you 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 a step-by-step how-to. Write 10-20 buyer questions as a TOML prompt set, run docker, configure OpenAI (ChatGPT's provider) and Claude keys or the local Codex/Claude Code CLIs, and set a daily budget. Then read the recommended/mentioned/absent grade, position and top pick for each question. Show a sample graded answer and contrast it with checking by hand in ChatGPT, where memory and personalisation skew results.

## Done when
A re-run of prompt 3 cites this page or names Popcorn in at least one search 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.

# Publish popcorn.zone/blog/ai-visibility-tools-compared: Popcorn vs Peec, Profound, Otterly, Scrunch

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 whether ChatGPT recommends my product when people ask about my category?
- What tools track how often AI assistants like ChatGPT, Claude, Perplexity and Gemini mention a brand?
- Is there a way to measure our share of voice in AI chatbot answers?
- How do I monitor whether AI search engines cite our website?
- What's the best way to benchmark my brand's visibility in LLM answers against competitors?
- How can I see which web pages AI assistants rely on when they answer questions in my category?

## What the assistant said
P5 search answers were shaped by tryprofound.com, peec.ai, otterly.ai and scrunch.com. 'Popcorn pages seen: NONE.'

## 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
Write or update the page at popcorn.zone/blog/ai-visibility-tools-compared 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
Compare Popcorn with Peec AI, Profound, Otterly.AI, Scrunch, Ahrefs Brand Radar and Semrush AI Visibility row by row. Popcorn's rows: MIT licensed and self-hosted (one Docker container with SQLite); TOML prompt sets in your own git repo; Claude and OpenAI via API or local Claude Code/Codex CLIs; separate search and recall tracks; recommended/mentioned/absent grading with position, top pick, share of voice and objections; a ranked fix list; a daily budget cap. Confirm competitor engines and pricing from their own pages, and date the table. The homepage 'alternative to Peec AI and Profound' line is still pending, but a tagline cannot be cited as a comparison, so this page has to exist separately.

## Done when
On a re-run of prompts 3, 5, 6, 8, 9 and 12, at least one search answer names Popcorn or 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.

# Get popcorn.zone indexed: submit sitemap to Bing/Google, add llms.txt and JSON-LD

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 or Peec AI for a small marketing team?
- 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?
- 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?
- How does Cheap Seats decide whether an AI assistant recommended a brand?
- 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 does it cost to run Cheap Seats every day, and how do I keep the spend under control?

## What the assistant said
P8 search cites badpopcorn.ai/how-it-works, not popcorn.zone/docs/how-grading-works, even though that page shipped in PR #8.

## Who wins the question today
https://badpopcorn.ai/?lang=en. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at https://popcorn.zone/sitemap.xml 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
Neither the homepage rewrite (PR #4) nor /docs/how-grading-works (PR #8) has been seen in any search answer; the target is still 'not seen', so the pages are not being retrieved at all. Submit popcorn.zone/sitemap.xml to Bing Webmaster Tools and Google Search Console and request indexing for /, /docs and /docs/how-grading-works. Add /llms.txt that opens 'Popcorn (popcorn.zone) is an MIT-licensed, self-hosted AI visibility tracker, source at github.com/metcalfc/popcorn; not affiliated with badpopcorn.ai, trypopcorn.ai, popcorn.co or popcorn.ai'. Add SoftwareApplication JSON-LD with license MIT and sameAs pointing to the GitHub repo. Link the homepage and the GitHub README to every docs page.

## Done when
Bing 'site:popcorn.zone' lists /docs/how-grading-works, and on a re-run at least one popcorn.zone URL appears in 'Popcorn pages seen' for 4 or more of the 11 prompts, including prompt 8.

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

# Publish popcorn.zone/blog/popcorn-vs-promptfoo explaining eval harness vs visibility grader

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
- Is there an open-source alternative to Profound or Peec AI?
- Is there a self-hosted AI visibility tracker I can run in Docker?
- What's a good open-source way for a developer-tools startup to check whether AI assistants recommend it over alternatives?
- Can I test the same buyer questions against several AI models and compare the answers?
- How do engineering-led companies measure whether LLMs recommend their product, without a marketing tool?

## What the assistant said
P16: top pick promptfoo on both the recall and search answers from claude-code-opus

## Who wins the question today
https://github.com/promptfoo/promptfoo. 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-promptfoo 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
Promptfoo is the assistants' default recall answer, so position Popcorn against it. Explain that Promptfoo is a general LLM eval tool, while Popcorn is built for brand visibility. Popcorn grades each answer recommended, mentioned or absent, records position, top pick, share of voice and objections, and builds a ranked fix list naming the page, the claim and the prompts it should flip.

## Done when
Rerun prompts 11 and 16 on search. Popcorn is named alongside or above Promptfoo in at least one 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.

# Publish popcorn.zone/docs/self-hosting with Docker, Helm/Kubernetes and exe.dev install

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
- We want to track AI answer visibility without sending our data to another SaaS vendor. What are our options?
- Is there a self-hosted AI visibility tracker I can run in Docker?
- Can we run an AI search visibility tracker on our own Kubernetes cluster?
- What's the cheapest way to track our brand in AI answers ourselves instead of paying for a SaaS subscription?

## What the assistant said
P6: top pick Gego, from hub.docker.com/r/ouai2h/gego, with no Popcorn page seen

## Who wins the question today
https://github.com/elmohq/elmo. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/self-hosting 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
Give a copy-paste `docker run` command, a Helm install for Kubernetes, and exe.dev VM steps. State that it is a single container with a SQLite file. State that prompts and answers go only to the model providers you configure, so no third-party SaaS vendor sees your data. Title and H1 should read 'Self-hosted AI visibility tracker: Docker and Kubernetes'.

## Done when
Rerun prompts 5 and 6 on search. Popcorn's docs page appears among the sources, and at least one answer names Popcorn as its Docker or Kubernetes pick.

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

# Publish popcorn.zone/docs/cli-and-ci with a scheduled CI workflow example

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
- Can I run AI visibility checks from the command line or in a CI pipeline?
- Can I test the same buyer questions against several AI models and compare the answers?
- How can I automatically ask ChatGPT and Claude the same set of questions every week and track how their answers about my category change?

## What the assistant said
P9: 'says only that the Popcorn repo "also appears on that topic page", giving no reasons to use it'

## Who wins the question today
https://llmpulse.ai/features/cli. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/cli-and-ci 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
Show the Popcorn CLI running a prompt set and exiting with the share-of-voice and recommended-rate results. Include a scheduled CI example that runs the set weekly; confirm the exact commands and the exit-code behaviour with engineering before publishing. State that the TOML prompt sets live in git and that changes go through pull requests, which LLM Pulse's hosted CLI does not offer.

## Done when
Rerun prompts 9 and 14 on search. Popcorn is recommended, not merely mentioned, in at least one answer, and this page is cited.

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

# Publish popcorn.zone/docs/cost explaining AI visibility pricing drivers and Popcorn's cost

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
- Otterly.AI or Peec AI for tracking AI search visibility on a tight budget?
- What's a cheap way to start measuring AI visibility for a small startup?
- How do AI visibility tools price their plans, and what drives the cost: prompts, models, brands or seats?

## What the assistant said
P13 search: shaped by otterly.ai/alternatives/pricing and get-ryze.ai pricing comparison.

## Who wins the question today
https://otterly.ai/alternatives/pricing/. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/cost 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 that hosted tools price by prompts, engines, brands and seats. Contrast that with Popcorn: no license fee (MIT), and cost is only your model API spend under a configurable daily budget, or $0 extra when run through the Claude Code and Codex subscriptions you already have. Add a worked example once the cost per run has been measured for a typical prompt set.

## Done when
Prompts 13 and 11 on the search track cite this page or name Popcorn 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.

# Publish popcorn.zone/docs/self-hosting covering upkeep, costs, data flow and tradeoffs

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

## What the assistant said
P7: 'couldn't verify an official self-hosted AI visibility project under that name'.

## Who wins the question today
https://brandcitation.com/methodology. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at https://popcorn.zone/docs/self-hosting 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 self-hosting page that answers the objections the assistants invented. Maintenance: one container plus a SQLite file, with upgrade steps. Costs: a daily budget cap on API calls, or local CLIs on existing subscriptions. API vs consumer answers: the search track forces web search and the recall track uses no tools. Trend discipline: daily share-of-voice rank with every answer and citation kept. Data control: prompts go only to the providers you configure.

## Done when
Re-running prompt 7 shows popcorn.zone/docs/self-hosting cited in at least one search answer, and no answer says it 'couldn't verify an official self-hosted project'.

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

# Publish popcorn.zone/docs/costs with measured per-run spend and daily budget config

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 Otterly.AI for a startup that wants to track AI visibility cheaply?
- What does it cost to run Cheap Seats every day, and how do I keep the spend under control?

## What the assistant said
P11 search cites docs.popcorn.co/getting-started/pricing-and-credits, a different product.

## Who wins the question today
https://docs.popcorn.co/getting-started/pricing-and-credits/. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at https://popcorn.zone/docs/costs 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 that Popcorn the software is free (MIT) and the only running cost is model calls. Show how the daily budget caps API spend and how running through local Claude Code/Codex CLIs uses existing subscriptions. Publish a measured example first: the cost of one daily run of an 11-prompt set on both tracks for each configured model, measured before publishing.

## Done when
Re-running prompt 11 cites popcorn.zone/docs/costs instead of docs.popcorn.co or popcornai.art pricing.

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

# Publish popcorn.zone/docs/models-keys-and-budget: own API keys, CLI subscriptions, daily cap

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
- Should we build our own AI visibility tracker on the OpenAI and Anthropic APIs, or buy a tool?
- Which AI visibility tools let us use our own OpenAI and Anthropic API keys?
- How much does it cost in API fees to run our own AI visibility checks every day, and how do we cap it?
- What's the cheapest way to track our brand in AI answers ourselves instead of paying for a SaaS subscription?

## What the assistant said
P7: top picks were Lettertrace and an Apify actor; Popcorn was absent on all four answers

## Who wins the question today
https://www.producthunt.com/products/lettertrace. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/models-keys-and-budget 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 that Popcorn calls Claude and OpenAI through your own API keys, or through local Claude Code and Codex CLIs on your own subscriptions. Explain that a daily budget caps API spend. Include a worked cost example for N prompts × 2 tracks × M models per day, but measure real token and web-search costs from a Popcorn run before publishing any figures.

## Done when
Rerun prompts 7 and 8 on search. At least one answer cites this page and names Popcorn as supporting your own OpenAI and Anthropic keys with a spend cap.

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