Google Ads Optimization Score: What To Apply, What To Skip

A 100% Optimization Score is not the goal. The score reflects how many of the recommendations Google surfaces you have accepted, not how well the account performs. Which to apply, which to dismiss, and why auto-apply stays off.

Last updated: October 9, 2026

In This Guide

  1. Executive Summary
  2. Benchmarks & Numbers at a Glance
  3. What It Measures
  4. Is 100% the Goal
  5. Recommendation Types
  6. Recommendations to Apply
  7. Recommendations to Dismiss
  8. Risks of Auto-Apply
  9. Score in Audits
  10. Broad Match & Budget Recs
  11. Common Mistakes to Avoid
  12. What Changed Recently
  13. References

1. Executive Summary: Five Key Principles

Google Ads Optimization Score is a 0–100% real-time diagnostic that measures how closely an account’s configuration aligns with Google’s current recommendations—not how profitable, efficient, or strategically sound the account is.[1] Senior marketers managing accounts in 2026 should operate by five non-negotiable principles.

  • Score is a prioritization signal, not a performance KPI. A 10-point Optimization Score increase correlates with a median +14% lift in conversions according to Google’s own vendor claim, but the correlation between score and ROAS across 17,380 global accounts is only r = 0.29, while the correlation between score and ad spend is r = 0.81.[2][3] Chasing score without validating business outcomes is a documented path to higher spend, not higher profit.
  • Fix measurement before touching anything else. Automated bidding, Smart Bidding targets, and most high-impact recommendations optimize toward the conversion signal you supply. Incorrect, incomplete, or unqualified conversion data makes every downstream recommendation unreliable regardless of its score impact.
  • Apply, test, or dismiss every recommendation deliberately. Apply low-risk measurement and policy repairs immediately. Test bidding, budget, match-type, and expansion recommendations against a control. Dismiss recommendations that conflict with intentional strategy, and record the business reason for each dismissal.
  • Keep auto-apply narrowly scoped. As of January 26, 2026, Google removed “Add responsive search ads” from auto-apply entirely.[4] That change illustrates how the auto-apply catalog shifts without notice. Enabling broad auto-apply transfers recurring strategic decisions to Google’s system and compounds changes before they can be reviewed.
  • A lower score can be the correct score. Nineteen percent of accounts in a study of 17,380 global accounts reached 90%+ Optimization Score without accepting Google’s recommendations—primarily by dismissing irrelevant ones.[2] A deliberate dismissal policy that reflects actual strategy is preferable to a high score achieved by accepting recommendations that increase spend or reduce targeting precision.

2. Benchmarks and Numbers at a Glance

Metric Typical range or threshold Applies when Source
Optimization Score scale 0–100% All active Google Ads accounts; vendor claim, not a study finding [1]
Accounts scoring below 70% 32% of sampled accounts Study of 17,380 global accounts; active ≥ 90 days; monthly spend $500–$1,000,000 [2]
Accounts reaching 90%+ without accepting recommendations 19% of sampled accounts Same 17,380-account study; achieved by dismissing irrelevant recommendations [2]
Accounts that accepted Google’s recommendations 5.5% of sampled accounts (fewer than 1,000 of 17,380) Same study; note: not identified specifically as auto-apply adoption [2]
Accounts scoring 90–100 after accepting recommendations 333 accounts Subset of the 17,380-account study [2]
ROAS difference: accounts scoring 90–100 vs. accounts scoring below 70 186% higher ROAS at 90–100 score band Same 17,380-account study; global sample; correlation, not causation [2]
Correlation between Optimization Score and ROAS r = 0.29 (weak positive) 17,380 accounts; six-month period; monthly spend $500–$1,000,000; global [5]
Correlation between Optimization Score and ad spend r = 0.81 (strong positive) Same 17,380-account study; higher score is strongly associated with higher spend [5]
ROAS relationship above 70% Optimization Score Essentially flat between 70% and 90% Same study; incremental ROAS gain from pushing score above 70% is minimal [5]
Median conversion lift after a 10-point score increase +14% conversions Vendor claim; Google internal data; sample size not disclosed; not a controlled study [3]
Additional conversions after switching phrase match to broad match (Target CPA campaigns) Approximately +25% Vendor claim; Google internal data from 2020; sample not disclosed; requires stable Smart Bidding [6]
Additional conversion value after switching phrase match to broad match (Target ROAS campaigns) Approximately +12% Vendor claim; Google internal data from 2020; sample not disclosed; requires stable Smart Bidding [6]
CTR correlation with Optimization Score No correlation detected 17,380-account study; score improvement does not predict CTR improvement [2]
CPA relationship with Optimization Score Higher scores (especially 80%+) correlated with improved CPA; no USD figure published Same study; directional finding only; no controlled CPA change figure available [2]

3. What Optimization Score Measures

Optimization Score is calculated in real time from four inputs: account and campaign statistics, current settings and status, the estimated impact of available recommendations, and the account’s recent history of applying or dismissing recommendations.[1] Each unresolved recommendation reduces the score by its estimated impact weighting. Applying or dismissing a recommendation resolves the gap—which is why score movement does not reliably indicate that performance improved.

