OKRs & KPIs — a destination is not a dashboard

The two-line definition

A KPI is a gauge: it tells you a number — organic clicks, average position, Core Web Vitals. An OKR is a journey: a destination you chose (the Objective) and two to four gauges you have agreed to watch on the way (the Key Results).

KPIs without OKRs are a wall of dials. OKRs without KPIs are a vision board.

In SeoKestrel

OKRs live per client, per quarter. A Key Result can be auto-tracked: wire it to a KPI with a baseline and a target, and its progress updates itself from the nightly Search Console data — no spreadsheet, no “whose number is right”. The quarterly scorecard then scores each chair on its own metrics. Goals at the top, gauges underneath, accountability per chair.

Scorecards, briefly

Scorecards live under Scorecards in the sidebar: pick a client and a quarter, and each of the seven chairs — Head of SEO, Technical SEO Engineer, SEO Analyst, Content Strategist, Link/PR Lead, Dev Lead, CMO — gets its own card of metrics computed from the same nightly data. Chairs map to the functional roles from Team & roles: your role decides which card you chair, not which you may read — everyone sees all of them.

Four chairs, one table

The business owner cares about one KPI with a currency symbol. Their OKR: “Stop renting all our traffic from Google Ads” — KR1: organic share of revenue 20%→35%; KR2: non-brand organic clicks +50%; KR3: ten money pages in the top 5. The owner does not read position reports; the owner reads the trend line and the invoice. That is correct behaviour — it is what the monthly PDF is for.

The CMO lives between the owner’s “more revenue” and the team’s “we fixed canonicals”. Their OKR: “Make organic our most predictable channel” — KR1: traffic forecast accuracy within ±15%; KR2: three content clusters ranking top-10; KR3: the monthly report opened by the client every single month (yes, that is measurable; yes, it counts). Their KPIs — clicks, impressions, CTR by cluster — are the narrative layer between gauges and board deck.

The SEO technician distrusts any number that cannot be reproduced from a crawl. Their OKR: “Make the site boringly crawlable” — KR1: indexable pages with a self-referencing canonical 78%→98%; KR2: orphan pages to zero; KR3: p75 LCP under 2.5 s on the money templates. Technician KPIs are leading indicators — they move weeks before the owner’s revenue line does, which is exactly why both belong on the same scorecard.

The web designer discovers they were doing SEO all along the moment Core Web Vitals enter the chat. Their OKR: “Beautiful AND fast — pick two” — KR1: CLS p75 below 0.1 (the page stops jumping like it saw a spider); KR2: image weight −40% on key templates; KR3: zero render-blocking fonts. Designer KPIs are the technician’s KPIs wearing better typography.

How it all fits together

Read the chain bottom-up: the designer’s Core Web Vitals feed the technician’s crawlability, which feeds the CMO’s cluster rankings, which feed the owner’s organic revenue share. Same mountain, four altitude readings — when the bottom gauges move, the top gauges follow a quarter later.

The scorecard exists so each chair watches its own gauges instead of arguing about whose number is realest.

Good to know

• Aim for 2–4 Key Results per Objective. Ten KRs is not ambition, it is a KPI wall with extra steps.
• A KR you cannot measure from data you already collect is a wish. Wire KRs to KPIs that already flow in nightly.
• 70% progress at quarter-end on a stretch OKR is a success, not a failure — the scorecard treats it that way too.

FAQ

OKR vs KPI in one sentence?

Destination vs dashboard gauge.

Should every KPI be in an OKR?

No. You watch many gauges; you commit to a few. The rest are context.

Who writes the OKRs — agency or client?

Together, ideally during onboarding or a quarterly kickoff. The agency proposes (it knows what is achievable); the client ratifies (it knows what is valuable).