Google Search Console‘s Performance report tracks how your site shows up in Google Search, and it lets you slice that data by query, page, country, device, and date. When I'm digging into why a page's traffic moved, the first decision I make is which single dimension actually answers the question — query, page, country, or date — before I touch the Compare tool. Mixing dimensions too early is the fastest way to end up staring at numbers that don't mean anything.
This guide walks through what each filter measures, how comparison works, and where its limits are, based on Google's current Search Console documentation.
Terms to Know Before You Start
- Dimension: A category you can group your data by. Search Console's Performance report offers six: queries, pages, countries, devices, search appearance, and dates.
- Query: The exact words someone typed into Google before your page showed up in the results.
- Page: A specific URL on your site that appeared in a search result.
- Filter: A rule that narrows the report to only the rows matching a condition you set — one country, one device type, a query containing a certain word, and so on.
- Compare: A Search Console feature that places two values from the same dimension next to each other — two date ranges, two countries, two pages — with a difference column showing the change between them.
- Clicks, impressions, CTR, position: The four core metrics attached to every dimension. CTR (click-through rate) is clicks divided by impressions; position is the average ranking spot Google assigned for that query or page.
How the Four Main Filters Differ
Each filter answers a different question, and in practice, treating them as interchangeable is the most common reason people misread their own reports.
- Queries show you the exact search terms tied to your clicks and impressions. Use this filter when you want to know what people typed to find you, or to check how one keyword is performing over time.
- Pages show you which specific URLs are earning the visibility. Use this filter when you want to know whether a page — a blog post, a service page, a listing — is gaining or losing ground, independent of which query brought people there.
- Countries show you where in the world your impressions and clicks come from. Use this filter to see whether content resonates differently outside your primary market, or to confirm a page meant for one region isn't quietly ranking somewhere it shouldn't.
- Dates show performance across a time window you choose, broken down hourly (for the most recent 24 hours), daily, weekly, or monthly. This is the backbone for almost every other comparison, since the real question is usually “compared to when?”
Search Console also supports filtering by device and search appearance, but queries, pages, countries, and dates are the four I reach for first when something looks off.
A Step-by-Step Field Guide to Filtering and Comparing
- Open the Performance report and decide the single question you're answering first. Trying to answer three questions with one filter setup is how reports get confusing fast.
- Add a filter from the filter panel at the top of the report, then choose the dimension — query, page, country, device, or search appearance — you want to narrow by.
- For queries and pages specifically, you can filter by an exact match, a “containing” or “not containing” match for part of the text, or a regular expression (a pattern-matching syntax) if you need more precision. Filtering by query or URL can shift your report totals, since Google truncates some low-volume query data for privacy reasons.
- Turn on Compare from the filter panel to place two values from the same dimension side by side — two date ranges, or one country against another. Search Console adds a difference column so the change is visible at a glance.
- Know the one-comparison rule. You can run only one active comparison at a time. Comparing dates and then comparing countries means two separate passes, not one combined view.
- Set your date range using the date filter at the top of the report. You can view the current day hourly, or step back through daily, weekly, and monthly views for longer trends. Search Console's historical window doesn't go back indefinitely, so very old comparisons usually aren't available inside the report itself.
- Read clicks and impressions together, not separately. A query with rising impressions but flat clicks often points to a ranking or snippet issue rather than a demand problem. A page with rising clicks but falling average position may just be catching more overall search volume.
What the Compare Feature Won't Tell You
Compare is good at showing you that something changed. It doesn't tell you why. A drop in clicks for a page could come from a ranking shift, a seasonal dip in search interest, a technical problem like a broken redirect, or something else entirely. I treat the Performance report as the starting point for an investigation, never the conclusion. If a comparison shows a real shift, the next move is usually checking the affected page or query on its own, confirming it's still indexed correctly, and looking at what else changed around the same time.
Educational Disclaimer
This article explains how Google Search Console's built-in filtering and comparison features work, based on Google's current published Search Console Help documentation. It's general educational information, not a guarantee of any specific ranking, traffic, or business outcome. Search Console's interface and features change over time, so always check the tool directly for its current options.
Sources
- Google Search Console Help: Performance report — Advanced filtering and comparison
- Google Search Console Help: Performance report — Overview and basic setup
- Google Webmaster Tools 101: An Overview — background on the tool Search Console evolved from and how it fits into monitoring your site's search presence.
- What Is SEO? — a foundational primer if you're new to search optimization concepts referenced in this guide, like queries, rankings, and click-through rate.
Last updated: September 16, 2026.
Leave a Reply