How the log analyzer worksFrom your server’s log file to clear numbers, step by step.
Your server already records everything that happens on your site. It does so in a simple text file. Here is what that file contains, how to read it, and how my tool turns it into log file analysis every hour.
What is a log file?
A logbook. Your server writes down every request it receives, one line per request.
A website lives on a computer called a server. Every time a browser asks it for something, the server answers. A page, an image, a stylesheet, a PDF file. And with each answer, it writes a line in a file. That file is the server log, often just called a “log”.
So a single visit produces many lines. When a person opens your home page, their browser asks for the page, then the logo, then the photos, then the fonts. Each request gets its own line. A bot often asks for the page alone. That is a first way to tell them apart.
On most web hosts that use cPanel, such as o2switch (a French web host), today’s log sits in a folder called “access-logs”. If archiving is switched on, older logs are compressed into a folder called “logs”, one file per month. The help page on how to connect an o2switch site shows where to tick that option.
These server logs are written in a very common format, Apache’s “combined” format. o2switch uses it and describes it in its documentation. Every line always follows the same order. That is what lets a program read them by the thousand.
There is also an error log, which records server breakdowns. My analyzer reads the access log, the one that tells you who came, when, and to see what.
How do you read a log file?
Here is what a real line looks like, with an example address. Hover over a piece, or tap it, to see what it means.
203.0.113.24 - - [23/Oct/2026:09:41:07 +0200] "GET /cours-adultes/ HTTP/2.0" 200 18452 "https://www.google.com/" "Mozilla/5.0 (iPhone; CPU iPhone OS 18_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.6 Mobile/15E148 Safari/604.1"The address of the computer or phone making the request. It is what lets you check that a bot really is who it says it is.
Two fields that are almost always empty, shown as a dash. You can ignore them.
The day, the time to the second, and the time zone offset. Here, 9:41 am, Paris time.
What was asked for: the method (GET to read a page), the page address, and the protocol version.
200 means “here is the page”. 301 means “it has moved”. 404 means “it does not exist”. 500 means “the server is down”.
The weight of the response, in bytes. Here, a little over 18 KB.
The page the visitor came from, when their browser shares it. Here, they arrive from Google.
The name the visitor gives itself: an iPhone with Safari, here. A bot writes its own name there, like Googlebot or GPTBot. But that name can be fake.
Reading one line is easy. Reading 50,000 lines a day is not. And above all, a single line does not tell the whole story. The browser name can lie. The referrer can be made up. A person and a bot can look identical.
This is where the tool does its work. It looks at each line alongside the ones around it, checks the addresses against the official lists, and puts each visit in the right family.
What the tool does, every hour
Four steps, with nothing for you to do. The first read happens within the hour after you connect.
It fetches the new lines
It picks up where it stopped. On the first day, it also reads the month’s archive, if your web host keeps one.
It checks the bots
Every bot that calls itself Googlebot, Bingbot, GPTBot or ClaudeBot is compared with the address lists published by Google, Microsoft, OpenAI, Anthropic, Perplexity and Apple.
It classifies each visit
Real person, search engine bot, AI bot, tool, social network, fake bot or attack. Every line goes into its family.
It adds up the totals
Visitors, visits, page views, sources, errors. Then it compares with previous days and prepares the morning alerts.
The families the tool sorts each visit into
Every line of the log ends up in one of these families. This sorting is what makes the numbers right.
Real people
A believable browser that loads the page’s images and styles, or moves from one page to another, or arrives from a search engine, an AI or a social network.
Search engine bots
Googlebot, Bingbot, and the bots of other search engines. They crawl your pages to put them in their results. See the page on Googlebot in your logs.
AIs that read during a conversation
ChatGPT-User, Claude-User, Perplexity-User. They open a page because a person is asking the AI a question, right at that moment.
The indexes of AI search engines
OAI-SearchBot, Claude-SearchBot, PerplexityBot. They read your pages so they can suggest them later in answers.
Bots that feed the models
GPTBot, ClaudeBot, CCBot, and others. They collect text to train future AIs. It is all explained on the page about AI bots.
Tools and services
Bots from analytics tools, monitoring tools and social networks that build a link preview. They are counted separately, so they do not inflate your visits.
Fake bots
They carry the name of Googlebot or an AI, but their address is not on the official list. The tool unmasks them and sets them aside.
Browsers with no human signs
A browser that loads no images, comes from nowhere and moves through pages too fast. The tool does not count it as a person.
Break-in attempts
Bots that look for a login page, a forgotten file or a known weakness. They never count in your visitors.
How does the tool recognize a real person?
This is the most important question. One mistake here, and every number is wrong.
A bot can give itself the name of any browser. So the name alone is not enough. The tool looks at behavior. A real person loads the files that come with the page: the images, the styles, the scripts. Or they move from one page to another by following your links. Or they arrive from Google, an AI or a social network.
Some bots imitate these signs. For example, they invent a referrer that seems to come from your own site. The tool knows your site is served over HTTPS: a real browser therefore sends an https address. An http referrer coming from your own site gives the imitation away.
Another sign: a visitor who opens dozens of addresses in one minute, almost all of them redirected, is not a person. It is a bot looking for a way in. I added this rule in October 2026, after spotting it on a site I follow. The numbers got smaller, but at last they were true.
Finally, the tool never keeps your visitors’ IP address. It computes a fingerprint from the address, the browser and a key that changes every day. That key is erased after two days. A visitor is therefore counted once a day, with no way of knowing who they are.
A visit is a series of pages opened less than 30 minutes apart. After that, the tool counts a new visit. It is the same rule as most analytics tools use.
Three ways to send the log to the tool
The dashboard lives at dashboard.lucasfonseque.fr. Your log, though, sits with your web host. So it has to be sent. There are three ways to do it.
The WordPress plugin
You install it like any other plugin. It reads your hosting’s log and sends the new lines every hour.
It is the simplest method. It is detailed on the WordPress plugin page.
Under reviewThe upload script
A small file, placed on your hosting, that your web host runs every hour through a cron job. It sends the new lines, and nothing else.
It also works for sites that are not built with WordPress.
AvailableThe file upload
You download the log from your web host and drop it into the tool. Handy for trying it out, with nothing to install.
On the other hand, you have to repeat it by hand to get up-to-date numbers.
SoonThe step-by-step guide for each web host is in the analyzer help center. During the beta, if you get stuck, write to me: I will help you connect your site.
Then, three ways to open the tool
The same dashboard, on your computer, inside WordPress or on your phone.
On your computer
You open dashboard.lucasfonseque.fr in your browser, like any website. You log in, and your numbers are there.
Nothing to install. It works with Chrome, Safari, Firefox or Edge.
AvailableIn WordPress
The WordPress plugin shows the summary right inside your site’s admin. One button opens the full dashboard.
It also takes care of sending your log every hour. You have nothing else to set up.
Under reviewOn your phone
You open the tool in your phone’s browser, then add it to your home screen. An icon appears, like an app.
On iPhone, tap “Share”, then “Add to Home Screen”. No app store, nothing to download.
AvailableWhat the log sees, and what it does not
I would rather tell you right away. No tool sees everything.
Every request that reaches the web server: people, bots, attacks.
Pages served by a cache plugin such as WP Rocket. They still go through the server, which records them.
Errors: pages not found, redirects, breakdowns.
Visitors who refuse cookies or block ads.
Time spent on a page, scrolling, clicks. The log only sees requests.
Visits absorbed by a cache placed in front of the server. For o2switch, the documentation states that LiteSpeed Cache or xtremCache absorb a large part of the traffic, which then no longer reaches the logs.
Visits served by a content delivery network, or CDN, that does not pass on its own logs.
Free to start, then €9 to €99 a month, excl. VAT
One free plan, then four paid plans. Prices exclude VAT. Pay yearly and two months are free.
free plan
€0forever
No credit card.
1 site
1 user
30 days of history
subscription
€990excl. VAT per monthexcl. VAT per year
or €90 a year, excl. VAT, 2 months free10 months paid out of 12, 2 months free
1 site
1 user
3 months of history
7-day free trial
€19190excl. VAT per monthexcl. VAT per year
or €190 a year, excl. VAT, 2 months free10 months paid out of 12, 2 months free
3 sites
1 user
13 months of history
subscription
€39390excl. VAT per monthexcl. VAT per year
or €390 a year, excl. VAT, 2 months free10 months paid out of 12, 2 months free
10 sites
3 users
25 months of history
Read-only access for 5 clients
subscription
€99990excl. VAT per monthexcl. VAT per year
or €990 a year, excl. VAT, 2 months free10 months paid out of 12, 2 months free
50 sites
5 users
25 months of history
Read-only access for 50 clients
Every new account tries the Standard plan for 7 days, no credit card needed. After that, you pick a subscription, or stay on the free Starter plan.
What is a log file?
It is a text file in which your server writes down every request it receives. One line per request: the visitor’s address, the time, the page, the response and the browser name.
It is also called a server log, or server logs. It exists on almost every hosting plan, even if nobody ever looks at it.
Where do I find my site’s log file?
On web hosts that use cPanel, such as o2switch, you can download it from the raw access logs tool, in the “Metrics” section. Today’s log is also in the “access-logs” folder of your hosting.
If archiving is switched on, past months are compressed into the “logs” folder. The help center shows where to tick that option.
How do I read a log file without a tool?
You can open it in a plain text editor, after unzipping it if it ends in .gz. Each line reads in the order explained earlier on this page. Or drop it as it is into the free log analyzer, which reads it in your browser.
But beyond a few dozen lines, it is unreadable. That is exactly why I built the analyzer.
Why are there two logs, one for http and one for https?
Your server often keeps one log per type of connection. If your site is served over https, the http log holds almost nothing but redirects to https.
The tool reads the https log, the one where the real visits are. On the sites I connected at o2switch, its name ends in “ssl_log”.
How long does my web host keep the logs?
It depends on the web host and on your settings. The o2switch documentation says that, by default, only the latest logs are kept, and that you have to tick archiving to keep the history.
Once your site is connected, it is no longer a concern: the tool keeps your numbers on its side, according to the history included in your plan.
What is the difference between an Apache server log and another server’s?
Apache and Nginx are the two best-known web servers. They can write the same line format, called “combined”. It is the one the analyzer knows how to read.
For o2switch, the documentation states that the logs provided are Apache’s, in combined format.
Does the tool change anything on my site?
No. It reads the log and does not touch any page. It adds no script and no cookie.
Only its technical analysis bot opens your pages, like a visitor, to check their titles and links. It introduces itself under its own name, and the tool does not count it in your visitors.
Will my numbers match Google Analytics?
No, and that is normal. The log sees the visitors who refuse cookies, and Google Analytics does not. On my own site, in July 2026, Google Analytics saw only 43% of the real visits.
The two tools do not measure quite the same thing. I suggest you look at trends, rather than comparing the numbers visitor by visitor.
Are my visitors’ IP addresses stored?
No. The tool computes a fingerprint that changes every day, then forgets the address. The key used for the calculation is erased after two days.
The raw logs received are kept while they are being read, then deleted after 70 days at most.
Your log has already written everything down.
All that is left is to read it. Create your free account.
You create your account with your email. It’s free.
You confirm your address. The 7-day Standard trial starts, no credit card needed.
You connect your site. The tool reads your log within the hour.
Page published on November 4, 2026 · Last updated on November 4, 2026
Start free