The score reflects alignment with Google’s recommendation framework for the account’s selected advertising objectives—such as maximizing conversions or conversion value—not alignment with the advertiser’s actual business economics, margin structure, lead quality requirements, or incremental revenue goals.[1]

Google’s campaign goal is now displayed alongside the Optimization Score in the interface.[7] Goals are determined primarily by bidding strategy and can be set to conversions, conversion value, clicks, or impression share. This makes it critical to confirm that the campaign’s bidding goal matches the actual business objective before interpreting or acting on score data.

Score can move without any meaningful change in business performance. New recommendation types introduced by Google, campaign condition changes, and shifts in recommendation availability can all alter the score independent of advertiser action. Treat an unexplained score drop as a prompt to inspect the Recommendations page—not as evidence that the account degraded.

Worked example (illustrative)

Score Drop Caused by a New Recommendation Type, Not Performance Decline

  • Setup: A Chicago legal services account spending $18,000 per month on Search campaigns, currently holding a 78% Optimization Score with stable conversion volume of 42 qualified form fills per month at a $428 average CPA.
  • Numbers: Google introduces a new recommendation category—”Enable enhanced conversions for leads”—weighted at 8 score points for this account. The score falls from 78% to 70% (78 − 8 = 70) with no change in bids, budgets, keywords, or ads. Conversion volume remains 42 that month; CPA remains $428.
  • Decision: The account manager reviews the recommendation, confirms that enhanced conversions for leads is technically feasible and legally permissible under the firm’s privacy policy, and schedules implementation within 14 days. The dismissal queue is not used; the recommendation is resolved by applying it.
  • Why: The 8-point score drop was caused entirely by the arrival of a new recommendation, not by deteriorating performance—confirming that score movement must always be traced to a specific recommendation before any strategic response is taken.[1]

Worked example (illustrative)

Score at 91% Despite Weak ROAS—Why the Score Misleads Without Context

  • Setup: A national e-commerce account spending $55,000 per month on Shopping and Performance Max campaigns, reporting a 91% Optimization Score after accepting several Google recommendations over the prior 60 days.
  • Numbers: Platform-reported ROAS is 3.1x ($170,500 in reported conversion value ÷ $55,000 spend). However, post-purchase survey data and back-end order data show that 31% of reported conversions are duplicate-counted, reducing true ROAS to approximately 2.1x ($117,645 ÷ $55,000). The account’s minimum acceptable ROAS for profitability is 2.5x. The study of 17,380 accounts found only an r = 0.29 correlation between Optimization Score and ROAS.[5]
  • Decision: The account manager pauses further recommendation applications, audits the conversion setup to eliminate double-counting, and does not treat the 91% score as confirmation of account health.
  • Why: A high Optimization Score does not validate conversion measurement quality; the weak ROAS correlation means score cannot substitute for back-end revenue verification.[5]

4. Is 100% the Goal?

Google states that a 100% score means the account “can perform at its full potential,” but this is a vendor claim, not a verified performance guarantee.[1] The practical evidence is less encouraging. In the 17,380-account study, the correlation between Optimization Score and ROAS is only r = 0.29, and ROAS is essentially flat between 70% and 90% score bands.[5] The correlation between score and ad spend is r = 0.81—meaning that the surest outcome of a higher score is higher spend, not higher profit.[5]

A 100% score is achievable in two very different ways: by applying all recommendations Google offers, or by dismissing every recommendation that does not apply to the account’s strategy. Nineteen percent of accounts in the same study reached 90%+ without accepting recommendations.[2] This proves that dismissal is a legitimate and score-effective strategy, not a workaround.

The appropriate target score depends on account maturity, strategy, and risk tolerance. A score above 70% is a reasonable operational baseline—the study data suggest meaningful ROAS improvements are concentrated below 70%, while incremental gains above 70% are marginal.[5] A score below 70% warrants a systematic review of what recommendations are outstanding and why. A score above 90% achieved by accepting recommendations that broadened targeting, increased budgets, or switched bidding strategies should be validated against CPA, ROAS, conversion quality, and profit—not accepted as proof of success.

Worked example (illustrative)

Deliberate Dismissal Strategy Reaches 92% Without Accepting Budget or Broad Match Recommendations

  • Setup: A Seattle B2B software account spending $22,000 per month on Search, starting at a 61% Optimization Score with 7 active recommendations: 2 measurement fixes, 1 broken ad destination, 1 sitelink asset addition, 1 broad match expansion, 1 budget increase, and 1 Target CPA change.
  • Numbers: The 3 low-risk recommendations (measurement fixes + broken destination) are applied, contributing an estimated +14 score points. The sitelink asset is reviewed, confirmed accurate, and applied for an estimated +8 points. The broad match recommendation (+9 points estimated), budget increase (+6 points estimated), and Target CPA change (+4 points estimated) are each dismissed with documented business reasons. Score movement: 61 + 14 + 8 = 83% after applying; then the 3 dismissals resolve the remaining gaps: 83 + 9 = 92% after dismissals. Final score: 92%.
  • Decision: Dismiss broad match (account uses exact and phrase match to control B2B lead quality), dismiss budget increase (monthly budget is set at $22,000 based on Q3 2026 pipeline capacity, not Search impression share), and dismiss Target CPA change (current $210 target is validated against a $1,800 customer lifetime value; Google’s suggested $185 target lacks sufficient conversion history justification).
  • Why: Dismissing a recommendation resolves it from the score calculation just as applying it does, so a deliberate dismissal policy can reach 90%+ without accepting recommendations that conflict with strategy.[2]

