agentleFS
narayan-metaflownarayan-metaflow/metaflow-marketing-skills/skills/paid-search-ads-playbook/SKILL.md

paid-search-ads-playbook

Skill14 starsChanged 7 months agoMITView on GitHub

Google and Microsoft paid search planning: structure, keywords, match types, negatives, RSAs, bidding lens, and landing-page alignment for conversion-focused spend.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for Google Ads (Microsoft Ads analogs) planning: structure, keywords, match types, negatives, RSAs, bidding lens, and …

    line 8
  2. Distinctive:

    Budget: Avoid dilution—fewer strong campaigns beat many starved ones early.

    line 25
  3. Distinctive:

    Networks: Search vs Performance Max / Display—do not mix goals blindly.

    line 26
  4. Distinctive:

    Policy: Avoid superlatives without proof.

    line 51
  5. Distinctive:

    Manual / eCPC: When automation lacks data.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to Activate

Use this skill for Google Ads (Microsoft Ads analogs) planning: structure, keywords, match types, negatives, RSAs, bidding lens, and landing-page alignment. This is paid search, not organic SEO—intent is conversion and efficient spend, not rankings.

First Questions

  1. Business & offer — What sells, margin, and primary conversion (lead, purchase, trial)?
  2. Geo & language — Countries, cities, languages?
  3. Budget & goal — Daily/monthly cap, target CPA/ROAS (or learning phase expectations)?
  4. Funnel stage — Brand, non-brand, competitor, remarketing?
  5. Existing assets — Live account structure (if any), feed/SAIQ, conversion tags health?
  6. Landing pages — URLs per offer; mobile speed and message match?

Account & Campaign Structure

  • Separation of intent: Brand, generic non-brand, competitor, and remarketing belong in distinct campaigns (or clear ad groups with budget control at campaign level).
  • Naming: Consistent convention (geo | network | intent | offer).
  • Budget: Avoid dilution—fewer strong campaigns beat many starved ones early.
  • Networks: Search vs Performance Max / Display—do not mix goals blindly; call out when PMax or Display changes assumptions.

Keywords & Match Types

  • Match types (modern Google): Exact and Phrase are precision tools; Broad requires strong negatives and monitoring.
  • Themes: One tight theme per ad group (5–15 closely related keywords, not kitchen-sink lists).
  • Cannibalization: Same keyword in multiple ad groups/campaigns causes auction confusion—consolidate or use negatives to sculpt.
  • Expansion: Mine search terms reports (conceptually); add winners as keywords, losers as negatives.

Negative Keywords

  • Build shared negative lists (geo exclusions, job seekers, free-only intent, irrelevant industries).
  • Ad-group-level negatives to sculpt traffic between sibling groups.
  • Review weekly in early phases; stale negatives hide volume.

Responsive Search Ads (RSAs)

  • 15 headlines / 4 descriptions where possible; pin only when legally or brand-required (pinning reduces combinations).
  • Coverage: At least 3 distinct value props, 2 CTAs, 1 keyword-rich headline, 1 trust/credibility.
  • Policy: Avoid superlatives without proof; medical/financial sensitivity.

Bidding & Goals (Framing, Not Live Optimization)

  • Learning: Major changes reset learning; batch edits.
  • tCPA / tROAS: Need conversion volume; suggest thresholds honestly.
  • Manual / eCPC: When automation lacks data.
  • Portfolio: Align bid strategy with actual conversion lag and value rules.

Conversion Tracking & Quality

  • Primary vs secondary conversions—avoid optimizing on weak proxies.
  • Enhanced conversions / consent—note when relevant.
  • Landing page: Message match headline ↔ ad; one clear CTA; speed and mobile UX.

Tools and data sources (keyword/API + page read)

  • Volume & CPC signals: seo_search_volume, seo_keyword_ideas, seo_related_keywords, seo_keyword_suggestions for seeds and expansion.
  • Paid estimates: seo_ad_traffic_by_keywords for impression/click/cost scenarios when comparing bid levels.
  • SERP context: seo_serp_analysis when auction insight helps (ads + organic layout).
  • Landing pages: web_scrape to audit copy, CTAs, and offer clarity—never guess page content without a URL.

Be explicit: tool outputs are estimates; validate in the ad platform.


Quality Gate (before final deliverable)

  • Campaign/ad group map matches intent separation (brand vs non-brand vs competitor vs RLSA)
  • Each ad group has a tight theme; no duplicate keyword conflicts across groups
  • Match type choices justified; broad groups paired with negative strategy
  • Negative keyword lists proposed (shared + ad-group sculpting)
  • RSAs: enough unpinned assets; pins only where required
  • Bidding lens matches data volume and business goal
  • Conversion tracking assumptions stated; gaps flagged
  • Landing page message match called out per major ad group
  • Next 7-day action list for the user (what to build first in-platform)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.