google-ads
When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube ads." For paid mix, use paid-ads-strategy.
What this skill does
# Paid Ads: Google Ads
Guides Google Ads setup, campaign structure, keyword targeting, and optimization. Google Ads excels at high-intent search traffic; use when people actively search for your solution.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
## Two Modes: PMF Testing vs Conversion-Driven
| Mode | When | Budget | Landing page | Metrics |
|------|------|--------|--------------|---------|
| **PMF testing** | Pre-PMF; validate idea before building | $47–500; start small | Simple LP: headline, benefits, problem solved, CTA ("Join Waitlist," "Get Early Access") | CTR, sign-up rate, bounce rate; low CTR/high bounce = messaging/positioning issue |
| **Conversion-driven** | PMF validated; commercialization | Scale; ROAS target | Full funnel; ad-to-page alignment | ROAS, CAC, conversion rate |
**PMF testing**: No full product needed. Build landing page with Unbounce, Carrd, or Webflow. Run ads to relevant search terms; measure clicks, engagement, signups. Test messaging (e.g., "Fastest App for Freelancers" vs "Simplest Time Tracker for Teams"), pricing (different price points in ads/LP), and audiences (keyword targeting, in-market). Allow 4–6 weeks for PMax learning phase. Use as learning tool, not just marketing channel.
**Reference**: [Marketing Cactus – Using Google Ads to Test Product-Market Fit](https://mktcactus.com/en/using-google-ads-to-test-product-market-fit-before-launching/)
## Campaign Structure
```
Account
├── Campaign: Brand (Search)
├── Campaign: Non-Brand (Search)
├── Campaign: Competitor (Search) — optional; bid on competitor brand + "alternative"/"vs"
├── Campaign: Retargeting (Display)
└── Campaign: Performance Max
```
### Competitor Brand Keywords
**When**: Bid on "[Competitor] alternative," "[Competitor] vs [You]" to intercept high-intent traffic. Google allows competitor terms as keywords; you cannot use competitor names in ad copy without permission.
**Landing page**: Use a **dedicated landing page** (comparison/alternatives page), not a blog article. Users searching competitor brands expect direct alternatives—a blog increases bounce; a comparison page matches intent and converts better. See **alternatives-page-generator** for structure.
**Best practices**:
- Separate campaign; exact/phrase match; add your brand as negative
- H1 mirrors search intent (e.g., "[Competitor] vs [You]")
- Feature comparison table; one-line differentiator; strong CTA
- Expect lower Quality Score, higher CPC than non-brand; optimize LP relevance
**Naming**: `GOOG_[Objective]_[Audience]_[Offer]_[Date]` (e.g., `GOOG_Search_Brand_Demo_Ongoing`)
## Campaign Types
| Type | Best for |
|------|----------|
| **Search** | High-intent queries; keyword-targeted; landing page critical |
| **Display** | Awareness; retargeting; broader reach |
| **YouTube** | Video; awareness; consideration |
| **Performance Max** | Automated; cross-channel; feed + search + display |
## Performance Max (PMax) Optimization
**Learning period**: Run at least **6 weeks** for algorithm ramp-up. Works best as complement to Search, not replacement.
**Asset groups**: Organize by *audience intent* (e.g., high-intent searchers, cart abandoners, category researchers), not product category alone. Audience signals improve CPA and ROAS vs. no signals.
**Asset requirements** (per asset group):
- ≥5 images (include 1200×1200)
- ≥5 text assets (4 headlines, 5 descriptions)
- Video when possible
- Refresh creative regularly to maintain performance
**Signals**: Add remarketing lists and Customer Match to accelerate learning.
**Weekly health check**: Flag if brand terms >30% of conversions; unexpected geo conversions; any placement >15% of total spend; asset group performance below "Good."
## Keyword Strategy
- **Brand**: Protect brand terms; exclude from non-brand campaigns
- **Negative keywords**: Build weekly; avoid irrelevant queries. Add **support terms** (login, forum, pricing, help) from **keyword-research**—these are existing customers, not prospects.
- **Match types**: Broad (discovery) → Phrase → Exact (control)
**Keyword sources**: Use **keyword-research** for keyword list, clusters, and intent. Map each cluster to a dedicated landing page; relevance improves Quality Score and lowers CPC.
## Quality Score Levers
| Factor | Action |
|--------|--------|
| Expected CTR | Improve ad relevance; test headlines |
| Ad relevance | Align ad copy to keyword intent |
| Landing page | Ad-to-page alignment; fast load; mobile-friendly |
**Target**: Quality Score ≥6; higher = lower CPC, better ad rank. **Benchmark**: Improving Quality Score from 5 to 7 can reduce CPC by 30–50%.
## Bidding Strategy
| Conversions/month | Strategy |
|-------------------|----------|
| <30 | Manual CPC (smart bidding needs volume to optimize) |
| 30–50 | Target CPA; minimum for effective smart bidding |
| 50–100 | Target CPA |
| 100+ | Target ROAS |
**Smart bidding**: AI-powered bidding (Target CPA, Target ROAS) typically delivers better ROI than manual when conversion volume is sufficient; requires ≥30 conversions in 30 days to work effectively.
## Tracking
- **Enhanced Conversions**: Server-side signals for better attribution
- **Offline conversion imports**: B2B; CRM → Google Ads
- **UTM**: Consistent parameters for GA4 cross-check
## Paid–Organic Cannibalization
When you rank organically (position 4+) for a keyword and also run PPC, paid ads can absorb clicks that would go to organic. **Audit**: Cross-reference GSC organic rankings with Search Terms report. If organic ranks well, test pausing PPC on those terms to free budget for higher-impact keywords.
**Reference**: [Backlinko – SEO and PPC: 8 Smart Ways to Align](https://backlinko.com/seo-and-ppc)
## Pre-Launch Checklist
- [ ] Conversion tracking tested with real conversion
- [ ] Landing page loads <3s; mobile-friendly
- [ ] UTM parameters working
- [ ] Negative keyword list built (include support terms from keyword-research)
- [ ] Budget set; targeting matches audience
## Related Skills
- **pmf-strategy**: PMF validation framework; when to use PMF testing vs conversion-driven
- **paid-ads-strategy**: Channel selection; budget allocation; ad-to-page alignment; competitor brand bidding
- **alternatives-page-generator**: Competitor brand keyword ads → dedicated LP (not blog); comparison page structure
- **keyword-research**: Keyword list, clusters, intent; support terms for negative keywords; PPC data feeds back SEO priority
- **traffic-analysis**: UTM for attribution; paid–organic cannibalization audit
- **landing-page-generator**: LP structure for paid traffic; PAA → FAQ
- **analytics-tracking**: Conversion tracking; ROAS measurement
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".