Done for you

Everything on this page, done for you before you launch

We build the campaign properly the first time — so you are not unpicking it three months from now.

✓  Keywords validated against real search volume, grouped by intent

✓  Responsive search ads written to the asset counts that actually perform

✓  A negative keyword list built before you spend, not after

✓  Delivered in 24 hours as a spreadsheet you keep

See what you get — $129

Human-reviewed · No subscription · We never touch your Google Ads account

5. Recommendation Types Explained

Google organizes recommendations into six broad categories, each of which can affect score by a different weighted amount depending on account conditions.[8] The categories are: Bidding and budgets, Keywords and targeting, Ads and assets, Conversions and measurement, Campaign setup and maintenance, and Automation and audience (including Customer Match, broad match with brand inclusions, and app-related actions).[8]

Recommendation availability is account-specific and changes dynamically as Google’s best practices evolve. The Auto-apply settings page should be treated as the current source of truth rather than any static external checklist.[4] The estimated score impact of each recommendation is displayed in the interface; Google states this is the mechanism by which score uplift is communicated, though per-type benchmark values are not publicly reported as standardized figures.[2]

For bidding recommendations, Google may suggest a Target ROAS based on recent actual ROAS (excluding conversion-delay-affected data) or a Target CPA based on the previous 30 days adjusted for conversion delays.[9] These suggested targets are starting points for evaluation, not commercially validated figures. A suggested CPA based on 30 days of data may reflect a period with atypical seasonality, a landing-page test, or a tracking anomaly.

A specific newer recommendation type combines broad match keywords with brand inclusions, restricting broad-match coverage to specified brands or related products and services.[8] This is a more constrained version of standard broad match and may be appropriate in cases where standard broad match would be dismissed.

Worked example (illustrative)

Evaluating a Suggested Target CPA Before Accepting a Bidding Recommendation

  • Setup: A Phoenix home security account spending $9,500 per month on Search, running Maximize Conversions bidding with 38 conversions (qualified appointment bookings) in the trailing 30 days. Google surfaces a recommendation to switch to Target CPA and suggests a target of $245.
  • Numbers: Trailing 30-day actual CPA: $9,500 ÷ 38 = $250. Google’s suggested target of $245 is 2% below the current actual CPA. The account’s maximum allowable CPA based on a $1,100 average customer value and a 22% gross margin is $242 ($1,100 × 0.22 = $242). The suggested $245 target is $3 above the break-even threshold. The 30-day window includes a July 4, 2026 promotional week that drove 11 of the 38 conversions at a $180 CPA, skewing the period average downward.[9]
  • Decision: Do not accept the $245 suggested target. Set a manual Target CPA of $235—5% below the $242 break-even—to provide a margin buffer, then use a Google Ads experiment to compare $235 tCPA against the current Maximize Conversions setting over a 28-day period starting August 4, 2026.
  • Why: Google’s suggested CPA target is based on recent data that includes a promotional period, making it unrepresentative of steady-state economics; the threshold rule is that no tCPA target should exceed the margin-adjusted maximum allowable CPA.[9]

6. Recommendations to Apply

Not all recommendations carry equal risk. The following categories are generally safe to apply after a brief human review because they repair operational defects, improve measurement fidelity, or add incremental value without altering strategic targeting or spend levels.

Measurement and tracking repairs are the highest-priority category. Conversion tag fixes, enhanced conversions setup, consent-mode adjustments, offline conversion imports, and attribution corrections should be resolved before any other recommendation is evaluated. Every bidding and budget recommendation downstream depends on the accuracy of this data.

Policy and serving repairs—disapproved ads, broken destination URLs, billing issues, and suspended assets—are operational defects, not optional optimization ideas. These reduce serving efficiency and are always worth fixing immediately.

Ad assets—sitelinks, callouts, structured snippets, image assets, price extensions, and promotion extensions—add inventory for Google’s auction-time serving system and are generally low-risk, provided the copy is accurate, commercially appropriate, and consistent with the landing page. Verify that each asset reflects current pricing, availability, and claims before applying.

Ad-quality improvements such as adding higher-rated responsive search ad headlines and descriptions can be applied when the suggested copy preserves brand voice, legal claims, and intended positioning. Do not apply AI-generated copy automatically; read every suggested asset before accepting.

Technical cleanup such as resolving conflicting negative keywords, enabling auto-tagging, and fixing duplicate conversion actions are low-risk when the change does not remove intentional segmentation or historical data continuity.

Worked example (illustrative)

