/improve-search-visibility

name: improve-search-visibility
description: >-
  Search and AI-answer visibility (SEO, AEO, GEO). Use when the marketer asks "am I in the answer when
  people ask ChatGPT or Google for products like mine?", "improve my SEO", "why does ChatGPT recommend
  my competitor", "are we in AI Overviews", "organic traffic is flat", "ChatGPT says something wrong
  about us", "fix my app store listing" or "my Google Business Profile and local search". Shows,
  question by question, where the brand is named and who wins instead, with a search roadmap and five
  fixes to apply this week. Never edits anything live. Not for writing the full page — use
  make-content; not Amazon or marketplace listings (not covered yet); not paid search — use
  run-paid-campaigns.
version: 0.1.0

improve-search-visibility

One marketer want: "When people ask ChatGPT or Google for products like mine, am I in the answer — and what do I fix this week?" It follows the research pattern (read `../marketing-guide/research-pattern.md` (in the `marketing-guide` skill) before the first search): a free pass first with no questions, one message with the draft answer and one credit yes, then one readable report.

What you get

1. **The answer and the report in the first turn** — the first message gives counts ("ChatGPT names you on 0 of 8 buying questions; it names A, B and C instead, mostly from vendor 'best of' lists") and links the finished report, with the only decisions left. Nobody has to ask for the report. 2. **One readable report** (through the shared write-report atom), opening with "In short" — what we checked, the findings with how sure, then "Do this first" — then the story: where you show up, where you don't, who wins instead and why, what's broken on your site and profiles, your search roadmap (which page should answer which question, in what order), the five fixes in plain words, what couldn't be checked, and sources. The finished text and code for each fix sit in a closing section for whoever edits the site. It opens with one click and is saved to the brand. 3. **Briefs for the new pages** the roadmap calls for, ready for the page writer.

Before you start

1. **Setup first:** do the `marketing-guide` skill (`../marketing-guide/SKILL.md`) §1–2 (connect, brand, brain read) before anything else; the job line is "I check your search visibility through it." (`get_started` with `wants: "more"`; match the named brand loosely: "Goosework" → Gooseworks.) 2. **Read what you already know.** Brain path: chapters 2 "What we sell", 5 "Who we sell to", 7 "Competitors", 8 "Search terms", 9 "Why people pick us" and 17 "Accounts and tools" (Search Console, analytics); `gooseworks:brain_search` for gaps (`[search …]` learnings, a pronunciation fact). Fallback: `gooseworks:brand_read` with sections `summary`, `products`, `onboarding`, `competitors`, `learnings`, `sources` (lean is enough for the claims marker) and `gooseworks:competitor_read`. Then research-audience's `research/audience/voc-bank.md` and research-market's `research/market/demand.md` if present; this playbook's last `search/questions.md`, `search/page-map.md` and latest `search/visibility/` report (a re-run reuses the question set, topped up to the mix in `references/question-list.md`). **Load the last run** — the Start steps of the `run-memory` skill (`../run-memory/SKILL.md`) with `references/run-memory.md`: steps 1–2 now (the last record, its per-question baseline and its open fixes); steps 3–4 after the free pass, from today's answers — each open fix checked for whether it went live (fetch the page, sitemap or profile — every part shown, never "done" from a draft) and, past its review timing from the day it was first seen live, what moved after it. **An earlier run's answers are the baseline, never this run's evidence:** compared like with like (same question, same way of asking), shown as "last checked <date>", never counted in today's numbers. Load the `claims-gate` skill (`../claims-gate/SKILL.md`) and read the contract only. 3. **Ask nothing yet.** No intake questions before the free pass. Countries default to the brand's market from the brain or site (else the US); who ships is unknown until asked; comparison pages are recommended as briefs only until the marketer says competitors may be named. Answers saved on an earlier run (in `search/questions.md`) count as known: the first message states them as assumptions to confirm, never asks them cold. A second run on the same day overwrites that day's files and bumps the roadmap's version.

Steps

1. Free pass — do everything free before the first message

Do all of `references/free-pass.md`, for the brand and its main rivals, without stopping to ask. Two rules on top of it:

• **Rank the draft five** with `references/prioritising.md` before the first message, so the five shown there are the five the report keeps (unless the top-up changes the evidence — then the report says what changed).
• **Every number traces to a source opened this run** (a page read, a search result, an answer captured), cited with its date. A figure from memory — stars, users, funding, prices — is cut or checked first; never write it as fact.

2. One message: the answer, the report, and the decisions left

Write and deliver the report first (step 5's writing and delivery rules) — in the same turn, before this message, never "say the word and I'll write it". Then the message, in plain words, no tool names, ids or codes. On a repeat run it opens with **since last time** in 3–5 lines (run-memory step 4): today's count against the last check's on the same questions, which of last month's fixes shipped and what moved after them, who moved in. Then **counts first** for what was checked this run ("ChatGPT, asked signed out today: named on 0 of 8 buying questions, 5 of 5 brand questions"; with no browser: "web search today: on page one for 1 of 8 buying questions" and ChatGPT "not checked today — last checked 18 Oct"), who wins