Server Logs as a Backstop

A record that does not depend on anything

Analytics works by a tag running in the visitor's browser, which requires the page to load, the script to run, the visitor not to block it, and consent where that applies.

Server logs are written when the request arrives, before any of that.

So they continue recording when a tag is removed by a theme update, blocked by a browser, or declined at a banner.

Which makes them the backstop for exactly the failures that are otherwise invisible.

What they are good for

• Confirming a tag has broken.
• A rough traffic trend that never stops.
• Which pages exist and get requested.
• Errors visitors are hitting.
• What is consuming your bandwidth.

The first is the most valuable use. A month where analytics shows a collapse and the logs show normal traffic is a tracking failure rather than a business one, and nothing else tells you that.

What they count differently

Worth understanding before comparing anything.

A log records requests, so one page view can produce dozens of lines as images and files are fetched.

They include bots heavily, frequently more than half of all requests, so raw totals overstate human traffic substantially.

They cannot see anything happening after the page loads, so a form submission handled by a script may not appear.

And they identify visitors poorly, so visit and user counts are approximations.

So this is a trend and a diagnostic rather than a measurement, and treating it as a replacement produces wrong conclusions.

Where to find them

Since most people have never opened the relevant screen.

A hosting control panel usually offers raw access logs and a generated statistics report built from them.

The generated version is readable without any technical knowledge and is the one to start with.

It typically shows monthly visits, popular pages, referring sites, and error counts.

Ask your host where yours is if it is not obvious, which is a two-minute support question.

Some hosts keep only a few days of raw logs by default, which is worth checking and sometimes changing.

A worked example

A business saw their analytics traffic fall by roughly two thirds over a weekend and assumed something serious had happened.

Their host's statistics showed the same traffic as the previous month, unchanged.

A plugin update on the Friday had removed the tracking code from every page except the home page.

Without the logs they would have spent a fortnight investigating a decline that had not occurred.

The comparison took four minutes and it is available to anybody with hosting.

They now check the two against each other whenever a figure moves sharply.

Use it as a sanity check, monthly

Which is the practical routine.

Once a month, note the visits figure from your host's statistics alongside the one from your analytics.

The two will not match and that is expected; what matters is that they move together.

A month where one falls sharply and the other does not is the signal, and it takes thirty seconds to spot.

Add it to the same row of the same spreadsheet as everything else.

That single extra column is the cheapest insurance available against measuring nothing for three months.

They also answer the privacy question

Worth knowing for anybody uncomfortable with tracking.

Server logs record the request, which includes an address that is personal information under Canadian rules, so they are not outside privacy considerations entirely.

They do not, however, involve a third-party service, a cookie, or anything following a visitor between sites.

For a business wanting the roughest possible traffic figure with minimal tracking, the host's own statistics are a legitimate answer.

Check your retention period and your privacy notice mention them, which most do not.

Do not try to read the raw files

Since that is where people give up.

A raw log is millions of lines and is not readable by looking at it.

The generated report is what you want, and it is produced automatically on most hosting.

Where you genuinely need the raw version, that is a job for somebody with the right tools rather than an afternoon in a spreadsheet.

For the backstop use described here, the summary is entirely sufficient.

The one exception is a specific investigation, where somebody looking for what happened at a particular minute genuinely does need the raw file.

They are also the record of what went wrong

A separate use worth knowing about before you need it.

When a site is compromised, breaks after an update, or behaves strangely for one group of visitors, the logs are frequently the only evidence of what actually happened.

Whoever investigates will ask for them, and a host keeping only three days of history means the evidence has gone before anybody noticed the problem.

Ask what your retention is and extend it if the setting exists, which on most hosting it does.

That costs a little storage and is the difference between an explanation and a guess when something eventually goes wrong.

The counter-case

Logs are a poor primary measurement.

The bot inflation is large enough that trends can be distorted by a single aggressive crawler, and there is no reliable way to separate them in a basic report.

They also tell you nothing about behaviour, sources, or conversions, which is most of what analytics is for.

And on some hosting the statistics are disabled by default or badly out of date, which is worth checking before relying on them.

Where that is the case, asking the host to enable them is a support message rather than a project.

Find your host's statistics screen, note the monthly figure alongside your analytics one, and use the pair as a sanity check.

The five minutes

1. Find the statistics screen in your control panel.
2. Note this month's visits.
3. Put it beside the analytics figure.
4. Expect them to differ.
5. Watch whether they move together.
6. Check the retention period.
7. Add a column to your spreadsheet.

Step five is the whole value, since two figures moving together confirm a real change and one moving alone confirms a broken tag, which is otherwise indistinguishable.

The wider privacy-conscious options are covered in what you can measure without tracking anybody.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.