Walkthrough · Beginner · 20 minutes
How to Read Your Website Statistics
Read your traffic straight out of the server's own logs, with nothing to install — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
The job: read your traffic straight out of the server's own logs, with nothing to install. Time to set aside: 20 minutes. Skill needed: beginner.
Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Skill rating
20 minutes
Time budget
5
Steps in total
24/7
Support on call
No prior knowledge assumed — a hosting account, a browser and 20 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.
The outline first, then the detail
Set out end to end, the route is: find the panel's stats tools, patterns before totals, tell people from machines, skim the three lists that matter and add analytics for behaviour.
No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.
One caution before you click anything
Setting AWStats against Google Analytics and deciding one of them is broken. They measure different populations: every request including bots, versus consenting browsers that ran a script. The gap is written into the definitions.
It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.
A habit worth borrowing
The 404 list is where server stats become something you can act on. Every repeat 404 is a live visitor meeting a wall, and most are cured permanently by one redirect each.
Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.
The parts that look after themselves here
Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.
Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.
Why this job is shorter on our plans
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
The rate you register at is the rate you renew at, so year two costs precisely what year one did — nothing lying in wait on the invoice.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
The dull parts automated
SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
Honest about how big it is
Read your traffic straight out of the server's own logs, with nothing to install is a beginner-level job — set aside 20 minutes, with the platform-absorbed steps marked.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Quick Start
Order placed to site online
- 1
Find the panel's stats tools
AWStats and the raw access logs sit under cPanel's Metrics section. These are server-side figures: no snippet, no consent banner, nothing to set up.
- 2
Patterns before totals
How the months compare, how the week is shaped, and which pages people land on. Shape carries the story, whereas any single day's figure is mostly noise.
- 3
Tell people from machines
Server-side stats count crawlers along with everybody else. The robots section in AWStats shows how much of the traffic is automation, which is why analytics tools always report a smaller, human-only figure.
- 4
Skim the three lists that matter
Top entry pages show what pulls people in, the 404 list shows what is broken, and referrers show who links to you. A monthly skim covers it.
- 5
Add analytics for behaviour
Logs count requests; analytics follows journeys. Run both, and stay clear about which question each system was built to answer.
Built In
Fitted to every plan
- Webmail in the browser plus IMAP, POP and SMTP for any client
- SSH, Git and Composer on the developer plans
- WordPress and 400+ further applications installed in one click
- Spam and virus screening on every mailbox by default
- 99.9% uptime as the target, watched around the clock
- Softaculous included for one-click application installs
- WebP image optimisation built in, at no extra charge
- Your existing site brought across by our engineers, at no charge
- A renewal figure identical to the one you registered at
- The name's first year included when you order annually
Frequently Asked
The questions that come up most
Why does AWStats report more traffic than Google Analytics?
AWStats counts every request, bots and crawlers included, along with visitors whose browsers blocked the tracking script. Analytics counts consenting browsers that ran it. Both answer honestly: one describes machine load and the other a human audience.
Are server statistics enough on their own?
For plenty of sites, yes. Traffic shape, leading content, referrers and errors answer most owners' questions with no privacy burden at all. Bring client-side analytics in once you need journeys and conversions traced through the site.
Can I choose the PHP version myself?
Yes — PHP is set per site from the control panel, so a legacy application and a current one can run side by side in one account. Extensions and per-site tuning are on the same screen, and none of it goes near a support ticket.
Is there a safe place to try changes?
Yes — plans with staging let you copy the live site, work on the copy, then publish it once it behaves. That turns 'hope the update works' into 'know it works' before a single customer meets it.
Keep reading
How to Enable LiteSpeed Caching
Turn the server's cache engine on and verify it is genuinely delivering hits — beginner level, about 20 minutes.
How to Set Up Domain Forwarding
Route everyone who visits one domain straight on to another — beginner level, about 5 minutes.
DNS (Domain Name System) (Glossary)
The plain-English definition this page rests on, with a worked example.
Laravel Hosting
Laravel-ready hosting with Composer, SSH and Git-driven deployment.
Domain Names
Find, register and transfer names — year one free with annual hosting.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Your site has earned better hosting.
Every plan carries the essentials other hosts bill as extras — and support that answers.
View Laravel Hosting plans