How Do You Find the Pages Losing Clicks in Search Console?

How do you find which pages are losing clicks in Google Search Console?

Open the Performance report for Search results, set the date filter to compare two equal periods, switch to the Pages tab, and read the Difference column. Export the table and sort by click change. The pages with the largest drops are where to start, before you rewrite anything or blame an algorithm update.

This tutorial is for one specific situation. You run marketing for a B2B company with a site of roughly 50 to 500 pages. Someone noticed organic traffic is down in your analytics tool, and you have been asked to explain why. You have Search Console access but have mostly used it to check that the site is indexed.

The goal is to go from "traffic is down" to a short list of pages, the queries they lost, and a likely cause for each. That list is what turns a vague worry into a plan, and it takes less than an hour once you know the steps.

Why should you start with Search Console instead of your analytics tool?

Search Console shows what happened inside Google Search itself: impressions, clicks, click-through rate, and average position, by page and by query. Analytics shows visits after the click. If clicks fell, Search Console tells you whether you were shown less, clicked less, or both, which points to different fixes.

Google's Performance report documentation defines clicks as the number of times a user clicked your site from Google Search results and impressions as how many times your site appeared in results. It defines CTR as clicks divided by impressions, and average position as the average position of the topmost result from your site.

Those four numbers are the whole diagnosis. A page that lost impressions is being shown less, often because of ranking changes or lower demand. A page that kept impressions but lost clicks is being shown but chosen less, which points to the search result itself. I always separate those two before deciding what to do.

Step 1: How do you set up the date comparison?

In the Performance report, open the date filter, choose Compare, and pick two periods of equal length. I usually compare the last 3 months with the same 3 months a year earlier, which removes seasonality. If the drop is recent, compare the last 28 days with the previous 28 days instead.

Google's help article on advanced filtering and comparison says you can have only one comparison at a time, and adding a new comparison filter replaces the existing one. It also recommends weekly or monthly granularity when comparing two ranges, because aggregating by week or month neutralizes the day-of-the-week effect.

That granularity tip matters more than it sounds. B2B sites often get far less search traffic on weekends. If your two periods have a different number of weekends, a daily chart will show fake swings. Switching to weekly views makes the real trend visible.

Step 2: How do you find the pages that lost the most clicks?

With the comparison active, click the Pages tab below the chart. The table now includes a Difference column. Export the table, open it in Google Sheets or Excel, and sort by the click difference from most negative to least. Your top ten losers are the working list.

Google's documentation notes that when you compare, the results table displays a Difference column for each row. Many Search Console reports also provide an export button for chart and table data. I prefer working in a spreadsheet at this point, because I want to add my own notes and columns next to each page.

Before going further, check whether the losses are concentrated or spread out. If three pages explain most of the drop, you have a page problem. If every page dropped by a similar share, you may have a site-wide issue, such as an indexing problem, a tracking change, or a broad shift in demand, and page fixes will not solve it.

Step 3: How do you tell whether a page lost rankings or lost clicks?

For each losing page, compare its impressions, CTR, and average position across the two periods. Falling impressions with a worse position means a ranking loss. Steady impressions with falling CTR means the result is being shown but chosen less. Add a column in your sheet labeling each page with one of those two patterns.

The ranking-loss pattern usually traces to competition, content that went stale, or a technical change like a broken internal link or a changed title. The CTR-loss pattern is different. It often means the search results page changed around you, for example new features above your listing, or that your title and description stopped matching what searchers want.

I covered the bigger picture of results that answer the query without a click in my piece on zero-click search strategy. When a page shows the CTR-loss pattern, that article explains why rewriting the page body may not help, and what to change instead.

Step 4: How do you find which queries each page lost?

Add a page filter for one losing page, using the URL filter with the page address, then switch to the Queries tab with the comparison still active. The Difference column now shows which queries drove the loss for that one page. Usually two or three queries explain most of it, and those tell you what the page stopped winning.

Google's comparison documentation notes that filtering by query or URL can affect report totals because of data truncation and the omission of anonymized queries. So do not expect the query rows to add up exactly to the page total. Use them to find the pattern, not to reconcile every click.

Read the lost queries carefully. If they are informational questions, the page may be losing to AI-generated answers or to a better guide. If they are commercial queries like a product category plus "pricing" or "software," the loss matters more for pipeline and deserves attention first.

Step 5: How do you decide what to fix first?

Rank the losing pages by business value, not by click loss alone. A pricing, comparison, or product page that lost 40 clicks may matter more than a blog post that lost 400. Mark each page with its role in the funnel, then fix the high-intent pages first and accept some losses on low-intent ones.

This is where Search Console data meets your CRM. If you track which pages lead to demo requests, you can weight each loss by its likely pipeline impact. I wrote about how to find out which SaaS blog posts lead to demo requests, and that list is the best way to decide which drops actually hurt revenue.

For each high-value page, write one sentence on the likely cause and one action. "Ranking loss on pricing comparison, competitor published a newer guide, refresh with current plans." That sentence becomes a ticket. A list of ten of those is a far better report to leadership than a chart of falling traffic.

What mistakes should you avoid when reading the comparison?

Do not compare periods of different lengths, and do not read the newest days as final. Google notes the newest data can be preliminary and may change over the next few hours. Also avoid reacting to small drops on low-traffic pages, which often reflect normal variation rather than a real problem.

The preliminary data note comes from the same Performance report documentation, which says preliminary data appears as a dotted line on the chart. If your comparison ends today, the last day or two may look worse than they will once data settles. I end comparisons a few days back when precision matters.

The other mistake is skipping the site-wide check. If tracking broke, a redirect chain changed, or pages dropped out of the index, you will see losses everywhere. Before you rewrite content, confirm the pages are still indexed and that nothing in your site setup changed in the period. My guide to finding schema errors in Search Console covers another technical check worth running at the same time.

What should you do next?

Run the comparison today: last 3 months versus the same period last year, Pages tab, exported and sorted by click difference. Label each of the top ten pages as a ranking loss or a click loss, list the lost queries, and pick the three highest-value pages to fix this month.

Then save the setup so you can repeat it. A monthly version of this check catches drops while they are small, before they show up as a missed pipeline target. It is one of the simplest habits I know for keeping organic search honest.

If you want help turning your Search Console data into a prioritized fix list, or connecting it to the pages that actually create pipeline, reach out through pravinkumar.co. I build websites and the automations behind them for lead generation, and SEO diagnosis is part of that work. Let's chat.