Bug reports a client can write and a developer can use
A good bug report is not a long one — it is one with context. What a developer actually needs to know, and how much of it can be captured automatically.
Read the articleResources
Practical writing for web agencies and teams: how to collect bug reports a developer can act on, what to monitor on client sites, and how to check cookies, security and WordPress.
A good bug report is not a long one — it is one with context. What a developer actually needs to know, and how much of it can be captured automatically.
Read the articleUptime, TLS expiry, PageSpeed, SEO regressions, DNS changes, email authentication and cookies — how often to check each one, and why that interval.
Read the articleA practical checklist for a site owner: what loads before consent, where banners go wrong, what Google Fonts does, and what a scan can and cannot tell you.
Read the articleVersions, plugins, exposed files, the admin panel, headers and backups — ten checks you can run from the outside in about an hour.
Read the articleFree tools
Every article ends with a tool for running the same check on your own site. All of them are free and none of them need an account.
Security, SEO, speed, email and blacklists in one check.
FreeVersions, plugins and the usual unsafe defaults.
FreeWhat a site sets before anyone consents.
FreeSPF, DKIM, DMARC and a deliverability score.
UpdatesWhat is new in the product — releases, improvements and fixes by date.
A 14-day trial, unlimited reporters and 14 monitoring services in one panel. Installing it takes five minutes.
14-day trial · unlimited reporters · six languages