Skip to main content

Pages performance

In plain English

This shows your 15 most successful pages on Google, and how they're doing.

Four things to understand:

  • Impressions — how many times your page showed up in Google results.
  • Clicks — how many times someone actually clicked it.
  • CTR — clicks divided by impressions, as a percentage. If 100 people saw your page and 5 clicked, that's 5%.
  • Position — roughly where you appear in Google's results. Position 1 is the top.

The most useful thing you can spot here: a page with a good position but a low CTR. That means Google is showing you near the top and people are choosing someone else. Usually that's because your page title and description are dull — and rewriting them is quick, cheap, and can multiply your traffic without changing your ranking at all.

How to use it

  1. Click "Daily Ops" in the left-hand menu, then the "Pages" tab.
  2. Look down the "Position" column for anything ranked 1, 2, or 3.
  3. Check the CTR next to it. At position 1–3 you'd expect roughly 10–35%. If it's under 5%, that's your quick win.
  4. Rewrite that page's title and description to be more appealing — say what the customer gets, not just the product name.
  5. Learn your top five pages by heart. If one disappears from this list one day, something has broken and you'll spot it immediately.
  6. For anything needing deeper digging, go to the GSC engine.

⏱ ~2 min · 💳 Pro+ · 🎯 Know which pages earn, without leaving your ops screen

Why this matters for your business

Search Console is a good tool with a bad daily-use property: it takes about ten minutes to answer a two-minute question. You want to know whether your money pages are still earning. Instead you get a date-range picker, a property selector, a dimension toggle, and a table that defaults to queries rather than pages.

So most merchants check it weekly at best, and a page that quietly lost half its clicks goes unnoticed for a fortnight.

This tab is the two-minute answer. Fifteen rows, sorted by clicks, already aggregated by page. It's on the screen you already open every morning, which is the entire reason it works — the best monitoring is the monitoring that's in the path you already walk.

It is deliberately not an SEO tool. There's no keyword breakdown, no filtering, no date comparison. When a row looks wrong you go to the GSC engine, which has all of that. This tab's job is to tell you that something is worth looking at.

What this typically unlocks

OutcomeTypical result
Frequency of checking page performanceDaily instead of weekly-if-remembered
Time to answer "are my money pages fine?"~2 minutes
CTR opportunities spottedContinuously — high impressions, low clicks stands out
Search Console logins neededNear zero for routine checks
Time to notice a page losing trafficDays, not weeks

What you actually get

Fifteen rows, five columns.

ColumnWhat it meansWhat to watch for
PageThe URLYour money pages should be here. If one isn't, that's the finding
ClicksVisits earned from searchThe ranking column — highest first
ImpressionsTimes the page appeared in resultsHigh with low clicks = title/snippet problem
CTRClicks ÷ impressions, as a percentageCompare against what's normal for the position
Avg positionImpression-weighted average rankWeighted, not naive — see below

Impression-weighted position

This is the detail that makes the column trustworthy.

A page typically ranks for many queries. A naive average treats them all equally, so a page ranking #3 for a query with 10,000 impressions and #60 for a query with 12 impressions would average to about #31 — a number that describes nothing real and looks alarming.

Weighting by impressions gives:

(3 × 10,000 + 60 × 12) ÷ 10,012 ≈ 3.1

Which is the honest answer: for the searches that actually happen, this page ranks around third. Long-tail queries where you rank poorly stop dragging down a page that's performing well on the queries that matter.

Reading CTR against position

CTR only means something relative to where you rank. These are rough reference points for evaluating a row:

PositionRoughly expected CTRWell below this means
125–35%Title or snippet isn't matching intent
2–310–18%Competitors have stronger snippets
4–65–9%Rich results above you are absorbing clicks
7–102–4%Normal — focus on rank, not CTR
11+< 1.5%Rank is the problem, not the snippet

A page at position 2 with 4% CTR is the single most actionable row you can find. You've done the hard part — ranking — and you're losing the click on the easy part. That's a title tag and meta description rewrite, and it can pay off within a crawl cycle.

What the tab deliberately doesn't do

Not hereWhere it lives
Per-keyword breakdown for a pageGSC engine → Pages
Date-range comparisonGSC engine
Ranking history over timeRank tracker
Pages 16 and beyondGSC engine
Decay detection and alertingDecay detection

How it works (without the technical bits)

Three properties worth knowing:

  • It reads a completed run. The tab never shows a half-finished import, so numbers don't shift under you mid-read.
  • The run timestamp is shown. You always know how fresh the data is — important because Search Console itself reports with a lag of a day or two.
  • The total page count is shown alongside the top 15, so you know whether you're seeing 15 of 40 or 15 of 4,000.

If no completed run exists yet — a newly-connected property, or a first import still in progress — the tab says so plainly rather than showing zeros that would read as a traffic collapse.

Real merchant scenarios

Scenario A — The position-2 page losing every click

