If you logged into Google Ads recently and noticed something unfamiliar in your ad previews — headlines from your Responsive Search Ads appearing where sitelinks used to live — you're not imagining things, and you're definitely not alone. Google quietly rolled out a significant change that allows up to two RSA headlines to serve in the sitelink position when the system predicts it will improve performance. This isn't a bug. It's a feature. And whether it helps or hurts your campaigns depends entirely on how prepared your creative assets are to handle it.
Google's ad serving system has always been hungry for real estate. The search results page is a battlefield, and Google's machine learning is constantly looking for ways to make ads more prominent and more clickable. This latest update is a natural extension of that philosophy.
When Google determines that your RSA headlines are strong enough — and relevant enough to the query — it can now pull up to two of those headlines out of the traditional headline slot and serve them in the sitelink extension area below your main ad copy. The headlines still count as headlines in the RSA context, but visually they appear as additional blue clickable links beneath your description lines, occupying space that previously was exclusively reserved for sitelink extensions.
The trigger is purely predictive. Google's auction-time system evaluates whether swapping in RSA headlines instead of (or in addition to) sitelinks is likely to generate a higher click-through rate or better conversion performance for that specific query, user, device, and auction. If the model says yes, it serves the headlines there. If not, your sitelinks show as normal.
A common question in the r/PPC community is whether this is something to be excited about or worried about. The answer, as with most Google Ads changes, is: it depends on the quality of your creative assets and how you've been managing your RSAs.
Practitioners who have invested in writing purpose-built, varied RSA headlines — including benefit-focused, CTA-focused, and feature-focused variants — will likely see a performance lift from this. The system now has more options to present compelling information to users.
On the other hand, advertisers who have been treating RSAs as a "set it and forget it" format, stuffing in repetitive or thin headlines, are suddenly exposed. If your RSA headlines are generic or overlap heavily with each other, Google may now be surfacing those weak headlines in highly visible positions, potentially hurting CTR and quality score signals.
The first thing any practitioner should do after learning about this change is pull up every active RSA in their account and look at the headlines with fresh eyes — specifically asking: "Would I be comfortable if this headline appeared as a standalone sitelink link?"
Sitelinks have historically been short, action-oriented, and self-contained. They work as navigational anchors. Your RSA headlines were written to work in combination — Headline 1 + Headline 2 + Headline 3 as a unit. Some of them may not stand alone well.
Common headline types that perform poorly as standalone sitelink-style links:
Going forward, the gold standard for RSA headlines is one that can function both as part of a three-headline combination AND as a standalone clickable link. Think of it as writing headlines that pass a "dual-position test."
Strong dual-position headlines share these characteristics:
Previously, Google's advice on RSA headline diversity was about ensuring the machine learning had enough variation to find the best three-headline combinations. Now, diversity takes on an additional dimension: you want headlines diverse enough in type and length to serve well across two distinct ad unit positions.
A useful framework for headline categorization within a single RSA:
| 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 |
| Keyword-match | "Plumbers in Austin TX" | ✅ Good | ⚠️ Weak standalone |
| Feature-heavy (long) | "Award-Winning 24/7 Customer Support Team" | ✅ Good | ⚠️ May truncate |
| Social proof | "Rated 4.9 Stars by 10,000+ Customers" | ✅ Excellent | ✅ Good |
| Dependency-based | "And We'll Match Any Price" | ⚠️ Context-dependent | ❌ Confusing alone |
This is the question that trips up a lot of practitioners: if RSA headlines are appearing in the sitelink space, does that mean your actual sitelink extensions get dropped?
Based on how Google's system works, this appears to be an either/or decision at the auction level. When Google serves RSA headlines in the sitelink position, it is replacing sitelinks for that impression — not adding additional slots. You don't get sitelinks AND RSA headlines in the extension area simultaneously.
This has a meaningful implication for accounts that have invested heavily in crafting high-quality sitelinks. If Google's model decides RSA headlines are more likely to perform, your manually curated sitelinks — with their carefully written descriptions and specific landing pages — get bypassed entirely.
RSA headlines that appear in the sitelink position will link to the same landing page as your ad — the final URL of the RSA. They cannot link to different pages the way true sitelinks can. This is a significant functional difference.
If a user sees "Shop Women's Running Shoes" as a sitelink-position RSA headline and clicks it, they go to your homepage or main landing page — not a women's running shoes category page. True sitelinks would send them directly to that specific page.
This means for e-commerce accounts, lead gen funnels with multiple entry points, or any advertiser where the journey varies significantly by user intent, well-crafted sitelinks with specific destination URLs retain enormous value that RSA headlines in the sitelink position simply cannot replicate.
Navigate to your RSA asset report (Ads > click on the RSA > View asset details) and look at which headlines are receiving "Best," "Good," or "Low" performance ratings. Headlines Google is choosing to serve in the sitelink position are likely to be among your higher-performing assets — but not always. The model is making predictions, not guarantees.
Watch for these signals that the change may be hurting performance:
In my experience managing accounts at scale, format changes like this one often surface differently across device types. Mobile users in particular respond to ad formats differently — the sitelink position on mobile is highly prominent and a poor headline in that slot can actively reduce CTR.
Pull your data segmented by device for the past 30–60 days versus the same period after this change rolled out. If you're seeing mobile CTR diverge from desktop CTR in a way that wasn't previously present, RSA headlines in the sitelink position on mobile may be a contributing factor.
Keep an eye on your impression share and Auction Insights data. If competitors who also have strong RSA headline libraries start gaining ground in the ad extension space, you may need to accelerate your RSA creative refresh cycle. The accounts that move fastest to optimize their headline libraries for this new dual-position reality will have a competitive advantage in the near term.
This update should prompt a change in how your creative team (or you, solo practitioner) approaches RSA development. Here's the updated workflow I'd recommend:
To summarize everything above into a concrete action plan, here are five things to do this week:
The practitioners who navigate this change best will be the ones who treat it not as a disruption but as an invitation to raise the quality bar on their RSA creative. If your headlines are strong enough to work as standalone links, they're strong enough to excel in every position Google might serve them in. That's always been the goal — this update just makes it more visible when you've fallen short.