The Monthly Search Console Report Every Content Owner Should Run
Published · Eugene
The short version: open Search Console, switch the Performance chart from Daily to Monthly, and turn on Compare. Then run five checks, in order — your total clicks month over month, the pages that lost the most clicks, the pages that lost clicks while holding position, the queries that are rising, and whether last month's refreshes recovered. Fifteen minutes, five decisions.
That's the whole routine. Everything below is how to run each check and — more importantly — what to do with what it tells you.
What this report is for, and what it isn't
Two things get called a "monthly Search Console report," and they're different jobs.
One is a deliverable: a Looker Studio dashboard or a PDF that goes to a client or a boss at the end of the month. If that's what you're after, you want a template, not this article.
The other is a decision routine: fifteen minutes that tell the person who actually owns the content which pages need them this month. That's this one. Nothing here gets exported to impress anybody. Every check ends with a specific URL and something to do about it.
It's also deliberately not a site-health check. Most of what currently ranks for this topic — including Search Engine Land's monthly-metrics guide, which is a solid piece of work — walks you through indexing errors, Core Web Vitals, sitemaps and manual actions. That's a genuinely useful review, and it answers the question is my site broken? This routine answers a different one: which of my pages are quietly losing traffic, and what do I do about them? I run this on my own sites, by hand, in the free tool.
First: switch the chart to Monthly
Do this once and the rest of the routine gets easier.
In the Performance report, look at the chart area for a drop-down that says Daily. Click it and choose Monthly. Google added weekly and monthly views in December 2025, and they're free to everyone, on Search results, Discover and Google News.
It matters more than it sounds. Google's own note on the feature says it's "particularly powerful when comparing date ranges" — because when you compare one period against another at daily granularity, the weekends don't line up, and the chart turns into a sawtooth you have to squint through. At monthly granularity that noise disappears and you can see the actual line.
One small thing to know: Google also changed the export file structure slightly to match the granularity you pick, so if you keep a spreadsheet from month to month, expect the tab names and column headers to have shifted.
Now turn on Compare in the date picker and set this month against last month. That's your setup. Everything below happens in this one report.
Check 1 — the one trend number (2 minutes)
Read one number: total clicks, this month versus last.
You're not looking for a target. You're answering a single question — is this a wobble, or a slope? One down month on its own means very little. A third consecutive down month is a trend, and it's the signal to keep reading rather than close the tab.
If the drop is sudden, site-wide, and steep — everything fell at once, in the same week — stop running this routine and go diagnose it as an event instead. That's not decay; that's a cliff, and Google's guide to debugging Search traffic drops is the right starting point. Decay is a slope across individual pages while your site total looks almost fine, which is exactly why nobody notices it.
The decision: carry on, or switch to diagnosing a sitewide event.
Check 2 — which pages lost the most clicks (5 minutes)
This is the heart of it. With compare mode still on, click the Pages tab and sort by Clicks Difference until the biggest losses sit on top.
Two rules keep this list honest, and they're the ones I use as thresholds in my own work:
- Roughly 20% or more below the page's baseline. Pages have a normal range. Decay is dropping out of it and staying there.
- At least about 10 clicks a week. A page earning three clicks can "lose 67%" because two people didn't search. That's noise. Below the floor, percentages are meaningless.
Then rank what's left by clicks per month at stake, not by percentage — because a page that lost 40% of its 20 clicks matters less than one that lost 15% of its 800. Multiply the weekly gap by 4.33 to get the monthly figure.
Worth noting that Google agrees with the principle. Its documentation for Search Console Insights states that trending items are ordered "based on an increase or decrease in the number of clicks, not the percentage change." Absolute clicks lost is the honest ranking.
The full click-by-click version of this sweep — which windows to compare, how to keep a seasonal page from reading as a dying one — is its own walkthrough: how to find declining pages in Search Console. And once you have the ranked list, which blog posts to update first covers what to do with the top of it.
The decision: one, maybe two pages to refresh this month. Not ten.
Check 3 — which pages lost clicks but held position (3 minutes)
Now read a second column on those same rows, because two very different problems look identical in the clicks number.
- Clicks down, position held → you're still being shown as often, and chosen less. That's a title and meta description problem, and it's the cheapest fix in this entire routine — an hour, no rewrite.
- Clicks down, position dropped too → you've lost ranking. A new title won't save it; the page needs real work.
I treat a slip of a full position or more as a real ranking move, and a CTR drop of 15% or more as a real click-through problem. The full diagnosis lives in high impressions, low clicks.
There's a newer possibility to hold in mind here. If your position is steady and your CTR is sliding anyway, the result page itself may have changed shape around you — an AI Overview now answering above the blue links. Google began rolling out generative AI performance reports in June 2026, showing how often your URLs appear in AI Overviews and AI Mode. Two caveats before you go looking: they're going out to a subset of sites first, so you may simply not have them yet, and they currently report impressions only — no clicks, no CTR, no queries. Useful context, not yet a measurement.
The decision: title rewrite, or full refresh.
Check 4 — what's rising (2 minutes)
One check that isn't about decay, because the cheapest content decision you'll make all month is usually hiding here.
Sort the Queries tab by clicks gained instead of lost. You're looking for a query you're getting impressions on that you never deliberately wrote for. When you find one, you have a choice that costs almost nothing: add a section to the page already ranking for it, or write the piece properly.
Pages drift into queries you never targeted. Noticing early is free.
The decision: one section to add, or one post to write.
Check 5 — did last month's refresh work? (3 minutes)
This is the check nobody else's monthly routine includes, and it's the one that makes the rest of it compound.
Take the page you refreshed last month. Filter the Performance report to that single URL, set compare mode to the 28 days after your edit against the 28 days before it, and read the clicks.
Two honest caveats. First, don't look too early — I don't trust a reading with less than a week of after-data, and 4 to 8 weeks is where the number gets meaningful, because rankings move before clicks do. Second, you need the edit date written down. Not roughly remembered. If you don't record it when you publish the change, you'll be guessing at the window a month later, and a guessed window makes the whole comparison worthless.
The method, including the three ways this measurement will quietly lie to you, is how to tell if a content refresh actually worked.
The decision: you now know whether your refresh playbook works — which tells you what to do to the next page, instead of relearning it every time.
Where Search Console Insights fits
Google gives you a partial version of this for free. Search Console Insights automatically surfaces which of your content is trending up and trending down, and groups similar queries together on larger sites. It's a genuinely good starting point, and if you do nothing else, open it.
Where it stops is the part that decides your afternoon. Insights tells you a page is trending down; it doesn't tell you whether that drop clears a threshold worth acting on. It doesn't rank your pages by the clicks per month now at stake. It has no view of what you changed, so it can't tell you whether last month's refresh worked. Insights is the what. The five checks above are the so what.
What this routine deliberately skips
Being honest about the edges:
- Site health. Indexing errors, Core Web Vitals, sitemaps, manual actions — all real, all worth checking, none of them in here. Google's basic Search Console usage guide is a better starting point for that, and quarterly is usually often enough unless something's on fire.
- Seasonal pages. Month-over-month will slander them every time. Tax content falls off in May; gift guides fall off in January. For those, use the 16-month window and compare against the same month a year earlier.
- The row limit. The Search Console interface shows up to 1,000 rows per report. On a large site, that's a real ceiling on the Pages and Queries tabs — worth knowing before you conclude a page has vanished.
The hard part isn't the fifteen minutes
It's the twelfth month.
Running this once is easy and genuinely useful. Running it every month — remembering the edit dates, keeping the export, noticing the page that's slipped 8% three months running — is bookkeeping, and bookkeeping is the thing that quietly stops happening after a busy fortnight. That's not a character flaw. It's the entire reason content decay works: it's slow enough that skipping one month never feels like it cost you anything.
That's the job RefreshRadar does instead. It watches every page in your Search Console continuously, applies the same rules this routine uses — the 20% drop, the 10-clicks-a-week floor, the position and CTR splits — and emails you the ranked list with the reason in plain English and the clicks per month at stake. When you mark a page updated, it runs check 5 for you.
Connect Search Console read-only and see your three worst-decaying pages — free — no card, about 30 seconds, and we never post or change anything. Think of it as running this month's report without having to remember to. If nothing on your site is decaying, we'll tell you that instead.
FAQ
Frequently asked
How often should I check Google Search Console?+
Once a month is the right cadence for content decisions. Search Console data settles over a few days, and clicks bounce around week to week for reasons that have nothing to do with your writing, so checking daily mostly feeds you noise. Keep Google's email alerts switched on for genuine emergencies, and give the back catalog fifteen deliberate minutes a month.
What should I look at in Search Console each month?+
Five things, in this order. Your total clicks this month against last month. The pages that lost the most clicks. The pages that lost clicks while holding their ranking position, which is a title problem rather than a content problem. The queries that are rising. And whether the pages you refreshed last month actually recovered. Each of those ends in a decision about a specific page.
How do I see monthly data in Search Console?+
Open Performance, then Search results, and look for the drop-down in the chart area that says Daily. Google added weekly and monthly options there in December 2025. Switching to Monthly aggregates the chart by calendar month, which makes month-over-month comparisons far easier to read because the weekday pattern stops distorting the shape.
How far back does Search Console data go?+
Sixteen months. That is the full window Search Console keeps, and it is why a year-over-year comparison is always available to you for any page older than a year. Use it whenever a page has a season, because comparing December to November will make every seasonal page look like it is dying.
Is Search Console Insights enough on its own?+
It is a good starting point and it costs nothing. Insights automatically surfaces which of your content is trending up and trending down, ordered by the change in clicks rather than the percentage change. Where it stops is the part that decides your afternoon. It does not tell you what size of drop is worth acting on, it does not rank pages by the clicks per month now at stake, and it never checks whether the fix you shipped last month worked.