Measuring results

SEO reporting that separates work from results.

See which website changes went live, then follow Google impressions, clicks and recorded AI mentions. Klusio’s reporting keeps sources and comparison periods visible. Enquiries and revenue need their own tracking; a change in search performance alone does not establish what caused it.

Explore the four measurement layers Discuss what your site can measure

A measurement trail for one page

Illustrative example: a page answering “What does a dormer cost?” The days and outcomes below are examples, not customer results or promised delivery times.

Suppose clicks and impressions rise after publication. That gives a reason to investigate the page’s contribution. It does not yet prove an increase in enquiries or that this page alone caused the change.

Day zero: preserve the baseline: Record the available Google figures and AI observations before or around publication.
Day zero: record publication: Save the final URL returned by the authorised website connection.
Day one: confirm the live page: Fetch the final address and check that the intended content is present.
Day nine: check Google’s handling of the URL: Check the available evidence for the final URL. A reachable page alone does not prove that Google has indexed it.
Day thirty: compare the measurements: Compare equivalent periods with the baseline. Keep missing or delayed measurements visible.
Day sixty: enquiries may still be too early to assess: Too little measured activity can make a conclusion unreliable. Plan another appropriate check.

Four layers that answer different questions

An appearance in a search result, a website visit, an enquiry and a sale are different outcomes. The further an outcome is from the publication, the more other factors can influence it. The order below illustrates that distance; it is not a numerical confidence score.

1. Visibility: Google impressions show search appearances; AI measurements show mentions in selected answers. Search Console and the AI tracker are separate sources. Being shown does not establish that someone clicked.
2. Clicks and visits: Search Console records clicks through from Google. Analytics can measure visits and behaviour where configured and permitted. Clicks are not a count of unique visitors, and visits are not enquiries.
3. Enquiries: Form submissions and recognised contact actions require lead tracking or another valid measurement connection. A phone-button click is not proof of a completed call. Several visits and channels may contribute.
4. Revenue: Your own administration establishes which quotation was accepted and what the work earned. Klusio cannot infer revenue from an enquiry; it needs the information you supply.

Every figure has a source

These five sources measure different things. Adding them into one total would hide the information you need. A missing period is shown as missing, not zero, so a connection failure is not mistaken for a fall in results.

Sources and their limits
Source	What it measures	What it does not establish
Google Search Console	Organic Google impressions, clicks, positions and queries for your domain.	Traffic from ads, social media or direct visits.
AI measurements	Mentions and source references in answers to selected questions.	Website visits or enquiries; mentions cannot be added to clicks.
Live website check	Whether the intended work is reachable at the final URL.	That Google has indexed or ranked the page.
Analytics	Behaviour after someone reaches the site, with a valid setup and applicable consent.	Activity that the setup or consent settings do not allow it to record.
Lead measurement	Submitted forms and recognised contact actions.	Every call after a website visit, or which enquiries became customers.

From a keyword overview to one question

The original Dutch recording shows the keyword overview and an individual query. The overview brings together available positions, impressions and relevant pages. Opening a question adds the competing pages visible in the measured search results.

Use the source and date beside each figure. The comparison provides context for a change; it does not prove why a competitor or your page moved.

Watch the original product recording Dutch interface · optional

Original Dutch-language keyword-analysis recording. The explanation above describes the workflow in English; playback is optional.

Preserve a baseline and return to the result

A new page and a technical correction can need different follow-up schedules. The workflow preserves what was known at the start and checks again when the available evidence can support a useful comparison.

Before or around publication: baseline: Preserve available search positions and relevant AI observations. Missing historical information stays missing.
Soon after execution: live check: Fetch the final URL and check that the intended work is there. Saved is not the same as live.
When evidence is available: Google visibility: Check the final URL’s available indexing and search evidence. The timing depends on Google and the type of work.
Later: compare suitable periods: Follow-ups may be scheduled after 14, 30, 60 or 90 days, depending on the action. Not every action receives all four checks.
Choose what to do next: Continue, improve, measure again or wait for more evidence. Work with a useful recorded outcome can inform the next choice.

Say how strong the connection is

A rise after a change is not automatically proof of its cause. These four conclusions distinguish a traceable route from a partial or unavailable explanation. “Too early” and “cannot determine” are useful results when they say what is missing.

Directly traceable: The recorded visitor route reaches the changed page and includes the measured action. This supports a traceable journey, not a claim that no other influence mattered.
Partly attributable: The work coincided with a change, but other factors also played a part. Describe the plausible contribution and those other factors.
Too early to assess: The page has not been measured long enough, the data is sparse or the source is still reporting with a delay.
Cannot determine: A necessary connection is absent or the data cannot support the conclusion. A guess must not be presented as a measurement.

Your connections determine what can be measured

Search Console supplies the organic Google baseline. A publishing connection supports execution and live checks. Analytics or measurement code adds permitted behaviour data. Lead tracking adds recognised form submissions and contact actions.

A WordPress publishing connection alone does not measure visits and enquiries. An AI mention is not a website visitor. A call made later or outside the website is rarely attributable automatically. Review which layers are covered before expecting an answer from them.

The growth guarantee uses two measures

Day one is the first successful Klusio publication on your website. The baseline is the 30 complete calendar days immediately before that day. We compare it with days one to 30 using organic impressions and clicks from Google Search Console.

If neither measure is higher and the conditions are met, the subscription fee for your first paid month is refundable. The final assessment normally follows within 3 days after the measurement window because Google reports with a delay. Rankings, indexing, AI mentions, enquiries and revenue are not guaranteed.

Keep the same project measurable: Search Console must be correctly connected and readable by day one and throughout the period. Keep the website accessible and do not remove or block the content, measurement, indexability or connection.
Refund scope: The guarantee can be used once per business and Chamber of Commerce registration. Advertising, separate add-ons, usage costs and work outside the subscription are excluded.

The limits remain visible

Klusio cannot prove that one change caused an enquiry without a traceable route, or provide visit and enquiry figures without the necessary measurement setup. Revenue depends on information from your own administration.

Calls outside the tracked website route remain untracked. Advertising and social activity are not included in organic search figures. Estimates remain estimates. A missing source is not replaced with an invented measurement.

Find the baseline for your own website

Discuss your existing connections and the questions you want the measurements to answer. The free growth scan can identify a sensible first improvement and the connections needed to follow it.

Questions and answers

Can Klusio prove that one change caused an enquiry?

Sometimes a visitor’s route to a form submission can be followed directly. Often several factors contribute. Klusio shows the measurement trail and the strength of the connection without claiming an unproven cause.

Why do I not see results immediately after publication?

The page first needs to be live and accessible, and Google may still need to index it. Google and AI platforms also report with a delay. “Too early to assess” is the correct conclusion when the evidence is not yet available.

Does a WordPress publishing connection automatically measure enquiries?

No. Publishing and measurement are separate capabilities. Visits and enquiries need a valid analytics, measurement-code or lead connection, with the applicable consent and configuration.

Which results count for the growth guarantee?

The growth guarantee is available only on Groei Marktleider and Klusio Partner with Klusio running fully on autopilot. It does not apply to Groei Start, Groei Pro, self-managed execution or a workflow requiring approval before publication. Only organic impressions and clicks from the connected Google Search Console property count under the published conditions. Positions, enquiries, revenue and AI mentions are not substitute signals.

What if a connection fails during the period?

The gap remains visible. A period without data is marked as missing, not recorded as a result of zero. This avoids presenting a technical interruption as a decline.

Let’s look at your website.

Tell us what you want to improve. We’ll show you how Klusio could help, in English.

Request a demo