Two Spouts

Google's limited ad serving expands to Search in 2026

On June 12, 2026, Google extended its limited ad serving policy to Search. What the new 'qualified advertiser' tier means for B2B SaaS Google Ads accounts.

Published June 15, 2026 · By Two Spouts

On June 12, 2026, Google updated its limited ad serving policy to cover additional scenarios on Google Search — extending a framework that previously governed broader ad products and YouTube to the most commercially important surface the company operates. The change is quieter than a bidding overhaul or a tracking deadline, because there is no single date when something breaks. But for B2B SaaS advertisers it introduces a new failure mode that has nothing to do with how much you bid: your ads can be served less often simply because Google does not yet consider your account a qualified advertiser on certain searches.

That is a different kind of risk than most SaaS teams are set up to monitor. Quality Score, bid strategy, and budget are all things you tune inside the auction. Qualification sits above the auction — it decides whether you get into the higher-risk parts of it at all. This post explains what actually changed, how Google decides who is qualified, why several common B2B SaaS patterns sit closest to the line, and what to verify now while the enforcement window is still opening rather than closed.

What Google changed on June 12, 2026

Limited ad serving is not new. Google introduced it years ago as a way to throttle impressions for advertisers it had not yet established enough trust in, and extended it to YouTube in 2024. The June 12, 2026 update brings the same logic to Google Search, where it now functions as a systematic qualification layer rather than a handful of edge-case rules. As PPC trade outlet ppc.land described it, the policy is "moving from targeted scenarios to a systematic qualification layer across Google Search." That phrase is the important part: it is no longer a niche policy that catches obvious bad actors, but a standing assessment applied across the search surface.

Crucially, the rollout is gradual. Google has said implementation will be completed by 2028, which means the qualification bar is expected to rise over roughly two years rather than snap into place. For advertisers, that is both reassuring and easy to misread. There is no deadline to panic about — but there is also no "we are fine, nothing happened on launch day" signal to rely on. An account that scrapes through under a loose 2026 threshold can quietly fall below a stricter 2027 one without any change on its own side. The right mental model is a slowly tightening filter, not a switch.

What "limited ad serving" actually means for impressions

When an advertiser is treated as not-yet-qualified, Google can cap how often its ads appear on the searches it considers higher-risk for a poor ads experience. In Google's own policy language, "Google may limit ad impressions from unqualified advertisers on searches that are more likely than others to result in negative ads experiences." Read that carefully: the limiter is impressions, the trigger is the advertiser's qualification status, and the scope is specific high-sensitivity searches rather than the whole account at once.

This is why limited ad serving is so easy to miss in reporting. It does not show up as a policy disapproval on a specific ad, and it does not produce a clean "blocked" status you can filter for. It shows up as impressions that simply do not materialize on certain queries — an impression-share gap that looks like competition or low bids until you rule those out. A SaaS account could be paying for, and winning, the auctions it is allowed into while never being entered into a slice of higher-scrutiny searches at all. The symptom is suppressed reach on exactly the terms where trust matters most, and the cause is invisible unless you know to look for it.

How an advertiser becomes "qualified"

The qualification signals Google emphasizes are about identity and trust, not auction mechanics. Its guidance centers on clear branding: avoid confusion about who you are or whether you are associated with other brands, clearly display your own brand in both your ads and your landing page, and — if you reference another brand — be explicit about the nature of your association while keeping your own identity unmistakable. Google has also said it weighs user reports about an advertiser especially heavily when deciding qualification, which means the experience real searchers have with your ads feeds directly back into how often you are allowed to show.

None of these levers live in the bidding or keyword settings most teams spend their time on. You cannot bid your way to qualified. You earn it by being an identifiable, consistent, non-confusing advertiser whose ads, landing pages, and underlying business all line up. For established B2B SaaS brands that sell under one name and send traffic to their own clearly branded site, this is largely automatic. The accounts that struggle are the ones where the name in the ad, the entity on the billing account, and the brand on the landing page do not obviously match — or where the campaign strategy deliberately leans on another brand's name. That mismatch is exactly what the qualification rubric is built to catch.

Why B2B SaaS accounts are more exposed than they look

Several routine B2B SaaS tactics sit unusually close to the qualification line. Competitor-conquesting campaigns — bidding on rival product names to intercept comparison shoppers — are the clearest example. They are legitimate and widely used, but they put another brand's name in front of users while you serve your own, which is precisely the "association with other brands" scenario Google's guidance singles out. If your conquesting ads or landing pages are not scrupulously clear that you are not the competitor, you are feeding the qualification model the ambiguity it is looking for. We cover the strategic side of this in our guide to competitor analysis for SaaS, and the policy change raises the cost of getting the execution wrong.

The second exposure is structural. Many SaaS companies advertise under a product brand while the Google Ads billing account, legal entity, and domain registration carry a parent-company or holding name. To a human that is obviously the same business; to an automated identity check it can read as a mismatch. Add the common pattern of routing paid traffic to thin, unbranded performance landers — pages stripped down for conversion-rate testing that barely show the company name — and you compound the problem. The same minimalist landing pages that test well for conversion can read as low-identity to the qualification layer. Before assuming your landers are safe, run them through our landing-page audit with brand clarity, not just conversion rate, as a first-class criterion.

The tracking-verification angle SaaS teams miss

