Your first Search campaign should buy clear intent, not become a keyword warehouse
Search is valuable because it can be controlled: which intent you buy, which keywords trigger ads, and which page receives the click. Start with Phrase / Exact to keep the sample readable; treat broad and AI Max as later expansion after conversion, page, and negative-scope evidence is clearer.
Lesson artifact: Search launch structure sheet
Document campaign goal, ad group intent, keywords, match type, RSA promise, landing page, launch-protection negatives, and first pause/expand rules; leave systematic negative governance for the search-term review lesson.
Structure readiness
2/5
Google Ads Basics 03
Bring the previous article's conversion acceptance sheet into setup: read the signal before buying terms
The previous article, Google Ads Setup: Account and Conversion Signal QA, verifies whether the system can recognize a real business action; this lesson turns the selected Search path into an account structure. Keep the 20oz leak-proof travel mug case: only after primary conversion, order dedupe, value, and currency have evidence should search terms, RSA promise, and final URL form a small explainable sample. This lesson does not reopen who bids, and creating an ad is not the same as proving the first week.
Bring from the previous article
The accepted primary conversion, test order, transaction ID, value, currency, three-system comparison, and pause line.
This lesson completes
One search intent per ad group, one RSA and page that answer it, and launch-protection negatives only.
Next route
Take the structure sheet to Google Ads Budget and Bidding: Sample, Profit, and Stop Lines for budget and bidding guardrails; systematic search-term and negative governance comes later.
Map the structure before opening the backend
A first Search campaign is not a form; one intent should be answered by one ad and one page
The previous article, Google Ads Setup: Account and Conversion Signal QA established basic tracking acceptance. Keep the same 20oz leak-proof travel mug. The owner wants to buy active searches such as “leak proof travel mug,” but the budget cannot test tumbler, coffee-gift, competitor, and brand terms at once. If every keyword goes into one ad group and every click lands on the homepage, even 200 clicks in week one will not tell us whether intent, RSA promise, final URL, or page proof failed. A created ad only means the object was saved; it does not mean the structure is readable.
Use one simple rule to build the structure: one main search intent, one ad group, one RSA set that answers the same question, and one final URL that can keep the promise. Phrase and Exact are not guarantees of identical queries; they are easier starting points for a cold-start read. An RSA is not complete because every field is filled. Its headlines should cover what the product is, what problem it solves, why it is credible, and what the click will find. Launch-protection negatives do not replace full search-term governance on day one.
Write the tumbler case into the launch sheet in order: define market, language, brand/non-brand boundary, and primary conversion; separate “leak-proof commuter mug,” “coffee gift,” and “DIY/repair” as different decisions, with only the first entering this ad group; make RSA headlines and descriptions promise leak protection, 20oz capacity, and commuter use; confirm the final URL shows matching specifications, price, delivery, and returns; then write launch-protection negatives, the week-one read, and pause conditions. Every row should be executable by another operator.
Keep the first-week read causal: check whether search terms still match the intent, whether the page keeps the ad promise, whether Purchase is recorded with the accepted signal from Google Ads Setup: Account and Conversion Signal QA, and whether the budget bought a readable sample. If queries are relevant but add-to-cart is weak, route to page fulfilment. If low-intent terms pollute the query report, record it through Google Search Terms: Observe, Negate, or Split. If the sample is too thin, use the budget guardrail in Google Ads Budget and Bidding: Sample, Profit, and Stop Lines. This structure makes the next decision clearer; it does not prove Search has won or authorize widening match and raising budget together.
Make one search intent fully answerable by one ad set and one page before expanding terms; if the structure is unclear, do not buy more clicks.
Plain terms first
Understand the structure layers before clicking through setup
This lesson uses Search campaign, ad group, Phrase match, Exact match, RSA, and negative keywords. Know their jobs before filling the structure sheet.
Search campaign
A Search campaign is a Google Ads campaign triggered by user search queries. It is best for validating active search demand.
- Where you see it
- You choose the Search campaign type in Google Ads, then set goals, budget, keywords, ads, and landing pages.
- What breaks
- If the first Search campaign mixes brand, non-brand, competitor, and generic terms, the readout becomes hard to interpret.
- Ecommerce example
- A leak-proof commute tumbler can first validate clear demand such as "leak proof travel mug" through non-brand Search.
Ad group
An ad group organizes keywords and ads inside a Search campaign. One ad group should carry one close search intent.
- Where you see it
- You add keywords in an ad group and write responsive search ads matched to that keyword set.
- What breaks
- Mixed intent makes one ad and page answer too many searches, so review cannot isolate the problem.
- Ecommerce example
- "waterproof dog seat cover" and "dog hammock for car" may fit one group; "free dog seat cover" should be excluded or held.
Phrase match / Exact match
Phrase match can match searches that include the meaning of the keyword; Exact match steers closer to the same meaning or intent. They protect readability in a first pass.
- Where you see it
- You use quotation marks for Phrase match and brackets for Exact match when adding keywords.
- What breaks
- If match scope is too broad, spend can flow into queries the page cannot answer.
- Ecommerce example
- Start with "waterproof travel mug" and [leak proof travel mug], then expand from search term evidence.
Responsive Search Ads / RSA
Responsive Search Ads combine multiple headlines and descriptions. The point is not filling slots; it is covering product, problem, proof, and click reason.
- Where you see it
- You enter multiple headlines and descriptions when creating a Search ad.
- What breaks
- If copy is generic, Google can assemble many versions that still fail the search intent.
- Ecommerce example
- "Leak-proof commute mug," "fits car cup holders," and "30-day returns" are closer to purchase intent than "Premium Lifestyle Accessory."
Negative keyword
Negative keywords stop ads from showing on irrelevant searches. They are a first-campaign budget guardrail, not just a later cleanup.
- Where you see it
- You add negative keywords at the campaign or ad group level.
- What breaks
- Without starter negatives, free, tutorial, job, support, wholesale, or irrelevant-location queries can spend first.
- Ecommerce example
- When selling tumblers, first evaluate excluding free, DIY, repair, jobs, used, and other poor-fit searches.
Checkable assumptions
Write the auction assumptions before reading real terms and orders
Use this theory only to record intent, budget/goal, and page evidence; it is not proof of current platform rules or business outcomes.
Truthful Auctions for Automated Bidding in Online Advertising is a mechanism-design study of automated bidding in online advertising. It models ad-impression value as public information and budget and ROI constraints as private conditions, uses incentive-compatibility and individual-rationality conditions to discuss auction outcomes, and compares mechanisms in synthetic bidding settings. It does not include a real-platform or country sample. In this lesson, it only reminds you to record search intent, campaign goal and budget assumptions, and the evidence available on the final URL as checkable premises.
This theory and synthetic comparison do not prove current Google matching, ranking, or payment rules, and they do not prove income, ROI, profit, or causal conversion effects. After launch, validate the assumptions against real Search terms and orders, including page fit; if they do not line up, hold expansion.
Main artifact
Search launch structure sheet
This turns campaign, ad group, keywords, ads, page, and negatives into one launch check. Every layer must explain search intent.
Campaign goal
Answer one main question, such as non-brand purchase demand.
Goal, market, language, budget, and brand boundary are clear.
Brand, competitor, generic, and problem terms are blended.
Ad group intent
Each group carries one close search intent.
One ad and one page can answer the group.
Using one ad group as a keyword warehouse.
Keywords and match type
Start with high-intent, narrow, explainable keywords.
Start with Phrase / Exact and document held terms.
Expanding too broad on day one.
RSA promise
Headlines and descriptions match the query intent.
Covers product, problem, proof, and click reason.
One generic ad for every keyword.
Landing page and negatives
First screen supports the promise; negatives block low intent.
Page, negatives, pause/expand rules are documented.
Specific ads send traffic to a generic homepage.
Intent cluster
One ad group should not carry every idea
To decide whether terms belong together, ask one question: can the same RSA and landing page answer them?
Category purchase terms
"waterproof dog seat cover"
"leak proof travel mug"
Relevant product page or tight collection page
Can directly validate purchase intent.
Problem / use-case terms
"keep car clean from dog hair"
"coffee mug for commute"
Product page that explains the use case and solution
If the page can answer it, this can be a second intent group.
Brand terms
"your brand travel mug"
"your brand dog seat cover"
Brand page or most relevant product page
Read separately so it does not hide non-brand performance.
Competitor terms
"competitor alternative"
"brand x vs brand y"
Needs a compliant, truthful comparison page
Usually hold in round one to avoid mixing intent and compliance risk.
Low-intent / poor-fit terms
free
DIY
repair
jobs
used
Should not enter first purchase validation
Use starter negatives or hold, so budget does not spend here first.
Intent-to-page alignment router
Prove this keyword group can be answered by one page
Google Ads asks for keywords, ads, and a final URL, but the account stays readable only when search intent, RSA promise, landing page, and negatives stay on one line. Pick a scenario and see how it should launch.
Product-type buyer
Ad group rule
Can become a first-round core ad group because the searcher already named the product type.
Match type start
Start with Phrase / Exact to protect the search-term sample before broad expansion.
RSA promise
RSA should state product type, key proof, and shipping or return reason.
Landing page requirement
Use the closest product page or tight collection page; first screen needs product, specs, proof, and buy path.
First readout
Read whether search terms still show buying intent, CTR is reasonable, and add_to_cart / purchase reconcile with Shopify.
Do not do this
Do not mix this group with broad content terms, competitor terms, or support searches.
Starter negatives
20oz Search structure practice
Choose the query mess, then choose the launch action
This clickable drill is for beginners: the same 20oz tumbler search data can show mixed intent, missing page proof, brand pollution, or low-intent leakage. The wrong action is worse than not launching.
Step 1: choose the query mess
Step 2: choose the launch action
Instant feedback
Good action20oz tumbler product buyers
Your selected action
Split into one-intent ad groups
When terms still show product-buying intent but use different angles, split by intent so one RSA and one page can answer each group.
Good action
Good: use it as a core buyer-intent group and keep RSA plus product-page proof around leak-proof, 20oz, commute use, and shipping.
Write back to the structure sheet
Ad group: 20oz leak-proof commute tumbler; keywords: Phrase / Exact; page: 20oz product page; negative candidates: free, DIY, repair, jobs, used.
Do not do this
Do not casually add terms like "coffee accessories," "gift cup," or "bulk tumbler" into this group.
Search build sandbox
Write keywords, ad group, RSA, network, and page into one readback-ready classroom build record
This is not the Google Ads backend and it does not create campaigns, ads, negatives, or account settings. It gathers the fields that must be clear before a real build into one local classroom record that you can save, restore, and export.
Read the admin state first, then write the conclusion into this worksheet
Save and export handle only the classroom record in this browser, and the export is marked classroomOnly: true. It cannot prove an ad is approved, served, converted, or profitable.
Step 1: choose this search demand
Current build brief
Non-brand 20oz product buyer
How to use Keyword Planner
Use product and use-case seed terms in Keyword Planner, then group candidates by whether one page can answer them. Planner output is a candidate and forecast, not an automatic add list.
Ad group
Ad group: 20oz leak-proof commute tumbler. The ad and page answer only capacity, leak proofing, cup-holder fit, and returns.
Final URL
The matching product page needs capacity, seal proof, price, shipping, returns, and a CTA above the fold. Do not send this high-intent click to a homepage.
Brand and negative boundary
Read brand terms in a separate campaign or ad group, not in this non-brand buyer group.
Launch-protection negative candidates
Negative candidates: free, DIY, repair, jobs, used. Write the scope before deciding whether to exclude.
Step 2: match-type scenario
Modern semantic matching makes Phrase and Exact different from old literal-match rules. Choose the correct classroom starting action for this demand.
Current match-type readback
Phrase match
This classroom action fits the demand
Phrase or Exact keeps this round focused on one buying intent. They still match by meaning, not by a literal character lock.
Do not explain modern matching with old rules
“Phrase locks word order” and “Exact only matches identical characters” are not current acceptance conclusions. Read the actual search terms report before keeping, negating, or splitting.
Step 3: location, language, and Networks
A target country or city is not the same as the location option. If the campaign must reach people physically in the target area, explicitly read back the Presence option. Language targeting is based on languages users understand, not only query language.
Fields to write into the Campaign settings record
Target regions, Location options, service and ad languages, Networks, whether Search Partners are included, start date, and budget boundary.
Build boundary for brand and negatives
Non-brand 20oz product buyer
Brand readout
Read brand terms in a separate campaign or ad group, not in this non-brand buyer group.
Negative candidates and scope
Negative candidates: free, DIY, repair, jobs, used. Write the scope before deciding whether to exclude.
Wrong-choice explanation
Mixing brand and non-brand buyer terms in one ad group, or making a term account-level negative first, makes budget, queries, and future tests harder to interpret.
Step 4: RSA asset previewer
Make three headlines and two descriptions keep one page promise first
Official RSA field boundary checked 2026-07-26
One RSA needs at least 3 headlines and 2 descriptions, with up to 15 headlines and 4 descriptions. Headlines support up to 30 characters and descriptions up to 90. Double-width characters such as Chinese, Japanese, and Korean count as 2. This classroom counter follows that double-width rule, but the Google Ads input and policy status remain final.
Classroom preview
This is not a live Google Ads preview. It only checks whether one promise still points to the same page and does not show every possible combination.
Ad · example result
20oz Leak Proof Travel Mug | Fits Car Cup Holders | 30-Day Returns
example-store.com / commute-mug
Sealed lid for commuting. See size, price, shipping, and returns on the product page. Check leak-proof details and commuter use before you buy.
Within character limits does not mean the ad can release
You still need to check assets, Final URL, policy status, Ad Preview, and actual serving in the admin surface before proceeding.
Step 5: pinning decision
Google Ads normally combines RSA headlines and descriptions in different orders. Discuss pinning only when legal or critical brand text must appear every time.
Current AI Max version boundary
AI Max is an optimization layer in an existing Search campaign, not a new campaign type
At this review, AI Max includes search term matching and asset optimization. When enabled, read back Final URL expansion, text customization, brand controls, and URL controls in the current account surface.
Wrong premise: enable Final URL expansion and assume RSA pinning will always be respected. Current Google guidance says Final URL expansion or URL inclusions can mean pinned assets are not respected.
If you plan to use Broad or AI Max, treat this classroom worksheet as evidence to read back before an experiment, not as a switch-on instruction.
Classroom build gate
Judge by explainable fields and evidence, not a fixed click count or number of days
Older click or day counts are classroom observation prompts, not Google Ads launch thresholds. First make keywords, page, network, RSA, policy, brand, and AI Max boundaries readable.
Keep the hold and complete the worksheet gaps
Complete the readbacks, evidence fields, and RSA limit check before deciding whether to return to Google Ads for the live build.
Classroom gate: 0/6 readbacks, 0/4 records
Save, restore, and export affect only the classroom record in this browser.
Official setup boundaries
Official setup proves how the system works, not that your structure judgment is right
This prevents a common misread: completing the official Search campaign workflow does not mean the campaign deserves launch. Validate intent, match scope, RSA promise, negative scope, and landing-page proof.
Create a Search campaign
- Official docs can prove
- The official workflow walks through campaign goal, bidding, targeting, ad group, keywords, and ads.
- Structure-sheet use
- The structure sheet should state what this campaign validates: non-brand buyer terms, brand defense, problem-solving terms, or comparison terms.
- Cannot prove
- It does not prove brand, non-brand, competitor, and broad discovery terms belong together.
Keyword match types and broad match setting
- Official docs can prove
- Broad match is the default and broadest match type; Phrase / Exact can still match related meaning, not only literal text.
- Structure-sheet use
- The first-round sheet should explain why Phrase / Exact protects the sample and when broad or the broad match campaign setting is allowed.
- Cannot prove
- It does not prove broad is always wrong or Phrase / Exact is always safe; both need search-term and page-fit review.
Responsive Search Ads and asset reports
- Official docs can prove
- RSA combines multiple headlines and descriptions and learns useful combinations; the ad-level asset report helps compare assets.
- Structure-sheet use
- The sheet should write RSA as product, problem, proof, and click reason, not just filled headline slots.
- Cannot prove
- It does not prove every combination answers intent or that the landing page supports the promise.
Negative keywords and account-level scope
- Official docs can prove
- Search campaigns can use broad, phrase, and exact negative keywords, but negative match types behave differently from positive match; account-level negatives affect Search / Shopping inventory.
- Structure-sheet use
- Before launch, write negative candidates and scope: campaign, ad group, or account-level, so brand or high-value terms are not blocked by accident.
- Cannot prove
- It does not prove more negatives are always better; overblocking can remove useful demand.
Landing page experience
- Official docs can prove
- Google looks at landing page relevance to ads and keywords, usefulness, ease of navigation, and whether users see what they expected after clicking.
- Structure-sheet use
- Each ad group should record final URL and first-screen proof: product, specs, promise, CTA, shipping, or returns proof.
- Cannot prove
- It does not prove the page will convert or replace Shopify, GA4, and Ads conversion reconciliation.
Ad-level asset report timing
- Official docs can prove
- The RSA ad-level asset report compares assets within an RSA; Google notes full performance statistics are available only for dates on or after June 5, 2025.
- Structure-sheet use
- Do not rebuild structure from one headline label in week one; first confirm search terms, page fit, and conversion sample quality.
- Cannot prove
- It cannot prove one headline caused sales by itself, and it does not replace search-term and landing-page review.
Broad / AI Max boundary
Hold automation during cold start; do not permanently ban broad
The first Search campaign should make the sample readable. Broad, the broad match campaign setting, or AI Max are not forbidden; they need conversion, query, page, and negative-scope evidence first.
Hold
Conversion tracking is not accepted, Search terms sample is thin, page fit is unclear, or negative scope is not documented.
Keep Phrase / Exact to protect the sample; do not treat broad or AI Max as a cold-start repair button.
Check later
You have 50-100 clicks, high-intent Search terms look stable, but conversions are still low or post-click breakpoints are visible.
Diagnose page, price, shipping, trust, and checkout first; if needed, test one controlled expansion variable.
Route to advanced
Conversion signal is stable, Smart Bidding is readable, and Search terms plus negative lists are auditable.
Route broad / AI Max to budget, bidding, or advanced optimization lessons instead of scaling it in this first setup lesson.
Negative keyword scope map
Choose the level before blocking demand
More negatives are not automatically safer. Before launch, place starter negative candidates at the right level: one ad group, the campaign, a reusable list, or the full account.
Ad group
Terms that only pollute one intent group, such as repair, DIY, or support inside one group.
Do not block terms that may still be valuable in another ad group.
Campaign
Brand separation, market or business boundary, and low-intent searches clearly excluded from this first campaign.
Do not block broad roots before Search terms evidence proves the problem.
Negative keyword list
Reusable competitor, support, used, jobs, wrong-product, or similar stable exclusions.
Do not put temporary edge-case tests into a long-lived shared list.
Account-level
Risk terms the whole account should not buy, such as illegal, free, jobs, repair, or clearly unsupported categories.
Do not harm Shopping, PMax, brand, or future high-value demand by mistake.
Where to verify it
Before launch, do not say "it is set up"; point to the admin path and fields
The first Search campaign is not accepted by saving images. Next week, a reviewer should follow the admin path and find the same fields: goal, budget, keywords, copy, landing page, status, changes, and week-one readout.
Campaign settings / goal, bidding, and budget record
Google Ads > Campaigns > Campaign settings > goal, bidding, budget, networks, locations, languages, and start date.
- What this proves
- Proves the Search campaign validates one job and that budget, market, and language did not pollute the sample.
- Do not do
- Do not keep changing goal, bidding, or location after launch; if you must, record it for change-history review.
- Next route
- If budget or bidding becomes unreadable, return to Budget and bidding basics.
Ad group / keyword intent record
Google Ads > Ad groups > Keywords; keep keyword source, match type, final URL, and held terms together.
- What this proves
- Proves the ad group is not a keyword warehouse and that one page can answer the shared intent.
- Do not do
- Do not add every Keyword Planner idea; terms the page cannot answer should be held or listed as negative candidates.
- Next route
- If queries drift, move next to Search terms, negatives, and match types.
RSA / assets / final URL promise record
Google Ads > Ads > Responsive search ad; record headline, description, path, asset status, policy status, and final URL.
- What this proves
- Proves query, ad promise, and first-screen page proof are the same story.
- Do not do
- Do not claim offers, comparisons, inventory, or returns the page cannot prove; do not fill generic headlines just for Ad strength.
- Next route
- If clicks are good but post-click behavior is weak, return to CRO page role or landing-page fit.
Ad Preview / change history release record
Tools > Ad Preview and Diagnosis; Campaigns > Change history; record preview query, location, device, eligible / disapproved / limited status, and launch changes.
- What this proves
- Proves the ad is not just a row in a table; it has diagnosable serving conditions and a launch change record.
- Do not do
- Do not validate ads by Googling them yourself; personalization and auctions can mislead, and it can create unnecessary impressions.
- Next route
- If status is disapproved, limited, or not showing, fix serving status before optimization.
Week-one readout / keep, pause, expand record
Google Ads > Search terms, Keywords, Ads, and Landing pages; reconcile with GA4 events, Shopify Orders, and change history.
- What this proves
- Proves week one is not edited from one ROAS number; decisions come from query sample, post-click behavior, and order evidence.
- Do not do
- Do not rebuild the structure on day two; wait for the minimum sample and record why to keep, pause, expand, or fix the page.
- Next route
- Next lesson: search terms, negatives, and match-type review.
Search campaign brief
Turn keyword cluster, ad group, RSA, and Final URL into one launch brief
Choose the search situation closest to your launch, then copy the fields into the structure sheet. This is not extra paperwork; it prevents the first Search campaign from launching without a clear reason for the keywords, page, and week-one signal.
Launch brief fields
Non-brand product buyer
Keyword cluster
"leak proof travel mug", [20oz insulated tumbler], "commuter coffee tumbler"
Ad group
Ad group: 20oz leak-proof commute tumbler; only carry product-purchase intent.
RSA promise
RSA promise: 20oz, leak-proof, commute cup-holder fit, 30-day returns; avoid generic premium lifestyle copy.
Final URL
Final URL: 20oz leak-proof commute tumbler product page with specs, leak-proof proof, price, shipping, and CTA above the fold.
Negative seed
Negative seed: free, DIY, repair, jobs, used; keep brand terms in a separate record, not in the non-brand group.
Week-one observation window
Week-one window: wait for a readable search-term sample, CTR, CPC, add_to_cart, purchase, or order evidence before keep, pause, or expand decisions.
Write back to copyable lesson notes
Write back: launch only 20oz product-buyer terms; page and RSA answer the same demand; week-one edits come from queries, post-click behavior, and order evidence.
Week-one observation window
Read the sample before rebuilding
Week one should protect interpretability. The launch record should say what to read, what not to change together, and when 50-100 clicks become enough for structural judgment.
Day 0
Confirm conversion tracking is accepted, the campaign is eligible, Campaign settings are clean, and Ad Preview plus Change history preserve the launch record.
Do not change the core structure because the interface prompts you; record the launch state first.
Conversion status, Ad Preview query, change timestamp, and launch judgment.
Day 1-2
Check whether impressions and clicks start. If there is no spend, review bid strategy, budget, location, keyword coverage, and ad status first.
Do not rewrite every RSA or break apart all ad groups because day one or two has no conversions.
Whether spend started, whether settings block delivery, and whether the query sample is still too small.
Day 3-7
Read Search terms daily, add obvious low-intent negatives, and check post-click behavior plus order samples.
Do not change match type, budget, RSA, and landing page together; change one explainable variable at a time.
Search terms, negative action, CTR, add_to_cart, purchase, and Shopify order id sample.
50-100 clicks
Use CTR, search terms, CVR, post-click behavior, and order samples to diagnose structure, page fit, or conversion trust.
Do not kill the campaign from one or two days of ROAS; confirm sample size and the problem location first.
The keep, pause, expand, or page-repair decision sentence.
Worked example
Carry one keyword cluster into ad group, RSA, Final URL, and negatives
Click the three steps below and follow one 20oz leak-proof commute tumbler from keyword cluster to launch rules. The point is not memorizing terms; it is checking that every field answers the same search demand.
Current step
1. Keyword cluster and match type
Plain meaning
A keyword cluster is not every related term you can find. It is a small group of searches that one page can answer. Match type controls how far Google can expand from those terms. Phrase / Exact keeps round-one data easier to read. Broad is not forbidden; it is just harder for a beginner to diagnose in the first pass.
What to write
Keyword cluster: "leak proof travel mug", [20oz insulated tumbler], "commuter coffee tumbler". Match type: Phrase / Exact only in round one. Hold: best coffee accessories, gift mug, coffee blog ideas.
Why this works
These terms ask for the same thing: a commute-friendly, leak-proof tumbler with clear capacity. One 20oz leak-proof product page can answer them. Generic and gift terms carry different intent, so adding them early makes the first search-term report hard to read.
Avoid this
Do not add every Keyword Planner idea. The first Search campaign is not trying to cover the whole market; it is trying to produce one readable search sample.
Keyword entry rule
The first keyword set should be small and readable
More keywords do not automatically help. In round one, beginners need readability: high intent, a real page, controlled match scope, and business value.
Does the query show purchase, comparison, or solution intent?
Enter first keyword candidates.
Hold or negate informational, free, tutorial, job, and support terms.
Is there a page that directly answers it?
Map it to an ad group and landing page.
If no page exists, do not buy clicks yet.
Is match scope explainable?
Start with Phrase / Exact and watch search terms.
Hold broad until conversion, negatives, and page evidence are stronger.
Does the term have enough business value?
Connects to product, margin, inventory, and page evidence.
If it only brings cheap visits without revenue logic, hold it.
RSA and page promise
The more specific the ad promise, the more the page must support it
Responsive search ads should cover product, problem, proof, and click reason. The first screen must support the same promise.
Waterproof dog car cover
Waterproof, dirt-resistant, easy to clean
Material, size, reviews, installation image
Product page first screen shows waterproofing and car fit
Commute travel mug
Leak-proof, car-cup-holder fit, fast shipping
Size, seal design, shipping speed, returns policy
Product first screen shows size, seal, and shipping promise
Problem-solving query
Answer the problem before naming the product
Comparison image, use case, real reviews
Use-case section or collection page should not make users hunt for the answer
Fill the sheet
Write the first Search campaign as a reviewable account action
These four lines feed the pre-launch copyable lesson notes. Do not add unexplained terms or buy clicks for pages that cannot answer them.
Copyable lesson notes
Turn the current Search structure into a next-week review record
Copy this into the ad log or task. Next review should not guess why this grouping, keyword set, or landing page was chosen.
Before copying
If readiness is below 5/5, the note can still be copied, but it should be treated as missing evidence, not launch approval.
Search launch structure copyable lesson notes Structure readiness: 2/5 Current intent scenario: Product-type buyer 20oz structure practice: 20oz tumbler product buyers Current launch action: Split into one-intent ad groups Action judgment: Good: use it as a core buyer-intent group and keep RSA plus product-page proof around leak-proof, 20oz, commute use, and shipping. Structure-sheet line: Ad group: 20oz leak-proof commute tumbler; keywords: Phrase / Exact; page: 20oz product page; negative candidates: free, DIY, repair, jobs, used. Stop action: Do not casually add terms like "coffee accessories," "gift cup," or "bulk tumbler" into this group. Search campaign brief: Non-brand product buyer Keyword cluster: "leak proof travel mug", [20oz insulated tumbler], "commuter coffee tumbler" Ad group: Ad group: 20oz leak-proof commute tumbler; only carry product-purchase intent. RSA promise: RSA promise: 20oz, leak-proof, commute cup-holder fit, 30-day returns; avoid generic premium lifestyle copy. Final URL: Final URL: 20oz leak-proof commute tumbler product page with specs, leak-proof proof, price, shipping, and CTA above the fold. Negative seed: Negative seed: free, DIY, repair, jobs, used; keep brand terms in a separate record, not in the non-brand group. Week-one observation window: Week-one window: wait for a readable search-term sample, CTR, CPC, add_to_cart, purchase, or order evidence before keep, pause, or expand decisions. Brief write-back: Write back: launch only 20oz product-buyer terms; page and RSA answer the same demand; week-one edits come from queries, post-click behavior, and order evidence. Search build sandbox: Non-brand 20oz product buyer Sandbox match action: Phrase match Networks readback action: Read back current Networks setting first RSA pinning: No pinning, keep combinations readable Sandbox gate: classroom readback or evidence is still missing, keep the hold Admin evidence: keep field records for Campaign settings, Ad group / Keywords, RSA / Assets / Final URL, Ad Preview / change history, and week-one readout. Do not use images as primary proof. Campaign goal: To fill Ad group intent / keywords / match type: To fill RSA / landing page: To fill Negative starter / pause / expand rules: To fill
Build examples
Bind one keyword set, one ad promise, and one page proof
The first Search build is not stuffing every related keyword. Each ad group must explain why these terms are bought, what the ad promises, and what proof the page gives.
Single-product cold start
Leak-proof commute mug
Ad promise: Ads promise leak-proof commute use and heat retention, not gifts, wholesale, or coffee education.
Page proof: The first screen needs leak-proof structure, capacity, retention time, return promise, and real product images.
Hold back: Hold generic terms like "best coffee accessories" because the page cannot answer all intent behind them.
Multi-variant product
Dog car seat cover
Ad promise: Ads focus on waterproof back-seat pet travel, not pet beds or cat carriers in the same group.
Page proof: The page must support car fit, size, installation, waterproof material, and cleaning.
Hold back: Use "free dog seat cover" and "DIY dog hammock" as negative candidates so week-one sample stays clean.
Stop / Go
Stop and go rules before Search launch
Common mistakes, acceptance criteria, and long-tail review requirements become launch boundaries. If they do not pass, do not scale budget yet.
All keywords are stuffed into one ad group
Each ad group serves one search intent
Intent grouping and landing page are documented
Brand, non-brand, competitor, and generic terms are blended
Brand terms are read separately; competitor/generic terms have boundaries
Campaign goal and brand boundary
Specific ad, generic page
RSA promise matches the landing page first screen
Headline, proof, CTA, and landing page URL
No starter negatives or pause rules
Low-intent terms are blocked and keep/pause/expand rules are clear
Starter negatives and first-review rules
Closeout
The first Search round does not need to cover every term. In series order, move next to budget-bidding to set daily budget, bid strategy, week-one sample, and the stop/go line; if Search terms already exist, use search-terms-negatives-and-match-types for query, negative, and match-type review.