From Search Clicks to Real Enquiries: A Website Measurement Story
Published: 2026-11-19

TL;DR: Small-business owners can use this history to build a measurement loop that follows the path from a search result to a useful page and then to a confirmed contact action. It shows how one website project defined a successful enquiry, repaired gaps between tracking code and account settings, and tested a read-only report that leaves improvement decisions with a person.
The question behind the dashboard
In February 2026, I started with a practical question: could visitor statistics and form submissions help guide website improvements, and could I check search rankings with a free tool? For a small business, visits alone leave an owner with an unfinished decision: whether searchers reach useful pages and take a next step.
I wanted to connect the website’s marketing system to visitor and form data, then use those signals to decide what to improve. Search visibility belongs in the same picture, but it answers a different question. A search result can earn many impressions and some clicks, while relevance, page activity, and successful contact each need their own measure. Those signals help the owner locate where a useful visitor journey gains momentum and where it needs attention.
I also raised a separate February concern about the size and speed of the growing blog index. Giving each article its own search-friendly address would make individual pages easier to find and evaluate. That concern supported the measurement work: useful pages need stable destinations before their search performance can be compared over time. It remained a supporting thread, while the main project question stayed focused on meaningful enquiries.
This was a work-in-progress measurement design. Its early records focus on establishing a baseline so later reports can show how traffic and enquiries change. The useful starting point for another small business is the same: name the decision the data should help with. “Get more traffic” is broad. “Find which search pages bring visitors who complete a contact step” gives the owner a question that can be measured and acted on.
Separate visibility from a real enquiry
The first important distinction was between a person trying to contact a business and a contact that the system successfully receives. In a February form test, I reported that the form had submitted but the expected thank-you message was missing. I then made the requirement precise: show that message only after a successful submission, and present an interruption message with another contact route when delivery fails. Count a button press as an attempt; record a successful enquiry after the application confirms receipt.
That changes what a small business should count. A form-start event records someone beginning the process. A submit-click event records an attempt. A confirmed-success event records the point where the application receives a successful response. In plain English, an event is a recorded action, such as a page view or a form submission. A conversion is an action the business has chosen to count as valuable, such as a successfully received enquiry. Google Analytics 4 (GA4), Google’s web analytics service, supports custom events for interactions that need a specific meaning; its official events guide explains how those events are defined and reported.
The project’s later code history included a September change to form validation and conversion measurement. The principle is reusable: make the event name match what the system has proved. If a visitor reaches the success state, record that event. If a request fails, show the alternative route and record the failure path separately when that information is useful. This keeps a report from treating every attempt as an arrived message.
The measurement map also limited event details to what supports a decision. A page path, page type, or button label can describe where an action happened. Google’s Analytics data safeguards prohibit sending personally identifiable information to Google Analytics. A small business can answer “Which page led to a successful form?” with an event and page label, while keeping the visitor’s message and contact details outside the analytics record.
Make measured evidence guide the next SEO decision
By mid-September, I shifted attention from technical search improvements toward organic traffic and qualified enquiries. I said the existing conversion-event foundation was ready for measurement and directed further search decisions to rely mainly on measured search and conversion data. September commits also recorded work on site architecture and contact paths. The next useful step was to activate the data sources and use them to choose where to work.
That shift led to several October changes around marketing-system page visits. The project added a shared tracking loader, sent page-view events, allowed the tracking pixel through the site’s Content Security Policy, and documented the setup requirements. A Content Security Policy (CSP) is a set of browser rules that limits which sources a page can load scripts, images, and other resources from. A tracking script can be present in the code and still need the correct browser permission before it can send a signal.
The project used two kinds of on-site measurement for different jobs. Mautic, a marketing automation platform, recorded page visits within its own visitor and contact workflow. GA4 recorded website events such as page views and form-related actions. Google Search Console measured search-result performance before the visitor arrived. These sources are complementary: one describes search discovery, another describes activity on the site, and the marketing system can support contact follow-up.
The distinction between installed instrumentation and received data became an explicit engineering boundary. A code change can show that a tracking path was added; a separate live check should confirm the expected event appears in the intended analytics property. That check matters for any owner using web analytics, because a green code review and a real recorded event answer different questions. The September decision gave the project a stronger target: use evidence from the actual search and contact paths to guide the next improvement.
Recover the measurement setup and test the data path
On October 19, I suspected the analytics tag had been set earlier and overwritten, and asked for the Git history to be checked. The investigation found that the website’s event-tracking code still existed while its analytics identifier in runtime configuration was empty. The code had a route to send events, but the active setting that tells the route which analytics property to use had been lost. Git history provided the earlier configured value, and an October 20 change restored it.
The recovery exposed four separate dependencies that owners and developers should check independently: tracking code, runtime settings, account permissions, and the selected analytics property. A working measurement path needs each one aligned. The code defines the event, runtime settings identify the destination, account access authorizes the request, and the selected property supplies the site data.
Later in October, the project corrected a measurement-property selection and the authentication path used to request data. Google’s Analytics Data API guide describes reports as combinations of dimensions and metrics requested for a specific property. In everyday terms, a dimension names the kind of row—such as a page—while a metric gives the number to compare, such as sessions or events. The property selection determines which site’s data those rows describe.
After the access and property corrections, I asked for a live test. The recorded check returned ready responses from both the search and analytics APIs and produced a report. That result verified that the credentials, selected properties, and report request worked together for a test run. It established the data path for later comparisons; measuring sales or search-position changes requires subsequent reports over a chosen baseline. Any site owner can use the same recovery sequence: inspect the code, confirm its runtime settings, check account access, verify the selected property, then run a small report with known dimensions and metrics.
Turn the report into a human-reviewed improvement loop
The final October milestone was a read-only daily report job. It gathered search-query and page information from Search Console, then paired that view with landing-page sessions and event counts from GA4. The documented report ranked opportunities such as pages around search positions 5 through 20 and pages with many impressions but relatively few clicks. These ranges were the project’s own prioritization rules. Google’s documentation describes the available metrics; each site owner sets the page-position bands that fit their goals.
In plain English, an impression is a time a page appears in search results, and a click is a visit that starts when someone selects that result. The click-through rate (CTR) is the share of impressions that received clicks. Search Console’s Search Analytics API can group search data by dimensions such as page and query and return measures including clicks, impressions, CTR, and average position. GA4 adds what happened after the visitor arrived: sessions and recorded events. A session is a period of activity on the site, which can include several page views or actions.
These measures help locate a next question. A page with many impressions and few clicks may need a clearer search-result title or description. A page with search visits and few contact events may need a closer look at whether it answers the visitor’s question and makes the next action clear. A page with form starts and few confirmed successes calls for a check of the form flow. The report points to evidence for a person to inspect, who can interpret the context and choose the next change.
The job’s authority ended at reading data, checking site health, and ranking suggestions for human review. A person retained control of site edits, publishing, commits, and deployment. The recorded history confirms a successful API report run and a wrapper check. A current schedule inspection leaves recurring execution and email delivery unverified, making schedule confirmation the next operational step. The history establishes a tested report path; future reports can compare lead, ranking, revenue, and traffic changes against an agreed baseline.
A measurement checklist for a small website
A small business can begin with a compact loop:
- Choose one valuable action. Define success in system terms: the server accepted the contact form. Count a click on Submit as an attempt.
- Map the visitor path. List the search result, landing page, useful on-site actions, and the final confirmed contact state.
- Name each signal by what it proves. Keep search impressions and clicks separate from page views, form starts, and successful submissions.
- Collect only useful event details. Use a page path or button label to support the decision. Keep a visitor’s message and contact details out of analytics event parameters.
- Test both outcomes. Submit a valid form and confirm the success event; trigger a failure and confirm the alternate contact route.
- Check the data connection. Confirm the tracking code, runtime setting, property, permissions, and API response one by one.
- Rank ideas from evidence. Combine search visibility with page activity and successful contact events, then let a person decide which change to make.
- Measure again. Compare the same pages and actions after the change, and record the period and baseline so later decisions have context.
Start with one contact action and one report. Once the events match what the website actually confirms, the owner can decide whether to expand the measurement map or change the site.