The ads themselves are not the problem, and removing them is not the fix. Google’s page experience signals, which fold in Core Web Vitals, mobile-friendliness, HTTPS, and the absence of intrusive interstitials, do not penalize the mere presence of above-the-fold advertising. What actually gets penalized is layout instability and interstitial-like blocking behavior. For a news publisher that can’t sacrifice ad revenue, the correct priority is engineering the ad slots so they don’t cause Cumulative Layout Shift or behave like full-screen interruptions, not stripping them out.
Why ads and page experience aren’t actually in conflict
Google has been explicit, going back to its original 2016-2017 intrusive interstitials guidance and carried forward into page experience documentation, that standard display ads occupying a reasonable amount of screen space are not treated as intrusive interstitials. The policy targets interstitials that pop over content, that appear immediately or shortly after arrival and are difficult to dismiss, or that use a deceptive layout to make the underlying content seem accessible when it isn’t. A banner ad sitting above the fold, even a large one, doesn’t meet that bar as long as it doesn’t cover content the user came to read and isn’t a full-screen takeover.
The actual mechanism that connects ads to a real page experience penalty is Cumulative Layout Shift, one of the three Core Web Vitals. CLS measures unexpected movement of visible elements as a page loads. Ad slots are one of the most common causes of high CLS because ad networks frequently don’t know the dimensions of the creative that will load until the ad request resolves, so if no space is reserved, the ad drops into place and pushes the surrounding content down, shifting everything the user was about to read or tap. That shift, not the ad’s existence, is what Core Web Vitals field data captures and what feeds into the page experience assessment Google’s ranking systems use.
The mechanism: reserving space vs. letting ads dictate layout
The standard, well-documented fix is reserving explicit space for ad containers before the ad creative loads, so the surrounding layout doesn’t move when it does. This means setting explicit width and height (or aspect-ratio) on the ad container element sized to the largest likely creative for that slot, rather than letting the container collapse to zero height and expand once content arrives. Google’s web.dev guidance on optimizing CLS specifically calls out ad slots as a common offender and recommends reserving a slot size in advance, even using a placeholder or minimum height, so the shift happens before the user has started reading rather than after.
A second mechanism worth prioritizing is where the ad sits in the DOM load order relative to primary content. If ad-slot resolution blocks or delays the rendering of the headline and lede, that hurts both perceived load speed and any Largest Contentful Paint measurement if the ad or a large image within it is the largest element painted. Lazy-loading ads that are below the immediate viewport, while still reserving their space, keeps the above-the-fold rendering path focused on the actual editorial content first.
Third, watch for ad behavior that crosses from “static banner” into genuinely interstitial territory: ads that expand on scroll to cover content, ads that trigger an unexpected full-screen takeover after a delay, or sticky ad units that grow and shrink unpredictably as the user scrolls, all of which can shift from “standard ad” into “intrusive interstitial-like behavior” in Google’s assessment, independent of CLS. The safest pattern for a fixed sticky ad unit (common in news sites, a persistent bottom or top bar) is a stable, unchanging size that doesn’t expand over content on interaction.
Why programmatic ad stacks make this harder than it sounds
News publishers rarely control ad rendering directly the way a simple site with a single ad network might. Programmatic setups routinely involve header bidding across multiple demand partners, waterfall fallbacks when a preferred ad size doesn’t fill, and creative served from third parties whose actual dimensions aren’t known until the auction resolves in the browser. This is precisely why ad-driven CLS is such a common, structural problem for publishers specifically, rather than a simple oversight: the ad tech stack is, by design, resolving what to show and at what size after the page has already begun rendering, which is the exact sequence that produces layout shift if space isn’t pre-reserved.
The fix has to account for that reality rather than assuming a single fixed-size ad unit. Reserving space for a variable-size programmatic slot means sizing the container to the largest plausible creative the ad configuration allows for that slot (many programmatic setups define a fixed set of allowed sizes per placement), and using CSS min-height or aspect-ratio on the container so smaller-than-maximum creatives still render inside a stable, pre-allocated box rather than causing the container to shrink and then jump when a larger creative wins a later auction refresh. Refreshing ad slots after initial load, common in news sites to maximize revenue per session, needs particular attention: a slot that refreshes to a differently-sized creative mid-read is exactly the kind of unexpected-shift-after-initial-load behavior CLS is measuring, so refresh-triggered resizing deserves the same reserved-space treatment as the initial load.
Practical prioritization for a constrained publisher
Given a news publisher can’t remove the ad revenue, the actionable sequence is: first, audit current CLS scores specifically on article pages using field data from the Chrome UX Report (via PageSpeed Insights or Search Console’s Core Web Vitals report), since that’s the actual ranking-relevant data source, not a lab tool, and segment the audit by template (homepage, article page, category page) since ad density and behavior often differ meaningfully across templates. Second, work with the ad ops or programmatic team to implement fixed or aspect-ratio-reserved containers for every ad slot above the fold, including refresh-triggered slots, treating this as a layout engineering problem rather than an ad-removal problem. Third, review any interstitial, sticky, or expanding ad formats specifically against the intrusive interstitial exceptions (legally required notices, small banners using a reasonable amount of screen space) to make sure none of them have drifted into blocking primary content on mobile, paying particular attention to any format that expands on scroll or after a time delay, since that’s the specific behavior pattern most likely to cross from acceptable advertising into interstitial territory. Fourth, coordinate the fix with whichever team actually owns ad tag implementation, since CLS caused by ads is frequently a shared problem between editorial/product and ad ops, and a durable fix usually requires both sides agreeing on reserved dimensions as a non-negotiable implementation standard for any new ad placement, not just a one-time cleanup of existing slots. None of this requires reducing ad inventory or above-the-fold placements; it requires making the existing ad placements structurally stable so they don’t register as either a Core Web Vitals failure or an interstitial violation.
A worked example of fixing the shift, not the ad
Consider a regional news site running a 300×250 programmatic slot directly above the headline on article pages. Before any fix, the container has no reserved dimensions, so it renders at zero height until the auction resolves roughly 400ms into the page load; when the winning creative arrives, the container snaps to its actual size and pushes the headline and lede down, producing a CLS contribution of about 0.18 from that one slot alone, enough by itself to push the page from “needs improvement” into “poor” on a page that was otherwise clean. The publisher’s ad ops team confirms the placement always resolves to one of three allowed sizes for that slot, so the front-end team sets the container’s min-height to match the largest of the three and adds a neutral placeholder background. After the change, the container occupies its final space from the first paint regardless of which creative wins, and the same slot’s CLS contribution drops to roughly 0.02, low enough that the page as a whole moves back into the “good” range in the following weeks of field data. The ad itself never moved position or shrank; only the timing of when its space was claimed changed, which is exactly the distinction between an ad-removal fix and a layout-engineering fix.
