Start with a measurement checklist
Before opening a dashboard, write down the few things your website needs to measure. For a small site, that might be visits to important pages, clicks to an external booking service and successful contact-form submissions. Note where each action happens and what you expect the analytics tool to record. This gives you a testable list rather than a vague goal of making the numbers look right.
Identify which pages share a layout and which use a different template, such as a blog post, landing page or confirmation page. A tracking script may work on the homepage but be missing from another template. Also note any paths that should not be tracked, such as a staging site. Keep this checklist alongside your website maintenance notes so you can repeat it after a redesign or plugin change.
Test a visit from browser to report
Use a fresh browser session and visit several pages from your checklist. If your analytics tool offers a live or debug view, check whether each visit appears there. Record the page address you tested and the time, allowing for the delay your tool describes. Then check a standard report later; a successful live test does not always mean the data will appear in reports as expected.
Repeat the test on a phone or at a narrow screen width if the site uses a different mobile layout. Try a direct visit and a visit from a link on another page of your site. Check that page addresses and titles are recognizable and that navigation does not unexpectedly create duplicate page views. On sites that change content without loading a new page, confirm that moving between views is recorded only when intended.
One missing test visit is not proof that tracking is broken. Browser privacy settings, extensions, consent choices and reporting delays can affect what you see. Record the conditions of your test rather than repeatedly changing settings until a number appears.
Check important actions, not just page views
For each action on your checklist, perform one controlled test and look for the corresponding event. A contact form deserves particular care: submitting it, seeing a success message and reaching a confirmation page are different steps. Decide which one represents a completed enquiry, then check that an unsuccessful submission does not count as a success. If the form sends data to another service, confirm that your chosen point of measurement still works.
Review event names and any details attached to them. Clear, consistent names make reports easier to use; several names for the same action can split a total across reports. Check that events do not include form contents, email addresses or other personal information. If a button can be clicked more than once, decide whether your report should count clicks or completed outcomes, and label it accordingly.
Look for data you should not count
Test your consent choices. If your site offers visitors a choice about optional analytics, compare what happens before a choice, after acceptance and after rejection. The behavior should match the notice and settings you have published. Check again after changing a consent tool, tag manager or website theme, because these parts can affect when tracking starts.
Next, look at traffic from your own team, test submissions and any staging domain. Where your setup allows exclusions, verify them with a controlled visit rather than assuming they work. Be careful not to exclude genuine visitors who share a network with your organization. If an exclusion is impractical, annotate tests in your notes and avoid treating small changes in reported totals as meaningful.
Make the check repeatable
Finish by comparing your test log with what appears in the reports: pages, actions, names and approximate timing. You are checking whether the setup behaves as designed, not expecting dashboard totals to match a server log or a manual count exactly. Different tools apply different rules, and some visits will not be measured.
Save a short record of the pages and actions tested, browser and consent settings used, results, and any fixes made. Recheck after changes to forms, templates, navigation, consent settings or tracking code. A brief routine is more valuable than a one-time inspection: it helps you spot when a change to the website has quietly changed the data you rely on.
