Mapping Ad Inventory Before You Change Your Theme

A theme change feels visual until the first revenue report looks wrong. The usual story is familiar: the new article template is cleaner, the homepage is faster, everyone likes the card grid, and then the editor notices that in-article revenue fell because a sticky unit disappeared on mobile.

For a small publisher, an ad inventory map is not a finance document. It is a pre-redesign safety check. It tells the designer which placements are intentional, which ones are legacy clutter, and which units are risky enough to review before anyone ships a new template.

Start with page types, not ad units

Do not begin by listing every ad tag in the account. Begin with the pages readers actually see: homepage, category pages, short news posts, long guides, author pages, search results, and policy pages. A 728x90 leaderboard behaves very differently on a category archive than it does above a 1,400-word guide.

For each page type, take a screenshot at desktop and phone width. Mark the ad positions directly on the screenshot. A spreadsheet helps later, but the screenshot catches what reporting cannot: the unit that pushes the introduction below the fold, the sidebar slot nobody sees on mobile, the mid-article placement that lands between two paragraphs that should stay together.

Use four labels: keep, move, test, remove

A useful inventory does not treat every placement as sacred. Put each slot into one of four labels.

Label	When it fits	What to tell design
Keep	Revenue is material and the placement does not interrupt reading.	Preserve it in the new template and measure after launch.
Move	The unit matters, but its current position damages layout or Core Web Vitals.	Find a calmer location before development starts.
Test	The slot has unclear value or mixed device performance.	Ship behind a flag or compare for two weeks.
Remove	The slot is low value, visually noisy, or policy-sensitive.	Do not recreate it just because it existed.

This prevents the worst redesign habit: rebuilding old clutter inside a prettier shell.

Add revenue range, not fake precision

Small teams often do not need a perfect model. A simple range is enough: high, medium, low, unknown. Pull the last 30 days by placement if your ad stack supports it. If it does not, use the closest proxy: page type RPM, viewability, click share, or the ad server line item name.

One publisher I worked with found that a lower article unit looked unimportant until they separated desktop and mobile. Desktop barely moved; mobile carried most of the value because readers reached that point after newsletter clicks. The redesign brief changed from “remove lower units” to “keep one lower mobile unit, but give it more breathing room.”

Mark policy and trust risks in plain language

The inventory should include a notes column for risk. Write it like an editor, not like a lawyer: “too close to download button,” “appears before the first paragraph on mobile,” “hard to distinguish from related links,” “refresh behavior needs review.”

That column is where monetization and editorial trust meet. A placement can earn money and still be wrong for the next version of the site. If a reader has to fight through two ads before seeing the answer promised by the headline, the theme is not reader-friendly.

The handoff should fit one page

The final artifact can be modest. Use one row per page type and placement: page type, device, current location, label, revenue range, risk note, redesign instruction, owner. Attach screenshots for the two or three highest-risk templates.

Before the design ticket moves to build, ask one question: “If this slot disappears or moves, who will notice first?” If the answer is nobody, remove it. If the answer is revenue, analytics, or an editor who owns a series, give the slot a decision instead of letting it drift.

Use this before the design ticket is opened

A Monthly Ad Policy Review Routine for Lean Teams, AdSense Layout Basics for Reader-Friendly Pages, and RPM, CPM, and Clicks: Ad Metrics Explained for Editors.

What to check after launch

Compare seven days before and seven days after, but do not panic over one metric. Look at page RPM, viewability, scroll depth, newsletter signup rate, and complaints from readers. If revenue rises while scroll depth collapses, the redesign may have created a short-term win with a long-term cost.

A good ad inventory map protects the redesign from guesswork. It lets the team change the theme with eyes open: which placements fund the work, which ones annoy readers, and which ones deserve to disappear.