Applying a Measurement Fix Before Acting on Any Other Recommendation

  • Setup: A Dallas dental group account spending $7,200 per month on Search, reporting 54 conversions per month (phone calls + form fills). Google surfaces 4 recommendations: (1) fix a broken conversion tag on the appointment form (+6 score points estimated), (2) switch to Target CPA at $133 (+11 points), (3) add 3 broad-match keywords (+7 points), (4) increase daily budget from $240 to $310 (+5 points).
  • Numbers: After auditing the conversion tag, the account manager finds the appointment form tag fires on page load rather than on form submission, inflating reported conversions by an estimated 40%. True monthly conversions are approximately 54 × 0.60 = 32. True CPA is $7,200 ÷ 32 = $225—not the platform-reported $133 that Google used to suggest the tCPA target. Fixing the tag and waiting 30 days for restated data changes the accurate conversion baseline before any bidding change is made.
  • Decision: Apply recommendation 1 (fix the broken tag) immediately. Dismiss recommendations 2, 3, and 4 for 30 days pending restated conversion data. Set a calendar reminder for November 10, 2026 to re-evaluate.
  • Why: Google’s tCPA suggestion of $133 is based on inflated conversion data; applying it before fixing measurement would instruct Smart Bidding to pursue a target 41% below the true CPA, causing the campaign to restrict delivery and lose profitable volume.[1]

Worked example (illustrative)

Applying Asset Recommendations After Manual Copy Review

  • Setup: A Boston personal injury law firm account spending $31,000 per month on Search. Google surfaces a recommendation to add 4 new sitelink assets generated by Google AI, estimated to improve score by 5 points. The suggested sitelinks include “Free Case Review,” “No Win No Fee,” “Millions Recovered,” and “24/7 Legal Help.”
  • Numbers: The firm’s current sitelink CTR is 12.4% across existing 6 sitelinks. Adding 4 more sitelinks is low-risk from a spend perspective (assets do not increase CPC directly). However, “Millions Recovered” requires verification against Bar Association advertising rules in Massachusetts (205 CMR 4.00 et seq.) before use, and “No Win No Fee” must match the exact contingency fee language in the firm’s retainer agreement.
  • Decision: Apply “Free Case Review” and “24/7 Legal Help” immediately after confirming accuracy. Submit “Millions Recovered” and “No Win No Fee” to the firm’s compliance team for review by October 24, 2026 before applying.
  • Why: Ad asset recommendations are low-risk from a bidding and budget perspective but require human copy review for regulated industries; applying legally inaccurate assets creates compliance exposure that outweighs the 5-point score gain.[1]

Not ready to change anything today?

We post the sharpest bits of these guides — what a change is worth, how long it takes to show up, and when to leave it alone. Short enough to read on your phone.

Follow on LinkedIn Follow on Instagram

7. Recommendations to Dismiss

Dismissing a recommendation is not a failure—it is a legitimate governance action that resolves the recommendation from the score calculation just as applying it does.[1] The key discipline is to dismiss deliberately, with a documented business reason, rather than leaving recommendations unresolved or dismissing them reflexively without evaluation.

The following recommendation types most commonly warrant dismissal in well-managed accounts:

  • Budget increases that exceed profitability limits, approved monthly spend, or cash-flow capacity. A “limited by budget” label is a delivery diagnosis, not a profit guarantee.
  • Bid-target changes based on insufficient conversion history, a skewed measurement window, or a suggested target that exceeds the margin-adjusted maximum allowable CPA or minimum acceptable ROAS.
  • Broad match or audience expansion that would dilute a deliberately narrow, high-intent funnel—particularly in regulated industries, luxury categories, B2B accounts with long sales cycles, or accounts where offline lead qualification reveals significant quality variation.
  • Keyword additions that introduce competitor terms, low-intent informational queries, or irrelevant product categories.
  • Automatically generated ad copy that alters pricing claims, legal language, tone, promotional terms, or brand positioning without human review.
  • Campaign-type upgrades—such as recommendations to move a Standard Shopping campaign to Performance Max—where the advertiser cannot isolate, audit, or qualify the resulting traffic mix.
  • Removal of keywords, ads, or structures retained intentionally for testing, regional segmentation, brand protection, or historical reporting continuity.

When dismissing, use Google’s account-level or campaign-level dismissal controls and record the reason, owner, and review date in an external log or using campaign labels. This creates an audit trail and prevents the same recommendation from being applied inadvertently by another team member.

Worked example (illustrative)

