Why your Google Ads Search campaign is spending on the Display Network
Updated June 15, 2026
Google Search campaigns can serve ads on the Display Network through Display Expansion, which is on by default and spends "unspent Search budget" across YouTube, Gmail, and partner sites. Those impressions are cheap, plentiful, and usually low-intent: in one real campaign, Display was 59% of impressions (42,622) at $337 and zero conversions over 30 days. Negative keywords don't help — it's a serving-surface problem, not a query one. The fix is the Networks setting: uncheck Display Network so the campaign runs search-only.
A real incident: 59% of impressions, zero conversions
A B2B search campaign — the same DB Access Control campaign behind the 68%-hidden search-terms analysis — was quietly serving more than half its impressions somewhere it was never meant to. Over 30 days the Display Network accounted for 59% of the campaign's impressions: 42,622 of them, $337 spent, zero conversions. It is a "search" campaign. The console rolled Display and Search into one campaign total, so nothing flagged it.
How a Search campaign ends up on the Display Network
Google runs two networks. The Search Network is "Google search results pages, other Google sites like Maps and Shopping, and search sites that partner with Google to show ads." The Display Network is "Google sites like YouTube, Blogger, and Gmail, plus thousands of partnering websites across the Internet." Search ads answer intent; Display ads interrupt it.
A Search campaign can serve on both, and by default it does: "By default, new ad campaigns are set up to show ads across the entire network." The setting is Display Expansion on Search campaigns, which "can help you get additional conversions on the Google Display Network using unspent Search budgets." It is on unless someone turned it off — the classic Search-campaign leak.
Why it racks up impressions, not dollars
Display inventory is cheap and effectively unlimited, so the leak shows up as a flood of impressions long before it shows up as money. This campaign's weekly Display impressions tell the story:
2,648 → 39,974 → 0
Week two served 39,974 Display impressions for a few hundred dollars — pennies per thousand, and no intent behind any of them. Someone watching a YouTube video is not searching for database access control. Google's own framing gives it away: Display Expansion spends "unspent Search budget," so it is built to find somewhere to put the money the Search auction did not absorb. On a niche B2B campaign, that somewhere is a long tail of irrelevant placements.
What works — and what doesn't
This is a serving-surface problem, not a query problem, so negative keywords won't touch it. Negatives filter which searches match; Display impressions are not searches. The fix is the network setting itself:
- Audit the Networks setting on every Search campaign. Default is everything on. Expand the "Networks" section; if "Display Network" is checked, the leak is live.
- Set Search campaigns to search-only. Uncheck the Display Network option. It applies per campaign, since there is no account-wide switch.
- Watch impressions, not just spend. Cheap clicks mean a Display leak hides in the spend column but screams in the impression column. A B2B search campaign serving 40,000 impressions in a week is the tell.
- Segment reports by network. Google reports Display and Search as one campaign total. Segment by network to split them, or the 59% stays invisible.
How the change actually shipped
The campaign runs on Adjar: every campaign's network setting is config in a git repo, continuously compared against what is live. The drift surfaced as a diff.
[[campaigns]]
name = "DB Access Control | SEARCH | 2026-Q2"
- networks = ["search", "search_partners", "content"]
+ networks = ["search", "search_partners"]
Display impressions dropped to zero from June 8; the live network is search-only again, matching the managed config. Because the check is a comparison and not a memory, "is any Search campaign serving on Display?" gets answered on every run, not the next time someone happens to expand the Networks section. The June Analytics "Display" line is residue now; it clears in July.
Frequently asked questions
- Why is my Google Ads Search campaign showing on the Display Network?
Because Display Expansion is enabled. New Search campaigns are set to "show ads across the entire network" by default, which includes the Display Network. Unless someone unchecked the Display Network option in the campaign's Networks settings, the campaign can serve display ads on YouTube, Gmail, and partner sites alongside search results.
- Does Display Expansion spend my Search budget?
Yes, but Google says it "won't typically affect your spend on Search and will aim to use only unspent Search budget" — the money the Search auction didn't absorb. On low-volume or niche campaigns there's often a lot of unspent budget, so Display can quietly take a large share of impressions.
- How do I stop a Search campaign from serving on the Display Network?
Open the campaign's settings, expand the "Networks" section, and uncheck "Display Network" so only Search (and optionally search partners) remain. It's per campaign; there's no account-wide toggle. After the change, the campaign serves search-only.
- Will negative keywords stop Display Network spend?
No. Negative keywords filter which searches trigger your ad. Display impressions aren't triggered by searches, so negatives don't apply. Stopping Display spend on a Search campaign is a network setting, not a keyword exclusion.
- How do I see how much a Search campaign spent on the Display Network?
Google reports Display and Search together as one campaign total. Segment the campaign by network ("Search Network" vs "Display Network") to split them. That breakdown is the only way to see the Display share — like the 59% of impressions in this article — without it hiding in the campaign total.