Should I enable automated extensions?

Alexandre Airvault
January 14, 2026

What “automated extensions” means in Google Ads today (and why the wording matters)

If you’ve been running Google Ads for a while, “automated extensions” was the common phrase for Google-created add-ons like dynamic sitelinks or dynamic callouts. In today’s Google Ads UI and documentation, these are generally referred to as assets, and the automation falls into two main buckets that behave differently.

Account-level automated assets (the classic “automated extensions”)

These are automated assets that can be created and served at the account level and shared across eligible campaigns. The most common examples are dynamic sitelinks, dynamic callouts, and dynamic structured snippets. The key idea is simple: if the system predicts an automated asset will improve performance, it can generate and show it with your ad. These automated assets can show alongside or instead of your manually created assets, depending on what’s predicted to work best for that auction.

Cost-wise, you’re generally charged the same way you always are for ad interactions (for example, clicks), and Google Ads limits charges to no more than two clicks per impression across an ad and its assets. One notable exception is that clicks on seller ratings themselves aren’t charged (clicks on the ad still are).

Text customization (formerly “automatically created assets”) at the campaign level

Separate from account-level automated assets, there’s another automation layer that generates additional headlines and descriptions for responsive search ads. This capability was formerly known as “automatically created assets,” and it has been transitioning into text customization as part of AI Max for Search campaigns settings (with upgrades beginning May 27, 2025).

Two practical details matter here: first, these system-generated headlines/descriptions don’t count against the responsive search ad limits (15 headlines and 4 descriptions). Second, generation quality depends heavily on your landing pages—if your pages are thin, unclear, or frequently changing, you should expect weaker or fewer usable assets.

Should you enable them? In most accounts, yes—if you do it with guardrails

After managing accounts for 15+ years, my default position is: enable automated extensions/automated assets when you have solid fundamentals in place, then manage them actively. When advertisers get into trouble with automation, it’s rarely because automation exists—it’s because they turned it on in an account that wasn’t ready, then didn’t review what the system created.

The upside: more relevance, more coverage, and less manual busywork

Automated assets exist for one reason: to help your ads take up more useful real estate and connect people to what they actually want. Dynamic sitelinks can route users to deeper pages that match intent. Dynamic callouts and structured snippets can surface credibility points and product/service breadth without you writing 50 variations. And if you’re aiming for stronger responsive search ad performance, text customization can add incremental message testing without consuming your manual asset slots.

Another advantage that experienced advertisers appreciate: automated assets can react faster than most teams can. If your site content changes often (inventory, seasonal categories, shipping messages, location details), automated assets can sometimes keep ads aligned with reality—provided your landing pages are accurate and well-structured.

The downside: less message control (and a higher standard for landing pages)

The main drawback is straightforward: the system may choose messaging or destinations you wouldn’t have chosen. That can be harmless (“About Us” sitelink shows sometimes) or painful (an outdated promo, a weak category page, or a callout that creates compliance issues).

Also, automation can expose messy site architecture. If your navigation, headings, or page templates are inconsistent, Google can still generate assets—but they may be vague, redundant, or off-brand. In regulated categories, or whenever legal disclaimers must appear with specific claims, automation needs especially careful review.

Finally, understand the “instead of” behavior: if you’ve invested in strong manual assets, you don’t want automated assets replacing them with weaker options. The solution isn’t automatically “turn it all off”—it’s to build a better manual asset set, then remove or opt out of only the automated pieces that don’t meet your standard.

When enabling automated extensions is the right move (and when I’d be cautious)

I usually recommend enabling automation when…

You’re running lead gen or ecommerce with clear site structure, you have multiple strong landing pages per theme, and you already maintain a healthy set of manual assets (sitelinks, callouts, structured snippets, images where appropriate). In this scenario, automated assets typically act as incremental performance helpers—filling gaps, finding additional pathways, and improving ad usefulness for long-tail queries.

I’m also more comfortable enabling these features when you have stable conversion tracking and clean measurement, because you can evaluate impact without guessing.

I’m cautious (or selectively opt out) when…

If your business has strict compliance requirements, highly controlled brand language, frequent short-lived promotions, or a website where important messaging sits behind scripts, PDFs, or gated content, automation is more likely to misfire. I’m also cautious when a single Google Ads account spans multiple brands/locations/service lines with very different rules—automation can accidentally generalize what should stay segmented.

