Where to Place AdSense Ads Without Hurting Readers

This site does not run ads. We have not placed a single AdSense unit on GreenlightMySite, so this guide has no revenue figures and no claims about which position earns the most. It rests on Google’s published placement rules and on layout principles we apply to our own pages, and everything marked as our recommendation is a judgment you should test on your own readers.

What the rules fix and what they leave to you

Google’s placement policy is a list of things you may not do. Labels must not mislead: if you label an ad unit, only “Advertisements” or “Sponsored Links” are allowed. Ads may not sit where they can cause accidental clicks, and the policy names the vicinity of buttons, menus, navigation and game windows. You may not imitate navigation or buttons, draw attention to an ad with animations or arrows, or format the content around it so that it looks like an ad. Rewarding clicks, refreshing ad units automatically and redirecting users are prohibited, as are pop-ups and pop-unders opened without a user action, and a site with more than 3 pop-ups.

A second policy, on ads on screens without publisher content, decides which pages may carry ads at all. Google does not allow its ads on screens with no content or low-value content, pages under construction, alert and navigation screens, or dead ends such as thank-you, exit and error pages. The test it gives for the rest is that your content is the focal point of the page.

What the rules do not contain is a number. Google publishes no maximum count of ads per page and no density threshold, and the old limit of three ads per page was removed. So the policy cannot tell you whether a layout is acceptable; it only tells you what makes it unacceptable. The next two sections are our way of filling that gap.

Slot by slot on an article page

This table is our recommendation for a long-form article page like the one you are reading. “Risk” means the risk to readers and to policy compliance, not to revenue.

On the number of ads, we suggest starting with one or two on a page of about 1,400 words and adding more only if readers still finish the article. The check that costs nothing: scroll on a phone, and if any single screen shows more advertising than article, remove one.

Reserve the space before the ad arrives

An ad unit loads after the rest of the page. If its container has no height until the ad fills it, the text below jumps down at that moment, and that jump is layout shift. Cumulative Layout Shift is one of the three Core Web Vitals, and Google’s threshold for a good score is 0.1 at the 75th percentile of page loads. A slot that fills late is an obvious candidate for that shift, which is why our Core Web Vitals guide lists late-arriving elements among its six levers.

The fix is to give the slot a minimum height before the ad appears. The heights below are placeholders based on the 300 by 250 and 728 by 90 sizes that are common in display advertising. Google gives no figure to reserve, and we have no live ad to measure, so treat them as a starting point and revisit them once real ads render.

<aside class="ad-slot" aria-label="Advertisement">
  <p class="ad-slot__label">Advertisements</p>
  <!-- the ad unit code goes here -->
</aside>

.ad-slot {
  min-height: 280px;          /* label plus a unit about 250 px tall */
  margin: 2rem 0;
  text-align: center;
}
.ad-slot__label {
  margin: 0 0 0.25rem;
  font-size: 0.75rem;
  color: #5b6573;
}
@media (min-width: 768px) {
  .ad-slot--wide { min-height: 120px; }   /* label plus a unit about 90 px tall */
}

There is a trade-off. Reserve too much and an unfilled slot leaves a blank band in the article; reserve too little and the text still moves. We would choose the height that the most common unit fits, and then look at the pages. The label inside the slot uses the permitted wording, and it sits within the reserved height so it does not add to the shift. A consent banner is another element that can push content down: show it as an overlay fixed to the bottom of the viewport rather than inserting it above the page, then run Lighthouse with the banner enabled.

Consent comes before the first ad

For visitors in the European Economic Area and the United Kingdom, and in Switzerland too, Google requires legally valid consent for cookies and local storage and for personalization. Serving personalized ads there has required a consent management platform (CMP) certified by Google and integrated with the IAB’s TCF since 16 January 2024 in the EEA and the UK, and since 31 July 2024 in Switzerland. Without one, you do not get personalized ads for those visitors. Google maintains a list of certified platforms, and our cookie consent guide goes through the choice in plain words.

Our commitment for this site is simple: a certified consent platform goes in before the first ad appears. The privacy policy also has to describe advertising cookies the way Google asks, and the wording requirements are in our AdSense requirements checklist. The privacy policy generator writes the paragraph. Consent and placement meet in the layout as well, since the platform’s banner is the first thing a new visitor in those regions will see.

A pre-flight pass before switching ads on

Run these six checks on a copy of the site with ads enabled, and again after every template change.

1. Phone scroll. On a real phone, scroll the whole page. No single screen should hold more advertising than article.
2. Thumb test. Tap where you normally tap: links, buttons, the menu, the end of a table. If an ad sits within a thumb’s reach of any of them, move the ad.
3. Label check. Any text above an ad reads Advertisements or Sponsored Links, or there is no label.
4. Page types. No ads on error pages, thank-you pages, empty search results or thin pages, and none on pages under construction.
5. Neighbors. Nothing next to an ad copies its look: cards with the same borders, colors and sizes, arrows, or lines such as “click here”.
6. Shift. Run Lighthouse before and after switching ads on. CLS should stay at or under 0.1.