Responsive Search Ads: A Practical Setup and QA Checklist

A responsive search ad can have plenty of headlines and still send people to the wrong page, promote an expired offer, or generate leads your sales team cannot use.

A useful review covers three things: whether the copy matches the search, whether the destination delivers on the promise, and whether the conversion data reflects the outcome you want.

This checklist is for paid acquisition marketers setting up new ads or reviewing an existing account.

Start with the search and the landing page

Before writing headlines, decide what the ad group is meant to answer. Someone looking for an implementation partner needs a different message from someone researching how a tool works.

Keep the keywords, offer, and landing page aligned. If the ad promises a specific service, the destination should explain that service and give the visitor a clear next step.

For a martech integration campaign, check that the landing page names the platforms you support, explains the scope, and makes it easy to book a call. Sending every service query to a generic homepage makes the visitor do more work.

Give each headline a distinct job

Responsive search ads support up to 15 headlines and four descriptions. Headlines can contain up to 30 characters, and descriptions up to 90. Google combines the assets, so each needs to work alongside different messages. See Google’s responsive search ad specifications.

Use the available space to cover different reasons to choose your business:

Service: what you deliver.
Buyer need: the problem the visitor wants to solve.
Scope: what is included.
Proof: a specific claim you can substantiate.
Next step: what the visitor can do.

For example, “Segment Implementation,” “Tracking Setup & Testing,” and “Book an Integration Call” communicate different information. Several versions of “Better Martech Results” provide much less variety.

Read the assets in different combinations. Remove repeated phrases, unexplained claims, and wording that only makes sense after another headline.

Use descriptions to answer practical questions

A description should add information the headline could not fit. Explain the service, the scope, or the next step.

For example: “Connect Segment to ad networks. Includes event planning, testing, and documentation.”

Check every price, timeline, and inclusion against the landing page. If a price applies only to a particular scope, the surrounding message needs to make that clear.

Pin assets when their position matters

Pinning gives you control over where an asset appears, but reduces the combinations available. Use it when a message must appear consistently, such as required wording or a specific campaign constraint.

Google identifies Headline 1, Headline 2, and Description 1 as positions for text that must appear in every ad. Confirm the pinning setup rather than relying on an unpinned asset to show. Read Google’s pinning guidance.

Document why an asset is pinned. That gives the next person reviewing the account enough context to avoid removing an intentional restriction.

Use Ad Strength to review the assets

Ad Strength provides feedback on asset relevance and variety. It can help identify gaps while you build or edit an ad.

It does not measure lead quality or profitability, and Google says it is not used to calculate Ad Rank or Quality Score. Review it alongside business outcomes. See how Google defines Ad Strength.

If an ad earns a strong rating but produces poor leads, inspect the search terms, offer, landing page, and conversion setup before adding more headlines.

Check the conversion you are asking Google to optimize

A form submission and a qualified sales opportunity represent different outcomes. Decide which outcome the campaign should pursue and check that the conversion settings support that goal.

Before launch, test the user journey. Confirm that the expected event fires, carries the right information, and does not record the same action twice.

If your sales outcome happens later in a CRM, assess whether offline conversion reporting belongs in the setup. Our server-side tracking cost guide explains how Cald scopes Segment implementations and offline conversions.

Review performance with enough context

Avoid using a fixed waiting period as the only reason to make or postpone a change. Consider traffic, conversion volume, conversion delay, and the size of the change.

Fix broken links, expired promotions, and tracking errors when you find them. For a messaging test, define the question and success measure before making the edit.

Review click-through rate alongside conversion rate, cost per qualified lead, or revenue where available. A message that attracts more clicks can also attract the wrong audience.

Keep a change log with the date, assets changed, reason, and expected result. Changing copy, targeting, landing pages, and bidding together makes the outcome harder to interpret.

Responsive search ads QA checklist

Before launch, and after meaningful changes, check:

The search intent, offer, and landing page match.
Headlines and descriptions provide distinct information and work in different combinations.
Prices, promotions, and claims are current and supported by the destination page.
Pinned assets have a documented purpose.
Final URLs and relevant sitelinks reach the intended pages.
The landing page and form work on mobile.
Tracking parameters survive the journey where required.
Conversion events fire as expected without unintended duplication.
Campaign and ad group names make reporting and ownership clear.
Someone owns follow-up checks after launch.

Use this as a repeatable review process. It gives the team a common definition of what is ready to launch and what needs attention.