AdSense In-Feed Ads: Layout Basics for Blog Listing Pages
AdSense in-feed ads for blog archives and category pages—how in-feed units differ from in-article ads and where they belong in listing layouts.

AdSense in-feed ads belong in listing templates—category pages, tag archives, homepage post grids—where readers scan many cards, not inside a single article paragraph (in-article ads).
This page is Feed-Then-Layout. It is not mobile layout (single-post phone slots). It is not display formats map alone—read that for unit vocabulary first. It is not WordPress code placement (theme surgery steps).
Add in-feed units only when archive traffic is real, your theme exposes a list container, and spacing matches post cards—not before single-post placements work.
Official: In-feed ads · About ad units · Ad placement policies.
Disclosure: AdSense is Google’s program. We do not publish your RPM.
Table of contents
- Feed-Then-Layout
- In-feed vs in-article vs responsive box
- When archive monetization is worth it
- Theme and HTML requirements
- Spacing and policy guardrails
- Workflow for small blogs
- FAQ
- Fix posts first, feeds second
Feed-Then-Layout
FEED-THEN-LAYOUT
1. TRAFFIC → do archives earn impressions?
2. TEMPLATE → list of cards with consistent markup
3. UNIT → create in-feed ad unit in AdSense
4. STYLE → match card padding and typography
5. INSERT → every N items—not every row
6. PHONE → scroll archive on real device
7. TRIM → remove if CLS or taps look accidental
In-feed is layout engineering, not a checkbox. Blogs with ten posts total rarely benefit; blogs with strong category SEO sometimes do.
In-feed vs in-article vs responsive box
| Unit | Lives on | Reader job |
|---|---|---|
| In-feed | Archive / category lists | Pick next post |
| In-article | Single post body | Read one article |
| Responsive display | Sidebar or mid-post box | General monetization |
Using an in-article snippet inside a card loop breaks styling and policy spacing—pick the unit type AdSense documents for feeds.
When archive monetization is worth it
Good signals:
- Category hubs rank and collect impressions in Search Console
- Homepage shows multiple recent posts with steady scroll depth
- You already placed one intentional in-article or mobile layout unit on posts
Weak signals:
- New site with thin archive pages
- Homepage is a single landing with no list
- Theme rebuild planned next month—wait until markup stable
Theme and HTML requirements
AdSense in-feed setup asks you to match container selectors and item structure so ads resemble neighboring cards. WordPress themes differ:
- Block themes vs classic PHP loops
- Grid plugins injecting their own markup
- Infinite scroll loading cards asynchronously—ads may misfire
Use the WordPress placement owner for paste discipline; use this page to decide whether the archive deserves an in-feed unit at all.
Preview view-source or inspector: if post cards lack consistent classes, fix theme markup before ad insertion.
Spacing and policy guardrails
In-feed ads fail UX when they look like fake posts:
- Title styling identical to real posts without clear ad labeling (Google handles labeling in many formats—still avoid deceptive surrounding copy)
- Cards glued to pagination buttons
- Units every row on mobile—readers cannot find content
Follow placement policies on accidental clicks. Pair with anchor and vignette restraint—archives already interrupt scan flow.
Workflow for small blogs
- Confirm ads.txt authorized and posts monetize cleanly
- Pick highest-impression archive template from Search Console
- Create in-feed unit in AdSense; note required selectors
- Insert ad every 4–8 items as starting experiment—not every card
- Test iPhone + Android scroll; watch CLS in PageSpeed
- If blank, run ads not showing triage before duplicating snippets
Hybrid sites using Auto ads should check whether Auto already injects in-page formats on archives—avoid double boxes.
FAQ
Do in-feed ads work on tag pages?
Yes if the tag template renders a compatible list—verify markup, not only URL pattern.
Can I use in-feed with infinite scroll?
Risky—ads may load oddly as JS appends cards. Test thoroughly or disable infinite scroll on monetized archives.
Will in-feed hurt category SEO?
Poor layout and CLS can hurt UX signals. Well-spaced units on helpful archives rarely cause SEO issues by themselves.
Should I monetize search results pages?
Usually no—many themes should stay noindexed; ad placement on low-value search URLs is poor practice.
Fix posts first, feeds second
Monetize single posts with display format and in-article discipline first. When archive URLs earn impressions, apply Feed-Then-Layout: match card spacing, insert in-feed units sparingly, test mobile scroll, trim anything that looks like camouflaged navigation.
Keep learning
More guides in the same topic lane.
PDF to Text or PDF to Word: Which Job?
Need copy-paste plain text from a PDF or an editable Word file? Choose PDF to Text vs PDF to Word before upload—format, cleanup, and live tool links.
JPG to PDF or Protect PDF: Which Job First?
Photos still need a PDF packet, or the PDF only needs a password? Route JPG stacks vs Protect PDF before you lock the wrong file or skip the build step.
GSC Page Indexing or Sitemaps Report: Which First?
Page indexing explains why URLs are in or out of Google search. Sitemaps checks whether Google read your XML file—use this guide to pick the right GSC report.