The Weekly Audience Review That Fits on One Page
A one-page weekly audience review for small publishers covering acquisition, recirculation, newsletter behavior and revenue signals.


A weekly audience review should not feel like opening an airplane cockpit. Small publishers need a page that answers four questions: who arrived, what they did next, whether the newsletter relationship improved, and whether revenue signals changed enough to investigate. Anything beyond that can wait for a deeper monthly review.
The one-page format works because it creates editorial decisions. A dashboard that looks impressive but does not change the calendar is decoration.

Start with one sentence about the week
Start with a sentence, not a chart. "Search brought more new readers to two evergreen posts, but newsletter clicks fell after we led with a broad operations essay." That sentence tells the team where to look. It also prevents metric tourism, where everyone points at a different number and no one decides anything. The sentence can be imperfect. It just has to be specific enough to test.
Section 1: acquisition
Use three numbers: sessions or users by main channel, top three entry pages, and the one channel that changed most. If organic search rose, name the pages. If social spiked, name the post and source. If direct traffic jumped, check whether a newsletter or partner link was tagged incorrectly before celebrating brand demand. The acquisition question is simple: did the right readers arrive for reasons we understand?
Section 2: recirculation
Recirculation shows whether the site helped readers continue. Track internal link clicks if available, related-article clicks, or a proxy like pages per session on article entries. Then read the actual pages. Low recirculation may be a content issue, layout issue, or missing link issue. If a post about ad density does not link to ad inventory mapping, the fix is not a new dashboard. The fix is an internal link.
Section 3: newsletter
Track signup rate from article pages, clicks from the latest newsletter, unsubscribes, and replies if the list is small enough to read manually. Replies are messy data, but they often explain what cleaner numbers hide. A lower click rate may be acceptable if the email intentionally sent readers to a preference center. A higher click rate may be less impressive if unsubscribes doubled.
Section 4: revenue signal
Do not turn the weekly review into a revenue autopsy. Use directional signals: page RPM by top article group, ad viewability if available, sponsorship clicks if relevant, and any policy or layout issue noticed during the week. The useful question is whether revenue moved because reader behavior changed, inventory changed, or something broke. If you cannot answer, add an investigation task rather than guessing.
Meeting rhythm and decision log
Give the review 25 minutes: five to read the top sentence and numbers, ten to inspect the pages or emails behind the biggest movement, five to choose one editorial action, and five to assign ownership and review date. At the bottom of each weekly page, write the action and expected signal. That log protects the team from changing five things and learning nothing.
Read one article during the review
Numbers get sharper when the team opens a real page. If acquisition rose on one post, read the introduction and first internal link. If recirculation fell, inspect the mobile layout around the point where readers usually leave. If newsletter signups improved, look at the exact prompt and article context. The page often explains what the dashboard only hints at.
This habit also keeps the meeting editorial. Analytics can become abstract quickly, especially when people debate definitions. Opening one article reminds everyone that the goal is a better reader path, not a prettier report. The review is small on purpose: one week, one page, one decision, one page inspected closely enough to learn something.
The page should travel with the team. Save it beside the editorial calendar, not buried in an analytics folder. When an editor assigns next week’s work, the latest review should be close enough to influence the brief, the internal links, and the newsletter lead. Otherwise the review becomes a report instead of an operating habit.
Related reading
Use the weekly sheet alongside The Minimum Useful Analytics Dashboard for a Small Publisher, A Lightweight UTM Taxonomy for Independent Publishers, and RPM, CPM, and Clicks: Ad Metrics Explained for Editors.
The page should have a “so what” column
A weekly audience review is only one page if every metric earns its space. Add a “so what” column beside each section. Search rose, so what? Newsletter clicks fell, so what? Recirculation improved, so what? The answer should be an action or a deliberate decision to wait.
Save one comparison point
Compare this week with the prior week and the recent four-week pattern. That is enough for most editorial decisions. Year-over-year comparisons can help mature sites, but newer publishers often use them to create false precision. The one-page review should help the team move, not perform analytics sophistication.


