Skip to content

Changelog

What changed,
and why.

Entries are added when something a reader could notice changes — a check added, a finding reworded, a behaviour corrected. Not every push.

Releases

last updated 30 September 2026
  • The paid service has a page of its own

    /services says what an engagement includes and how one starts: a demo with a person, then set-up together. There is still no signup and no checkout, and the free scan is unchanged.

  • Which AI assistants name you, and which AI bots read you

    Paid engagements can track the questions you care about in Claude, ChatGPT, Gemini and Perplexity each week, and count from your own server's requests which AI crawlers fetch which pages, checked against the addresses their companies publish.

  • A full-site audit, with accessibility on every page

    The site audit crawls a whole site against more than three hundred checks, including accessibility mapped to WCAG 2.2 A, AA and AAA, can sign in to reach pages behind a login, and records what changed between crawls.

  • Speed, page changes and Search Console, in one place

    Speed is measured on a schedule and from real visitors; watched pages report their changes; and Search Console and Analytics sit beside the audit's findings. Uptime monitoring is built and coming soon.

  • Accounts are by invitation, with roles

    Clients sign in to Website Health, a product of its own, with owners, members and viewers. Accounts are opened by us, not by a signup form, and the free scan still needs none.

  • Scanner v2.1.0

    A site we cannot reach no longer gets a score

    If the scanner never receives a page, there is nothing to measure, so the report now says so instead of publishing a number. A site behind a bot wall or a firewall rule was previously scored on the handful of checks that run without a document, which read as a verdict on the site rather than on the scan.

  • Fifteen new reference pages, and an API you can read

    Checks that people look up by name — robots.txt, XML sitemaps, TTFB, cache headers, viewport, tap targets, the lang attribute and more — now have their own pages with the fix for each stack. The scan API is documented at /docs: two calls, no key.

  • The scanner and the report got a workbench

    The chrome is dark now and the report sits on it as paper, so the severity marks read as marks. Quick try actually runs the scan rather than filling the box, and the smallest text on the site went up a step.

  • Scanner v2.0.0

    Accessibility became a scored category

    Thirteen accessibility checks, a sixth category in the score, and an AI readiness score that asks whether there is anything on the page once a crawler is let in — not merely whether it was let in.

Run a scan on your own site.

Usually under a minute. No account, no card.

Run a scan