Dismissing a Keyword Addition That Introduces Low-Intent Traffic

  • Setup: A Miami luxury yacht charter account spending $14,500 per month on Search, running exact and phrase match keywords averaging $18.40 CPC and a $420 cost per qualified lead. Google surfaces a recommendation to add 12 new broad-match keywords including “boat rental Miami,” “pontoon boat rental,” and “fishing charter,” estimated to increase score by 9 points and projected to generate 38 additional conversions per month.
  • Numbers: The account’s offline CRM data shows that leads originating from “boat rental” and “pontoon” query themes have a 1.2% close rate versus an 8.7% close rate for current exact-match yacht-specific queries. At a $420 cost per lead and 38 additional projected leads, projected additional spend is $15,960 per month (38 × $420). At a 1.2% close rate, projected additional closed bookings: 38 × 0.012 = 0.46 per month—approximately 1 booking every 2 months. Average charter booking value: $8,500. Revenue per dollar spent at 1.2% close rate: ($8,500 × 0.46) ÷ $15,960 = $0.25 per dollar—well below the account’s 1.8x minimum revenue-per-spend threshold.
  • Decision: Dismiss all 12 keyword additions. Document the reason: “Query themes inconsistent with luxury charter buyer intent; projected close rate 1.2% vs. 8.7% for current keyword set; economics fail the $1.80/$1.00 revenue-per-spend threshold.” Set a review date of April 1, 2027 to reassess if offline data changes.
  • Why: Platform-projected conversion volume does not account for offline lead quality; the dismissal preserves a funnel where every dollar of spend is directed at high-intent, closeable traffic.[1]

8. The Risks of Auto-Apply

Auto-apply is not inherently unsafe, but enabling it broadly transfers recurring strategic decisions to Google’s system and creates compounded changes that can be difficult to diagnose or reverse.[4] The most significant structural risk is that multiple automatic changes can accumulate before a weekly review cycle catches them, making it impossible to attribute a performance shift to a specific change.

The risks most frequently realized in practice include:

  • Spend escalation from reach-expanding recommendations. Auto-apply does not directly increase campaign budgets, but recommendations that broaden match types, add keywords, or expand audiences can increase impression volume and total spend within the existing daily budget.[4]
  • Bad optimization signals scaled by automation. If form fills, call conversions, or imported conversions are not properly qualified, auto-applied bidding changes will optimize and scale low-quality leads.
  • Brand and compliance exposure. Automatically created or modified ads may require legal, compliance, or brand-team review before serving—review that auto-apply bypasses.
  • Loss of strategic segmentation. Auto-applied broad match, audience expansion, or campaign-structure changes can dissolve carefully designed segmentation that took months to build.
  • False confidence from a rising score. A higher score after auto-apply activity reflects adoption of Google’s recommendations, not verified improvement in profit, lead quality, or incremental revenue.[2]

The clearest recent example of auto-apply risk is structural: from January 26, 2026, Google removed the “Add responsive search ads” recommendation from Auto-apply entirely.[4] Advertisers who had relied on this feature to maintain ad coverage discovered the change only when new ad creation stopped. This illustrates that the auto-apply catalog changes without advance notice, and governance policies built on a static assumption about available categories will drift.

Recommended auto-apply policy for 2026: Keep auto-apply off by default for budgets, bids, keywords, match types, targeting, audience expansion, and measurement settings. Consider enabling narrowly scoped categories—such as fixing disapproved ads or broken destinations—only after confirming their scope in a test account or reviewing recent auto-apply history for the specific category. Review Auto-apply History and Change history at least weekly for any account with auto-apply enabled.

Worked example (illustrative)

Diagnosing a CPA Spike Caused by Compounded Auto-Apply Changes

  • Setup: A Minneapolis home services account spending $12,000 per month on Search with auto-apply enabled for bidding, keywords, and ad assets. The account manager reviews performance on November 3, 2026, and finds that CPA has risen from $87 to $134 over the prior 21 days—a 54% increase. Conversion volume fell from 138 per month (annualized pace) to 90 (current 21-day pace × 1.43 = 129, but daily pacing is declining).
  • Numbers: Auto-apply History shows 3 changes in the prior 21 days: (1) October 13—Target CPA changed from $87 to $104 (Google’s suggested target based on a 30-day window that included a Labor Day 2026 promotional period); (2) October 17—14 new broad-match keywords added; (3) October 21—2 new AI-generated responsive search ad headlines applied. Change history confirms all 3 changes occurred automatically. Search terms report shows 34% of impressions in the past 14 days match non-service queries (e.g., “home improvement ideas,” “DIY HVAC repair”) introduced by the broad-match keyword expansion.
  • Decision: Pause the 14 auto-applied broad-match keywords immediately. Revert Target CPA to $87. Remove the 2 AI-generated headlines and restore prior ad assets. Disable auto-apply for bidding, keywords, and ad assets. Schedule a 14-day monitoring period starting November 3, 2026 before making further changes.
  • Why: Three compounded auto-apply changes within 8 days made causality impossible to isolate in real time; disabling auto-apply for strategic categories is the only way to maintain change control at this account’s $12,000/month spend level.[4]

“So what do I actually have to hand over?”

Nothing. No access to your Google Ads account, no login, no agency link request. You tell us the business and the offer; we send back a spreadsheet.

You import it yourself, or hand it to whoever runs the account. It is yours to keep and re-use — there is no ongoing fee and nothing to cancel.

How it works — $129

9. Using Score in Audits and Across Accounts

At the individual account level, Optimization Score functions as a recommendation workflow metric: it shows which recommendations are outstanding and how much score each represents. At the portfolio or manager-account level, it functions as a triage tool for identifying accounts with significant unresolved opportunities—but only when scores are aggregated correctly.

Google’s API documentation specifies that a multi-account aggregate score should use each customer’s optimization score weight, not a simple average.[10] The correct formula is:

