🚀 Executive Summary
TL;DR: Google Ads aggressively pushes ‘optimizations’ that often increase ad spend by broadening targeting and increasing bids, conflicting with advertisers’ ROAS goals. The solution involves disabling all ‘Auto-apply’ recommendations in the Google Ads interface and adopting a ‘DevOps Mindset’ where all campaign changes are deliberate, documented, and justified, effectively treating ad accounts like production infrastructure.
🎯 Key Takeaways
- Google Ads ‘Recommendations’ are primarily an AI-driven upsell mechanism designed to increase ad spend, not necessarily to optimize for your specific Return On Ad Spend (ROAS) goals.
- The most effective and permanent solution to prevent unwanted budget increases is to navigate to the ‘Recommendations’ tab, click ‘Auto-apply,’ and explicitly uncheck all recommendation categories.
- Adopting a ‘DevOps Mindset’ or ‘Campaigns as Code’ philosophy for Google Ads ensures all changes are deliberate, documented, and justified, providing an audit trail and making the platform’s ‘Optimization Score’ irrelevant in favor of actual ROI.
Tired of Google Ads constantly pushing unwanted ‘optimizations’ that drain your budget? Learn the root cause and discover three solid methods to regain control of your ad spend, from quick dismissals to a permanent, automated mindset.
Stop the Noise: How to Tame Google’s Aggressive Ad Recommendations
I remember a frantic Slack message from a junior marketer a while back. “Darian, the ad spend for the new SaaS trial campaign is through the roof!” I jumped on a call with him, and we dug in. Sure enough, the daily budget we’d carefully set was obliterated. The culprit? A single click. He’d seen a “95% Optimization Score” with a big friendly blue button from Google Ads suggesting he “Apply all” recommendations. One of those recommendations switched his bidding strategy to ‘Maximize Conversions’ without a target CPA, effectively giving Google a blank check. It felt like watching a deployment script go rogue on prod-db-01 because someone trusted the linter’s auto-fix a little too much. It’s a painful lesson, and it’s why I treat the Google Ads UI with the same caution I reserve for a rm -rf / command.
First, Why Is This Happening?
Let’s be clear: the Google Ads “Recommendations” engine isn’t your friend. It’s an incredibly sophisticated, AI-driven upsell mechanism. Its primary goal is to increase your ad spend. While it frames these suggestions as “optimizations,” many of them are blunt instruments designed to broaden your targeting, increase your bids, and automate decisions you should be making strategically. It’s not malicious, it’s just business. The platform’s goal (spend more) is often in direct conflict with your goal (achieve a higher ROAS). Recognizing this is the first step to taking back control.
The Fixes: From Band-Aid to Cauterization
You’ve got a few ways to tackle this, depending on how much time you have and how permanent you want the solution to be. Here’s my playbook.
1. The Quick Fix: Manual Whack-A-Mole
This is the fastest, but most temporary, solution. You go into the Recommendations tab and manually dismiss the suggestions you don’t want. You’ll see a list of cards, each with a suggestion.
- Find a recommendation you disagree with (e.g., “Add new keywords”).
- Click the three dots in the top-right corner of the card.
- Select “Dismiss all”.
- You’ll have to provide a reason. I usually just pick “Other reason” to move on quickly.
This is fine if you just need to clear the noise for a day, but they will come back. It’s a repetitive task that’s ripe for human error, just like manually patching servers one by one.
2. The Permanent Fix: Disable Auto-Apply
This is the real solution and the one I insist on for any account I manage. Google can, and will, automatically apply certain recommendations if you don’t explicitly tell it not to. You need to turn this off. Now.
- In your Google Ads account, navigate to the Recommendations tab.
- In the top right corner, find and click on Auto-apply.
- This takes you to a new page with two tabs: ‘Manage’ and ‘History’. Stay on ‘Manage’.
- You will see a long list of recommendation categories like “Bids & Budgets” and “Keywords & Targeting”. Go through every single one and uncheck the box.
- Don’t be fooled by the descriptions. Uncheck them all. When you’re done, click Save at the bottom.
Pro Tip: Google occasionally adds new auto-apply categories. Schedule a recurring calendar reminder for the first of every month to check that page and ensure nothing new has been opted-in on your behalf. Trust, but verify.
3. The ‘Nuclear’ Option: The DevOps Mindset
Even with auto-apply turned off, the UI will still pressure you to accept recommendations to boost that vanity “Optimization Score”. The ultimate fix isn’t in the UI, it’s in your process. Treat your ad account like you treat your production infrastructure: all changes must be deliberate, documented, and justified.
Instead of reactively clicking buttons in the UI, adopt a “Campaigns as Code” philosophy. When a change is needed, document it. Even a simple text file or a shared document is better than nothing. This creates an audit trail and forces you to think through the “why” of a change, rather than blindly trusting an algorithm.
Here’s what a simple, manual change log entry might look like. This is how we enforce discipline and prevent knee-jerk “optimizations.”
# === Google Ads Change Log: Q4-Enterprise-Campaign ===
# TICKET: MKTG-412
# AUTHOR: darian.vance
# DATE: 2023-11-15
#
# CHANGE:
# - Paused keyword: "free cloud credits"
#
# REASON:
# - Analysis of Search Query Report shows low conversion rate and
# high cost-per-lead. Attracting wrong audience segment.
# Google recommendation to "increase bid" for this keyword is
# explicitly REJECTED as it would amplify a failing strategy.
This approach shifts the power dynamic. You are no longer a passive user accepting suggestions. You are an architect making intentional decisions based on data. The “Optimization Score” becomes irrelevant; the only metric that matters is your actual return on investment.
👉 Read the original article on TechResolve.blog
☕ Support my work
If this article helped you, you can buy me a coffee:

Top comments (0)