This guide to SEO KPIs and metrics helps you connect search visibility with useful business outcomes. A metric describes activity; a KPI is a measure you choose because it helps judge a specific objective. For a service business, qualified enquiries may matter most. For a store, completed purchases may be the priority. Impressions and rankings help explain those outcomes, but do not replace them.
Set up a measurement plan before reading the numbers
Use Google Search Console for visibility and clicks from Google, and Google Analytics 4 (GA4) for measured activity after a visit. Neither establishes on its own whether someone became a customer. Connect website reporting to accepted enquiries, bookings or orders in your business records. Make sure the people interpreting the report understand what is and is not collected.
Use Bing Webmaster Tools to track impressions from Bing search alongside Google Search Console for Google search. Keep the search engine identified when comparing visibility reports.
Name the desired outcome, the event representing it, the report used to count it and the person checking the data. Test tracking before drawing conclusions. Record website redesigns, URL changes, consent changes and tracking releases in a change log. A reporting break can reflect measurement changes rather than customer behaviour. Compare complete periods using consistent filters and attribution scope.
Organic impressions, positions and clicks
Organic impressions: where your pages appear
Impressions describe appearances in search results. In Search Console, open the search performance report, select a complete period and review impressions by query and page. Apply country and device filters where they matter to your market. Increasing impressions can indicate broader visibility, but not necessarily visibility for searches that will bring suitable visitors.
Read the query and landing page together. An article gaining unrelated impressions needs a different response from a service page gaining relevant discovery. Check a longer history for recurring demand patterns. Avoid treating every fall as a technical failure or every increase as evidence that an editorial change worked.
Keyword positions: follow comparable query-page pairs
Average position in Search Console summarises observed positions; it is not a fixed ranking seen by every person. Enable the position metric and review a query with its page, country and device context. Keep a stable list of important query-page pairs alongside the sitewide view. The aggregate can improve simply because poorly positioned impressions disappear.
Check whether the intended page appears for each topic. If another URL starts appearing, compare their purposes and internal links before merging or deleting anything. Ranking movements alone do not prove better business performance. Review impressions, clicks and accepted enquiries before deciding which change deserves attention.
Organic click-through rate: turn appearances into visits
CTR describes clicks relative to impressions. Find it in the Search Console performance report and review queries and pages with comparable filters. A changing mix of brand searches, locations, devices or search result layouts can change the total. A higher CTR can accompany fewer clicks if low-click impressions disappear, so keep the underlying counts visible.
Where relevant impressions remain but clicks weaken, review whether the title and description describe the page clearly. Compare the same query group after a change. Do not promise services or locations that the page cannot support, and do not assume that changing a description controls how every search result will look.
Organic traffic and page views
Organic search sessions: measure visits consistently
In GA4, use Traffic acquisition and filter the session channel group to Organic Search. Sessions describe visits, not unique customers. Search Console clicks and Analytics sessions measure different stages and need not match. Collection settings, consent and attribution can affect the comparison. Investigate discrepancies rather than forcing the tools to show identical totals.
Break visits down by landing page, country and device. Overseas readers of an informational article may not be potential customers for a local service. A decline concentrated on mobile devices also needs a different investigation from a sitewide decline. Record tagging changes before interpreting fewer measured sessions as less search demand.
Organic page views: understand the journey
Use Pages and screens for views and the Landing page report for where sessions begin, with an Organic Search comparison. Repeated views are not new visitors. More browsing can mean useful exploration or unclear navigation. If people move between a service page and contact information without enquiring, review the explanation and next step, then validate the hypothesis with feedback.
Leads, sales and conversion rates
Organic leads: count accepted enquiries
A lead should represent an accepted enquiry, not merely a click on a submit button. In GA4, configure an appropriate event such as generate_lead and mark it as a key event. Review it with an Organic Search session filter. Test successful submissions and failure paths, and do not send names, email addresses or message contents to Analytics. Keep Google's key-event setup guide available for implementation review.
Reconcile the reported events with your inbox or CRM. Separate spam, unsuitable requests and qualified enquiries. A telephone-link click shows intent to call, not a completed conversation. If the total grows while useful enquiries fall, investigate targeting and measurement before describing the campaign as successful.
Organic sales: verify completed purchases
For ecommerce, validate purchase events against accepted orders. Use GA4 purchase reporting with a clearly documented organic traffic scope, and keep attribution consistent. The GA4 ecommerce purchases report provides a reference for purchase metrics. Product views and add-to-cart events describe earlier steps, not completed sales. Check duplicate events and cancellations before presenting the result.
For services, a won project may happen after several conversations away from the website. Keep a separate sales record with evidence of the acquisition source. Do not assign an invented value to every enquiry and call it realised revenue. Website attribution is useful evidence, not a complete account of every influence on a purchase.
Organic conversion rate: define the denominator
Conversion rate is conversions divided by the total number of visitors, expressed as a percentage. For an organic conversion rate, use conversions and visitors from organic search within the same reporting scope. Identify the search source, such as Google or Bing, when comparing organic conversions by engine. This visitor-based definition is distinct from the GA4 session key-event rate below.
In GA4, a session key-event rate describes the share of sessions containing a key event. A user-based rate answers a different question. Review the specific accepted-enquiry or purchase event, not an unexplained aggregate of unrelated actions. Keep the session scope and outcome definition identical between periods and show underlying session and outcome counts alongside the rate.
Adding another key event can change what the overall rate means without improving the business. Small samples can also make movement look dramatic. Compare landing pages with similar purposes and check whether a tracking release or a broken form explains the change before rewriting content.
Engagement rate and bounce rate in GA4
GA4 reports engagement rate, and bounce rate is its inverse: the share of sessions that were not engaged. It is not simply the share of single-page visits. An engaged session meets the applicable duration condition, contains a key event or includes multiple page or screen views. Review Google's engagement and bounce-rate definitions and document your configuration.
Review these metrics in acquisition or landing-page reporting with an Organic Search filter; report customisation may be needed to display bounce rate. Compare pages doing similar jobs. A short answer page and an enquiry journey need different interpretations. Lower bounce rate alone does not prove satisfaction, and a tracking change can alter engagement without changing the experience.
Lost organic clicks: investigate the cause
In Search Console, compare complete, equal-length periods and sort query or page changes by lost clicks. This measures a decline from recorded clicks, not an estimate of every search where someone could have clicked. Check impressions, position, demand and the dates of site changes together. Use Google's traffic-drop diagnostic process as a reference.
Inspect affected URLs for index status, canonical selection, redirects and missing content. Compare previous copy where available. A drop following a migration or rewrite is a hypothesis to investigate, not proof of its cause. Prioritise pages losing useful enquiries and avoid broad changes before identifying where the loss is concentrated.
Backlinks, authority scores and local visibility
Backlinks: review relevant referring pages
Search Console's Links report shows external linking evidence, but is not an exhaustive web inventory. Review relevant referring sites and linked pages rather than chasing a raw total. After a migration, check that linked articles, images and resources still resolve or redirect to equivalent replacements. Matching a competitor's link count is not a reliable objective.
Domain and Page Authority: supporting comparisons only
Domain Authority describes a domain-level third-party comparison; Page Authority concerns an individual page. These are not Google scores or proof of future rankings. Find them in the relevant provider's reporting, not Search Console. Keep the provider consistent when comparing periods, since different indexes and formulas are not interchangeable. Investigate important referring-page changes directly instead of optimising for a score.
Local visibility: measure the places you actually serve
Use Google Business Profile performance for available interactions such as calls, direction requests and website clicks. Pair it with relevant country or locality views in your website reporting where available. These interactions are not completed sales, and reported location is not proof that someone qualifies for your service. Confirm outcomes against business records and check that listed services and locations are accurate.
Separate brand from non-brand queries
In Search Console, define a query filter for your business name, spelling variants and recognisable branded terms. Compare that group with the remaining reported queries using the same dates and filters. Brand demand can grow through referrals or other marketing, while generic service searches describe another discovery route. Query tables do not expose every search, so label these as reported query groups rather than a complete division of all traffic.
Build a simple monthly KPI report
Keep a repeatable report with an outcome summary, comparable periods, visibility and traffic measures, qualified enquiries or purchases, completed changes and next actions. Separate brand from non-brand queries, articles from service pages and relevant markets. Include a short data-quality note for missing tracking, incomplete records or changed definitions. Do not bury those limitations beneath charts.
For each important movement, state the observation, your hypothesis, the evidence needed and the next owner. Connect the work plan to the constraint, not a reporting quota. Our guide to how SEO is scoped in the Caribbean can help you compare reporting responsibilities and implementation work in proposals.
Turn a report into a decision
Use a compact comparison table rather than exporting every available chart. For each chosen KPI, include its definition, source, current period, comparison period and an interpretation. Label the exact event counted as a lead and distinguish accepted enquiries from qualified enquiries. Keep a separate work log so readers can distinguish completed implementation from a recommendation that has not yet been acted on.
For example, if service-page clicks remain stable but accepted enquiries fall, check the form and the quality of visits before concluding that visibility is the problem. If impressions rise on an article while service enquiries are unchanged, report the visibility gain without claiming additional sales. These are investigation examples, not client results or universal explanations for those patterns.
Finish the review with a decision and an owner: check tracking, inspect an affected page, improve an unclear explanation or gather more evidence. Record why that action was chosen and revisit the same measure in the next report. When the data is incomplete, say so explicitly instead of filling the gap with an assumed result. A useful monthly report makes uncertainty manageable rather than pretending it does not exist.
- Confirm that dates, filters and event definitions match the previous report.
- Reconcile accepted outcomes with business records and flag missing evidence.
- Name the next action, its owner and the observation it should help explain.
Frequently asked questions
Which SEO KPI should you prioritise?
Choose the outcome closest to your objective, such as qualified enquiries or accepted purchases. Use visibility and traffic metrics to explain how people reached it.
Should Search Console clicks equal GA4 sessions?
No. They measure different stages with different collection and attribution rules. Check filters and tracking before interpreting a discrepancy as a fault.
Does a high bounce rate mean a page failed?
Not automatically. In GA4 it reflects sessions without engagement under the configured definition. Read it alongside the page's purpose, accepted outcomes and tracking quality.
If you need help connecting measurement with implementation, review our SEO services or discuss your website with MDX.
Planning a project like this? See our SEO service or tell us about your project.



