Crawler Log Analyser vs SEO Skill Server Log Analyzer
Crawler Log Analyser
github.comSEO Skill Server Log Analyzer
seoskill.devSide by side
| Figure | Crawler Log Analyser | SEO Skill Server Log Analyzer |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · SEO Log File Analysis Tools | 7.7 (#9) | 7.1 (#24) |
| Integrations | The README says JSON output is the integration boundary and lists no Slack, Prometheus, Elasticsearch, or SaaS integrations. | The terminal command's JSON output is described as useful for an agent or script, and CSV output can be used in a spreadsheet or another analysis tool. |
| Intended users | The maker positions it for operators of self-hosted static sites who need to inspect real crawler behavior in nginx access logs. | The report is for people who have a combined or JSONL access log and need evidence of real server requests. |
| Maker | SpeyTech identifies Spey Systems Ltd as the company behind its repositories and describes it as a Scottish software and systems engineering company based in Inverness. | SEO Skill identifies itself as a joint by Ian Nuttall; the opened pages do not state a headquarters or founding date. |
| Purpose | The project describes itself as operational SEO observability for self-hosted static sites running nginx. | The browser analyzer finds Googlebot, Bingbot, and AI crawler activity in server access logs. |
In their own words
Crawler Log Analyser
Crawler Log Analyser has no write-up on Specifiction yet; its figures are above.
SEO Skill Server Log Analyzer
SEO Skill Server Log Analyzer examines access logs to identify requests whose user-agent strings match Googlebot, Bingbot, and AI crawlers. It accepts combined Apache or NGINX logs and JSONL or NDJSON exports up to 250 MB. Results group requests by crawler family, URL path, and HTTP status, remove query strings from paths, and show the first and last valid request dates. CSV exports cover crawler summaries, paths, errors, and status codes, but omit raw requests and full user-agent strings. The browser analyzer processes the raw log locally; the maker says logs are not uploaded or kept as a searchable copy. The same parser can run from a terminal and return JSON or a selected CSV table, for use with scripts, agents, spreadsheets, or other analysis tools. A user-agent match only identifies what a request claimed to be, not which company sent it. Malformed rows or processing limits can yield partial results, so missing crawler activity in such results is unknown. The documented command accepts explicit row, path, and returned-detail limits.