Server Log Analyzer
Server Log Analyzer is a free tool that reads your access log in your browser and shows how Googlebot, Bingbot and AI crawlers visit your site.
- Free
- No sign-up
- Runs in your browser
Search Console tells you what Google decided about your site. Your server log tells you what Google actually did: every visit, every page it asked for and what your server gave back. Paste a few days of your access log, or pick the file, and the tool picks out the visits from Googlebot, Bingbot and AI crawlers such as GPTBot and ClaudeBot. You see visits per crawler per day, the pages that gave errors or redirects, the pages crawled most and least, the addresses with ?extras that waste crawls, and big or slow files when your log records them. It all runs in your browser, so your log never leaves your computer, and you can download the summary as a CSV. No account needed.
Your workspace
Everything runs in your browser. Your log is never uploaded, so it is safe to use a real one.
Where do I find my server log?
- cPanel hosting: open Metrics, then Raw Access, download the file for your domain and unzip it.
- Your own Nginx or Apache server: usually /var/log/nginx/access.log or /var/log/apache2/access.log.
- Cloudflare: Instant Logs or Logpush, saved as JSON lines (only on Cloudflare plans that include logs).
- Windows IIS: the files in C:\inetpub\logs\LogFiles.
- No access? Ask your hosting company or developer for "the raw access log for the last 7 days".
Fill in the details above, then press the button to see your result.
Guide
How to use it
- 1Download your access log from your hosting panel (in cPanel: Metrics, then Raw Access) or ask your host for the last 7 days of it.
- 2Paste the lines into the box, or choose the .log or .txt file. Up to 50,000 lines are read.
- 3Press Analyse. Start with server errors and pages not found, which hurt the most.
- 4Check the most and least crawled pages: your important pages should be visited often, not filters or old addresses.
- 5Fix what the tool points out, download the CSV for your records, and compare with a fresh log in a few weeks.
What the results mean
- Server access log
- A plain text file your web server writes, with one line for every visit: who asked, when, which address and what the server answered. Most hosts keep it for a few days or weeks.
- Googlebot
- Google's crawler, the program that reads your pages so they can appear in Google. It mostly visits as a phone, because Google ranks sites by their phone version.
- User-agent
- The name a visitor gives when it asks for a page, such as "Googlebot" or a browser name. It is easy to fake, so a visit that says Googlebot is not always Google.
- Status code
- The three-digit answer your server gives each visit. 200 is a working page, 301 a redirect, 404 page not found and 500 or above a server error.
- Crawl waste
- Crawler visits spent on addresses that do not need to be in Google, such as sort orders, filters and tracking tags. On a small site it rarely blocks anything, but it hides problems and slows how fast new pages are found.
Common questions
Is my log uploaded anywhere?
No. The page reads the log inside your own browser and nothing is sent to Upgrowly or anyone else. That matters because logs hold your visitors' IP addresses. You can even disconnect from the internet after the page loads and it still works.
How do I know a visit was really from Google?
Any program can call itself Googlebot, so the tool shows what visitors claim and warns about Google visits from unusual addresses. To be sure, do a reverse DNS lookup: run host followed by the address in a terminal. Real Googlebot addresses end in googlebot.com or google.com, and looking that name up again returns the same address.
Which log formats does it read?
The usual Apache and Nginx access logs (the combined format most hosts use), IIS logs from Windows servers, and JSON lines such as Cloudflare Logpush. Lines it cannot read are counted and left out, with a few shown so you can see why.
Why does Googlebot visit some pages much more than others?
Google visits pages more when they are important, linked from many places and change often, like your home page. Pages that are hard to reach, missing from the sitemap or rarely updated get visited less. If a page that matters to you is rarely crawled, link to it from your menu or home page.
How much log should I use?
A week is a good start for a small business site: enough to see patterns without hitting the 50,000-line limit. For a busy site, a single day may already be that many lines, so check a day at a time.