Marketing & SEO Workflows

Builds a Branded Search campaign — defensive coverage on the business's own brand terms plus optional competitor conquesting — with trademark-aware ad copy and the brand-exclusion coordination that keeps PMax/Shopping from cannibalizing brand traffic. Emits a human .xlsx plus a campaign-spec.json (brandedsearch). Reads account-context.yaml. Use when the user says "branded search", "brand campaign", "defend my brand", "competitor conquesting", "bid on my own name".

Builds a Demand Gen campaign blueprint — audience-led, creative-heavy campaigns across YouTube, Discover, and Gmail. Covers audience strategy (your-data, lookalikes, custom segments), image and video creative sets, ad formats, and the upper/mid-funnel measurement caveats. Emits a human .xlsx plus a campaign-spec .json (demandgen). Reads account-context.yaml. Use when the user says "demand gen", "demand generation", "youtube campaign", "discovery ads", "top of funnel".

Builds a complete Performance Max campaign blueprint: chooses a split strategy (campaign-level + asset- group-level), then designs asset groups, listing groups, ad copy (headlines/long headlines/descriptions), search themes, audience signals, sitelinks, negatives, image/video briefs, budget/bidding ramp, landing- page requirements, and an Editor-ready workbook. Generalized for any business: reads account-context.yaml, no brand/vertical hardcoding. Use when the user says "build pmax", "performance max", "create a pmax campaign", "pmax blueprint".

Builds a standard Search campaign blueprint: ad-group structure (tight theming), keyword lists with match types, responsive search ads (RSAs), negative keyword lists, extensions, and bidding. Emits a human .xlsx plus a campaign-spec.json (adgroups variant) the pusher can export to Google Ads Editor. Reads account-context.yaml; no hardcoding. Use when the user says "build search", "search campaign", "keyword campaign", "create search ads".

Validates conversion tracking BEFORE any spend — the 1 failure point in Google Ads accounts. Checks conversion actions (purchase/lead), counting settings, primary vs secondary, double-count risk by source (store channel e.g. Shopify vs GA4 import vs gtag), enhanced conversions, server-side/CAPI, and value tracking — and judges them HOLISTICALLY (which actions each campaign actually fires) before any verdict. Use when the user says "conversion tracking", "is my tracking right", "GA4 import", "enhanced conversions", "why are my conversions wrong", or as the gate before plan/builder.