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/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/docs/guides/prove-content-impact on daily runs and fix-to-prompt proof

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 often should we re-check whether AI assistants recommend us, and how do we track changes over time?
- How do I prove to leadership whether our content work is changing what AI assistants recommend?

## What the assistant said
P14 claude search: top pick 'Otterly.AI'. Codex cited help.otterly.ai/monitoring-interval.

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

## Your task
Write or update the page at popcorn.zone/docs/guides/prove-content-impact 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 re-check and report change. Set a daily run within a daily budget, watch the day-by-day share-of-voice rank and rates, and tie each shipped fix to the prompts it was meant to flip. Report those prompts before and after, with the stored answers and citations as proof. Include a sample leadership one-pager built from the fix list's 'prompts it should flip' field.

## Done when
A re-run of prompt 14 or 15 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/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.

# Publish popcorn.zone/docs/guides/search-vs-recall explaining both tracks with an example

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
- Do ChatGPT and Claude say different things about a product with web search on versus from training data alone, and how do I measure both?

## What the assistant said
P13: every search answer was shaped by vendor API docs and generic tool lists. No source explained measuring both modes.

## Who wins the question today
https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool. 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 that each question can be asked with web search forced on or with no tools at all. The two give different answers because one reflects current web pages and the other reflects training data. Show how Popcorn runs both tracks on every prompt and reports them side by side. Include a real anonymised example where the two tracks disagree; pick it from a Popcorn run first.

## Done when
A re-run of prompt 13 cites this page 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/docs/guides/diagnose-ai-traffic-loss: GSC, Bing, GA4 then Popcorn

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
- 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?
- How can I tell whether Google AI Overviews and AI Mode mention our brand for the topics we care about?

## What the assistant said
P7 codex search: top pick 'Ahrefs Brand Radar', shaped by support.google.com/webmasters/answer/16984139.

## Who wins the question today
https://developers.google.com/search/blog/2026/06/gen-ai-performance-reports. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/diagnose-ai-traffic-loss 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
Cover the free first-party checks: Search Console generative AI performance reports, Bing Webmaster Tools AI Performance, and GA4 referrals with utm_source=chatgpt.com. Then explain the gap those leave: they show clicks and impressions, not whether the assistant recommends you or a competitor. Close that gap by running the buyer questions on Popcorn's search track for AI Overviews-style answers and its recall track for model belief.

## Done when
A re-run of prompt 1 or 7 cites this page 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/docs/guides/choosing-prompts with measured prompt-count variance

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
- Which questions should we track to measure AI visibility, and how many prompts do we need before the numbers mean anything?

## What the assistant said
P11 codex search: top pick 'Ahrefs Brand Radar', shaped by ahrefs.com/aeo/choose-prompts-to-track.

## Who wins the question today
https://cloro.dev/blog/ai-visibility-sample-size/. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/choosing-prompts 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 method for picking buyer questions: split them into category, comparison, problem and info prompts, and store them as TOML files changed through pull requests. Give sample-size guidance only after measuring it: run one prompt set repeatedly in Popcorn and publish the observed run-to-run variance in the recommended rate. Do not cite a prompt count without that data.

## Done when
A re-run of prompt 11 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.