Level one
Brands
The top-level container. Everything belongs to a brand, which is what makes a re-audit a comparison rather than a fresh start.
A working tool built on top of a forty-field SEO finding record. Brands, then audits, then findings, with every finding stored as data rather than as a paragraph.
AuditBuilder is findings management for SEO audits. You create a brand, run audits under that brand, and record findings under an audit. The finding is the unit the entire tool is built around, and it carries forty fields covering identity, scope, evidence, impact, remedy, risk, priority and lifecycle.
That structure is what makes an audit something other than a document. A register of records can be sorted by severity, filtered by effort, handed to a development team as a work queue, exported into whatever format each reader needs, and set beside the same brand's audit from six months ago.
It is the record structure my SEO Audit deliverable specifies, running as software instead of as a template I copy.
SEO audits are almost always written as prose. The finding is the atomic unit of an audit, but nothing stores it as a unit, so the audit cannot be diffed, re-run, filtered by severity, or handed to a dev team as a queue. It can only be read in the order somebody typed it.
A document is also frozen. The day it is delivered is the last day it is accurate, because there is nowhere to record that finding eleven shipped, finding four was declined and why, and finding nine was verified in production three weeks later.
Storing the finding as a record fixes all of that at once, and none of it can be fixed while the finding is a bullet point.
It gets used in four situations, and the fourth one is why signup is open.
Three levels of record, and then the exports that come off them.
Level one
The top-level container. Everything belongs to a brand, which is what makes a re-audit a comparison rather than a fresh start.
Level two
An audit is a dated pass over a brand. Its findings belong to it, so two audits of the same brand sit side by side instead of overwriting each other.
Level three
Forty fields per finding. Evidence capture is manual image upload in this version, but the locator fields are stored regardless, so automated capture can be added later without anyone re-entering a record.
Output
PDF, CSV, JSON and Google Sheets are the first export targets, chosen because they are what the client, the developers and the project manager each actually open. Google Slides comes later.
Stated up front rather than discovered: there is no billing and no support. The tool is free, it is maintained because I use it on my own client work, and nobody should adopt it expecting a support desk. That is a feature of the arrangement, not an apology for it.
Independent SEO consultants and in-house leads who run the same audit repeatedly and want the findings to outlive the delivery date. If you have ever re-typed last quarter's findings into this quarter's document, it was built for you.
Signup is open and login runs through GitHub OAuth. Google is not enabled as a provider yet.
This is the one product here you can sign up for and use today.
Status and access
A single-page app on the edge with a hosted Postgres backend behind it.
Stack
The tool is free and the specification behind it is published in full. If you would rather have the audit run, argued and sequenced by the person who wrote both, that is an engagement.