/ Blog
Home Blog Contact Buddy Ads Builder Audit Engine

Google Ads Showing RSA Headlines as Sitelinks

Ad Copy & Creative

Google Ads now allows up to two RSA headlines to serve in the sitelink position when its auction-time model predicts a higher CTR or conversion rate. This is intentional behavior, not a bug. When it happens, RSA headlines replace your sitelink extensions for that impression — they do not stack on top of them. Any of your 15 RSA headlines can appear there, so every headline must be able to stand alone as a self-contained link.

Key takeaways

  • Google's system can serve up to two RSA headlines in the sitelink extension area at auction time, replacing — not supplementing — your sitelink extensions for that impression.
  • RSA headlines appearing in the sitelink position always link to the RSA's final URL, not to separate landing pages the way true sitelinks can.
  • Every headline in your RSA is now a candidate for the sitelink position, so weak, context-dependent, or truncation-prone headlines can surface in a highly visible spot.
  • Well-crafted sitelink extensions retain unique value because they carry specific destination URLs that RSA headlines cannot replicate.
  • The fix is to audit all 15 headline slots against a "standalone sitelink test" and rewrite any that fail before they cost you CTR.
Key terms
Responsive Search Ad (RSA)
A Google Ads format that accepts up to 15 headlines and 4 descriptions, then uses machine learning to find the best-performing combinations at auction time.
Sitelink extension
An ad asset that shows additional clickable links below your main ad, each pointing to a specific destination URL separate from your main landing page.
Auction-time serving
Google's process of deciding, in real time for each individual search, which combination of ad assets and formats to show based on predicted performance.
Ad Strength
A diagnostic score in Google Ads that rates the relevance, quantity, and diversity of your RSA headline and description inputs on a scale from Incomplete to Excellent.
Dual-position test
A practitioner check for each RSA headline asking whether it works both as part of a three-headline combination and as a standalone clickable sitelink-style link.

What is Google actually doing when RSA headlines appear as sitelinks?

Google's ad serving system evaluates every auction independently and can pull up to two of your RSA headlines out of the traditional headline row and render them in the sitelink extension area below your description lines. [1] The trigger is predictive: if the model determines that surfacing those headlines in that position is likely to generate a better click-through rate or conversion outcome for the specific query, user, device, and auction context, it will do so. [2] If not, your sitelinks display normally. This question surfaced recently in the r/PPC community as practitioners noticed the change in their ad previews and weren't sure whether it was a bug or a policy shift — it is the latter.

Key Insight: Your RSA headlines now compete for two distinct positions simultaneously — the traditional headline slots and the sitelink extension area. A headline that was previously hidden in a low-rotation slot now has a new pathway to user eyeballs, for better or worse.

Yes — for any impression where Google chooses to serve RSA headlines in the sitelink position, your manually created sitelink extensions are bypassed entirely for that auction. You do not get both sitelinks and RSA headlines in the extension area at the same time. [3] This creates a meaningful tension: your sitelinks and your RSA headlines are now competing for the same extension real estate.

However, RSA headlines in the sitelink position always point to the RSA's final URL. They cannot route users to separate pages the way true sitelinks can. This functional difference is significant — especially for e-commerce accounts, multi-product advertisers, and lead generation funnels with distinct entry points. A headline like "Shop Women's Running Shoes" appearing in the sitelink slot will send a user to your homepage or main landing page, not to a women's running shoes category page. A properly configured sitelink extension would send them directly there.

Best Practice: Do not deprioritize your sitelink extensions in response to this update. Your sitelinks handle specific navigation destinations; your RSA headlines handle benefit messaging and CTAs. Keep both strong and clearly differentiated — Google's system will choose the best option per auction.

Why does this expose weak RSA headlines?

Previously, a low-quality or context-dependent headline buried in your RSA's rotation was unlikely to cause visible damage — it might simply serve less often or be outcompeted by stronger combinations. Now, any of your 15 headlines is a candidate for a sitelink-style link, which is one of the most prominent positions in a search ad. [4]

Headline types that perform poorly in the sitelink position

Common Mistake: Assuming RSA headlines only matter in the headline row. With this update, any of your 15 headlines can appear as a sitelink-style link. Weak, repetitive, or brand-inconsistent copy now surfaces in a position previously reserved for your most deliberate sitelink writing.

How should I rewrite RSA headlines to work in both positions?

The standard to aim for is a headline that passes a "dual-position test" — it works as part of a three-headline combination AND as a standalone clickable link. Research on ideal RSA headline counts consistently points to 15 headlines as the target, so you have enough slots to cover both use cases without sacrificing creative variety.

Characteristics of a strong dual-position headline

Headline categorization framework

Headline type Example Traditional slot Sitelink position
Benefit-focused (short) Free Same-Day Delivery ✅ Excellent ✅ Excellent
CTA-focused Get Your Free Quote Now ✅ Good ✅ Good
Social proof Rated 4.9 Stars by 10,000+ Customers ✅ Excellent ✅ Good
Keyword-match Plumbers in Austin TX ✅ Good ⚠️ Weak standalone
Feature-heavy (long) Award-Winning 24/7 Customer Support Team ✅ Good ⚠️ May truncate
Dependency-based And We'll Match Any Price ⚠️ Context-dependent ❌ Confusing alone
Best Practice: Aim to have at least 8–10 of your 15 RSA headlines pass the standalone sitelink test. Reserve the remaining 5–7 slots for longer-form or context-dependent headlines that work best in combination — Google will preferentially serve those in traditional headline positions where the surrounding context supports them.

How do I monitor whether this is hurting or helping performance?

