Verified against ChatGPT · 2026-08-09
Write Google Search RSA headlines with a pinning strategy instead of 15 interchangeable variations
Produces the full set of Responsive Search Ad headlines and descriptions for a Google Ads campaign, grouped by which ones should be pinned to which position versus left for Google's algorithm to rotate, based on what each headline is actually for.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are building a Google Search Responsive Search Ad (RSA) for the campaign below, and the goal is not just 15 headlines that all say roughly the same thing — it's a deliberate mix where some headlines are safe to let Google's algorithm rotate freely and a few are risky or precise enough that they need to be pinned to a specific position. CAMPAIGN / AD GROUP THEME Same-day emergency locksmith service, downtown metro area only. SEARCH INTENT BEING TARGETED Locked out right now, needs someone within the hour, price-sensitive but urgency beats price. KEYWORDS THIS AD GROUP TARGETS emergency locksmith near me, 24 hour locksmith downtown, locked out of house help LEGAL OR FACTUAL CONSTRAINTS Cannot say "licensed" in states where we only hold a business permit, not a locksmith license. LANDING PAGE PROMISE 30-minute average response time, flat $75 call-out fee shown before booking. Write 12 headlines (max 30 characters each) and 4 descriptions (max 90 characters each). Group the headlines into three tiers: (1) keyword-echo headlines that closely mirror the target keywords for Quality Score relevance — these can rotate freely; (2) differentiator or offer headlines that make a specific factual claim — flag these as candidates for pinning to Position 1 since they carry the actual selling argument and shouldn't get buried under a generic keyword-echo headline by the algorithm; (3) trust or objection-handling headlines (pricing transparency, guarantee, social proof) — flag these as candidates for Position 2 or 3. Every headline must be something the landing page actually delivers on — do not write a headline promising something not present in the stated landing page promise, since a mismatch between ad and landing page is a direct Quality Score and compliance risk on Google Ads, not just a bad user experience. Do not fabricate a specific number, statistic, or claim not given to you in the campaign details; if a headline would be stronger with a number you don't have, mark it "[NEEDS INPUT]" instead of inventing one. Respect the legal/factual constraints exactly. OUTPUT FORMAT: a table with columns Headline, Character Count, Tier, Pin Recommendation — followed by the 4 descriptions, then a 2-3 sentence rationale for the overall pinning strategy given this specific search intent.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Google's RSA engine auto-rotates and combines headlines by predicted performance unless a headline is explicitly pinned to a position, which means a set of 15 headlines that are all roughly interchangeable in meaning gives the algorithm nothing to actually differentiate between combinations — the pinning-tier structure in this prompt gives the model a reason to write headlines with genuinely different jobs (keyword relevance for Quality Score, a differentiator claim, an objection-handler) rather than 15 rephrasings of the same value proposition, which is the default output when a prompt just asks for "RSA headlines." Tying every headline explicitly back to the stated landing page promise addresses a specific, real Google Ads risk: ad-to-landing-page message mismatch is something Google's Quality Score system and ad review both penalize, not a cosmetic concern, so a model that isn't constrained this way will happily write a more exciting headline than the landing page can back up. The instruction against fabricating numbers matters more in Search than in social ad copy because Search ads sit next to an explicit factual claim the user is actively fact-checking through intent (they typed "same day" or "24 hour" themselves), so an invented statistic is both a compliance risk and a credibility risk the moment the landing page doesn't match it. Requiring a rationale for the overall pinning strategy tied to the specific search intent forces the recommendation to be diagnostic rather than a generic best-practice restatement, since the right pinning approach for a high-urgency local-service search is different from an informational, comparison-shopping search.
What you get back
Headline: "Locked Out? 30-Min Help" | 22 chars | Tier 2 (differentiator) | Pin to Position 1 — carries the urgency+speed promise that matches the stated landing page response time and should not be displaced by a generic keyword-echo headline.
Verified against
ChatGPT GPT-5.1 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