Portfolio score = Σ(customer score × score weight) ÷ Σ(score weight)

Averaging raw percentages equally across accounts of different sizes, spend levels, and campaign counts produces a misleading portfolio figure. A $500/month account with a 95% score and a $500,000/month account with a 62% score should not be averaged to 78.5%—the larger account’s recommendations carry far more dollar impact.

Audit framework for individual accounts:

  • Export account and campaign scores, all active recommendations with estimated score uplift, auto-apply subscriptions, Change history for the prior 90 days, and current conversion tracking status.
  • Classify each recommendation by type: measurement, policy, creative, bidding, budget, targeting, or expansion.
  • Rank by expected business impact—not score impact—combining estimated uplift with spend concentration, conversion volume, CPA/ROAS relative to target, and recommendation reversibility.
  • Fix measurement defects before evaluating any other recommendation.
  • Document every dismissal with a reason, owner, and review date.
  • After applying material changes, monitor conversion quality, search-term mix, CPA/ROAS, and impression share for a minimum of 14–28 days before drawing conclusions.

Worked example (illustrative)

Weighted Portfolio Score Calculation Across a Five-Account Agency Portfolio

  • Setup: An agency manages 5 Google Ads accounts with the following October 2026 scores and score weights (as returned by the Google Ads API).
  • Numbers: Account A: score 88%, weight 0.41. Account B: score 62%, weight 0.28. Account C: score 79%, weight 0.15. Account D: score 91%, weight 0.09. Account E: score 55%, weight 0.07. Simple average: (88 + 62 + 79 + 91 + 55) ÷ 5 = 75%. Weighted calculation: (88 × 0.41) + (62 × 0.28) + (79 × 0.15) + (91 × 0.09) + (55 × 0.07) = 36.08 + 17.36 + 11.85 + 8.19 + 3.85 = 77.33%. The 2.33-point difference is small here, but in a portfolio where a high-spend account has a very low score, the gap widens materially. More importantly, Account B (62%, weight 0.28) and Account E (55%, weight 0.07) are the correct triage priorities—not the accounts with the highest raw scores.
  • Decision: Direct the next audit cycle to Account B first (lowest weighted score among high-weight accounts), then Account E. Pull the full recommendation list for both accounts and classify recommendations before the October 28, 2026 client review.
  • Why: The Google Ads API exposes score and score-weight fields specifically to enable weighted aggregation; using a simple average misrepresents where unresolved recommendation opportunity is concentrated in the portfolio.[10]

10. Broad Match and Budget Recommendations

Broad match and budget recommendations are the two categories most likely to increase spend without a proportional increase in qualified conversions. They are also the two most frequently surfaced recommendation types in accounts with significant unresolved opportunities. Treating them with the same workflow as measurement or asset recommendations is one of the most common and costly errors in Google Ads account management.

Broad Match

Google’s vendor claim is that switching from phrase match to broad match in Target CPA campaigns generates approximately 25% more conversions, and in Target ROAS campaigns approximately 12% more conversion value.[6] Both figures are from 2020 internal data with undisclosed sample sizes and should be treated as directional, not as applicable benchmarks for any specific account.

Broad match is appropriate when conversion tracking is accurate, Smart Bidding is stable with meaningful conversion history, search-term quality is monitored at least weekly, negatives and exclusions are well maintained, and the business can tolerate exploratory traffic while performance is judged on valuable conversions.[1] It is not appropriate when lead quality varies substantially, offline qualification data is absent, queries must be tightly controlled, or the recommendation would replace proven exact-match coverage without a controlled experiment.

A 2026 recommendation variant combines broad match with brand inclusions, restricting matching to specified brands or related products and services.[8] This constrained version may be testable in cases where standard broad match would be dismissed.

Budget Recommendations

A “campaign limited by budget” flag means additional eligible impressions exist above the current daily budget ceiling. It does not prove that additional impressions will convert at the current CPA or ROAS.[1] Increase budget only when the campaign is meeting its CPA or ROAS target, incremental conversions are likely to be valuable, and Search impression share and lost-to-budget data support expansion at the margin.

Auto-apply does not increase campaign budgets directly, but the broader recommendation ecosystem can increase traffic and spend through other changes.[4] Budget decisions require explicit human authorization at every increment.

Worked example (illustrative)

Testing Broad Match in an Isolated Experiment Before Full Rollout

  • Setup: A San Diego HVAC account spending $8,400 per month on Search, running Target CPA at $95 with 88 conversions per month (booked service calls) from exact and phrase-match keywords. Google surfaces a broad-match recommendation estimated to increase conversions by approximately 25%[6] and score by 11 points. The account has 14 months of stable conversion history and a verified call-tracking integration.
  • Numbers: Google’s vendor claim of +25% would project 88 × 1.25 = 110 conversions per month. At the current $95 tCPA and 110 conversions, projected spend would rise to $10,450 per month (110 × $95)—an increase of $2,050 from the current $8,400. The account’s maximum allowable monthly budget for Q4 2026 is $11,000. A 50/50 Google Ads experiment is set up: the control arm retains exact and phrase match; the test arm adds broad match to the same keywords. Each arm receives 50% of traffic, implying approximately $4,200 per arm per month.
  • Decision: Run the experiment from November 1–28, 2026 (28 days). Success criterion: test arm CPA ≤ $105 (10% above current $95 target) with ≥ 35 conversions in the arm (sufficient for 90% statistical confidence at this volume). If both criteria are met, roll broad match to 100% of traffic on December 1, 2026. If not, dismiss the broad-match recommendation and log the result.
  • Why: Google’s +25% conversion claim is a vendor claim from 2020 internal data with no disclosed sample size; a controlled experiment is the only way to validate whether the lift applies to this specific account and market at the current cost-per-acquisition threshold.[6]