In these cases, you can still use automation, but you’ll want tighter governance: remove individual automated assets you don’t like, and consider opting out of specific automated asset types that create risk (rather than disabling everything across the board).

How to enable automated assets safely (my practical framework)

Step 1: Build strong manual assets first so automation complements (not replaces) quality

Before you lean on automated assets, give the system a high-quality “menu” to choose from. For sitelinks, that usually means having multiple, genuinely distinct destinations (pricing, services, locations, testimonials, booking, contact, etc.) and keeping them fresh. For callouts and structured snippets, it means coverage across your real differentiators (not filler like “Great service”).

This matters because when manual assets are thin or repetitive, automation tends to get blamed for poor output—when the real issue is that the account didn’t provide enough strong options in the first place.

Step 2: Review what Google created (and remove what you don’t want)

The system gives you visibility and control, but you have to use it. Automated assets and text customization can be reviewed through asset reporting, where you can filter by assets that were automatically created. If you see a dynamic sitelink, callout, or structured snippet you don’t like, you can typically pause it (to stop serving while keeping the option to re-enable) or remove it (to prevent it from serving again).

For account-level automated assets specifically, you can also turn off particular automated asset types from the account-level automated assets settings area. This “surgical” approach is usually the best balance: keep the automation that helps, disable the pieces that create risk.

Step 3: Treat it like an optimization test, not a belief system

Don’t decide based on ideology (“automation is good” or “automation is bad”). Decide based on results. Compare performance over a meaningful window (enough conversion volume to reduce noise), and watch not only conversion rate and CPA/ROAS, but also lead quality signals if you have them (qualified leads, booked calls that show, downstream revenue).

Also remember that the system can generate assets, then later stop serving them if they perform poorly or if the context changes (site edits, keyword shifts, ad edits). That’s helpful—but it’s not a substitute for a human keeping standards high.

Quick decision checklist: enable automated extensions if you can say “yes” to most of these

  • My landing pages are strong and specific (clear headings, clear offers, clean navigation, no outdated promos).
  • I already use manual assets that reflect what I actually want shown (not the bare minimum).
  • I can review asset reporting regularly and remove/pause anything inaccurate, off-brand, or risky.
  • My conversion tracking is trustworthy so I can evaluate impact without guesswork.
  • I’m comfortable with “predicted to improve performance” logic and understand automated assets may show alongside or instead of manual assets.

The expert recommendation (most advertisers): enable, monitor, and prune

In the majority of real-world accounts, enabling automated extensions (account-level automated assets) is worth it—as long as you commit to reviewing what’s created and removing what doesn’t meet your standards. If you want the benefits without the surprises, the winning approach is almost always the same: build excellent manual assets first, then let automation add incremental lift, and actively curate anything the system generates that you wouldn’t proudly claim as your own.

Let AI handle
the Google Ads grunt work

Try our AI Agents now
Topic What it is / how it works Main benefits Main risks & constraints When to enable When to be cautious / opt out Practical actions & checks Relevant Google Ads docs
Account‑level automated assets (classic “automated extensions”) System‑generated assets (e.g. dynamic sitelinks, dynamic callouts, dynamic structured snippets, seller ratings) created at the account level and shared across eligible campaigns. If Google predicts they’ll improve performance, they can show alongside or instead of your manual assets in a given auction. Costs follow normal ad interaction rules, with no more than two billable clicks per impression; clicks directly on seller rating details aren’t charged.
  • More SERP real estate and richer ad experiences without writing everything manually.
  • Can react faster than manual updates when site content changes (inventory, locations, seasonal content).
  • Often fills gaps for long‑tail queries and uncovers additional relevant landing pages.
  • Less control over exact messaging and destinations; may surface pages or phrasing you wouldn’t choose.
  • Can expose weak or messy site architecture (vague headings, thin content, inconsistent templates).
  • May sometimes show instead of strong manual assets if those aren’t well built or maintained.
  • Higher governance burden in regulated or tightly controlled brands.
  • Lead gen or ecommerce with clear, logical site structure and multiple strong landing pages per theme.
  • You already have robust manual assets (sitelinks, callouts, structured snippets, images).
  • Stable, trustworthy conversion tracking so you can measure impact.
  • Strict compliance, legal, or brand‑language requirements.
  • Frequent short‑lived promos that risk surfacing after expiry.
  • Single account spanning multiple brands/locations/service lines with different rules.
  • Key messaging hidden behind scripts, PDFs, or gated content.
  • Build strong manual sitelinks, callouts, and structured snippets first so automation complements them.
  • Use asset reporting to review dynamic sitelinks/callouts/structured snippets and pause or remove any that are off‑brand or risky.
  • Use account‑level automated asset settings to selectively opt out of specific asset types rather than disabling everything.
  • Evaluate performance (CTR, CVR, CPA/ROAS, lead quality) over a meaningful window and prune poor performers.