Beyond branding, trade analysis of the policy points to a quieter signal: the trustworthiness of your tracking infrastructure. ppc.land's read is that using uncertified or unverifiable tracking setups raises a technical signal Google's systems cannot confirm, which — combined with other account signals — can contribute to being assessed as unqualified. In other words, the same conversion plumbing you maintain for measurement now also feeds, indirectly, into how much your ads are allowed to serve. That ties this policy directly into the wave of 2026 tracking changes SaaS advertisers are already navigating.

This is where the timing gets uncomfortable. The qualification expansion lands in the same window as a cluster of conversion-tracking changes — the consent-mode decoupling and enhanced-conversions consolidation — that make misconfiguration more likely just as the cost of looking untrustworthy goes up. If your tracking is mid-migration and sending inconsistent or unverifiable signals, you are exposed on two fronts at once: degraded bidding and a weaker qualification posture. The defensive move is to keep conversion tracking on Google-supported, verifiable infrastructure and confirm it is firing cleanly — the same discipline we lay out in conversion tracking for SaaS and in the GA4 / Google Ads consent split breakdown.

Your pre-enforcement qualification checklist

Because there is no single deadline, the right response is a recurring verification pass rather than a one-time scramble. Start with identity alignment: confirm the brand name shown in your ads matches the brand on your landing pages and is reconcilable with the legal entity on your billing account. Where a product brand and parent entity differ, make the relationship explicit somewhere a verification process can see it — on the site footer, the about page, and the account's business information. Then audit any campaign that references another brand, especially competitor-conquesting, and make sure both the ad copy and the destination page leave no doubt about who is actually advertising.

Next, fold tracking trust into the same review. Verify that conversion tracking runs on Google-supported infrastructure, that tags fire as expected, and that you are not relying on an unverifiable third-party setup that could read as an unconfirmed signal. Keep your account's business identity verification current. Finally, watch impression share on your highest-intent and most sensitive terms for unexplained gaps — a sudden, bid-independent drop in impression share on a competitor or category term is the kind of symptom limited ad serving produces. Many of these checks overlap with the broader account hygiene we catalog in Google Ads mistakes for SaaS businesses, so it is efficient to run them together.

What to do as the threshold tightens through 2028

The strategic takeaway is that qualification is now a standing property of your account, not a box you tick once. Because Google is raising the bar gradually through 2028, the accounts that build clean identity and tracking hygiene early get two advantages: they avoid the impression suppression that catches laggards, and they accumulate the positive trust signals — consistent branding, low user-report rates, verifiable infrastructure — that make a rising threshold a non-event. The teams that wait until they notice a reach problem will be diagnosing an invisible cap under deadline pressure instead of preventing it.

For most established B2B SaaS brands, the work here is modest: reconcile a few naming mismatches, tighten conquesting execution, verify the tracking stack, and add a quarterly qualification check to the same rotation as your conversion-tracking and account audits. The cost of doing it now is a few hours; the cost of ignoring it is a slow, unattributed leak in reach on exactly the high-value searches where being trusted matters most. If you want a second pair of eyes on your account's branding consistency and tracking verification before the threshold tightens, our Google Ads audit covers both as part of the standard pass.

Frequently asked

What is Google's limited ad serving policy?

Limited ad serving is a policy framework that lets Google restrict how often an advertiser's ads show — independent of bid, budget, or Quality Score — when the account is judged not yet trusted enough for certain placements. It started on broader ad products, extended to YouTube in 2024, and on June 12, 2026 Google updated the policy to cover additional scenarios on Google Search. The mechanism is a qualification layer: unqualified advertisers can have impressions limited on searches Google deems higher-risk for a bad ads experience, regardless of how competitive their auction inputs are.

When does the Search expansion take effect?

Google published the updated policy on June 12, 2026 and has said the rollout is gradual, with implementation completed by 2028. That means there is no single switch-flip date for advertisers to dread — instead there is a widening enforcement window over roughly two years. The practical implication for B2B SaaS teams is that this is not a fire drill but a standing requirement: the accounts that get their branding, landing-page identity, and tracking verification in order early are the ones least likely to be caught by a tightening threshold later.

How does Google decide if an advertiser is "qualified"?

Google looks at trust and identity signals rather than auction performance. Its guidance emphasizes clear branding so there is no confusion about who you are or whether you are associated with other brands, clearly displaying your own brand in both ads and the landing page, and being explicit about any association when you reference another brand. Google has also said it takes user reports about an advertiser especially seriously when assessing qualification. None of these are bid or budget levers — they are about whether the account looks like a legitimate, identifiable business.

Does this affect B2B SaaS advertisers specifically?

Yes, in a way that is easy to overlook. B2B SaaS accounts frequently bid on competitor and category terms, run ads from a brand that differs from the legal entity on the billing account, and point traffic to bare landing pages with thin brand identity. Each of those can read as an identity or association ambiguity under the qualification rubric. SaaS teams that lean on competitor-conquesting campaigns or unbranded performance landers should audit those first, because they sit closest to the behaviors the policy is designed to scrutinize.

What should I do before enforcement tightens?

Treat it as a verification project, not a one-off fix. Confirm the brand shown in your ads matches your landing pages and your billing entity; remove or clarify any ad copy that could imply an association with another brand you do not have; make sure your tracking and conversion setup uses Google-supported, verifiable infrastructure; and keep your business identity verification current in the account. Run this as a recurring check rather than a single pass, because the qualification threshold is expected to rise gradually through 2028 rather than land all at once.

One more essay, one tool you can run on your account today, and a case study showing what the moves above look like in practice.