Builder branded search
Skill chanktb/claude-google-ads/skills/builder-branded-search
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 (branded_search). Reads account-context.yaml. Use when the user says "branded search", "brand campaign", "defend my brand", "competitor conquesting", "bid on my own name".From its SKILL.md
npx -y skills add chanktb/claude-google-ads --skill builder-branded-searchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 1 command, including `python ${CLAUDE_PLUGIN_ROOT}/skills/builder-pmax/scripts/spec_to_xlsx.py <campaign-spec.json> --output blueprint.xlsx`.
SKILL.md
7.6 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it
Google Ads — Builder: Branded Search
A focused Search campaign to (1) defend your own brand at near-certain ROAS and (2) optionally conquest
competitors. Pushes cleanly via Editor CSV. Builds on builder-search patterns with brand-specific rules.
Operating rules
- Read
brand_termsandcompetitor_termsfromaccount-context.yaml(set bysetup). Read guardrails. - Write to the working directory:
blueprint.xlsx+campaign-spec.json(campaign_type: "branded_search",ad_groups[]). - Coordinate brand exclusion: ensure PMax/Shopping have brand exclusion applied so they don't claim
brand conversions (clean attribution). Honor the
pmax-brand-exclusionguardrail.
Model dispatch (run cheap, decide expensive) — see ${CLAUDE_PLUGIN_ROOT}/references/model-tier-dispatch.md
- Scout (
haiku) — per-URL 200 checks; char-count validation; brand-misspelling expansion. - Routine (
sonnet) — pulling competitor domains from auction insights as conquesting candidates. Dispatch asgeneral-purpose; return raw candidates, don't decide. - Judge (main session) — STEP 1-2 ad-copy (brand-led, trademark-aware — never a competitor TM in ad text), STEP 3 separation, bidding, the brand-exclusion coordination call. Trademark safety is judgment; never delegate it.
STEP 1 — Brand-defense ad group(s)
- Keywords from
brand_terms(own brand + variants + common misspellings), Exact + Phrase. No broad. - Copy uses your own brand prominently, your USPs, and your real offers. Target high impression share at low CPC (brand intent converts cheaply).
- RSA: up to 15 headlines (≤30) / 4 descriptions (≤90), keyword-led, with CTA.
STEP 2 — Competitor conquesting — optional, trademark-aware, a SEPARATE campaign
- Only if
competitor_termsexist and the user wants it. Emit it as its OWN campaign-spec, not an ad group inside the brand-defense campaign — because bid strategy is campaign-level and conquesting needs Maximize Conversions, not the defense campaign's Target Impression Share. (You do NOT want to bid to dominate a competitor's SERP at absolute-top 90% — expensive, low-intent.) - Keywords from
competitor_terms(Phrase/Exact). - Trademark rules: do NOT put a competitor's trademark in the ad TEXT (headlines/descriptions/paths) —
only as keywords. Emit the competitor terms as a spec-level
trademark_avoid[]so the validator BLOCKS any in ad text. Lead with YOUR differentiators ("wholesale pricing", "free shipping", a price extension with your real prices on the competitor SERP), not the competitor's name. Expect lower CTR/QS, higher CPC. - Add YOUR
brand_termsas negatives so conquesting never overlaps the brand-defense campaign.
STEP 3 — Negatives & separation (Search levels: campaign OR ad-group)
- Negatives can sit at campaign level OR ad-group level in Search (unlike PMax = campaign-only). Use
campaign-level for account-wide junk (job-seeker, DIY, location) and ad-group-level only where it does
real work — here, negate
brand_termsin the conquesting ad group so defense and conquesting never cross-serve. Don't duplicate the same negative at both levels; pick the narrowest level that achieves it. - Keep brand-defense and conquesting ad groups cleanly separated.
- Extensions, likewise, can be campaign OR ad-group level in Search (PMax forces campaign-level). Default to campaign-level; only push sitelinks/callouts down to ad-group level if the groups are different enough to need distinct ones (e.g. brand-specific vs conquesting sitelinks) — and only if it's worth the upkeep.
STEP 4 — Bidding (Search ≠ PMax — pick a brand-appropriate strategy, NOT a "learning ramp")
- Check what the account already does for brand first. If a brand campaign exists, read its
bidding_strategy_type(a healthy brand campaign commonly runsTARGET_IMPRESSION_SHARE) and match it — don't reinvent. - Brand defense → Target Impression Share (absolute top of page, ~90%, with a max-CPC bid limit). The goal is to dominate your own brand SERP cheaply, not to maximize value. Brand has history, so do NOT frame it as "maximize conversion value, no target, learning" — that's a cold-prospecting default, wrong for brand. (Maximize Conversions is an acceptable alternative if you'd rather optimize to conversion volume.)
- Conquesting → Maximize Conversions (watch CPA, don't over-invest). It's colder and pricier than brand.
- Bid strategy is CAMPAIGN-level. Brand defense and conquesting want different strategies, so once conquesting has real budget, split it into its own campaign rather than forcing both under one strategy.
STEP 4b — Conversion goal (use the account's REAL action — never invent one)
Pull the enabled conversion actions (conversion_action.name, primary_for_goal) and use the account's
actual primary purchase action by name — e.g. a store's only purchase action may be the store-channel
purchase (Shopify's "Google & YouTube" channel tracks website purchases, Search-driven ones included), so the
Search campaign optimizes on THAT, not a made-up name. Set conversion_goals.scope: "campaign". If no web-purchase primary exists for Search, flag it for the operator to create.
STEP 5 — Output + verification
Emit campaign-spec.json (branded_search, ad_groups[] as in builder-search) + blueprint.xlsx.
Set campaign.status: "paused", conversion_goals.scope: "campaign". Build the extensions block the same
way as builder-pmax STEP 7b — sitelinks, callouts, structured snippets (the store carries many brands, so a
Brands snippet IS correct here, unlike a single-brand PMax), and a concrete prices asset built from real
store data (don't leave it a placeholder — pull "From" prices per category and a live URL each; a price
extension is especially strong on a brand/conquesting SERP). On a conquesting campaign, emit a
trademark_avoid list (the competitor terms) at the spec level — the validator BLOCKS any ad text
containing one, enforcing the no-competitor-TM-in-copy rule.
Render the human workbook from the spec (the shared renderer handles ad_groups → an AG sheet per ad group
with keywords, RSA, negatives, paths):
python ${CLAUDE_PLUGIN_ROOT}/skills/builder-pmax/scripts/spec_to_xlsx.py <campaign-spec.json> --output blueprint.xlsx
Verify with validate_spec.py: RSA limits/counts (Google-accurate counting,
${CLAUDE_PLUGIN_ROOT}/references/google-ads-formatting.md), keyword/negative match types (no broad),
no trademark_avoid term in any ad text (enforced), brand_terms negated in conquesting groups, Final
URLs live (200). Hand the JSON to pusher → Editor CSV (spec_to_editor_csv.py) + ready-to-copy blocks
(spec_to_paste.py).
Coordination note for the operator
Branded Search + PMax brand exclusion are two halves of one decision: PMax excludes brand traffic, this campaign captures it deliberately. Surface this so reporting and credit stay clean.
To build / refine later
- Auto-generate brand misspellings; pull competitor domains from auction insights.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in ~1.7k tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- output both blueprint.xlsx and campaign-spec.json
- read brand and competitor terms from context
- ensure pmax and shopping have brand exclusion
- use target impression share for brand defense
- use maximize conversions for conquesting
- put competitor conquesting in a separate campaign
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.