Two significant AdSense changes have landed in the second half of 2026, and they require different responses from publishers. One is already done: the Related Search format for AdSense Auto ads was retired on August 6, 2026. The other is incoming: impression measurement for display inventory will switch from count-on-download to begin-to-render beginning February 17, 2027
Most coverage of these two updates treats them as separate announcements. They are, but understanding them together reveals something more useful: Google is systematically tightening how it measures and surfaces ads, and publishers who understand the mechanics behind both changes will be better positioned to maintain revenue through the transition than those who treat each update as an isolated event.
This guide covers both changes with the detail publishers actually need: what changed, why Google made each change, how your account metrics will be affected, and what actions to take now versus what to prepare for in early 2027.
Update 1: Related Search for Auto Ads is Gone
What Happened
Starting August 6, 2026, the Related Search format no longer appears on sites that had it enabled through Auto ads. It was also removed as a format option from the AdSense frontend.
Related Search for Auto ads let publishers show users search terms related to the content of the page they were viewing. When users clicked a related search term, they were taken to a Google-powered search experience that showed ads and results from the site.
Google confirmed that no action is required from publishers, and that all remaining Auto ad formats will continue to function as normal. Some of them may replace the original Related Search slots.
Why This Matters More Than "No Action Required"
The "no action required" message is technically accurate. Your Auto ads will not break. But the revenue implication of this change depends entirely on how much of your Ad revenue came from Related Search clicks specifically, and that is something each publisher needs to check in their own account.
Related Search was a distinct monetization mechanism from standard display ads. When a user clicked a related search term, it initiated a search session that generated revenue different from a standard banner impression. Publishers with content-rich pages in high-traffic niches, where Related Search was generating consistent click-through to search results, may notice a revenue gap that the replacement Auto ad formats do not fully cover.
What to Do Now
Check your AdSense reporting for the period before and after August 6. If you have access to format-level reporting, compare performance from the two weeks prior to August 6 against the two weeks following. A revenue decline concentrated around that date suggests that Related Search was contributing meaningfully to your earnings, and that the replacement Auto ad formats are not fully compensating.
If you see a gap, the productive response is not to wait for it to close automatically. Review which Auto ad formats are currently enabled in your account and confirm that all remaining formats are active. Consider whether your pages are optimized for the formats that replaced Related Search, particularly in terms of ad placement density and content structure.
For publishers who used Related Search for Content specifically, rather than the Auto ads version, note that this format had different policy treatment and its own separate update cycle. The retirement announced in August 2026 covered the Auto ads format.
Update 2: Begin-to-Render Impression Counting Arrives February 2027
What the Change Is
In Google Ad Manager and AdSense, impression measurement for display inventory will switch from the count-on-download methodology to begin-to-render beginning February 17, 2027. No action is required.
Count-on-download involves counting an impression when an ad starts to download to a user's device. Begin-to-render counts an impression when the ad creative has successfully loaded and has started to render on the user's device.
The practical difference: COD counts ads that have loaded to a page but were potentially abandoned before fully rendering, such as if a user quickly navigates away. Therefore, following the shift, you may notice a decrease in total display impressions, as BTR counts an impression later in the ad serving process.
For full technical details on this update, Google's official guidance is available at AdSense Begin-to-Render Impression Counting page.
Why Google Is Making This Change
Begin-to-render is the industry standard and preferred methodology for impression counting. BTR streamlines publisher workflows and aligns impression measurement methodologies with demand-side platforms.
The alignment with DSPs is the critical context here. Publishers have historically seen discrepancies between what AdSense counts and what advertiser-side platforms count, because advertisers have been using begin-to-render standards while AdSense was counting earlier in the delivery process. This change eliminates that discrepancy at the source.
For publishers, the alignment means fewer impression discrepancies in advertiser reports, which in theory reduces the friction in programmatic ad buying and can support better fill rates over time.
What Happens to Your Numbers
Currently, Ad Manager and AdSense already use or are compliant with begin-to-render for native, app, and video inventory impression counting. The shift to BTR unifies impression counting methodologies across all inventory types.
For display banner inventory specifically, this is a real change. Publishers will see a decrease in reported impressions after February 17, 2027, because some ads that were previously counted under COD were never actually rendering. The decrease in impressions does not mean fewer ads were actually seen by users. It means that the count now reflects ads that rendered rather than ads that merely began downloading.
The revenue impact depends on your site's specific technical characteristics. Ad Manager publishers can estimate the potential difference between their current COD and future BTR impressions by reviewing their existing web display versus rendered metrics in reporting.
How to Estimate Your Impact Before February 2027
Google has provided a specific reporting path for this. To generate a report on the potential impact: sign in to Google Ad Manager, click Reporting then Interactive reports, click Create my own report, enter a report name and date range. Note that Google advises running a historical report with a start date after August 12, 2026. Add the dimensions of demand channel, inventory format, inventory type expanded, and device category. Add the metrics of Ad server impressions and Ad server begin to render impressions.
The difference between your current Ad server impressions and your Ad server begin-to-render impressions is your estimated exposure to the February 2027 change. If the gap is small, your site's technical setup is already aligned with the incoming standard. If the gap is large, investigating what is causing ads to download but not render is the productive use of the time between now and February 2027.
Technical Factors That Affect Your BTR Numbers
Synchronous scripts on creative assets mean serialization is occurring and lead to longer download times. If asynchronous scripts are present, they can be executed in a parallelized manner, meaning assets are more likely to download and trigger a begin-to-render ping.
Having more partners in the supply chain leads to longer download times and can result in fewer creatives that begin to render.
The practical implication: publishers with complex ad stacks, multiple header bidding partners, or heavy creative payloads will tend to see a larger gap between COD and BTR impressions than publishers with simpler, faster-loading implementations. Running the diagnostic report above tells you where you stand specifically before the change takes effect.
Lazy loading settings impact impression measurement for both COD and BTR methodologies. Raising renderMarginPercent or fetchMarginPercent causes assets to render earlier in the user experience but also increases resource demands on your network and the end-user's device.
Putting Both Updates Together: What They Signal
The Related Search retirement and the BTR impression counting change are different in kind but consistent in direction. Google is moving toward stricter, more accurate measurement of actual ad engagement. Related Search clicked through to search experiences; its retirement eliminates a format that sat between content pages and search results in a way that Google has been tightening policy around for several years. BTR impression counting eliminates the inflation in display impression counts that came from counting downloads rather than renders.
For publishers who have been running clean, technically sound ad implementations on content-driven sites, these changes are largely neutral in the long run. The short-term revenue effects around August 6 and February 2027 may create temporary reporting anomalies, but the underlying value of ads that actually render to actual users is not affected.
For publishers whose revenue relied heavily on Related Search click behavior, or whose impression counts include a large proportion of COD-but-not-rendered ads due to technical issues with their ad stack, these changes require active response rather than passive observation.
The September 2026 window, after the Related Search change has taken effect and before the BTR change arrives, is the productive time to run the diagnostic report, review your Auto ad format configuration, and address any technical issues in your ad implementation that the BTR gap reveals.
