google-ads-search-launchlisted

# google-ads-search-launch Source playbook: `playbooks/google-ads-search-launch/playbook.md`. This file is the Claude Code playbook shell over that runtime-agnostic source. This is a reusable draft operating playbook, not a one-off ad checklist. Use it with manual operator judgment when the operator wants to test whether a real offer can turn paid search intent into leads, calls, bookings, deposits, trials, or another concrete business outcome. It is usable today as a manual recipe and run-record template. It is not a single executable orchestrator, does not automate Google Ads/GTM, and is still collecting evidence from operator runs. The playbook's job is to turn one offer into one paid-search proof run: 1. define the bet and success criteria; 2. prepare or verify the lander and conversion path; 3. build a tightly scoped Google Ads Search plan; 4. preserve manual approval gates before spend or provider mutation; 5. record the run as a push playbook with review evidence and an outcome hook. It does not publish campaigns, change budgets, upload conversions, publish GTM, or mutate provider accounts. Those steps stay manual or provider-native until a future accepted adapter ships with approval gates and smoke evidence. ## Playbook Versus Run This file is the reusable Noontide recipe: an opinionated paid-search offer-validation sprint. The run belongs in the business repo: ```text pushes/<push>/playbooks/google-ads-launch-plan.md ``` Create or update that run file from