Setup. Kitchenware merchant, daily glance at the Pages tab.

Page Clicks Impressions CTR Avg pos
/collections/cast-iron 412 31,200 1.3% 2.1

The anomaly. Position 2.1 with 1.3% CTR. Expected range at that position is 10–18%.

Investigation in the GSC engine showed the title tag read "Cast Iron | Store Name" — accurate and completely uncompelling — with no meta description, so Google was assembling a snippet from navigation text.

Fix. Rewrote the title to "Cast Iron Cookware — Pre-Seasoned, Lifetime Guarantee" and wrote a real meta description.

BeforeAfter 3 weeks
CTR1.3%11.8%
Clicks/month4123,680
Position2.12.0

Nine times the traffic with no ranking change. The page had been ranking well and failing to convert the impression into a visit for months.

Scenario B — The page that quietly vanished

Setup. Merchant's top blog post consistently sat at row 3 of the tab. One morning it wasn't in the top 15 at all.

Because the tab is a daily glance, this was noticed the next day rather than at the next monthly review.

Cause. A site migration had changed the URL slug without a redirect. The old URL was 404ing; the new one had no history.

Fix. 301 redirect in place within two hours.

Recovery. Back to row 4 within eleven days. Estimated traffic saved versus catching it a month later: roughly 14,000 sessions.

Why the format caught it. A dashboard showing "organic traffic is down 6%" would not have made this obvious. A fixed list of your top 15 pages makes an absence conspicuous — you notice what's missing from a short list you know by heart.

Scenario C — Impression-weighted position preventing a false alarm

Setup. Merchant's product page appeared to have "average position 34" in a third-party tool and panicked.

In this tab:

/products/merino-base-layer 890 22,400 4.0% 5.2

Why the difference. The page ranked for around 340 queries. Three high-volume ones sat at positions 3–6; the remaining 337 — long-tail phrases with a handful of impressions each — ranked between 40 and 90. The naive average was 34. The impression-weighted average was 5.2.

Which is right? 5.2. For the searches that actually happen, this page is on page one. The long tail is upside, not damage.

Outcome. A planned "rescue this page" project was cancelled. The team worked an actual problem instead.

Scenario D — Seeing what isn't there

Setup. Merchant had invested heavily in a new category page for a strategic product line.

Six weeks later it still wasn't in the top 15, despite having more content and better internal links than pages that were.

Cause. Found via the site crawler: the page was excluded by a stale rule in robots.txt left over from staging. It had never been indexed.

The lesson. The tab is as useful for absence as for presence. A fixed top-15 list makes "why isn't my most important page here?" a question you actually ask.

Best practices

Learn your top five by heart. Then an absence registers instantly, which is the fastest detection mechanism there is.

Scan CTR against position, not in isolation. 4% is excellent at position 8 and alarming at position 2.

Fix titles and meta descriptions before chasing rank. A CTR fix on a page already ranking is the cheapest traffic on the platform.

Check the run timestamp when a number surprises you — Search Console reports with a lag, so "yesterday" is usually the freshest possible.

Use this tab to decide whether to investigate, and the GSC engine to do the investigation. They're built for different jobs.

Note the total page count. 15 of 4,000 means the tab is showing the tip; 15 of 22 means you're seeing nearly everything.

Don't treat this as your SEO reporting. Fifteen rows, one run, no comparison. It's a glance, not a report.

Don't compare CTR across positions. The relationship is non-linear and the comparison is meaningless.

Don't panic at a single day's movement. Search Console data is noisy day to day; look for sustained change.

Don't assume missing means broken. A page can drop out of the top 15 because another page grew. Check the absolute clicks in the GSC engine before treating it as a loss.

Plan tiers

CapabilityFreeStarterProAgencyEnterprise
Top-15 page summary
Impression-weighted position
Run freshness timestamp
Full per-keyword drill-down
Decay detection + alerting
Multi-property roll-up

Frequently asked

Why only 15 pages? Because it's a glance on an operations screen, not a report. Fifteen fits without scrolling and covers the pages that matter for most stores. The full set is in the GSC engine.

Why don't these numbers match Search Console exactly? Search Console applies its own filtering and privacy thresholds, and this reads a completed engine run rather than a live query. Trends match; absolute figures can differ slightly.

How fresh is the data? As fresh as the last completed run, and the timestamp is shown. Search Console itself lags by a day or two, so same-day data doesn't exist at the source.

The tab is empty. No completed run yet — either the property isn't connected or the first import is still running. Connect it in the GSC engine.

Why is a page's position better here than in other tools? Impression weighting. Most tools average raw positions across all queries, which lets a long tail you rank poorly for drag down a page that performs well where it counts.

Can I see a page's keywords from here? Not in this tab — that's the GSC engine's page drill-down, which shows every query, its position, and its contribution.

Does this include paid traffic? No. Organic search only.

See also