Start with your RSA asset report — navigate to Ads, click the RSA, and select "View asset details" to see which headlines are rated Best, Good, or Low. [5] Headlines Google is selecting for the sitelink position are likely among your higher-rated assets, but the model is making predictions based on expected performance, not guarantees. Understanding how to read RSA headline performance data is essential for diagnosing whether this format change is working in your favor.

Warning signals to watch

Segment by device

In accounts I manage at scale, format changes like this surface differently across device types. The sitelink position on mobile is especially prominent, and a poor headline there can materially reduce CTR. Pull data segmented by device for 30–60 days before and after you first noticed the change. If mobile CTR diverges from desktop CTR in a way not previously present, RSA headlines serving in the sitelink position on mobile may be a contributing factor.

Key Insight: Your sitelinks now have a new competitor for extension real estate: your own RSA headlines. Excellence in both is the answer — not choosing one over the other.

What to do next

  1. Run a full RSA headline audit this week. Pull every active RSA into a spreadsheet. Mark each headline pass or fail on the standalone sitelink test. Target at least 8 of 15 passing per RSA. Prioritize highest-spend ad groups first. You can accelerate this using a Google Ads audit agent to surface weak asset ratings at scale.
  2. Rewrite failing headlines immediately. Replace context-dependent, incomplete, or generic headlines with self-contained, benefit-driven alternatives. Keep rewrites under 30 characters where the headline is intended to serve well in the sitelink position.
  3. Refresh your sitelink extensions. Ensure sitelinks are clearly differentiated from your RSA headlines in messaging and that each points to a specific, relevant landing page. Sitelinks lose their unique value if they're redundant with your RSA copy.
  4. Set a performance baseline now. Save CTR, Quality Score, and conversion rate data segmented by device for the past 30 days as your pre-audit benchmark. Compare at 30 and 60 days post-rewrite. Use the keyword and landing page analyzer to identify ad groups where landing page relevance may compound the issue.
  5. Update your creative brief template. Add a "sitelink position suitability" field to however you document RSA creative decisions. This change is not going away, and building the habit now prevents reactive audits every time new ads are added without the dual-position lens applied.
Common Mistake: Treating this as a one-time audit rather than a workflow change. RSA headlines are added continuously as accounts scale. Without updating your creative process, you will drift back into having weak headlines in high-visibility positions within a few months.

Frequently asked questions

Can I prevent Google from serving my RSA headlines in the sitelink position?

There is no account-level toggle to disable this behavior. The closest control available is pinning headlines to specific positions within the RSA, which restricts which headlines can serve in which slots — but pinning aggressively also reduces the system's ability to find high-performing combinations and can lower Ad Strength. The better approach is ensuring all 15 headlines are strong enough that any one of them appearing as a standalone link is acceptable.

Will RSA headlines in the sitelink position link to different pages like true sitelinks?

No. When RSA headlines serve in the sitelink position, they link to the RSA's final URL — the same landing page as the main ad. They cannot route users to separate destination URLs. This is the most significant functional difference from true sitelink extensions, and it's the primary reason sitelinks remain valuable for advertisers with multiple distinct landing pages or product categories.

Does this affect Ad Strength scores for my RSAs?

Ad Strength reflects the relevance, quantity, and diversity of your RSA assets — it evaluates your creative inputs, not how those assets are served at auction. [5] Headlines that Google selects to serve in the sitelink position are likely already among your stronger performers, but Ad Strength itself is calculated independently of which position headlines appear in. Improving headline quality for dual-position use will generally improve Ad Strength as a byproduct.

How is this different from the RSA headline expansion update that was discussed previously?

The RSA headline expansion rollout introduced the concept of headlines serving outside their traditional positions. The sitelink position serving is a specific implementation of that broader principle — Google's system now treats the extension area below your description lines as an eligible placement for RSA headline assets when the auction-time model predicts it will improve performance.

Should I write shorter RSA headlines across the board to handle truncation in the sitelink position?

Not across the board. The recommended approach is to designate roughly 8–10 of your 15 headlines as "dual-position ready" — these should aim for under 30 characters. The remaining 5–7 slots can carry longer, context-dependent headlines suited to the traditional three-headline combination. Shortening everything sacrifices the descriptive depth that works well in headline rows. Use a creative asset validator to flag character counts and dependency issues before publishing.

Does this change how I should structure RSAs for new campaigns?

Yes. Current RSA structure best practice now calls for explicitly categorizing headlines by intended position use during the brief stage — not as an afterthought. Write benefit-focused, self-contained headlines first to fill the dual-position slots, then layer in keyword-match and context-dependent variants to complete the 15. This approach ensures your RSA is optimized for both the headline row and the sitelink position from day one.

References

  1. Google Ads Help. “About responsive search ads.” Accessed Nov 15, 2026.
  2. Google Ads Help. “About Ad Rank.” Accessed Nov 15, 2026.
  3. Google Ads Help. “About assets.” Accessed Nov 15, 2026.
  4. Google Ads Help. “Best practices for creating effective responsive search ads.” Accessed Nov 15, 2026.
  5. Google Ads Help. “About Ad Strength for responsive search ads.” Accessed Nov 15, 2026.
  6. Google Ads Help. “About Quality Score for Search campaigns.” Accessed Nov 15, 2026.
  7. Original community discussion: r/PPC thread on Reddit.

Related Reading

AI Disclosure: This article was generated with AI assistance based on a community discussion on Reddit r/PPC. Expert analysis and practitioner perspective by John Williams, Founder, AHMEEGO · Google Ads Practitioner with $350M+ in managed Google Ads spend. AI was used to draft and structure the content; all strategic recommendations reflect real campaign experience.