Technical SEO Audits That Tell You What to
Fix First
Most SEO audits arrive as a sixty-page PDF listing two hundred issues, ranked by nothing in particular. Somewhere in there are the three problems actually costing you rankings. Good luck finding them.
I run audits the way I’d want to receive one. A proper crawl of your site, then a prioritised list of what’s genuinely holding you back — ordered by impact, explained in plain English, with a clear view of what to do about each one.
I came to SEO from web development, which matters here more than anywhere. When I find a technical problem, I can usually tell you exactly why it’s happening and what the fix involves, rather than handing your developer a vague instruction and hoping.
What’s covered
Crawlability and indexing Whether Google can actually reach and understand your pages. Robots.txt, XML sitemaps, orphan pages, redirect chains, and crawl budget being wasted on URLs that shouldn’t exist.
Site speed and Core Web Vitals What’s genuinely affecting your rankings and user experience, separated from the lab-test numbers that look alarming but don’t matter.
Site structure Internal linking, URL structure, duplicate and thin content, and whether your most important pages are actually positioned to rank.
On-page fundamentals Titles, meta descriptions, heading structure, and schema markup — including the ones silently duplicated across dozens of pages.
Mobile and rendering How your site behaves on the devices most of your visitors actually use, and whether JavaScript is hiding content from search engines.
What you get
A prioritised action list — not an issues list. Ranked by likely impact on traffic and rankings, so you know what to do first and what can wait.
A walkthrough call where I explain the findings properly and answer questions. You shouldn’t need a translator to understand your own audit.
Optional implementation. If you’ve got a developer, they’ll get clear instructions. If you haven’t, I can do the work myself.
Who this is for
Businesses who suspect something technical is wrong but don’t have anyone in-house to diagnose it. Particularly useful if you’ve invested in content or links and rankings still haven’t moved — that’s usually a sign something structural is in the way.
FAQs
How long does an audit take? Typically [X] working days from getting access, depending on site size. Larger ecommerce sites take longer because there’s more to crawl and more that can go wrong.
Do you implement the fixes or just report on them? Either. Some clients want the audit and hand it to their own team. Others want me to do the work. Both are fine — I’ll price them separately so you can decide.
How is this different from running Screaming Frog myself? Tools find issues. They don’t tell you which ones matter for your site, your market, or your competitors. The value is in the prioritisation and the interpretation, not the crawl.
How often should I audit? Once a year for most sites, or after any significant change — a redesign, a migration, a platform switch. Those are exactly when things break quietly.
Not sure whether it’s technical, content, or links holding you back?
Book a free 15-minute call. I’ll take a look before we speak and
tell you honestly where I think the problem is.