Using CrawlStat

Projects

How CrawlStat stores your crawls, and how to browse, open, recrawl, compare, resume and delete them from the Projects screen.

One crawl, one file

Every crawl you run is saved as a single file on your computer, in CrawlStat's projects folder. The file holds everything: every URL, its status, headers, titles and links, the crawl's settings and log, the queue of URLs still to fetch, and the audit results.

Files are named after the site and the time the crawl started, for example example-com-20260224-1432.db. Each crawl gets a new file, so crawling the same site again never overwrites an earlier crawl.

While a crawl is open you may see two small companion files next to it, with the same name plus a short suffix. They're a normal part of how crawl files are saved, and CrawlStat cleans them up along with the crawl if you delete it.

The Projects screen

Projects is where you land when you open CrawlStat, and the first item in the sidebar. Its header shows how many crawls you have and where they're stored, with Refresh and New crawl buttons.

The Projects screen in list view, with overview tiles across the top and one row per site below
List view: one row per site, with its health trend, response breakdown and a bar for every crawl in its history.

Overview

Four tiles add up figures across your recent crawls: Crawls, URLs crawled, Broken URLs (everything that returned 4xx or 5xx) and Issues.

Two views

Below the tiles, a bar holds a Filter by site… field and a toggle between two views. CrawlStat remembers the one you picked.

Cards (titled Recent crawls) show one card per crawl, newest first:

  • The site, its start URL and its state: Finished, Running, Paused, Stopped or Failed. The crawl you have open is marked Open.
  • A health ring with the share of URLs that answered with a success or a redirect, and a verdict: Healthy, Some problems, Needs work or Not started.
  • Crawled, Errors, Warnings and the file Size.
  • A Compare button and either Resume (for a crawl that didn't finish, with how many URLs are still queued) or Recrawl.

One row per site (titled Sites) groups every crawl of the same site into a single row. www. and the bare domain count as one site. The columns are:

ColumnWhat it shows
SiteThe site and its latest start URL.
HealthThe latest crawl's health, and how many points it moved since the crawl before.
ResponsesThe mix of 2xx, 3xx, 4xx and 5xx answers and failures in the latest crawl, with a caption in plain words.
HistoryA bar for each crawl of the site, oldest to newest, so a trend is visible at a glance. Click a bar to open that crawl.
CrawledURLs crawled in the latest crawl.
IssuesErrors and warnings in the latest crawl.
Last crawlWhen the site was last crawled.

Click a column header to sort by it, and again to reverse. Click the chevron at the end of a row (Show earlier crawls) to list every crawl of that site underneath it.

Click a card or a row to open that crawl's page (see below). The list keeps your 20 most recent crawls. If a crawl file has been moved or deleted outside CrawlStat, it drops off the list automatically. Click Refresh to check again.

A crawl's page

The Overview of a single crawl: a health score of 100%, counters for crawled, broken, errors and warnings, and the top six issues
Open a crawl and you land on its Overview: health, the headline counts and the six issues worth your time first.
The Visualise tab showing the link graph: pages as circles in rings by clicks from home, sized by link value, with a tooltip showing depth, inlinks and link score
Visualise draws the site: rings are clicks from home, size is link value. Hover any page for its depth, inlinks and score.

Opening a crawl takes you to its own page. The header says which crawl it is: the site, its state, and a line with the start URL, when it ran, how many URLs it crawled, how healthy it is and the file size. All projects (the back arrow) returns to Projects.

The header's buttons work on this crawl:

  • Export a client report: a branded PDF or web page, once the crawl has finished. See Client reports.
  • Compare: compare this crawl with another. See below.
  • Resume or Recrawl, as on its card.

Below the header are the crawl's tabs:

TabWhat it's for
OverviewWhile the crawl runs, its live progress (Watching a crawl). Afterwards, its health, an accessibility verdict, Crawled, Broken, Errors and Warnings, and the top issues.
IssuesEvery problem found, ranked, with why it ranks and which pages it affects. See Issues.
PagesEvery URL, in a table you can filter, sort and export. See The Pages table.
PlanWhat to fix first, and a written report. See The plan.
VisualiseHow the site is structured: which sections hold the pages, and which link to which.
UX TestingTest a page against what it's for. See UX Testing.
AccessibilityThe site against WCAG. See Accessibility.

The accessibility check starts in the background as soon as you open a finished crawl, so its verdict is usually waiting on the Overview by the time you look.

If a crawl stopped before finishing, the Overview says how many URLs are still queued and suggests resuming it.

Recrawling

The Projects screen in grid view, with a card for each recent crawl showing health, counts and a Resume button
Grid view: a card per crawl. A stopped crawl keeps its queue, so Resume picks up exactly where it left off.

Recrawl (on a card, in a crawl's header, or in the ⋯ menu) crawls the site again with exactly the same settings: the same mode, start URL, limits, patterns and JavaScript rendering. It writes a new crawl file, so the earlier crawl is kept for comparison.

Recrawl with changes… in the ⋯ menu opens the New crawl dialog filled in with the earlier crawl's settings, with a summary that starts "As before:". Change what you need, then start it.

Comparing from Projects

The Compare button lists the crawls you can compare this one with. Crawls of the same site come first, with the one just before it marked Previous crawl; crawls of other sites follow. Pick one and the comparison runs straight away, with the older crawl on the left. See Comparing crawls.

Resuming a crawl

If a crawl didn't finish because you stopped it, the app quit, or your computer restarted, its card shows a Resume button and tells you how many URLs are still queued.

Click Resume and CrawlStat continues from where it left off. It uses the settings the crawl originally started with, not your current defaults, and that includes its URL limit.

Removing and deleting

On the Projects screen, each crawl has a ⋯ menu:

OptionWhat it does
RecrawlCrawls the site again with the same settings, into a new file.
Recrawl with changes…Opens the New crawl dialog with this crawl's settings filled in.
Copy file pathCopies the full path of the crawl file, for example so you can find it in Finder or back it up.
Remove from listTakes the crawl off the Projects screen. The file stays on disk.
Delete crawl file…Permanently deletes the crawl file and everything in it, after you confirm.

Where the files are

PlatformCrawl folder
macOS~/Library/Application Support/CrawlStat/projects
Windows%APPDATA%\CrawlStat\projects
Linux~/.local/share/crawlstat/projects (or $XDG_DATA_HOME/crawlstat/projects)

You'll also find the path in the Projects header, at the bottom of the New crawl dialog, and in Settings.

Backing up and sharing crawls

Because a crawl is one file, you can back it up, archive it, or send it to a colleague by copying the .db file. Copy it when CrawlStat isn't using it, so everything has been saved into the main file.

CrawlStat lists the crawls it has run on this machine. There isn't currently a way to open a crawl file from elsewhere from inside the app.