CLI: Ready-to-use Packages

Desktop Application

This section only describes the use of the command-line interface (CLI).
If you’re more interested in the desktop app, go to the desktop app page.

SiteOne Crawler ships as a single native binary (siteone-crawler) with zero runtime dependencies — no PHP, no Node.js, nothing to install alongside it. Just download, extract and run. Binaries are available for 🪟 Windows, 🍎 macOS and 🐧 Linux in both x64 and arm64 architectures.

If you’d rather compile it yourself, see CLI: Build from Source.

📦 Pre-built binaries

Download the binary for your platform from GitHub releases. At the top of the page you’ll find the latest (and therefore recommended) version — scroll down and expand Assets.

# Linux / macOS — download, extract, run
tar -xzf siteone-crawler-*.tar.gz
./siteone-crawler --url=https://my.domain.tld/

On Windows, unzip the *-win-x64.zip archive to any folder and run siteone-crawler.exe --url=https://my.domain.tld/ from a terminal (cmd.exe or PowerShell).

Run the binary without any arguments to launch the interactive wizard, or pass the command-line options directly for automation.

Note for macOS users

If macOS refuses to start the crawler from your Downloads folder, move the entire folder with the Crawler via the terminal to another location, for example to your home folder ~. This works around the Gatekeeper quarantine that applies to files downloaded by the browser.

🐧 Linux binary variants

For Linux, two binary variants are provided:

Variant	Compatibility	Performance
glibc (primary)	Requires glibc 2.39+ (Ubuntu 24.04+, Debian 13+, Fedora 40+)	Full native performance
musl (siteone-crawler-static)	Any Linux distribution (statically linked, no dependencies)	~50–80% slower due to the musl memory allocator

The glibc variant is recommended for current distributions — it offers the best performance. If you are running an older distribution (e.g. Ubuntu 22.04, Debian 12) and encounter a GLIBC_2.xx not found error, use the musl (-static) variant instead. The musl binary is fully statically linked and runs on any Linux system regardless of the installed glibc version. The performance difference is mainly noticeable during CPU-intensive operations such as offline and markdown exports.

🍺 Homebrew (macOS / Linux)

brew install janreges/tap/siteone-crawler
siteone-crawler --url=https://my.domain.tld/

🐧 Debian / Ubuntu (apt)

curl -1sLf 'https://dl.cloudsmith.io/public/janreges/siteone-crawler/setup.deb.sh' | sudo -E bash
sudo apt-get install siteone-crawler

Older distributions

On older distributions (Ubuntu 22.04, Debian 11/12, etc.) you may get a GLIBC_X.XX not found error. Install the statically linked variant instead:

sudo apt-get install siteone-crawler-static

See Linux binary variants for details on the performance difference.

🎩 Fedora / RHEL (dnf)

curl -1sLf 'https://dl.cloudsmith.io/public/janreges/siteone-crawler/setup.rpm.sh' | sudo -E bash
sudo dnf install siteone-crawler

Older distributions

If you get a GLIBC_X.XX not found error, use sudo dnf install siteone-crawler-static instead. See Linux binary variants for details.

🦎 openSUSE / SLES (zypper)

curl -1sLf 'https://dl.cloudsmith.io/public/janreges/siteone-crawler/setup.rpm.sh' | sudo -E bash
sudo zypper install siteone-crawler

Older distributions

If you get a GLIBC_X.XX not found error, use sudo zypper install siteone-crawler-static instead. See Linux binary variants for details.

🏔️ Alpine Linux (apk)

curl -1sLf 'https://dl.cloudsmith.io/public/janreges/siteone-crawler/setup.alpine.sh' | sudo -E bash
sudo apk add siteone-crawler

Build from source

Prefer to compile the crawler yourself, build a leaner binary without browser rendering, or build the static musl binary? See CLI: Build from Source. (Browser rendering is already included in the pre-built binaries above.)