Twenty-four checks, written up. Not a score out of a hundred and not an automated PDF. Someone opens your site, works through the list below, and sends you a document that names every problem, where it is, what it costs you and how long the fix takes.
Three fields. The third one is the one that makes the audit useful.
We answer your request and nothing else. No list, no sequence, no follow-up drip. If the five are gone this month we will tell you that instead of going quiet.
This is the whole list. It is here rather than behind the form because a checklist you can read before you hand over your email is the only kind worth publishing — and because you are welcome to work through it yourself.
01
02
03
04
05
06
Twenty of the twenty-four need no access at all — they are run against your published site. The four in The class system need read-only access to the Webflow project. If you would rather not give it, we run the twenty and the document says plainly which four are missing rather than quietly skipping them.
Every finding in the document has the same five lines. Severity, where it is, what it is, what it is costing you, and what it takes to fix. Two examples — made up, not from anyone’s site.
high
Medium
A typical audit comes back with somewhere between eight and twenty of these, sorted by severity, with the quick ones marked so you can clear them in an afternoon. It is a document, not a dashboard — you can forward it, print it, or hand it to a developer without anyone needing an account.
Free offers stop being free quietly, by getting slower and thinner until nobody notices they have gone. These are the numbers we would rather publish than quietly break.
5
Audits a month
When the five are gone they are gone until the first of the month. A real one takes three to four hours, and we have paying work.
3
Working days
From the day you send it. Not the same day — that promise belongs to actual enquiries, and we are not going to break it for a free audit.
0
Sales calls
The document arrives by email and that is the whole transaction. If you want to talk afterwards you have to ask us.
There is not one, but there is a limit — five a month, and it is on this page rather than buried. Some of the people we audit hire us afterwards. Most do not, and that is a perfectly good outcome: an audit you act on yourself still means you know where it came from.
Yes. This is the one hard requirement, and it is why the list above can be as specific as it is. If your site is on WordPress, Wix or Squarespace, the page you want is the technical SEO audit instead — that one is paid, and the fee comes off the work if you go ahead.
For twenty of the twenty-four checks, no — they can all be done from outside, on the published site. The four class-system checks need read-only access to the project. If you would rather not give it, we run the twenty and the document says plainly which four are missing.
The document puts an effort estimate on every finding, so you will be able to see for yourself whether the site needs three hours of work or three weeks. If most of it is quick, that is what it will say. If the site genuinely does need rebuilding, the findings will make that obvious without us arguing for it.
Yes, and plenty of people do. It is written to be read by whoever is going to do the work, with the location of each problem and the fix rather than a score out of a hundred. No account access is needed to read it.
Then the document is short and says so. That has happened, and it is not a wasted audit — knowing the build is sound is worth something, particularly if you inherited it from someone else.
Three fields, and a document back inside three working days. If your site is not on Webflow, the technical SEO audit is the one you want instead.