Worked example (illustrative)

Evaluating a Budget Increase Recommendation Against Marginal CPA Data

  • Setup: A Portland e-commerce account spending $5,000 per month on a Search campaign for premium outdoor gear, running Target ROAS at 4.0x. The campaign is flagged as “limited by budget” and Google recommends increasing the daily budget from $166 to $230 (an increase of $64/day, or approximately $1,920/month, to a new monthly total of $6,920).
  • Numbers: Current month performance: $5,000 spend, $20,400 reported conversion value, ROAS = 4.08x. Search Impression Share: 61%. Search Lost IS (budget): 18%. The campaign is genuinely constrained. However, the account manager pulls the Search terms report filtered to the past 30 days and finds that 22% of converting queries are branded terms (own brand) and 11% are competitor brand terms. Removing branded and competitor queries, non-brand ROAS is approximately 3.1x—below the 4.0x target. Incremental spend is more likely to fund competitive and mixed-intent queries than high-intent non-brand queries.
  • Decision: Do not accept the budget recommendation. Instead, add 14 competitor brand terms as negative exact-match keywords, and add the own brand terms to a separate brand campaign with an uncapped budget. Recheck non-brand ROAS after 21 days (by November 18, 2026). If non-brand ROAS rises to ≥ 3.8x, consider a $500/month budget increase as the next incremental step.
  • Why: “Limited by budget” identifies a delivery constraint, not a profitability opportunity; the marginal ROAS of incremental spend must be evaluated against the target before authorization, not assumed from the campaign’s blended headline ROAS.[1]

11. Common Mistakes to Avoid

The following errors recur across accounts at all spend levels. Each one is observable in the Recommendations page, Change history, or downstream performance data and can be corrected with a clear process.

  • Treating score as a performance KPI in client reports. The correlation between score and ROAS is r = 0.29; the correlation between score and spend is r = 0.81.[5] Reporting score alongside CPA, ROAS, and conversion volume without this context implies a relationship that the data does not support.
  • Applying bidding recommendations before validating conversion data. A tCPA or tROAS recommendation is only as reliable as the conversion signal Google used to generate it. Apply measurement fixes first; apply bidding changes after.
  • Accepting broad match without a negative keyword foundation. Broad match without robust negatives, location settings, and audience layering produces exploratory traffic that raises spend and dilutes conversion quality, particularly in B2B, regulated, or high-CPC verticals.
  • Enabling all auto-apply categories at account setup. The auto-apply catalog changes without advance notice—as demonstrated by the removal of RSA auto-creation on January 26, 2026.[4] A broad auto-apply subscription will eventually include categories that conflict with account strategy.
  • Dismissing recommendations without logging the reason. An undocumented dismissal looks identical to an oversight in an audit. Log every dismissal with a reason, owner, and review date.
  • Using simple score averages across a portfolio. Equal-weight averaging ignores spend concentration. Use the API’s score-weight field for accurate portfolio aggregation.[10]
  • Evaluating bidding changes during the learning period alone. Smart Bidding learning periods typically last 1–2 weeks depending on conversion volume. CPA and ROAS during this period are not representative of steady-state performance.
  • Accepting Target CPA or ROAS suggestions without checking the measurement window. Google’s suggested targets are based on the prior 30 days, which may include promotional periods, seasonal spikes, landing-page tests, or tracking anomalies that make the period unrepresentative.[9]
  • Ignoring the campaign goal displayed next to the score. A score of 90% against a “Clicks” goal means the account is well configured to maximize clicks—not conversions or revenue. Verify that the displayed goal matches the business objective before pursuing score improvement.[7]

Worked example (illustrative)

Catching a Goal Mismatch Before Acting on a High Score

  • Setup: A Sacramento financial advisory account spending $16,000 per month on Search, displaying an 84% Optimization Score in the interface. The account manager is preparing a quarterly review for October 2026 and notes that Google’s recommended next action is to “increase budget to capture more clicks.”
  • Numbers: The campaign goal displayed next to the score is “Clicks”—the campaign is running Enhanced CPC, which Google maps to a clicks-oriented objective. The account’s actual KPI is qualified consultation bookings (a form fill + a 15-minute phone screen). In the trailing 90 days: 1,840 clicks, 29 form fills (1.58% conversion rate), 11 qualified bookings after phone screen (37.9% qualification rate), $16,000 ÷ 11 = $1,454 cost per qualified booking. The account’s maximum allowable cost per qualified booking is $900 (based on a $4,500 average first-year AUM fee and a 20% gross margin).
  • Decision: Do not act on any Optimization Score recommendations until the campaign goal is corrected. Switch the campaign to Target CPA bidding with a $900 tCPA target, designate the qualified booking (offline import) as the primary conversion action, and reclassify the form fill as a secondary conversion. After 30 days of restated data, re-evaluate all recommendations against the new goal.
  • Why: An 84% score against a clicks goal is irrelevant when the business objective is cost-per-qualified-booking; acting on score recommendations before correcting the goal will optimize for the wrong outcome.[7]

