Prism
Start free
Search Performance · Opportunities

The queries sitting just off page one.

Queries you already rank for at positions 11 to 20, with enough impressions behind them to be worth the work, valued against the click-through rate your own site earns at the positions above them.

The band, and the bar

Positions 11 to 20, seen on at least five days.

Striking distance is an easy list to pad. Every threshold Prism applies is exported from the code that applies it and shown on the report, so you can tell why a query you expected is absent.

An average position of 10.5 to 20.5
Page two and the top of page three. Past that, getting to page one is not an improvement, it is a different page.
Seen on five days or more
A query Google showed you on one or two days has an average position that is an accident of when it was seen, not a ranking.
An impression floor that scales
The minimum scales with the length of the window rather than being a flat number, because 50 impressions means something very different over a week than over sixteen months.
Joined to the page that ranks
Each query carries the on-page state of the URL ranking for it, read from your last crawl, so you can see whether the fix is the page or the query.
The curve

Valued against your click-through rate, not an industry table.

The upside of moving a query is worth nothing if the number behind it came from somebody else's data. Prism fits the curve on your rows, every time the report runs.

Your own median, per position
Every qualifying row on the property is grouped by ranking position, and the median click-through rate in each band becomes the expectation for that band.
Bands that cannot be judged say so
A position band with fewer than eight qualifying rows is reported as unusable and its rows are excluded, rather than being measured against noise.
No purchased benchmark
There is no industry click-through table in Prism, because we cannot source one that would survive being questioned. Your own rows are the only curve that describes your own snippets.
Prism's Opportunities report: queries in striking distance of page one, pages earning below their expected click-through rate, and pages in sustained decline, each with its clicks, impressions and position.
Search Performance → Opportunities

Two more lists on the same report.

Below your own curve. Pages earning materially less than the median for the position they rank at. A row is flagged only when it is both well under that median and far enough from it to be distinguishable from chance, and only when recovering would be worth at least one click. Either test alone flags half the site.

In sustained decline. Pages tested across six consecutive 28-day periods with a trend test rather than a comparison of the first and last. A page that dropped once and recovered is not decaying, and one collapsed month cannot put a page on this list on its own.

the positions striking distance covers
11-20
the positions striking distance covers
days a query must have been seen on
5
days a query must have been seen on
days of history the decay test reads
168
days of history the decay test reads
credits used by the report
0
credits used by the report

Frequently asked questions

What counts as striking distance?

An average position between 10.5 and 20.5 over the window, which is page two and the top of page three. A query also has to have been seen on at least five days, because an average position built from one or two days is an accident of when Google happened to show you, and it has to clear an impression floor that scales with the window rather than a flat number.

How is the upside worked out?

Against your own click-through curve, not an industry table. Prism takes every qualifying row on the property, groups them by ranking position, and uses the median click-through rate in each position band as the expectation for that band. A band with fewer than eight qualifying rows is reported as unusable rather than being judged against noise. The upside of a query is what its impressions would earn at the bottom of page one on your own curve.

Why not use a published CTR benchmark?

Because we cannot source one. A benchmark table would be a number on your report that nobody here can defend, and a brand query and a comparison query at the same position behave nothing alike anyway. Your own rows are the only curve that describes your own snippets.

What else is on the report?

Two more lists. Pages earning materially less than your curve says they should, flagged only when they are both well below the median for their band and statistically distinguishable from it. And pages in sustained decline, tested over six consecutive 28-day periods with a trend test, so one bad month cannot put a page on the list.

The first list is usually the shortest route to more clicks.

Connect Search Console and Opportunities is there on the first sync. Striking distance, defined.