How Website-Toolkit works

Start on the audit page. Drop in a URL and your email, then click the verification link we send — there's no account, password, or card. The crawler does a full-site pass of up to 200 public URLs, checking for broken internal links, redirects, missing tags, external 404s, and cache behaviour.

When it finishes you get a private Magic Link by email: a password-free results URL you can bookmark or forward to a client as a quality-assurance report. That link is the home base for everything that follows.

Open the Magic Link to land on the results dashboard: a site-health score, summary stats, and tabs that group every finding by type — broken links, missing metadata, redirects, external 404s, and so on.

This is where you decide what actually matters. Work through the tabs, expand a category to see the affected pages, and get a feel for the size of the job. You can read it all in the browser or grab the Excel export if you'd rather work from a spreadsheet.

The audit has its own to-do list, built right on the results page. Add a finding and it becomes a tracked, tickable task — grouped by category, with the affected URL attached — without leaving the audit or creating a project first. You can also add your own tasks for anything the crawl can't see (copy changes, a missing legal page, a client request).

Because the list is built from the crawl rather than typed by hand, it stays tied to the site it came from. No “which page was this again?” a week later.

As you work through the list, tick items off. Marking a task as fixed records that the work is done and keeps your remaining workload honest — the dashboard always reflects what's still outstanding versus what's already handled.

When you re-crawl later (see monitoring below), the toolkit can tell you whether something you marked fixed has actually stayed fixed, or quietly broke again.

An audit is a snapshot; a project is the working surface you run a go-live or a move from. From the results page, convert the crawl into one of two project types:

• Launch project — for taking a new or rebuilt site live. You get a checklist of pre- and post-launch tasks, with the items your audit could already verify ticked off for you, plus a per-page Site Content log for checking every URL on desktop, tablet, and mobile.
• Migration project — for domain changes, URL-structure rebuilds, or host moves. Same checklist workflow with a pre- and post-migration task set, plus a redirect map that checks each old URL now 301s to the right page on the new site rather than 404ing or bouncing to the homepage.

The project remembers which crawl it came from, so results and checklist stay linked. Open the results again later and it knows a project already exists — it offers to take you there rather than starting a second one. Each project has a private edit link for you and a read-only share link for the client.

A project's settings are what make it more than a generic checklist. Open settings to tell it about the environments and how it should behave:

• Staging & live URLs — record both so the project knows which environment a given crawl belongs to. When you go live it can even suggest your live domain from the staging one and ask you to confirm.
• Staging login — store the HTTP Basic Auth username and password for a protected staging site, then trigger an authenticated crawl from inside the project so the version that actually matters gets the full audit. Credentials are saved with the project and never shown again after you save them.

Re-crawl and sync at any point: new pages get pulled in and flagged as needing checks, while every tick you've already made stays exactly where it was. The checklist keeps pace with the site instead of falling behind it.

Monitoring re-crawls your site on a schedule and tells you what changed against the baseline — a page that started 404ing, a section of content that vanished, a certificate about to expire.

Once a domain has at least one completed audit, open your client area and click Request monitoring on that domain. The audit is the baseline, which is why it has to run first. We'll schedule the recurring crawl and confirm it's live — you'll see the schedule in plain English against the domain.

Monitoring is what your plan actually limits. Adding domains and running audits are unlimited; the cap is on how many domains are monitored at once. If you want to move monitoring to a different site, click Cancel monitoring — the domain and all its past audits stay exactly where they are, and the slot is immediately free for another domain.

One thing worth knowing: a monitored domain's most recent audit is kept indefinitely, rather than ageing out with the others.

Paid accounts can manage their domains & audits from the client area. Add a domain, request an audit of up to 2000 URLs and easily access results.

Your client area also handles:

• Per-domain settings — spelling and content-change checks on or off, dictionary language, and URL filters to exclude sections you don't want crawled.
• Form testing and time tracking — turn either on and generate the token its browser extension needs.
• API and MCP access — generate a token that lets an AI assistant or a script read your audits, tick off issues as it fixes them, add domains and start audits. Rotate or revoke it any time; changes take effect immediately.
• Audit retention — each audit shows exactly when it will be deleted. Audits are kept for 90 days and only the two most recent are retained per domain, so download anything you need to keep. A monitored domain's latest audit is exempt and kept indefinitely.

To learn more, visit the Client Area page.

Three Chrome extensions extend the toolkit into the browser. Sign in with your account to unlock the premium features.

• Form Tester — save the details you use for testing forms once, then fill any form on any of your sites in a click. One token covers every domain on your account, and every fill is logged back to your client area so you can see what was tested and when.
• Focus Mode — Hide notifications and distractions with custom CSS rules to stay in the zone while working through a checklist.
• Time Tracker — start and stop a timer against a launch or migration project you're already working on. Time lands against that project automatically, and the reports in your client area show where the hours actually went, per project and across all of them.

Turn Form Testing or Time Tracking on from your client area to generate the token each extension needs.

Getting feedback on a build usually means an email that says “the thing at the top of the pricing page looks wrong.” The feedback widget replaces that with something you can act on.

Start a feedback project from your client area and you'll get a single script tag to drop onto the site — staging or live, it doesn't matter. Anyone visiting gets a small button in the corner. They click it, point at the element they're talking about, and leave a note. The element stays outlined, so there's no ambiguity about which one they meant.

They can attach:

• 📷 Screenshot — captured in the browser, with the element still outlined
• 📁 An image — uploaded from their machine
• 🎙️ Voice — a recorded voice memo, for when typing it out is the slow way

Everything lands in a dashboard grouped by category. Each item has a status you click through — Not started → In progress → Completed — plus text and status filters, so a long list of feedback stays workable.

The widget has no external dependencies and runs isolated from the host page's styles, so it can't break the site it's reviewing and the site can't break it.

Scroll tracking is part of the feedback widget above. It is an opt-in feature for your feedback projects that records evidence of page reviews. It measures how much of a page was seen and for how long.

To learn more, visit the Scroll Tracking Help page.