12. What Changed Recently (Last 30 Days)

As of October 2026, the most material documented change to Optimization Score and recommendations is the removal of “Add responsive search ads” from the Auto-apply settings page, effective January 26, 2026.[4] This change means that Google no longer automatically generates or applies new RSAs through auto-apply. Advertisers who relied on this feature for ad coverage, asset variety, and ad strength improvement must now manage RSA creation manually or through third-party tools.

The practical impact is twofold: first, accounts that had auto-apply enabled for RSA creation may now have static ad inventory that is not keeping pace with asset testing and coverage requirements. Second, the change illustrates the broader governance risk of relying on a static auto-apply configuration—the available recommendation types can change at any time, and a subscription list built in Q3 2025 may no longer reflect what is actually being applied in Q4 2026.

Beyond the RSA change, Google’s current guidance confirms several operational characteristics that practitioners should treat as standing policy rather than new developments:

  • Auto-apply operates at the account level, not the campaign level, and applies only when a recommendation is considered relevant by Google’s system.[4]
  • Auto-apply does not increase campaign budgets.[4]
  • The available recommendation types continue to expand dynamically; the Auto-apply settings page is the authoritative source of what is currently available and enabled.[4][8]
  • Google may suggest Target ROAS or Target CPA values after a new bid strategy is created or a recommendation is applied; these are starting points based on recent account data and conversion-delay adjustments, not commercially validated targets.[9]
  • The campaign goal is now displayed alongside the Optimization Score in the interface, making it more straightforward to detect goal mismatches before acting on recommendations.[7]

Recommendation categories currently documented by Google include: bidding and budgets, keywords and targeting (including broad match with brand inclusions), ads and assets, conversions and measurement, campaign setup and maintenance, and automation-related actions including Customer Match list refresh and Firebase app conversion actions.[8] Availability of any specific category remains account-specific.

Worked example (illustrative)

Auditing Auto-Apply Settings After the RSA Removal Change

  • Setup: An agency managing 12 Google Ads accounts across retail and home services verticals. Prior to January 26, 2026, 8 of the 12 accounts had “Add responsive search ads” enabled in auto-apply. The agency discovers in an October 2026 audit that these accounts have not had new RSAs created automatically since January 26, 2026—a gap of approximately 9 months.
  • Numbers: Across the 8 affected accounts, the average number of ad groups per account is 14 (112 ad groups total). Google’s ad strength guidelines recommend at least 1 RSA per ad group with “Good” or “Excellent” ad strength. A manual audit of ad strength ratings shows: 41 ad groups rated “Excellent,” 38 rated “Good,” 21 rated “Average,” and 12 rated “Poor.” The 33 ad groups rated Average or Poor represent 29% of total ad groups and are the priority for RSA review.
  • Decision: Build a 6-week RSA improvement schedule starting October 28, 2026: weeks 1–2 address the 12 “Poor” ad groups (2 new RSA headlines and 1 new description per ad group); weeks 3–4 address 10 of the 21 “Average” ad groups; weeks 5–6 address the remaining 11 “Average” ad groups. Set a recurring monthly calendar task to audit ad strength across all 12 accounts, replacing the auto-apply dependency that lapsed in January 2026.[4]
  • Why: The removal of RSA auto-creation from auto-apply on January 26, 2026 created a 9-month gap in ad asset maintenance across 8 accounts; the audit quantifies the backlog (33 ad groups requiring attention) and converts it into a specific remediation timeline with concrete weekly output targets.[4]

References

  1. [1] https://support.google.com/google-ads/answer/9061546?hl=en-GB support.google.com
  2. [2] https://www.optmyzr.com/blog/does-optimization-score-affect-google-ads-performance/ www.optmyzr.com
  3. [3] https://ads.google.com/intl/ky_us/home/tools/recommendations/ ads.google.com
  4. [4] https://support.google.com/google-ads/answer/10279006?hl=en support.google.com
  5. [5] https://observix.ai/blog/google-optimization-score-guide observix.ai
  6. [6] https://support.google.com/google-ads/answer/10195720?hl=en support.google.com
  7. [7] https://support.google.com/google-ads/announcements/9048695?hl=en-GB support.google.com
  8. [8] https://support.google.com/google-ads/answer/3416396?hl=en-GB support.google.com
  9. [9] https://support.google.com/google-ads/faq/10286469?hl=en support.google.com
  10. [10] https://developers.google.com/google-ads/api/docs/recommendations developers.google.com
Share the Post:

Related Posts