Google Ads guide

Google Ads Responsive Search Ads Checklist

Use this Google Ads responsive search ads checklist before publishing an RSA, when replacing assets, and during post-launch reviews. Confirm the ad-group theme, landing page, conversion action, headline and description roles, policy, pinning, supporting assets, and measurement baseline. Mark an item complete only when the account, preview, or operating record provides evidence.

Google says responsive search ads combine multiple headlines and descriptions and learn from different combinations. See About responsive search ads and best practices for creating effective RSAs for the current guidance.

For setup details, read how to set up Google Ads responsive search ads. For troubleshooting, see how to fix Google Ads responsive search ads.

Theme and destination

  • [ ] The ad group has one clear customer intent, product or service, audience, geography, and offer.
  • [ ] Different prices, qualifications, urgency, services, products, or next actions have separate themes when needed.
  • [ ] The final URL answers the theme and continues the ad’s promise.
  • [ ] The page works on mobile and desktop, loads with tracking parameters, and has no unexpected redirect or destination error.
  • [ ] The page clearly states the offer, availability, location, qualification, and next action.
  • [ ] Form, call, purchase, or other conversion action is visible and tested.

Do not ask one RSA to solve an ad group that contains unrelated promises.

Headline assets

  • [ ] Headlines cover the category, benefit, problem solved, proof, qualification, availability, offer condition, and next step where relevant.
  • [ ] Each headline is useful and truthful on its own.
  • [ ] Headlines are distinct rather than minor word-order variations.
  • [ ] Character limits, spelling, punctuation, trademarks, and claims are checked.
  • [ ] Location, price, inventory, shipping, and eligibility wording is accurate.
  • [ ] Keyword insertion or customization has been previewed for fallback, grammar, length, and policy.
  • [ ] The set uses the available space for coverage without adding filler.

Google’s asset documentation allows up to 15 headlines for one RSA. Use the limit as an opportunity for useful variation, not a quota.

Description assets

  • [ ] Descriptions explain the value, process, qualification, included details, and next step.
  • [ ] Each description adds information instead of repeating another asset.
  • [ ] Conditions and claims are accurate and approved.
  • [ ] Descriptions make sense in combinations with different headlines.
  • [ ] The call to action matches the page’s available action.
  • [ ] Up to 4 descriptions are used where the theme has useful coverage, without padding.

Preview and pinning

  • [ ] Likely combinations were read as complete ads, not only as individual fields.
  • [ ] No combination is contradictory, ungrammatical, or unsupported by the page.
  • [ ] Pins have a documented legal, brand, qualification, or offer reason.
  • [ ] Nonessential assets remain unpinned.
  • [ ] The pinned layout still has enough useful combinations.
  • [ ] A future owner knows which pins can be removed and when.

Google notes that pinned headlines and descriptions limit combinations. Pin the minimum necessary message.

Policy and supporting assets

  • [ ] Ad claims, prices, trademarks, punctuation, and restricted-category language comply with applicable policy.
  • [ ] The destination is accessible and belongs to the intended domain.
  • [ ] Sitelinks, callouts, images, calls, locations, and other relevant assets point to useful and approved destinations.
  • [ ] Automated text or asset creation has an owner and review process.
  • [ ] Brand, product, service, or legal wording is current.

Measurement and baseline

  • [ ] Current ads, assets, pins, final URL, ad group, keywords, and campaign settings are saved.
  • [ ] Primary conversion action, counting, values, currency, attribution, and conversion window are verified.
  • [ ] Lead quality, purchase value, margin, inventory, or service capacity is included where relevant.
  • [ ] Baseline impressions, clicks, spend, conversions, qualified outcomes, value, and landing-page behavior are recorded.
  • [ ] The test question, owner, start date, and review date are documented.

Launch checks

  • [ ] The RSA is saved in the intended campaign and ad group.
  • [ ] Policy review and eligibility status are understood.
  • [ ] Budget, bidding, locations, language, schedule, and network settings are confirmed.
  • [ ] Final URL and conversion events work after publishing.
  • [ ] Change history records the edit.
  • [ ] Urgent corrections have a rollback plan.

Post-launch review

  • [ ] Asset and combinations reports are reviewed with search terms.
  • [ ] Impressions, clicks, spend, CTR, conversions, qualified outcomes, cost, value or margin, and page behavior are compared with the baseline.
  • [ ] Ad Strength is used as a diagnostic, not the only success measure.
  • [ ] High-impression assets are checked for lead or purchase quality.
  • [ ] Low delivery is diagnosed across campaign, target, budget, eligibility, demand, page, and policy—not only copy.
  • [ ] One meaningful change is made at a time where possible.
  • [ ] The next owner and review date are recorded.

The adz.so free Google Ads audit is a truthful next step for reviewing supported account settings. It does not write RSA assets or guarantee the best combination. Use the checklist with Google Ads reports and real business outcomes.