How to Place Google Ads on a Website: AdSense Placement Guide

What you are actually placing on your site

If you want to earn revenue by showing Google ads, the relevant product is usually not Google Ads, which is the advertiser-side platform, but one of Google's publisher products.

Google AdSense is the simpler option for website monetization. Google Ad Manager is a more advanced platform for managing ad inventory, direct campaigns, and programmatic demand.

In both cases, the placement logic is the same: define ad slots, preserve readability, follow Google policies, and measure performance.

Current AdSense ad unit types include Display, In-feed, In-article, Multiplex, and Search engine.

Start with the user, not the click rate

Google recommends starting with user behavior rather than asking only where CTR might be highest. Before placing any ad, consider:

• Why the user came to the page
• Where their attention is likely to be focused
• Which actions should remain easy to complete
• Whether ads make the main content harder to find
• Whether users can clearly distinguish ads from site content

The core principle: ads should be visible, but they must not block content, imitate navigation, or encourage accidental clicks.

Recommended placement areas

Top horizontal banner

A top banner or leaderboard is the most common baseline placement. The typical size is 728 x 90 px. It can be placed:

• At the top of the page
• Below the main site header
• Above the content area or article title

Best suited for news websites, blogs, and informational pages with a clear header.

Risk: If there are too many ads above the first visible screen, users may not reach the content and will leave. A slot just above the fold is often more viewable than one at the very top of the page.

Sidebar ad unit

If your site has a sidebar, use it for rectangular or skyscraper-style units. Common sizes include:

• 300 x 250
• 300 x 600
• 160 x 600
• Responsive sidebar units

Best suited for desktop blog and media layouts where the sidebar remains visible while the user reads.

Risk: On mobile, sidebars usually move below the content. A fixed desktop placement is not a full strategy. Use responsive ads or create a separate mobile plan.

Ad below the main heading

An ad placed below the article title can work because it sits near the start of the user's attention path. The main restriction: the ad must not look like a navigation menu. Clearly separate it from breadcrumbs, tabs, and action links.

In-content ads

In-content units are placed between sections of an article. Google suggests this option when the user has already started reading and attention is focused on the content.

Best suited for long articles, tutorials, and reviews.

How to place them correctly:

• After a meaningful content block, not in the middle of a sentence or a list
• With enough vertical spacing above and below
• Away from download buttons, pagination controls, and interactive elements
• As responsive units so they work on mobile

Risk: Too many in-content ads degrade reading quality and make monetization feel aggressive.

End-of-content ads

An end-of-content ad works well when the user has finished reading and is ready to go somewhere else. This can sit before or after a comment section, depending on where your audience tends to leave.

Best suited for articles with comments, forums, tutorials, and long-form pages.

Viewability: what actually matters

An ad being on the page is not the same as it being seen. Three practical conditions determine viewability:

1. The user must scroll to where a meaningful portion of the ad is visible.
2. The ad must stay on screen long enough, not just flash past during fast scrolling.
3. The ad must be rendered by the time the user reaches it.

Practical implications:

• Page speed directly affects ad viewability
• Asynchronous tags and properly configured lazy loading help
• Above-the-fold is not automatically the most effective position
• Below-the-fold ads need compelling content that encourages scrolling
• Review analytics for real screen resolutions before choosing placements

Responsive ads and mobile

Google recommends responsive ads because units need to adapt to different layouts and devices. Before publishing any placement, check:

• How the ad looks on desktop, tablet, and mobile
• Whether it overlaps content on smaller screens
• Whether it creates excessive blank space
• Whether it appears too close to buttons, forms, or navigation
• Whether it harms Core Web Vitals or page speed

The default strategy should be responsive-first. Fixed sizes still work in stable desktop placements, but should not be the only option.

Auto ads: when to use them

Auto ads automatically choose and optimize placements. They are useful when:

• Your site has many different page templates
• You want to start testing quickly without manual setup
• You are willing to review the preview and exclude poor placements

Auto ads should not be left unchecked. Use the AdSense preview to review suggested placements, remove unnecessary areas, and exclude pages like login or contact screens. Auto ads are a starting hypothesis, not a finished layout.

What is prohibited or risky

Do not encourage accidental clicks

Ads must not be placed where users may confuse them with menus, navigation, back or next buttons, download links, play buttons, game windows, video players, or form controls.

Do not draw artificial attention to ads

Arrows, animations, symbols, or any other method that points users toward ads or makes them unnaturally prominent is prohibited.

Do not disguise ads as content

Do not style your page so that ads and editorial content look like one list, one gallery, or one recommendation block. Do not place images next to ads in a way that implies the image belongs to the advertiser's offer.

Do not ask for or incentivize clicks

Do not ask users to click ads, offer rewards for clicks, or frame ad clicking as a way to support the site.

Do not use unsuitable surfaces

AdSense placement is prohibited or restricted in email, on email-viewing pages, on private messaging screens, in popups or popunders that violate policy, on pages without verifiable content, and on pages with automatic refreshes.

A practical layout for a typical article

For a standard blog post or article, start with this layout:

1. Top area: A responsive leaderboard below the site header or above the article title
2. Desktop sidebar: 300 x 250 or 300 x 600, if the sidebar exists and does not distract from reading
3. Mid-article: One responsive in-content unit after 3–5 meaningful paragraphs or after the first major section
4. End of article: A horizontal or rectangular unit after the main content, before or after comments
5. Mobile review: Check separately, because the sidebar disappears and ad density feels stronger on small screens

Start with 2–3 ad units per page rather than the maximum possible number. Then test and adjust.

How to test placements

Google recommends experimenting rather than assuming a layout is optimal. A simple process:

1. Document your current placement setup as a baseline
2. Choose one hypothesis, such as moving the top banner lower or replacing a fixed unit with a responsive one
3. Run the test for one to two weeks if traffic is modest
4. Compare revenue, viewability, CTR, bounce rate, scroll depth, and page speed
5. Keep the winning variant
6. Avoid changing too many placements at once — you will not know what caused the result

Metrics to track: RPM (revenue per 1,000 pageviews), viewability and Active View, CTR, scroll depth, bounce rate or engagement rate, and Core Web Vitals.

Pre-launch checklist

UX check

• Users can immediately identify the main content
• Ads do not cover text, buttons, or forms
• Mobile does not show excessive ad density in the first visible screen
• Sidebar ads do not break the layout on any device
• In-content ads sit between meaningful sections, not inside a sentence or list

Policy check

• Ads do not look like menus or navigation elements
• No calls to click ads anywhere on the page
• No arrows, animations, or other artificial attention mechanisms
• Ad labels do not mislead users
• Ads are not placed next to download, play, or navigation controls
• Ads are not placed in email, private messages, popups, or pages without content

Technical check

• Responsive units are used wherever the layout is responsive
• The page loads quickly with ads present
• Ads do not unreasonably harm Core Web Vitals
• Lazy loading is configured so ads are ready when users reach them
• Auto ads preview has been reviewed and poor placements excluded
• Analytics separate desktop and mobile behavior