Quick wins

# 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/see-ai-search-results with CLI and UI steps

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?

## What the assistant said
P13 codex-sol search: top pick Profound, sourced from tryprofound.com/blog/expanding-analysis-for-query-fanouts-in-profound.

## Who wins the question today
https://www.tryprofound.com/features/answer-engine-insights/query-fan-out. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/see-ai-search-results 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 how-to on running a question on Popcorn's search track and opening the stored search results and citations the assistant used before it answered. Cover it in the web UI, CLI, JSON API and MCP server. Explain how comparing those results against the answer, the top pick and the objections raised shows why a competitor won.

## Done when
Prompt 13 on the search track cites popcorn.zone/docs and names Popcorn in at least 1 of 4 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.