Web analytics tools help you understand how people arrive, what they use and whether they complete an action that matters. Define the decision you want to make before adding more tracking or more dashboards.
For a small service business, useful questions include which pages introduce the service, whether visitors reach the contact journey and whether a real enquiry follows. The SEO tools hub explains how analytics complements search reporting, technical checks and research.
Choose a small measurement plan
Write down the purpose of the site and two or three actions that support it. For example: an enquiry successfully submitted, a booking confirmed or a completed purchase. A page view and a business result are different events.
A click on a phone number can indicate intent, but it does not establish that a conversation happened. A click on “send” does not prove that the form succeeded or that an email arrived. Label your measurements to reflect what they actually observe.
Analytics, reporting and historical investigation tools
The original collection included Google Analytics and Yandex Metrica. Reporting and historical-analysis resources from “More SEO Tools” now belong here because they help interpret the evidence. They do not all collect website traffic themselves.
Website measurement
-
Google Analytics — Google Analytics: use the current GA4 event-based setup to examine acquisition, page journeys and key events. Verify collection before interpreting a dashboard.
-
Yandex Metrica — Yandex Metrica is retained as a web-analytics and behavior-analysis option. Define what you need to observe and configure any recording or form-related features carefully.
Reporting and historical context
-
Panguin Tool — Panguin Tool is retained as a historical analysis resource for comparing traffic and update timelines. Availability and supported analytics connections need checking before use; a matching date does not prove causation.
-
Google Data Studio / Looker Studio — Google Data Studio, also known through its Looker Studio branding, is a reporting resource. It visualizes connected data; it does not collect missing website events by itself.
Set up measurement and verify it
- Choose the property and site. Confirm that the account and website you are configuring are the intended ones. Keep access with the people responsible for the business.
- Identify the existing installation. Check whether collection comes from the theme, a plugin or a tag manager. Avoid adding a duplicate copy without understanding the current setup.
- Configure the required events. Follow the current product documentation and the way your form, booking system or shop reports success.
- Test a complete journey. Perform a known test and check that the expected event appears once, with the intended meaning.
- Document the setup. Record event names, definitions, responsibility and the date of verification.
For Google Analytics, use the current GA4 event-based setup rather than older Universal Analytics instructions. Consult the official Analytics overview before following an old screenshot or property guide.
For any analytics platform, decide what information you need to collect and how consent, privacy settings and retention should be configured for your situation. Keep personal messages, credentials and unnecessary identifying information out of event names and URLs sent to analytics.
A worked example: understanding enquiry performance
Imagine that a fictional joinery site receives visits to a fitted-wardrobe service page but few enquiries. Begin by testing the page on a real phone. Read the offer, open the contact route and submit a test message. Confirm delivery independently of the analytics event.
Next, inspect the measurement. Is a successful submission recorded once? Is the event instead firing when someone merely opens the form? Has the contact page URL changed? A collection problem can make a working journey look unsuccessful, while a loose event definition can inflate results.
Once collection is understood, compare the page’s audience, sources and useful actions over a meaningful period. Keep the scope consistent. A low count can reflect traffic relevance, page clarity, technical friction or limited demand; the dashboard alone does not choose the explanation.
Read reports without mixing incompatible measures
Search Console clicks, analytics sessions and completed enquiries measure different things. Do not expect their totals to match exactly. Differences in scope, timing, collection and visitor choices can affect the comparison.
For your own routine, start with a page or channel and one question. Example: “Did visitors arriving at this service page reach and complete the enquiry journey?” Keep the date range, filters and event definition with the answer.
A dashboard is useful when it makes a decision easier. Add definitions, a source, an owner and a dated note about changes. An attractive chart without a stable definition can create more confusion than a small, well-explained table.
Use historical context without claiming causation
An archive or a traffic-versus-update timeline can help you remember when a page or trend changed. It does not prove that an algorithm update caused a decline or that a redesign improved conversions.
Keep your own change log: URL, date, change, reason and verification. If traffic falls, check collection and site availability as well as search visibility. Use the rank tracking guide for search context and the technical guide for access and performance investigations.
Frequently asked questions
Should I install several analytics tools?
Only when each answers a useful question that justifies its collection, maintenance and complexity. More tags do not automatically mean better understanding.
Is a form event a lead?
It depends on what the event means. Verify a real successful submission and distinguish it from opening a form or clicking a button.
What is a useful first dashboard?
A small view of relevant landing pages, acquisition sources and verified useful actions, with clear definitions and a comparable period.
Back to the SEO tools hub · Ask iMasterWeb about your website
Additional references to assess for your needs
These references complement the guide. Some are historical: check the service, destination and current terms before use. No price or outcome is guaranteed.