Quick wins

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

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

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

# 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/api: JSON API, CLI and MCP reference with dashboard examples

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
- Which AI visibility tools have an API so we can pull the data into our own dashboards?

## What the assistant said
P16 search: shaped by tryprofound.com/blog/introducing-the-profound-api-cookbook and developers.scrunch.com.

## Who wins the question today
https://docs.tryprofound.com/cookbook/introduction.md. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/api 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
Document the JSON API endpoints, the CLI and the MCP server with copy-paste examples for pulling share-of-voice rank, rates by day, answers and citations into a dashboard. Title and headings should use the buyer's words: "AI visibility API" and "export data".

## Done when
Prompt 16 on the search track names Popcorn or cites popcorn.zone/docs/api in at least 1 of 2 answers.

## 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/methodology on sampling, two tracks and auditable 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
- AI answers change every time you ask. How do AI visibility tools make their numbers reliable, and how can I check them?

## What the assistant said
P14 search: shaped by meikai.ai/blog/how-many-times-run-ai-visibility-prompts and thrivestack.ai research.

## Who wins the question today
https://www.meikai.ai/blog/how-many-times-run-ai-visibility-prompts. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/methodology 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 Popcorn makes noisy answers checkable: every question runs on both a search track and a recall track. Rates and share-of-voice rank are tracked day by day, and every answer, search result and citation behind each number is kept for audit. Before publishing, confirm and state the samples per prompt and how day-to-day variance is shown.

## Done when
Prompt 14 on the search track cites popcorn.zone/docs/methodology in at least 1 of 2 answers.

## 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/security on self-hosting, data flow and no third-party data custody

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
- Which AI visibility platforms meet enterprise security requirements like SOC 2?

## What the assistant said
P15 search: top pick Conductor, shaped by citedindex.com/collections/ai-visibility-tools-with-sso-or-soc-2.

## Who wins the question today
https://citedindex.com/collections/ai-visibility-tools-with-sso-or-soc-2. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/security 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
For SOC 2 buyers, state that Popcorn is self-hosted (Docker, Helm on Kubernetes, or an exe.dev VM) and stores data in a SQLite file you control. Prompts and answers go only to the model providers you configure, so there is no third-party vendor to assess. Say plainly that Popcorn itself holds no SOC 2 report.

## Done when
Prompt 15 on the search track names Popcorn as a self-hosted option in at least 1 of 2 answers.

## 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 cheapseats.dev/docs/agencies: multi-client prompt sets, owners, API reporting

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 fit for an agency tracking AI visibility for many clients?

## What the assistant said
"no public listing found in current roundups or comparisons" (P9, claude-code-opus search)

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

## Your task
Write or update the page at https://cheapseats.dev/docs/agencies 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 multi-client workflow: one TOML prompt-set repo per client with changes reviewed through PRs, and fix lists that name which of the brand's sites a fix belongs on and its owner. Cover per-prompt-set share-of-voice rankings tracked daily, the JSON API and MCP server for client reporting, and per-instance daily budgets. Confirm and state whether one instance serves many brands before publishing.

## Done when
On a re-run of P9, at least 1 search answer cites the agencies page and drops 'unverified agency features'.

## 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/raw-data-and-api documenting stored answers, citations, JSON API

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 every raw AI answer and citation behind an AI visibility score, not just a dashboard. Which tools give us that?

## What the assistant said
P10: top pick Scrunch on search for both models, sourced from Scrunch API docs

## Who wins the question today
https://developers.scrunch.com/api-reference/introduction. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/raw-data-and-api 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
State that every answer, search result and citation behind each score is kept in your own SQLite database. Show how to pull them through the JSON API and the MCP server. Include one example JSON response.

## Done when
Rerun prompt 10 on search. Popcorn appears among the tools named for raw answer and citation access.

## 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/how-to-evaluate-ai-visibility-tools with a scored checklist

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 do generative engine optimization tools work, and which ones are worth paying for?
- What should I look for when evaluating AI visibility or GEO tools?
- Are Semrush's AI Toolkit or Ahrefs Brand Radar enough, or do we need a dedicated AI visibility tool?

## What the assistant said
P2 search: no product picked, shaped by piabo.net/comparisons/geo-platforms-compared and tooljunction.io.

## Who wins the question today
https://marketerhire.com/blog/best-generative-engine-optimization-tools. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/blog/how-to-evaluate-ai-visibility-tools 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 buyers concrete criteria to check any tool against:
- Does it separate web-search answers from model recall?
- Does it keep every answer, search result and citation so numbers can be audited?
- Does it grade recommended vs mentioned vs absent, with position and top pick?
- Does it output a ranked fix list naming the page to change?
- Who owns the prompts and data?

Answer prompt 8 directly: Semrush AI Toolkit and Ahrefs Brand Radar track mentions, while a dedicated tool adds per-prompt grading and fixes. Show how Popcorn meets each criterion.

## Done when
Prompts 1, 2 and 8 on the search track cite this page or name Popcorn in at least 2 of 6 answers.

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