Responsive Ads: RSA vs. RDA, Asset Requirements, and Testing
Published:
Last Updated:
Category: Ad Operations
Authors: Shusaku Yosa
Responsive ads assemble eligible assets for different advertising situations. Responsive search ads, or RSAs, use text assets for search. Responsive display ads, or RDAs, combine visual and text assets for display inventory. Supplying more material is not enough: every eligible combination should communicate an accurate offer.
The specifications below concern Google Ads documentation checked on October 1, 2026. Do not apply them automatically to another platform or format.
RSA and RDA serve different contexts
Element | Responsive search ads | Responsive display ads |
|---|---|---|
Context | Search results | Advertising spaces across sites and apps |
Main assets | Headlines and descriptions | Images, logos, text and optional video |
Main creative task | Answer the query and explain the offer | Make the offer understandable visually |
Key review | Repetition, essential conditions and destination | Cropping, readability and asset combinations |
Check specifications before producing assets
Google’s RSA documentation allows up to 15 headlines of 30 characters and four descriptions of 90 characters. Double-width characters, including Japanese, count as two. An English character limit should therefore not be presented as the same number of Japanese characters.
RDA visual asset | Recommended example | Minimum example |
|---|---|---|
Landscape image, 1.91:1 | 1200 × 628 | 600 × 314 |
Square image | 1200 × 1200 | 300 × 300 |
Landscape logo, 4:1 | 1200 × 300 | 512 × 128 |
Square logo | 1200 × 1200 | 128 × 128 |
The RDA creation guide also covers file-size and text requirements. Check the actual upload interface for additional formats and automation options. Meeting the pixel dimensions does not ensure that a cropped image communicates the intended message.
Build an asset brief around distinct questions
Consider a fictional reservation-management tool for teams. The examples below are creative exercises, not claims about a particular product. Verify any feature, price or trial condition before using it in an ad.
Asset role | Example headline | Supporting explanation |
|---|---|---|
Problem | Review Booking Conflicts | Explain the specific overview or checking feature |
Use case | Team Booking Management | State which team members can share what information |
Comparison | Compare Features and Plans | Make plan and user-count conditions clear |
Next action | Read the Setup Guide | Describe what the destination contains |
Create different decision-relevant information rather than many near-identical synonyms. Check whether “completely free” could appear beside an asset describing a paid-only feature. Also look for contradictory dates, audiences or conditions. A combination should remain truthful when another asset is omitted.
Use pinning for a defined reason
RSA assets can be pinned, but not every position is guaranteed to appear in every serving context. Google distinguishes headlines pinned to positions one and two and descriptions pinned to position one from later positions that may not appear. Review the current behavior when an essential condition must accompany an offer.
Pinning reduces flexibility. Separate a mandatory disclosure or brand requirement from a preference about word order. Involve the responsible reviewer where a missing condition could make an ad misleading, and make sure the landing page also explains the offer accurately.
Review before publication
- Each headline and description makes sense on its own.
- Prices, dates, eligibility and free-plan limits remain consistent across combinations.
- Essential information is not assumed to appear in an optional position.
- Images and logos meet specifications and have appropriate usage rights.
- Cropping does not remove the product or a necessary condition.
- The destination delivers what the ad promises.
- Measurement distinguishes successful actions from failures and duplicates.
A preview shows representative layouts, not every possible placement. If automatically generated or modified assets are enabled, assign someone to review the permitted scope and resulting material.
Evaluate the business outcome
An ad-strength diagnostic can suggest improvements, but it is not revenue or qualified demand. Combination reports are also not equivalent to an experiment that assigns equal, random exposure to each variation. Selection, audience and timing can differ.
For each revision, record a hypothesis. For example: “The price condition is unclear, attracting inquiries from people outside the intended segment.” Clarify the condition, then inspect qualified-inquiry rate and CPA as well as CTR. A lower CTR can be acceptable if it removes irrelevant clicks and improves the downstream outcome.
Use a consistent review window and allow time for conversions to arrive. Avoid replacing assets repeatedly on the basis of a handful of impressions. When a causal comparison matters, design a suitable controlled test instead of treating descriptive asset rankings as proof.
Related guides
Review your results consistently
For ongoing data aggregation, comparison and reporting, review NeX-Ray’s integrations and features. Check the plan requirements for your analysis, then start for free.
Sources and verification
Public documentation checked on October 1, 2026. Availability and interface details can vary by account and market; check the linked documentation before configuring a campaign.