Campaign‑level text customization (formerly “automatically created assets”) Campaign‑level setting that lets Google generate additional headlines and descriptions for responsive search ads based on your landing pages and existing assets. Historically called “automatically created assets”, transitioning into text customization under AI Max for Search campaigns starting May 27, 2025. Generated text does not count against the RSA limits of 15 headlines and 4 descriptions. Quality and quantity depend heavily on the richness and clarity of your landing pages. ([support.google.com](https://support.google.com/google-ads/answer/11259373?hl=en&utm_source=openai))
  • Increases creative coverage and message testing without consuming manual asset slots.
  • Allows Google to tailor copy more precisely to query and context.
  • Can improve ad strength and performance when landing pages are strong.
  • May generate off‑brand, vague, or non‑compliant copy if site content is unclear or inconsistent.
  • Higher review burden in regulated industries or where disclaimers must accompany specific claims.
  • Relies on landing page quality; thin or rapidly changing pages yield weaker assets.
  • Campaigns with well‑structured, content‑rich landing pages that mirror your core messaging.
  • When you want more experimentation and incremental variants beyond what you can manually write.
  • When you can regularly review assets and combinations in reports.
  • Heavily regulated verticals (financial, medical, legal, etc.) or strict brand‑tone requirements.
  • Promotions or offers that change weekly and could easily become outdated.
  • Accounts where legal must approve every line of copy.
  • Turn on or manage text customization in Search campaign settings (as part of AI Max for Search campaigns).
  • Use the asset report and RSA combination report to see which automatically created assets serve, then remove unwanted ones. ([support.google.com](https://support.google.com/google-ads/answer/13548268?hl=en&utm_source=openai))
  • Ensure landing pages have clear headings, accurate offers, and current promos; avoid thin, boilerplate content.
  • Treat it as a test: compare performance with/without text customization, including downstream lead or sales quality.
Readiness checklist for enabling automation The decision isn’t “automation vs. no automation” but whether your account has the fundamentals to use it safely and profitably. The blog recommends enabling automated extensions/assets in most accounts once those fundamentals are in place, then actively monitoring and pruning.
  • Automation adds scalable coverage and relevance on top of a strong manual foundation.
  • Reduces manual busywork while still allowing granular control via review and removal tools.
  • Turning automation on in an unprepared account (weak pages, minimal assets, no measurement) often leads to poor outputs and misattribution of blame to automation.
  • Failure to review generated assets can allow inaccurate, outdated, or non‑compliant messaging to run.
Enable automated assets/text customization if you can say “yes” to most of:
  • Landing pages are strong, specific, and up‑to‑date.
  • You already have well‑built manual assets (not just the bare minimum).
  • You can review asset reporting regularly and clean up issues.
  • Conversion tracking is trustworthy.
  • You understand that automated assets may serve alongside or instead of manual ones based on predicted performance.
  • If several checklist items are “no” (weak pages, thin assets, poor tracking, no bandwidth for review), prioritize fixing those before enabling broad automation.
  • In high‑risk contexts, start small and selectively opt out of problematic asset types.
  • Use asset association and status controls to systematically pause/remove low‑quality automated sitelinks and related assets.
  • Use RSA asset and combination views to audit automatically created headlines/descriptions, then refine site content to guide better generations. ([support.google.com](https://support.google.com/google-ads/answer/2375416?utm_source=openai))
  • Monitor performance (CTR, CVR, CPA/ROAS, lead quality) before and after enabling each automation layer.
Overall expert recommendation Enable account‑level automated assets and campaign‑level text customization in most mature accounts, but treat them as tools to be managed, not a set‑and‑forget switch.
  • Incremental performance lift when built on top of strong manual setup.
  • Greater coverage and responsiveness to changing user intent and site content.
  • Poor outcomes if enabled without strong foundations or ongoing review.
  • Potential compliance/brand risks where oversight is weak.
  • “Enable, monitor, and prune”: start with a solid manual structure, then let automation add lift.
  • Keep only the automated assets you’d proudly approve as if they were written manually.
  • Be more conservative in high‑risk industries or multi‑brand setups; favor selective opt‑outs and heavier human review.
  • Regularly audit automated assets in the Assets view and RSA reports.
  • Iterate landing pages and manual assets based on what performs best in combination with automation.

Let AI handle
the Google Ads grunt work

Try our AI Agents now

Whether you should enable automated extensions (Google’s account-level automated assets like dynamic sitelinks and callouts) comes down to readiness: they’re often worth turning on when you already have strong manual assets in place, clear and up-to-date landing pages, and reliable conversion tracking, because automation can add coverage and keep ads relevant as your site evolves, but they require ongoing review to avoid off-brand messaging, outdated promo links, or compliance issues—especially in regulated or multi-brand accounts. If you want a simple way to “enable, monitor, and prune” without treating automation as set-and-forget, Blobr connects to your Google Ads and runs specialized AI agents that continuously audit assets and landing-page alignment, highlight what’s likely helping or hurting, and surface concrete recommendations you can apply while keeping your own rules and constraints in control.

What “automated extensions” means in Google Ads today (and why the wording matters)

If you’ve been running Google Ads for a while, “automated extensions” was the common phrase for Google-created add-ons like dynamic sitelinks or dynamic callouts. In today’s Google Ads UI and documentation, these are generally referred to as assets, and the automation falls into two main buckets that behave differently.

Account-level automated assets (the classic “automated extensions”)

These are automated assets that can be created and served at the account level and shared across eligible campaigns. The most common examples are dynamic sitelinks, dynamic callouts, and dynamic structured snippets. The key idea is simple: if the system predicts an automated asset will improve performance, it can generate and show it with your ad. These automated assets can show alongside or instead of your manually created assets, depending on what’s predicted to work best for that auction.

Cost-wise, you’re generally charged the same way you always are for ad interactions (for example, clicks), and Google Ads limits charges to no more than two clicks per impression across an ad and its assets. One notable exception is that clicks on seller ratings themselves aren’t charged (clicks on the ad still are).

Text customization (formerly “automatically created assets”) at the campaign level

Separate from account-level automated assets, there’s another automation layer that generates additional headlines and descriptions for responsive search ads. This capability was formerly known as “automatically created assets,” and it has been transitioning into text customization as part of AI Max for Search campaigns settings (with upgrades beginning May 27, 2025).

Two practical details matter here: first, these system-generated headlines/descriptions don’t count against the responsive search ad limits (15 headlines and 4 descriptions). Second, generation quality depends heavily on your landing pages—if your pages are thin, unclear, or frequently changing, you should expect weaker or fewer usable assets.

Should you enable them? In most accounts, yes—if you do it with guardrails

After managing accounts for 15+ years, my default position is: enable automated extensions/automated assets when you have solid fundamentals in place, then manage them actively. When advertisers get into trouble with automation, it’s rarely because automation exists—it’s because they turned it on in an account that wasn’t ready, then didn’t review what the system created.

The upside: more relevance, more coverage, and less manual busywork

Automated assets exist for one reason: to help your ads take up more useful real estate and connect people to what they actually want. Dynamic sitelinks can route users to deeper pages that match intent. Dynamic callouts and structured snippets can surface credibility points and product/service breadth without you writing 50 variations. And if you’re aiming for stronger responsive search ad performance, text customization can add incremental message testing without consuming your manual asset slots.

Another advantage that experienced advertisers appreciate: automated assets can react faster than most teams can. If your site content changes often (inventory, seasonal categories, shipping messages, location details), automated assets can sometimes keep ads aligned with reality—provided your landing pages are accurate and well-structured.

The downside: less message control (and a higher standard for landing pages)

The main drawback is straightforward: the system may choose messaging or destinations you wouldn’t have chosen. That can be harmless (“About Us” sitelink shows sometimes) or painful (an outdated promo, a weak category page, or a callout that creates compliance issues).

Also, automation can expose messy site architecture. If your navigation, headings, or page templates are inconsistent, Google can still generate assets—but they may be vague, redundant, or off-brand. In regulated categories, or whenever legal disclaimers must appear with specific claims, automation needs especially careful review.

Finally, understand the “instead of” behavior: if you’ve invested in strong manual assets, you don’t want automated assets replacing them with weaker options. The solution isn’t automatically “turn it all off”—it’s to build a better manual asset set, then remove or opt out of only the automated pieces that don’t meet your standard.

When enabling automated extensions is the right move (and when I’d be cautious)

I usually recommend enabling automation when…

You’re running lead gen or ecommerce with clear site structure, you have multiple strong landing pages per theme, and you already maintain a healthy set of manual assets (sitelinks, callouts, structured snippets, images where appropriate). In this scenario, automated assets typically act as incremental performance helpers—filling gaps, finding additional pathways, and improving ad usefulness for long-tail queries.

I’m also more comfortable enabling these features when you have stable conversion tracking and clean measurement, because you can evaluate impact without guessing.

I’m cautious (or selectively opt out) when…

If your business has strict compliance requirements, highly controlled brand language, frequent short-lived promotions, or a website where important messaging sits behind scripts, PDFs, or gated content, automation is more likely to misfire. I’m also cautious when a single Google Ads account spans multiple brands/locations/service lines with very different rules—automation can accidentally generalize what should stay segmented.

In these cases, you can still use automation, but you’ll want tighter governance: remove individual automated assets you don’t like, and consider opting out of specific automated asset types that create risk (rather than disabling everything across the board).

How to enable automated assets safely (my practical framework)

Step 1: Build strong manual assets first so automation complements (not replaces) quality

Before you lean on automated assets, give the system a high-quality “menu” to choose from. For sitelinks, that usually means having multiple, genuinely distinct destinations (pricing, services, locations, testimonials, booking, contact, etc.) and keeping them fresh. For callouts and structured snippets, it means coverage across your real differentiators (not filler like “Great service”).

This matters because when manual assets are thin or repetitive, automation tends to get blamed for poor output—when the real issue is that the account didn’t provide enough strong options in the first place.

Step 2: Review what Google created (and remove what you don’t want)

The system gives you visibility and control, but you have to use it. Automated assets and text customization can be reviewed through asset reporting, where you can filter by assets that were automatically created. If you see a dynamic sitelink, callout, or structured snippet you don’t like, you can typically pause it (to stop serving while keeping the option to re-enable) or remove it (to prevent it from serving again).

For account-level automated assets specifically, you can also turn off particular automated asset types from the account-level automated assets settings area. This “surgical” approach is usually the best balance: keep the automation that helps, disable the pieces that create risk.

Step 3: Treat it like an optimization test, not a belief system

Don’t decide based on ideology (“automation is good” or “automation is bad”). Decide based on results. Compare performance over a meaningful window (enough conversion volume to reduce noise), and watch not only conversion rate and CPA/ROAS, but also lead quality signals if you have them (qualified leads, booked calls that show, downstream revenue).

Also remember that the system can generate assets, then later stop serving them if they perform poorly or if the context changes (site edits, keyword shifts, ad edits). That’s helpful—but it’s not a substitute for a human keeping standards high.

Quick decision checklist: enable automated extensions if you can say “yes” to most of these

  • My landing pages are strong and specific (clear headings, clear offers, clean navigation, no outdated promos).
  • I already use manual assets that reflect what I actually want shown (not the bare minimum).
  • I can review asset reporting regularly and remove/pause anything inaccurate, off-brand, or risky.
  • My conversion tracking is trustworthy so I can evaluate impact without guesswork.
  • I’m comfortable with “predicted to improve performance” logic and understand automated assets may show alongside or instead of manual assets.

The expert recommendation (most advertisers): enable, monitor, and prune

In the majority of real-world accounts, enabling automated extensions (account-level automated assets) is worth it—as long as you commit to reviewing what’s created and removing what doesn’t meet your standards. If you want the benefits without the surprises, the winning approach is almost always the same: build excellent manual assets first, then let automation add incremental lift, and actively curate anything the system generates that you wouldn’t proudly claim as your own.