Introducing Website-Toolkit: One crawler for the whole life of a site
A website doesn’t have one big moment. It has several: the day it launches, the day it moves, and every quiet day in between.
A website doesn’t have one big moment. It has several: the day it launches, the day it moves, and every quiet day in between. Each of those moments has its own anxiety, and — until now — its own separate set of tools. You audit with one thing, track the launch in another, map redirects in a spreadsheet, and find out a page broke when the client emails.
Website-Toolkit is built on a simple idea: it’s all the same job. Crawl the site to learn what’s true, do the work, then verify nothing slipped. One crawler does the learning; everything else is a different lens on the same findings. The tool that finds a problem is the tool that tracks the fix — so you never copy an issue into a second tool or retype a URL.
Everything here is in beta right now — free with sensible limits while we find the rough edges. Here’s the shape of it.
It starts with a free audit
You drop in a URL, confirm it’s yours by email, and the crawler does a full-site pass — broken links, redirects, missing metadata, cache behaviour, the usual catalogue — up to 200 URLs. You land on a results page you can share as a private Magic Link or download as an Excel export. No account, no password, no card. Run one here.
That audit is the foundation. Every other module is built from it — which saves you time and effort compared to managing it by hand.
Launch projects: the audit becomes a checklist
When a site is heading for launch, one button on the results page turns the crawl into a launch project: a managed checklist of pre- and post-launch tasks, with the items your audit could verify ticked off for you. It treats staging and live as first-class settings, can crawl a password-protected staging site, and — the part that actually saves you — keeps pace as the site grows: re-crawl later and new pages appear as needing checks, while every tick you’ve already made stays exactly where it was.
Read the full launch-companion post →
Migration: prove every URL survived the move
Moving a site — new domain, new URL structure, or new host — has the same shape as a launch: crawl the site, do the work, prove nothing was lost. The migration project captures the old site’s URL inventory, then checks each address against the new site and tells you exactly which ones redirect correctly, which point at the wrong page, and which now 404 — while there’s still time to fix them, not three weeks later in a traffic graph.
Read the full migration post →
Monitoring: keep it right after you’ve walked away
A launch and a migration both end; a live site doesn’t. Monitoring re-crawls on a schedule you set and tells you what changed against the baseline you signed off — the link that started 404ing, the meta description that vanished, the SSL certificate expiring in twelve days. Not “is it up?” but “is it still right?” And a fresh regression drops straight into a project’s to-do list, so the alert becomes a tracked task rather than something you read and forget.
Read the full monitoring post →
One engine, one source of truth
This is the same full-site crawler that powers ToggleWP’s single-page checks inside WordPress — here it’s the whole-site view. The audit that finds the problems, the checklist that tracks the launch, the redirect map that verifies a move, the monitor that watches for drift: all one engine, all measuring against the same baseline you already produced. There’s no second copy of the truth to keep in sync, and nothing to copy across by hand.
It’s built for the solo freelancers and small studios who are the auditor, the project manager, and the person flipping the site live — all at once. If that’s you, the best way in is the free audit.