SEO KPIs: the short list worth reporting, and where each number comes from
Most SEO KPI lists are just every metric a dashboard can show, renamed as if picking all of them were a strategy. This one is shorter on purpose: six KPIs worth putting in front of a client or a manager, an explicit list of the metrics to stop reporting, and — for every KPI that survives — where the number actually comes from. If you haven’t settled what a report should look like once the KPIs are picked, see our SEO report template guide; if the question is how often to send it and what to say on the call, that’s SEO client reporting.
Picking the KPI set is the decision that quietly decides which tool you need, because two of the numbers below can’t come from a free, unmodified Search Console account at all. This guide names both halves plainly: what’s free, and what genuinely requires something more, rather than implying every metric needs a paid dashboard. For the wider question of what to monitor day to day beyond a fixed KPI report, see our SEO monitoring dashboard guide.
What makes a KPI a KPI, not just a metric
Every KPI is an SEO metric, but not every SEO metric deserves to be a KPI. A metric is anything you can count — impressions, backlinks, word count, page load time. A key performance indicator is a metric you’ve deliberately chosen to track over time because it connects organic search work to something a client, a manager, or the business itself actually cares about: leads, revenue, pipeline, or a defensible claim of ROI.
That distinction matters more than it sounds. Core Web Vitals scores and PageSpeed numbers are metrics worth watching for site health, but they’re diagnostic — you fix them when they’re bad and otherwise leave them alone. They’re rarely the line a client asks about on a call. A KPI, by contrast, is a number you’d be uncomfortable not being able to explain a change in, because someone is going to ask about it whether you report it or not.
Two tests are useful for deciding whether something belongs on your short list. First, can you explain a move in this number in one sentence tied to a real cause — a ranking change, a seasonal pattern, a site change — rather than “the algorithm did something”? Second, does moving this number change what anyone does next? If a KPI moves and nobody adjusts a budget, a page, or a priority because of it, it’s a metric, not a KPI. Our best SEO monitoring tools guide covers what different tools track if you’re still deciding what’s worth watching at all before you commit to a report.
SEO KPI guide: the six worth reporting
Six KPIs cover the questions a stakeholder actually asks: is organic search working, is it improving, and is it worth the spend. Each one below states what it measures, how it’s calculated, and why it earns a place on a short list rather than a long one.
Organic conversions
This is the KPI that answers “is organic search worth it,” and it’s the one that shows up most often on pages that rank for this topic. An organic conversion is a key event — what Google Analytics 4 calls a key event, formerly labeled a conversion — triggered during a session that arrived through organic search. A key event is any action you’ve explicitly marked as important to the business: a purchase, a form submission, a signed-up trial, a phone-number click.
Organic conversions matter more than raw organic traffic because traffic without a downstream action doesn’t pay anyone’s salary. A page that halves its organic sessions but doubles its organic conversion rate is a page doing its job better, not worse — and a KPI report built only on traffic would show that as a decline. Report the count and, where volume supports it, the conversion rate for organic sessions specifically, not blended across every channel.
Click-through rate (CTR)
CTR is clicks divided by impressions for a page or query, and it’s defined directly in Search Console’s own performance documentation: a high CTR means your listing matches what people searching for that term actually want, at the position you’re ranking in. It’s the second most common individually named KPI on pages that already rank for this topic, and it earns that spot because it isolates a specific lever — the title tag, the meta description, rich results — from ranking position itself.
CTR has to be read alongside position, never alone. A 2% CTR at position 3 is a real problem worth a title rewrite; the same 2% CTR at position 19 is close to what you’d expect and not evidence of anything broken. Report CTR per query cluster or page type rather than as one blended site-wide number, which tends to hide exactly the pages where a fix would move the needle.
Organic clicks and impressions
Clicks and impressions are the two rawest numbers Search Console reports, and together they’re the baseline every other organic KPI is calculated from — clicks divided by impressions is CTR, and the click trend over time is the closest thing to “organic traffic” that Search Console itself can show natively. Report them together, not separately: impressions rising while clicks stay flat usually means new rankings that haven’t earned trust yet, and clicks rising while impressions stay flat usually means CTR improved on the same visibility.
Treat impressions on their own with caution. A spike in impressions with no corresponding click growth is not automatically good news — it can just as easily mean Google started showing your page for queries it isn’t actually a good match for, which shows up as impressions with a falling average CTR rather than genuine growth.
Average position
Average position is Search Console’s own weighted-average ranking figure across every query and page combination in the reporting window, and it’s a fundamentally different number from what a dedicated rank tracker reports. It’s not a daily snapshot of where you rank for one keyword — it’s an aggregate across every query that surfaced your page at all, which means a handful of long-tail queries at position 40 can drag down the average even while your priority terms hold steady in the top five.
Report average position segmented by a query group you actually care about — branded, a specific topic cluster, or your priority keyword list — rather than as one property-wide number. A property-wide average position is nearly always the least useful number in the whole report, because it blends terms you’re actively targeting with thousands you aren’t.
Average engagement time
Average engagement time has no equivalent inside Search Console — it’s a Google Analytics 4 metric, calculated from time your site is in a user’s foreground across their engaged sessions, which GA4 defines as a session lasting longer than ten seconds, containing a key event, or including at least two pageviews. It’s the third most commonly named individual KPI on pages that already rank for this topic, and it’s the closest free proxy most reporters have for content quality once a visitor has actually landed.
Segment engagement time by organic traffic specifically, and by landing page, rather than reporting a single site-wide average. A blog post with strong engagement time and a product page with a fast, intentional exit both look “normal” for their type — comparing them against one average tells you nothing useful about either.
Branded versus non-branded split
This one is doable manually and worth doing: filter Search Console’s query report to isolate traffic containing your brand name from everything else. Branded search reflects existing demand and marketing spend elsewhere; non-branded search reflects new demand your organic work is actually creating. Reporting a blended traffic or click number without this split lets branded growth quietly cover for stalled non-branded performance, which is precisely the number a client is paying you to move.
The catch is consistency, not capability. Filtering one month by hand in the Search Console UI is a five-minute task; rebuilding that same filtered view every reporting period, across every property you manage, without it silently drifting when brand terms change, is where this KPI stops being free in practice even though the underlying data always was.
The metrics to stop reporting
A KPI report earns trust by what it leaves out. These show up constantly in SEO reporting decks and rarely survive contact with either of the two tests above — name them as vanity metrics rather than quietly dropping them, because a client who’s used to seeing one will otherwise assume its absence is an oversight.
Total keywords ranked, or “keywords in the top 10.” A bulk count rewards adding more tracked keywords, not better rankings on the ones that matter. A property tracking 10,000 keywords will always beat one tracking 200, regardless of which business is actually growing.
Domain Authority or any third-party authority score. These are proprietary scores built by SEO tool vendors, not a metric Google publishes, computes, or uses in ranking. They correlate loosely with size and link count, and reporting one as if it were a Google signal misrepresents what it measures.
Raw impressions on their own. Impressions without a CTR or click context can rise for reasons that have nothing to do with quality — Google testing your page for queries it’s a weak match for shows up as impression growth too. Pair it with CTR or drop it.
Backlink counts without qualitative context. A rising backlink count is easy to report and easy to game with low-quality links that do nothing for rankings. If backlinks matter to the story, report referring domains from sites with real relevance, not a raw total.
Pageviews without an engagement signal. A pageview with no time on page and an immediate exit is not evidence anything worked. Pair pageviews with average engagement time or a completion event, or leave them out.
Social shares as an SEO metric. Social shares measure social distribution, not search performance. They belong in a social report, not an SEO one, even when the same content drives both.
Where each number comes from
The honest, and usually skipped, part of a KPI report is naming which numbers are free, which need a second platform, and which need history Search Console itself no longer holds. Search Console retains a limited window of performance data before older rows age out of the account entirely — that ceiling is the reason the last column below exists.
KPI
Free in Search Console
Needs GA4
Needs retained history
Average position
Yes
No
For trends beyond the retention window
Click-through rate (CTR)
Yes
No
For trends beyond the retention window
Organic clicks and impressions
Yes
No
For trends beyond the retention window
Branded versus non-branded split
Yes, with manual filtering
No
For a consistent trend across periods
Average engagement time
No
Yes
Bound by GA4’s own retention settings
Organic conversions
No
Yes (key events)
Bound by GA4’s own retention settings
The first four rows are entirely free and always will be — nothing about them requires a subscription. What they don’t survive is time: Search Console retains 16 months of performance history and no more, a limit documented in Search Console’s own performance report guidance, and the account only ever holds that rolling window rather than an indefinite archive. Once a month ages past the 16-month mark, no export you didn’t already run can bring it back, and neither the Search Console UI nor its API can query it after the fact — Google’s own explainer on performance data filtering covers the row and export limits alongside the filtering behavior that shapes what’s visible even inside that window.
That retained-history gap is the honest place a paid tool enters this article, not the free-versus-paid rows above it. If a client asks for a year-over-year comparison and the relevant month already aged out of Search Console, the fix has to have happened before that month disappeared — either you were exporting on a schedule, or you’re using a tool that keeps its own longer copy of the same data. The cheaper plan retains Search Console and GA4 history past the point Google’s own interface drops it, which is what turns “we don’t have that comparison” into a report you can actually send. The higher plan extends that retention further and adds the branded-versus-non-branded splitting and scheduled reporting that otherwise means rebuilding the same filtered view by hand every period. Neither plan invents a new metric — they preserve and automate numbers Search Console and GA4 already produce for free.
SEO Gets Core — Search Console and GA4 in one view
Core is the first paid tier, listed at $39 per month, and the thing it changes is
that search data and behaviour data stop living in two separate tabs. It connects
Google Analytics 4 alongside Search Console, then layers on the reports that are
tedious to reproduce by hand: striking distance, keyword cannibalization, and
content decay. The client-facing half is what most agencies actually buy it for —
live portals shared by link, scheduled reports that send themselves, and PNG
export carrying your own branding rather than a vendor logo.
What to check
Vendor: SEO Gets
Plan level: first paid tier, above the free plan and below Pro
Check before buying: whether you specifically need GA4 alongside Search
Console, whether anyone will actually open the client portals, and whether the
opportunity reports tell you something your current process does not
Who it suits
The reader who has outgrown exporting Search Console by hand every month but has
not yet hit the retention wall. That is usually a freelancer or a small agency
reporting on several client properties, where the saving is measured in hours per
client per month rather than in any single feature. Connected properties and team
seats are unlimited on every tier including Free, so this plan is not a way to buy
more capacity — it is a way to buy the reports and the client-facing output.
Be aware
History stays at 16 months on this tier, matching Search Console’s own limit, so
if the problem you are solving is a year-over-year comparison that already aged
out, this plan does not solve it. Index reporting for indexed pages is a Pro
capability and is not included here either. And the free plan is a genuinely
working Search Console dashboard, so the honest question before paying is whether
GA4, the client portals or the opportunity reports are worth $39 a month to you
specifically — not whether the paid tier is better in the abstract.
SEO Gets Pro — the tier that removes Search Console’s ceilings
Pro is listed at $49 per month and exists to lift the two limits that eventually
stop everyone: Google Search Console retains 16 months of performance data and
throttles its API, and no dashboard built on top of it can invent history the
source no longer holds. This tier retains up to five years, removes the Search
Console API request limit, and adds index reporting so the number of pages Google
actually has indexed becomes something you can watch move rather than something
you spot-check. It also introduces the Super Site concept, extended storage, and
content change tracking.
What to check
Vendor: SEO Gets
Plan level: top tier, above Core
Check before buying: how old the site is, how many properties genuinely need
long history, and whether anyone will act on index reporting once they have it
Who it suits
The reader whose reporting question is historical — year-over-year comparisons,
the shape of a site before and after a core update, or an argument that has to be
made with data older than Search Console keeps. It also suits anyone whose current
setup is already hitting Search Console API quota errors rather than row limits,
because removing that ceiling is a capability rather than a convenience.
Be aware
The extended history and index reporting apply to one Super Site, so a portfolio
of equally important properties is a different calculation than a single flagship
site, and it is worth doing that arithmetic before upgrading. Retention also only
runs forward: a plan bought today does not retroactively recover months that have
already aged out of Search Console, which is the single most common
misunderstanding about paying for retention. If the site is younger than 16
months, the headline feature has nothing to retain yet and Core is the honest
recommendation.
A KPI without a target is a chart, not a report. Set targets from each property’s own trailing history rather than an industry benchmark pulled from somewhere else — a 2% CTR might be strong for a competitive commercial term and weak for a branded one, and a generic benchmark can’t tell the difference your own data already shows.
Build the baseline from at least a full seasonal cycle before committing to a number, twelve months where the business has that much seasonality, so a target doesn’t mistake a predictable dip for underperformance. Revisit targets on a fixed cadence — quarterly is common — rather than letting them run unchanged for years after the site, the SERP, or the business itself has moved on. And set targets only on KPIs you can actually attribute to organic work specifically; a site-wide revenue target that blends every channel isn’t an SEO KPI, whatever channel happens to be reported alongside it. Our SEO reporting dashboard guide covers building a live view of progress against targets once they’re set, separate from the periodic report itself.
Comparison: who should track which KPIs
Agency and freelance SEOs reporting to clients: track all six, split cleanly by client and property, with the branded-versus-non-branded split treated as non-negotiable — it’s the number that protects your own work from being credited to a brand campaign someone else ran. A white label SEO dashboard is worth building once you’re sending the same report shape to more than a couple of clients.
In-house SEO and marketing leads: organic conversions and average engagement time carry the most weight in a budget conversation, since they’re the two a non-SEO manager can connect to revenue without translation. Average position and CTR still matter, but frame them as diagnostic, not headline, numbers in that conversation.
Site owners and solo operators: start with clicks, impressions, and average position straight from Search Console — free, sufficient, and honest for a single site with no reporting audience beyond yourself. Add organic conversions once you have GA4 key events configured, and don’t build a six-KPI report before you need one.
Practical tips for reporting SEO KPIs
Segment before you average. A single site-wide number for position, CTR, or engagement time is nearly always less useful than the same metric split by query group, landing-page type, or branded status.
Export or warehouse data before it ages out. If a KPI needs a comparison older than Search Console’s retention window will hold, the export has to happen before that window closes, not after — see our Search Console BigQuery export guide for the upstream fix.
Pull past the UI’s row cap through the API when a KPI needs it. The Search Console interface caps exports at 1,000 rows; the Search Console API returns up to 25,000 rows per request, with pagination available for more.
Annotate changes on the same chart as the KPI. A dip that lines up with a known Google ranking update reads as expected; the same dip with no note reads as a problem nobody caught.
Keep the KPI set fixed across reporting periods. Swapping which metrics appear from month to month makes trend lines impossible to read and looks like the report is chasing whichever number happened to look good.
Say what you’re not reporting, and why. A short list with an explicit “we don’t report X because it’s a vanity metric” line builds more trust than a long list that implies everything shown matters equally.
Frequently asked questions
What is a good SEO KPI to track every month?
Organic conversions and average position, segmented by your priority query group, cover the two questions a monthly check-in usually needs to answer: is organic search producing outcomes, and is visibility on the terms that matter moving in the right direction. Add CTR and average engagement time once those two are stable and tracked.
What’s the difference between an SEO KPI and an SEO metric?
A metric is anything measurable — impressions, backlinks, page load time. A KPI is a metric you’ve deliberately chosen to track over time because a change in it connects to a business outcome someone acts on. Every KPI is a metric; most metrics never need to become KPIs.
Should I report keyword rankings as a KPI?
Average position from Search Console, segmented by query group, is a defensible KPI. A raw count of “keywords ranked” or “keywords in the top 10” is not — it rewards tracking more keywords rather than ranking better on the ones already chosen, which is why it belongs on the stop-reporting list above.
How many SEO KPIs should be in a report?
Four to six is enough for most properties. Beyond that, a report stops being something a client or manager can hold in their head, and every additional metric dilutes the ones that actually move decisions. If a KPI never changes what anyone does next, cut it rather than adding a seventh.
Why do organic conversions matter more than organic traffic?
Traffic without a downstream action doesn’t answer the question a client or manager is actually asking, which is whether organic search is worth the investment. A page that loses traffic but gains conversion rate is improving; a traffic-only KPI report would show that as a decline and miss the real story entirely.
Can I see SEO KPI trends older than Search Console’s retention window?
Not from Search Console itself once that data has aged out — the account holds a rolling window, not an indefinite archive, and neither the UI nor the API can retrieve rows past it. The only ways to compare against older periods are having exported the data before it aged out, or using a tool that separately retains it on your behalf.
Is CTR a reliable SEO KPI on its own?
Only when read alongside average position. The same CTR figure means something different at position 3 than at position 19, so reporting CTR without its corresponding position turns a genuinely useful KPI into a number that’s easy to misread.
Start from the six KPIs above, drop everything on the stop-reporting list, and you have a report worth sending. If you’re still deciding what belongs on a live SEO monitoring dashboard versus a periodic report, that guide covers the split. For the artefact itself, see our SEO report template; for how often to send it and what the client conversation should sound like, see SEO client reporting. And if the retained-history row in the table above is the one blocking a report you need to send this week, Search Console’s BigQuery export is the upstream fix worth reading next.
