Website audit
A written review of the site you already have, in the order I would fix it.
Who this is for
- Anybody about to spend money on a redesign who cannot yet say what is wrong with the current one.
- A team whose traffic or signups moved and nobody can explain why.
- A founder who suspects the site is fine and wants somebody to disagree with them in writing.
Who it is not for
- A site that is three weeks old with no traffic. There is nothing to audit yet — what you need is somebody to use it in front of you, and that is free.
- Anybody who wants the document to justify a decision already made. I will write what I find, and if what I find is that the site is fine, that is the report you get.
- Ranking guarantees. Nobody can give you one, and anybody who does is selling something else.
How I work
- 01
You tell me what you think is wrong
Before I look. Your theory is useful data even when it is incorrect, and reading the site with your suspicion in mind finds things a blind pass misses. It also means the report answers your question rather than a generic one.
- 02
I use the site the way somebody who does not care would
On a phone, on a bad connection, without reading carefully. Most of what is wrong with most sites is found here rather than in a tool: the thing that is not clickable, the sentence that assumes you already know, the form that fails silently.
- 03
Then the measurable half
Speed and Core Web Vitals, accessibility against WCAG, crawlability and indexation, structured data, the addresses that changed and never redirected, and what a language model actually understands about you from the markup. This part is checkable and the report shows its working.
- 04
One document, ordered by what it costs you
Not a list of 200 findings from a scanner. Each item says what is wrong, what it is costing, how hard it is to fix, and whether it matters this quarter. The first section is what to do this week; the last is what to ignore, which is usually the most useful part.
What you end up with
- A written report, ordered by impact rather than by category.
- The findings a tool would give you, with the ones that do not matter removed and said so.
- A "fix this first" list, short enough to actually do.
- A "safe to ignore" list, so nobody sells you the same fixes next quarter.
- Fifteen minutes of questions by email afterwards, included.
Questions
Is this an SEO audit?
SEO is part of it, not all of it. A site can be technically perfect for a crawler and still lose every visitor at the same paragraph, and a report that only covers the crawler half will not find that. The audit covers what people do on the site, what search engines can read, what language models understand about who you are, and how fast the whole thing loads — because in practice those four go wrong together.
What do I actually get?
A document. Not a call, not a slide deck, not a dashboard with a score out of a hundred. Writing it down means you can forward it to a developer and they can act on it without me being in the room, and it means every claim in it has to survive being read twice. If you want to talk it through afterwards, fifteen minutes of questions by email is included.
Will you tell me things I already know?
Some, and that is worth something on its own — a suspicion you have had for six months, written down by somebody else with the cost attached, is often what finally gets it fixed. But if the report is only that, tell me and I will say so in the summary rather than padding it.
Can you fix what you find?
Yes, separately, and there is an obvious conflict of interest in that, so here is how it is handled: the report is written and sent before any conversation about fixing anything, the price does not change based on whether you hire me afterwards, and every finding says how hard it is to fix so you can hand it to somebody cheaper. Plenty of these reports end with the client fixing it themselves, which is a fine outcome.
Tell me about
your project.
What you are building and what is in the way. Five minutes of typing, and a written reply within five working days.
Start a projectIf it is not a fit, I will say so in the reply and tell you why.