Request an audit
The teardowns show how this work is done, in public, for free. An audit is the same rubric applied to your site, with your own numbers in the room, delivered privately, with the fixes sequenced against what you can actually ship.
Scope and price are agreed in writing before any work starts. Availability is confirmed when you inquire.
- Six sub-scores and a composite
- Three prioritized fixes
- Right of reply before publication
- Published openly on this site
- Everything in the teardown, delivered privately
- Your analytics and revenue read alongside the rubric
- An implementation sequence written against your stack
- One working session to walk through it
- Everything in the audit
- Template-level specification for each fix
- Copy and structure for the capture units
- A re-score once the fixes are shipped
Every engagement is quoted in advance and invoiced on delivery. Scope is written down before work begins so both sides know what is included.
What you receive
- A score for each of the six rubric dimensions, with the evidence behind it
- A composite, calculated the same way as every published teardown
- Three fixes, ordered by expected return per hour of work
- What each fix should move, stated against the published band definitions rather than as a traffic or revenue forecast
- The rubric version and the date, so the score can be compared later
What we need from you
- Read-only access to your analytics
- Your email platform dashboard, or list size, open rate and send history
- A revenue figure, even a rough one, and how it is currently earned
- The platform and theme you publish on
Nothing shared privately is published. The evidence standard for public teardowns is deliberately stricter: public scores use public evidence only, so an audit can use more than a teardown can.
Who this is for
- Publishers already earning something, where a structural fix is worth more than another post
- Sites with enough archive that its behaviour can be read
- Operators who intend to ship the fixes rather than collect them
Who it is not for
- Very new sites. Read the rubric and build. There is not enough there to audit yet
- Anyone wanting a traffic or revenue forecast. This work does not produce one
- Anyone looking for validation. The rubric is published, so the standard is not a surprise
Audit inquiry
Answered with a yes, a no, or a question. No sequence and no follow-ups.
What access do you need?
Read-only analytics, your email platform dashboard, and a revenue figure. Nothing shared privately is published.
Do you implement the fixes?
No. The deliverable is specified well enough that you or your developer can build it. Any implementation referral is unpaid.
Will my site be scored publicly?
Not while an engagement is live, and an audit does not revise an existing public score. That rule is stated in the editorial standards.
How is the score calculated?
Identically to every published teardown: the unweighted mean of six sub-scores, rounded to one decimal place. The bands are published on the rubric page.
General contact
Corrections, right of reply, press, or anything the other forms do not cover. The corrections policy is published.
Nominate a teardown subject
Sites with a real archive and something at stake go first. You can nominate your own.