Free tool · log analyzer

Free log analyzerDrop your site’s log file and see who really visits: people, search engines, AI bots.

Every time someone opens a page on your site, your web host writes it down in a file: the server log, or log file. This free tool reads it for you, right in your browser. Your file is not sent anywhere.

Free, no sign-upNothing is uploaded.log and .gz files

Analyze your log file

Drop the file in the box, or choose it on your computer. No file at hand? The “See example” button creates a made-up log covering four days.

Drop your log file hereText file or .gz compressed, up to 300 MB

Your browser reads the file, on your computer. It is not sent anywhere: not to me, not to any other server. Once the page has loaded, the analysis works even without a connection.

Why this matters to me: a log contains your visitors’ IP addresses, and the CNIL, France’s data protection authority, points out that an IP address is personal data. The simplest way to protect it is to not let it travel.

What the free analyzer shows you

Ten figures and tables, calculated from every line of your file.

Lines read

The size of your log

Each line is one request made to your server: a page, an image, a stylesheet.

Lines the tool cannot understand are counted separately, and flagged at the bottom of the result.

Likely visitors

People, counted once a day

The same IP address with the same browser on the same day counts as one visitor.

It is an honest estimate, not a figure that is exact to the last visitor.

Share of people

What is left once bots are removed

The share of requests made by people, images and stylesheets included.

On many small sites it comes as a surprise: bots often make a big part of the requests.

Who makes the requests

Six groups

People, search engine bots, AI bots, tools and social networks, other bots, and attack attempts.

Each group has its own bar, from the biggest to the smallest.

Bots by name

Googlebot, GPTBot, ClaudeBot…

Bots that introduce themselves by name, with the company and the purpose: search engine, AI training, live reading.

The eight most active in your file.

Pages viewed by people

Your most-read pages

Only the pages opened by people, bots left out.

It is often very different from what you imagined.

External sources

Where your visitors come from

The sites that send people to yours: Google, Bing, ChatGPT, Facebook…

When the browser does not say where it came from, the visit does not appear here.

404 errors from people

Pages that no longer exist

Missing addresses opened by real people. These are the ones to fix first.

404 errors from bots are left aside.

Status codes

Server health

Normal responses, redirects, errors and outages, for all requests.

A long red bar on outages is worth a message to your web host.

How does the tool tell people from bots?

Four steps, applied to every line. None is perfect on its own, but together they give a good idea.

01 · The name

It reads the visitor’s name

Each line states the browser or the bot. The tool recognizes Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot and about fifteen others by name.

02 · The address requested

It spots attack attempts

Some bots look for sensitive files, such as /.env or /wp-config.php. These requests go into the attacks group, not into your visitors.

03 · The behavior

It looks at how the page is opened

A person’s browser also loads the images and the stylesheet, arrives from another site, or moves from one page to another. A bot posing as a browser rarely does.

04 · The count

It counts once a day

The remaining requests are grouped by IP address, browser and day. Each group becomes one likely visitor.

Which file format does the tool read?

The most common format on the web: the “combined” format of Apache and Nginx.

Most web hosts write their logs in the same format, called “combined”. It is the format described in the Apache server documentation, and the one Nginx uses when no other is chosen. A line looks like this:

203.0.113.7 - - [23/Oct/2026:09:41:07 +0200] “GET /contact/ HTTP/2.0” 200 18452 “https://www.google.com/” “Mozilla/5.0 (iPhone…)”

You read, in order: the visitor’s IP address, the date and time, the page requested, the status code from the server, the size sent, the site the visitor came from, then their browser. I go through each part, with an interactive line, on the log file page.

There is a shorter format, called “common”. The Apache documentation describes it as the same format without the last two fields: the referring site and the browser. Without them, it is impossible to tell people from bots. If your file is in this format, the tool tells you, and you can ask your web host for the “combined” format.

.gz compressed files are accepted as they are: your browser decompresses them itself. All recent browsers have been able to since May 2023. .zip files, however, must be unzipped first.

For size, the Apache documentation gives a rough idea: a log grows by about 1 MB, or more, every 10,000 requests. The tool accepts up to 300 MB. Beyond that, take the log for a week or a single day.

Where do you find your site’s log file?

It is not in WordPress, but at your web host. Here is where to look.

The access log is written by the server, not by your site. So you will not find it in the WordPress admin. Watch out for a trap: the debug.log file from WordPress is not an access log. It holds PHP errors, not visits.

On cPanel hosting, open the “Metrics” section, then the raw access logs tool, called Raw Access. According to the cPanel documentation, you download each domain’s log there, already compressed as .gz. Drop that file as it is into the tool above.

At o2switch, a French web host, the tool is called “Logs d’accès brut” (raw access logs), in the same Metrics section. o2switch states that, by default, only the latest logs are kept: they are deleted after the statistics are calculated. To keep a history, you have to tick the archive box. I show where it is on the connecting an o2switch site page.

