Local & instant · nothing is uploaded · runs entirely in your browser

LogCraft — Log File Analyser & AI-Visibility Dashboard

Drop any log file and instantly get a full 12-tab dashboard — error breakdown, activity timeline, AI-crawler & GEO/AEO visibility, security & anomaly detection, traffic sources, devices, geography, performance, sessions and a 404 report — then export a client-ready report in one click.

🪵 Format Auto-Detection 🚨 Error & Level Analysis 📊 Activity Timeline + Trends 🤖 AI Crawler & GEO Visibility 🛡️ Security & Anomaly Detection 🧭 Traffic Sources 📱 Devices & Browsers 🌍 Geography ⚡ Performance 🕒 Sessions 🔗 404 / Broken Link Report 📤 CSV & PDF Export
Drag & drop .log / .txt / .jsonl files here, or click to browse
Apache/Nginx access logs (any Combined/Common Log Format variant), syslog, app logs with ERROR/WARN/INFO levels, and structured JSON-lines logs — format is auto-detected, no config needed
Reading file… 0%
Initializing…

How to Read This Dashboard

New to log analysis? Click any question below — every chart in the dashboard above also has its own short caption explaining what it shows.

What is the Log Health Score?
A single 0–100 number summarising the whole file: error rate, server errors, bot/security signals and how concentrated failures are around one root cause all pull the score down. 75+ is healthy, 50–74 needs attention, below 50 means investigate now.
What counts as a "bot" vs an "AI crawler"?
"Bot" is any automated request — search engines (Googlebot, Bingbot), SEO tools (AhrefsBot, SemrushBot) and AI crawlers all count. "AI crawler" is the narrower, GEO/AEO-relevant subset: GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and similar user agents used to power AI answers and chatbot citations.
What's the difference between GEO, AEO and SEO?
SEO (Search Engine Optimization) targets ranking in traditional search results. AEO (Answer Engine Optimization) targets being the direct answer shown in a featured snippet or voice/chat response. GEO (Generative Engine Optimization) targets being cited or summarised by generative AI tools like ChatGPT, Perplexity and AI Overviews. The Bots & AI Crawlers and Traffic Sources tabs give you real evidence for the AEO/GEO side.
What does "P95 response time" mean?
The 95th percentile: 95% of requests were faster than this value, and 5% were slower. It's a better indicator of real-world worst-case speed than a plain average, because a few very slow requests can hide inside an average without showing up clearly.
What is a "session" and a "single-page session"?
A session groups consecutive requests from the same visitor using a session identifier in the log. A single-page session means that visitor viewed exactly one page before leaving — a bounce-style signal. A high rate isn't automatically bad, but a sudden spike is worth investigating.
Why do referrer/geography/performance/session tabs sometimes not appear?
Those tabs only appear when your log actually contains that data (a referrer + user-agent field, a country field, a response-time field, or a session field). A minimal Apache/Nginx log without those extras will only show Overview, Timeline, Status & Endpoints, Top Messages and Raw Log.
What does "wasted crawl %" mean for a bot?
The share of a bot's requests that hit a redirect, error or missing page instead of a real 200 OK page. A high wasted % for an AI or search crawler means it's spending its limited crawl budget on broken URLs instead of your actual content — fixing or removing those links helps that bot see more of your site.
How does the Security & Anomalies tab decide what to flag?
It's pattern-based, client-side heuristic detection — not a firewall. An IP gets flagged if it requests known attack-pattern paths (path traversal, SQLi/XSS attempts, sensitive-file or CMS-admin probing), uses a non-browser scripted client (curl, python-requests, etc.), racks up repeated 401/403 responses, or sends an unusually high number of requests within a single minute. Treat flags as a starting point for investigation, not a final verdict.
What is the Trend Snapshot on the Overview tab?
LogCraft splits this log's own time range into two equal halves (by line count) and compares error rate, bot traffic % and average response time between them — a quick way to see whether things are trending better or worse without needing to upload a second file.
What log formats does LogCraft actually support?
Any Apache/Nginx-style Common or Combined Log Format line (with or without referrer/user-agent), whatever extra fields your server/proxy adds after that (country, response time, session — under whatever key name it uses), structured JSON-lines logs (one JSON object per line, as used by Node/pino/winston, Python, and most cloud platforms), and generic timestamped/leveled text logs (syslog, application logs). If a line doesn't match any of these, it still shows up in Timeline and Raw Log using whatever timestamp/level text pattern is found.
What do the HTTP status code groups mean?
2xx success. 3xx redirect (page moved). 4xx client-side error — most commonly 404 Not Found, or 429 Too Many Requests. 5xx server-side error — the backend itself failed, which is usually the highest-priority category to fix.

