Compare Dates in Google Search Console Performance

Compare dates in Google Search Console Performance overlays two time windows so you can see whether clicks, impressions, CTR, or average position moved—not just what the last preset range totals say.

This page is about using the date comparison control. It is not GSC impressions without clicks (what zero-click visibility means). It is not improve organic CTR (how to win more clicks on the same ranking). It is not GSC average position for small blogs (how to read position in context)—though you will use that metric inside comparisons.

Direct answer: Turn on Compare in the Performance date filter, pick two equivalent ranges (or two custom ranges), read the delta columns in Queries and Pages, and note GSC lag before you react. Comparison finds trend questions; sibling owners answer what to fix.

Official: Performance report: advanced filtering and comparison and Performance overview.

Disclosure: Educational SEO. We do not invent traffic lifts, penalties, or earnings from GSC screenshots.

Table of contents

1. Why compare two date ranges
2. How to turn on date comparison
3. Which comparison windows are useful
4. Reading the chart and delta columns
5. Small-blog workflows that actually help
6. Misreads that waste your week
7. FAQ
8. Compare with a question, not a panic

Why compare two date ranges

The default Performance view shows one range—often the last three months. That is fine for a health check. It is weak when you need to know whether something changed after you shipped posts, adjusted titles, fixed coverage, or survived a quiet holiday week.

Date comparison answers movement questions:

• Did clicks on a money URL rise after a title edit, or did impressions fall too?
• Did a query you care about gain impressions without clicks—a pattern the impressions-without-clicks owner describes?
• Did average position drift on a cluster page while site-wide clicks looked flat?

Comparison does not tell you why Google moved. It tells you that the metric shifted between two windows you chose. The why step still needs Queries, Pages, Inspection, and honest content review.

If I am deciding whether a change was worth keeping, I compare the four weeks after the edit to the four weeks before—not a single weekend spike against a slow Monday.

How to turn on date comparison

In Search Console:

1. Open Performance → Search results for the property you track.
2. Click the date filter at the top of the report.
3. Open the Compare tab (wording may vary slightly; Google documents this under comparison filters).
4. Choose two periods—presets like last 28 days vs previous 28 days, or two custom ranges of similar length.
5. Click Apply.

The chart should show two lines (current vs comparison). The table below gains difference columns for supported metrics.

You can run only one comparison at a time in the UI. Adding a new comparison replaces the old one, per Google’s Help notes.

Keep search type (Web, Image, etc.) stable while you compare unless you deliberately want to measure a non-web slice. Mixing web and image in one story confuses everyone, including future you.

Which comparison windows are useful

Not every range pairing is equally honest. GSC dates use Pacific Time for most views, and recent days may be preliminary.

Google recommends Weekly or Monthly chart granularity when you compare date ranges that do not share the same weekday pattern—comparing a Monday-heavy week to a Saturday-heavy week on daily points can lie.

Avoid comparing a partial current day to a full prior day unless you know you are looking at hourly views and understand preliminary data rules from the dimensions and dates Help page.

Reading the chart and delta columns

With comparison enabled, treat each metric separately:

Clicks — Did more people choose your result? A click rise with flat impressions often means CTR improved—worth cross-checking against improve organic CTR before you celebrate.

Impressions — Did Google show you more often? Rising impressions with flat clicks can be discovery—or the Seen-Not-Clicked pattern. Do not auto-fix with Request indexing.

CTR — Derived from clicks ÷ impressions for that slice. Small impression counts make CTR swing wildly; do not rewrite titles because three impressions moved.

Average position — A rough depth average for the slice. Read it with impressions, as the average position guide explains—a better average with fewer impressions can still be noise.

Switch dimensions after comparison is on:

• Queries — Which searches gained or lost clicks between periods?
• Pages — Which URLs drove the site-wide delta?
• Countries / Devices — Did one device or region flip while totals looked stable?

Export if you need to annotate changes; Google’s common tasks Help mentions comparing timing of site changes to Performance shifts.

Small-blog workflows that actually help

After a title or meta edit on one URL. Filter Performance to that page URL. Compare 28 days before vs 28 days after the edit date (equal length). Look at clicks and CTR on the Queries tab for that page—not site totals. If clicks flatline but impressions rose, you may have visibility without choice; that is not proof the title failed alone.

Monthly sanity check. Last 28 vs previous 28 at Queries, sorted by impression delta. Note queries with impression gains and zero click gains—they may need intent or snippet work, not new URLs.

Post-publish check (calm version). New posts lag. Compare week-over-week too early and you will misread lag as failure. Give coverage time; use comparison to spot direction, not to demand instant clicks.

Core update window. Compare equal-length ranges straddling the update if you must—but remember SERP layout and competitors also moved. Comparison shows correlation timing; it does not isolate algorithm cause.

Misreads that waste your week

Treating comparison as a CTR fix guide. Movement tells you where to look. Fixing snippets is a different playbook on the CTR owner.

Reacting to incomplete recent days. Dotted or partial days are not a full verdict. Extend the range or wait for complete days before big rewrites.

Site-wide panic from one bad query. Filter to Pages. Often one URL or one head term moved while winners stayed steady.

Unequal ranges. Comparing 7 days to 90 days skews percentages. Keep windows the same length unless you have a documented reason.

Ignoring search type splits. Image impressions can inflate totals while web clicks fall. Compare within one search type when the decision is about blog posts.

Assuming pause in totals means deindex. Chart scale and waste impressions can flatten totals while Queries still show life—see your site’s GSC reality notes in workflow docs; zoom Queries before you ship clone posts.

FAQ

The frontmatter FAQ covers tool location, delta meaning, CTR disambiguation, comparison cadence, filters, flat charts, sibling owners, and penalty myths. Use those for schema; the body above is the walkthrough.

Compare with a question, not a panic

Pick one URL or query you already care about. Set an equal-length comparison that matches a real decision (before/after edit, or last 28 vs prior 28). Read Queries and Pages with delta columns. Write down one finding and one follow-up action—snippet work, content update, or wait for complete data.

Comparison is a disciplined question. It is not a reason to rewrite canonical tags, spam Request indexing, or clone a post because the totals chart looked flat for a week.