Had a great surprise this morning: yesterday’s deploy broke my SEO. 😅 And yes, I mean great. I built @37audits to catch exactly this kind of problem, so dogfooding my own tool — and having it catch a real issue I introduced myself — is a pretty good validation of the need. Here’s what happened: Yesterday, I updated the website copy to better explain our new monitoring feature. After finishing the copy, I committed, pushed, and called it a day. This morning, I opened 37audits.com/live-monitoring and… it was broken. 😬 The nice part? 37 Audits had marked the deployment on the audit history. The audit immediately before the deploy was healthy; the one after it showed the SEO issue. So it was SUPER easy to see exactly when the problem appeared and connect it to the deployment. Nothing like your own deploy breaking your site to prove why you’re building the tool. 😂

One of the most frustrating things about deploying a new version of a large system: A user finds a bug right after the release. But the release didn’t touch that part of the code. So… was the bug introduced by the new version, or was it already there? 🤔 Now, @37audits History marks deployments directly on the audit timeline, making it much easier to connect changes with issues.

😍

Just got my very first lead 😊

Working today on improving the API coverage of @37audits so I can expose it later as a MCP server. Doing that while I'm replacing the windshield of my monster truck 😉

Reactivating my X account this week. The goal is to post frequently showing my journey to make @37audits a profitable business in the next 4 months.

MCP of @37audits is ready and live. Documentation can be found here docs.37audits.com/mcp-server

Hello auditors!