From one server to many: How Website Toolkit fits your workflow

Whether you’re a solo freelancer who wants to stop manually checking client sites, or an agency that needs automated audits baked into your deployment pipeline, Website Toolkit is built to fit the way you already work – not the other way around.

Here’s a look at all the ways it can be triggered, and how you can choose between running it yourself or letting me handle everything.


The managed option: Let Website-Toolkit do the heavy lifting

If you don’t want to think about servers, tokens, or cron jobs, the managed platform is for you.

Sign up, get an API key, and your clients’ sites are audited on a schedule we control – from the WordPress dashboard. Every crawl reports back automatically. You get a monthly page budget per key, and the platform enforces it. You get the results. You don’t touch a server.

This is the right choice if you want to spend your time doing web work, not running infrastructure.


The self-hosted option: Your server, your rules

Buy the crawler, drop it on a VPS, and you own the stack. The crawler exposes several ways to trigger a crawl, so it slots into whatever process you already have.

Scheduled crawls (Via WordPress plugin)

Define a cron schedule in the WordPress plugin – something like “every Monday at 7am” – and it runs automatically, emails the results, and moves on. No cron tab to edit, no scripts to maintain.

Deployment webhooks

Connect it to Vercel, Cloudflare Pages, or any CI system. When a new deployment goes live, a webhook fires, the crawler audits the freshly deployed site, and you know within minutes whether something broke. Broken links, missing images, SEO regressions – caught before your client notices.

WordPress plugin trigger

The ToggleWP plugin can queue on-demand single page audits directly from your / your clients WordPress site. Publish or update a new page / post, the crawler picks it up, runs the audit, and the results appear – no email chain, no manual process.

Page-check API

Building something custom? Hit the REST API directly. POST a URL with your Bearer token, get a crawl ID back, poll for results or receive them via webhook. Useful for custom dashboards, Slack bots, or anything else you’re building on top of the audit data.

Email triggers

Point an IMAP mailbox at the crawler and trigger audits by sending an email. Old school, but surprisingly useful – forward a client email, get an audit back.

The public landing page

Optionally expose a public-facing page where anyone can submit a URL, verify their email, and receive a full audit report. Good for lead generation, or for giving clients a self-serve option without giving them API access.

Manual CLI runs

For one-off checks during development, just run it from the command line. --once, --check-page, --once-json — useful when you’re debugging a specific site and don’t want to go through the queue.


Budget controls work everywhere

Whether you’re on the managed platform or self-hosted, every API key carries a monthly page allowance. If a key hits its limit, new jobs triggered via the API or deployment webhook are rejected cleanly – no silent overruns. Usage is reported back after every crawl, so the numbers stay accurate across however many ways you’re triggering jobs.


Which setup is right for you?

ManagedSelf-Hosted
Server requiredNoYes
Setup timeMinutesAn afternoon
Budget enforcementIncludedIncluded
Custom integrationsVia APIVia API + full code access
White-label brandingYesYes
Data stays on your serverNoYes


If you’re just getting started, managed is the fastest path to value. If you have specific data residency requirements, want to integrate deeply with your own tooling, or just prefer owning your stack, self-hosted gives you everything with no lock-in.

Either way, the audits are the same. The reporting is the same. The only difference is who’s running the server.


Available as a managed service through Website-Toolkit.co.uk, or as a self-hosted purchase (with annual renewal) for teams who want full control.