At other web hosts, look for “logs”, “journals” or “statistics” in your customer area. The name and the location change from one host to another. The help center explains the cases I have checked, and the cPanel hosts page covers the other web hosts that use cPanel.

On a server of your own, Apache and Nginx often keep their logs in the /var/log/ folder. Older logs are usually compressed as .gz there, one file per day or per week.

The limits of the free analyzer

I would rather tell you about them. They also explain why the full analyzer exists.

First, bots are recognized by name only. Yet any program can write “Googlebot” in its line. Without checking its address, a fake Googlebot passes for a real one. You can check an address by hand with the tool on the Googlebot page.

Next, visitors are likely, not certain. A bot that imitates a browser very well can be counted as a person. On the other hand, a person who opens only one page, with no images, and without coming from another site, can be filed with the bots.

Third limit: the cache. If a cache plugin or a service like Cloudflare serves your pages, some visits never reach the server, and so never reach the log. o2switch says this about its caches: most of the traffic may never appear there.

Finally, nothing is kept. You see one file, at one moment. No history, no comparison with the week before, no alert. Close the page and everything disappears. This is on purpose, for privacy, but it is not enough to follow a site over time.

That is the whole job of the full log analyzer: it reads your log on its own, checks each bot’s address against the official lists, keeps the history, and warns you in the morning if something is wrong.

Free analyzer or full analyzer: what is the difference?

Both read the same log. What changes is what they do with it.

This free toolThe full analyzer
The logYou drop a file, by handIt is read on its own, every hour, or once a day on the free plan
HistoryNone: everything is erased when you close the pageFrom 30 days to 25 months, depending on the plan
Fake botsRecognized by name onlyAddress checked against the official lists, from the Lite plan
AlertsNoneAn email in the morning if needed, from the Lite plan
Your siteNot analyzedFull technical analysis and a score out of 100, from the Standard plan
PriceFree, no sign-upFree Starter plan, then from €9 a month, excl. VAT

All prices and plan details are on the pricing page. The full analyzer is in beta, open to everyone: sign-up is free.

Pricing

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.

Starter

free plan

€0forever

No credit card.

1 site

1 user

30 days of history

Lite

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

StandardRecommended

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

Advanced

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

Enterprise

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.

Questions about the free log analyzer

A file that will not load? Write to me.

Email me

Is my file sent anywhere?

No. Your browser reads it, on your computer. I receive neither the file nor the result.

You can check: once the page has loaded, turn off your connection, then drop your file. The analysis still works.

Which files does the analyzer accept?

Access logs in the “combined” format, the one used by Apache and Nginx, as text or compressed as .gz. The file name does not matter.

.zip files must be unzipped first. The maximum size is 300 MB.

How do I download my logs from cPanel?

In cPanel, open the “Metrics” section, then the raw access logs tool, Raw Access. Click your site’s domain to download its log as a .gz file.

Drop that file as it is into the tool. There is no need to unzip it.

Why is my file not recognized?

Most often, it is not an access log: an error log, or the debug.log file from WordPress, for example. Or your web host has changed the format.

Open the file in a text editor: each line should start with an IP address, with the date in square brackets a little further along.

Are the figures the same as in Google Analytics?

No, and that is normal. Google Analytics only counts visitors who accept its cookies and let its script run. The log sees every request, bots included.

I explain these gaps on the real visitors page.

Can I analyze the log of a site that is not mine?

Only if its owner trusts you with it. A log contains visitors’ IP addresses, which are personal data.

For a client, ask them for the file: with this tool, it does not leave your computer.

How can I tell whether a Googlebot is real?

Not here: the tool only reads the name. For a specific address, use the free checker on the Googlebot page, which queries Google’s addresses.

The full analyzer does this check for every bot, on its own.

What does “likely visitors” mean?

The log does not say who is a person. The tool works it out from behavior: images loading, the referring site, moving from one page to another.

Hence the word “likely”: it is a solid estimate, not an exact count.

Why do I see almost no visits?

Often because of the cache. If a cache plugin or a service like Cloudflare serves your pages, many visits never reach the server.

Also check the period: some web hosts only keep the log for the current day.

How do I see which AI bots read my site?

Drop your log: the “Bots that introduce themselves by name” table shows GPTBot, ClaudeBot, PerplexityBot and the others.

To find out whether your robots.txt file blocks them, use the robots.txt test.

Does the tool keep my results?

No. Nothing is saved, neither on my side nor in your browser. Close the page and everything disappears.

To keep a history, you need the full analyzer.

Let the analyzer read your log on its own.

No more files to drop: it reads the log every hour, keeps the history, and warns you in the morning.

1

You create your account with your email. It’s free.

2

You confirm your address. The 7-day Standard trial starts, no credit card needed.

3

You connect your site. You see your real visitors, day after day.

Page published on November 4, 2026 · Last updated on November 4, 2026

Start free