What This Tool Checks

LogCraft parses your file client-side and runs it through fifteen analysis modules — the file never leaves your browser, so it's safe to drop in logs with internal hostnames, IPs or user data.

🪵 Universal Format Detection

Auto-detects any Combined/Common Log Format variant (Apache/Nginx and countless custom fields), structured JSON-lines logs, syslog, and generic leveled app logs — no config, no format selection needed.

🚨 Error & Level Analysis

Counts ERROR / WARN / INFO / DEBUG lines, computes error rate, and flags when it's outside a healthy range.

📊 Activity Timeline + Trends

Buckets events over time, adds an hour-of-day pattern view, and compares the first vs. second half of the log to show if things are improving or worsening.

🌐 Status, Endpoints & 404s

HTTP status breakdown, top client IPs, top endpoints, and a dedicated 404/broken-link report showing exactly which URLs need fixing or redirecting.

🤖 Bots & AI Crawlers

Identifies every bot — including GPTBot, ClaudeBot, PerplexityBot and Google-Extended — shows which pages AI engines are reading, per-bot crawl efficiency, and a robots.txt/llms.txt check.

🛡️ Security & Anomaly Detection

Flags IPs showing path-traversal/SQLi/XSS probing, scripted (non-browser) clients, brute-force auth failures, or abnormal request bursts — with a risk-ranked table.

🧭 Traffic Sources

Splits human traffic into AI-assistant referrals, search engines, social and direct — plus the exact landing pages AI-referred visitors clicked into.

📱 Devices & Browsers

Desktop/mobile/tablet split, browser and OS breakdown, parsed straight from user-agent strings.

🌍 Geography

Breaks down requests by country when location data is present in the log.

⚡ Performance

Average/median/P95 response time and the slowest endpoints, when response-time data is present.

🕒 Sessions

Session count, pages per session and a bounce-style single-page-session rate, when session data is present.

🔁 Recurring Issue Detection

Groups similar error messages together so you can see which single issue is costing you the most.

💡 Recommendations Engine

Turns every module's findings into plain-language, prioritised next steps — critical, warning, and informational.

📤 CSV / TXT / PDF Export

Every table exports to CSV individually; the full report exports as a shareable TXT or a chart-included PDF.

🔗 Sortable Tables & Deep Links

Click any column to sort, filter tables by keyword, and share a direct link straight to any tab.

How to Use

Drag a .log or .txt file onto the drop zone (or click to browse), optionally add a keyword to highlight in the raw log view, and click Analyse Log File. Parsing happens instantly in your browser — nothing is sent to a server. Extra tabs like Bots & AI Crawlers, Security & Anomalies, Traffic Sources, Devices, Geography, Performance and Sessions appear automatically whenever your log contains that data. Use Export TXT or Export PDF for the full report, or the Export CSV button on any individual table.

Understanding Your Score

The Log Health Score (0–100) weighs error rate, server errors, security signals, bot/AI-crawler behaviour and how concentrated your failures are around a single root cause. 75+ = Healthy · 50–74 = Needs Attention · Below 50 = Investigate Now. Fix red (critical) items first, then amber warnings.