If you have spent any time in r/PPC, you have seen this thread shape a hundred times: someone inherits a Search account, sees “recommendations” pushing broad match everywhere, and asks whether exact is dead. The honest answer after managing north of $350M in Google Ads spend is that neither label wins the argument. What wins is structure: matching query intent to how much signal your account actually has, then letting bidding do the job it is good at—without handing Google an open checkbook on weak data.
Google has spent years nudging advertisers toward broad match paired with Smart Bidding. That is not a conspiracy; it is product design. Broad match gives the auction more eligible queries, which increases liquidity for Google and, in theory, gives automated bidding more datapoints to optimize. The problem is that liquidity helps models, not necessarily your P&L, when conversions are sparse, delayed, or polluted.
Exact match in 2026 is not your 2012 exact match. Close variants still apply. Synonyms and reordering still slip through. Even so, exact remains your highest-leverage lever for intent control: you are telling the system, “I want to buy this cluster of meaning, not whatever the language model thinks is adjacent.” Broad match, conversely, is a discovery tool. It is excellent at finding high-intent phrases you did not think to spell out—when the account has the feedback loop to punish junk.
What changed in practical account work is the minimum viable signal for broad to be responsible. In lead gen with CRM offline import and a tight MQL definition, broad often outperforms my manual keyword maps within eight to fourteen days. In a low-volume B2B niche with a thirty-day sales cycle and “Maximize conversions” on thin fire, broad is how you fund Google’s retirement plan.
I treat match type as a risk budget decision. Broad match increases variance: more upside, more tail risk. Exact match reduces variance: you pay more per click on the winners you can name, but you stop paying for the long tail of “kinda related” searches that never convert on your site.
One more 2026-specific wrinkle: responsive search ads and asset-level reporting make it tempting to blame creative when performance drifts, but match type changes the query mix underlying those assets. I always pull a two-week search terms sample before and after any broad expansion. If impressions shift toward longer, informational tails while RSA combinations stay static, you are not running an ad test—you are running an auction participation test. That distinction matters when you report results to finance.
Broad match earns its seat at the table when four conditions line up. First, primary conversion action is trustworthy: enhanced conversions or offline import, not a thank-you page that fires on accidental submits. Second, volume: enough weekly conversions (or high-value micro-conversions) that the bid strategy exits the chaotic early phase. Third, negative keyword hygiene is treated as a product, not a quarterly cleanup. Fourth, audience layering is real: first-party lists, customer match where allowed, and in-market or custom segments that narrow the blast radius.
In e-commerce with solid item-level feed discipline and dynamic exclusion lists, broad plus Performance Max (where appropriate) routinely surfaces SKU-adjacent queries that exact would never enumerate. In local services with tight geo rings and call tracking at the keyword level, broad can fill the map faster than a human can brainstorm synonyms—especially for emergency intent (“burst pipe,” “24 hour,” neighborhood modifiers).
The r/PPC debates often miss this nuance: broad match is not “set and forget.” It is higher maintenance in the search terms UI and in negation architecture. If you are not willing to negate weekly during launch and biweekly at steady state, do not run broad at scale. You are not running a match type; you are running a mining operation.
Exact match is still the correct default when stakes are high and language is precise: regulated verticals, trademark-sensitive brands, high CPC slots where a single wayward click burns real money, and any account where conversion tracking is “good enough for reporting” but not good enough for automation. It is also how you defend branded terms and hero non-brand head terms from being cannibalized by catch-all ad groups.
Another under-discussed win for exact: clean experimentation. When you change creative, landing page, or promo, isolating a tight exact set makes lift attributable. Broad confounds the read because query mix shifts underneath you.
If your Search impression share is volatile and Learning Limited is a permanent badge, exact (and tighter geo schedules) stabilizes the feedback loop enough that Smart Bidding can actually finish a thought. I have seen accounts where simply shrinking broad eligibility dropped CPA 18-30% before any creative work, purely from stopping garbage queries that the algorithm was “optimizing” toward.
The structure I deploy most often is deliberately boring: separate campaigns or at least separate ad groups by intent tier, with budgets scaled to risk. Tier 1 is exact (and selective phrase) on proven converters. Tier 2 is broad in its own campaign with a lower budget cap, a mandatory negative list shared from Tier 1, and audience signals that reflect customers, not “everyone in the country who once visited a website about business.”
| Layer | Role | Typical match | Risk control |
|---|---|---|---|
| Core revenue | Capture known high-intent queries | Exact (+ phrase) | Tight negatives, single-keyword ad groups for heroes |
| Discovery | Find new queries & angles | Broad | Lower budget, audience signals, aggressive ST negation |
| Brand defense | Own navigational intent | Exact / brand controls | Separate PMax brand rules where applicable |
| Testing | LP and offer experiments | Exact first, then expand | Fixed budgets, calendar pauses, pre-registered success metrics |
Cross-negative everything that should not bleed: brand negatives in non-brand broad, competitor negatives per policy, and employment/informational patterns if you are paying for commercial intent only. The hybrid fails when broad is allowed to arbitrage exact’s winners without paying for the learnings in a bounded sandbox.
Match type shifts efficiency curves, not just CPCs. Broad often shows lower CPCs on paper and higher CPA in reality when query quality slips. Exact tends to raise CPCs on the queries you care about because you are stacking bidders on the same tight intent window. Neither is “cheaper”; they are different shapes of spend.
Below are illustrative U.S. Search CPC ranges I use as sanity checks when auditing accounts (not guarantees—vertical, brand mix, and geo dominate). Treat them as order-of-magnitude guardrails, not bids to paste into your account.
If broad match CPC looks “cheap” but conversion rate is half of exact, you are not saving money; you are buying lower-quality clicks in bulk. I always compare CPA and ROAS at the search terms level rolled up over two to four weeks, not keyword-level averages, which lie politely.
When this question pops up on r/PPC, the highest-voted comment is sometimes binary. In real accounts, the work is sequential. Here is the sequence I use:
Match types are not a religion. They are risk knobs. Broad match in 2026 is genuinely powerful when your house is in order. Exact match is still the spine of accountable Search. The practitioners I respect on threads like the one that inspired this piece are not arguing for tribal loyalty; they are arguing from different baselines. Start from your signal quality, then pick the knob—and measure like your job depends on it, because it does.