"Run an audit on my site" sounds like one task. It isn't. The word covers at least five different kinds of examination, each measuring something different, and the tools are not substitutes for one another. Running the wrong one first is why so many owners end up with a PDF full of red warnings and no idea what to do on Monday morning.
This is a plain-language guide to what each major tool actually measures, what it cannot see, and the order to run them in so the results are useful rather than alarming.
The Five Questions "Audit" Might Mean
Before choosing a tool, decide which question you're asking: Is my site fast? Is it findable? Is it indexed correctly? Is it converting? Is it secure and accessible?
These have almost no overlap. A site can load in under a second and be invisible on Google. A site can rank well and convert terribly. Tools that answer one question confidently will say nothing at all about the others — and the reports rarely make that limitation obvious.
PageSpeed Insights and Lighthouse — Speed and Technical Health
Google's PageSpeed Insights runs Lighthouse, an open-source auditing tool, and reports Core Web Vitals: loading performance, interaction responsiveness, and visual stability. Lighthouse also ships in Chrome's developer tools, so you can run it on any page including ones behind a login.
One distinction causes endless confusion. PageSpeed Insights shows lab data (a simulated load on a standardised device) and, when enough traffic exists, field data from real Chrome users. Field data is what Google actually uses for its page experience signals. A perfect lab score with poor field data means real users on real devices are having a worse time than your simulation suggests — trust the field data.
What it cannot tell you: whether your content is any good, whether you're targeting the right keywords, or whether Google has indexed the page at all. Speed is a tiebreaker, not a ranking strategy. Fixing a slow site rarely lifts a page from invisible to visible on its own.
Google Search Console — The Only Source of Truth
If you run one thing, run this. Search Console is not a third-party estimate; it's Google telling you directly what it did with your site. It's free, and it's the only tool in this list with access to your real data.
Three reports carry most of the value. Performance shows the actual queries you appeared for, your impressions, clicks, and average position. Pages (indexing) tells you which URLs Google indexed and, crucially, which it chose not to and why. URL Inspection lets you check a single page and request indexing after you fix it.
The pattern owners find most useful: sort Performance by impressions and look for pages with many impressions and near-zero clicks. Those are pages Google is willing to show that nobody wants to click — usually a title and description problem, and among the cheapest wins available.
What it cannot tell you: anything about Bing, anything about competitors, and nothing about what happens after the click. It also reports on a delay, so today's fix won't show today.
Analytics — What Happens After the Click
Search Console stops at the click; analytics starts there. Google Analytics 4 tells you which pages people land on, how long they stay, what they do next, and where they abandon.
Set up conversion events before you analyse anything. Without them you're reading traffic reports, not performance reports, and traffic without conversions is a vanity metric. Define what counts — a form submission, a phone tap, a checkout — and everything else becomes interpretable.
What it cannot tell you: why people left. Analytics shows behaviour, not motivation. For that you need session recordings, heatmaps, or simply asking customers.
Instant Diagnostics — Fast Orientation, Not Diagnosis
Tools that take a URL and return an immediate score — including our own free website diagnostic — are heuristic. They infer from what's visible at the URL: structure, meta tags, obvious technical signals. They are genuinely useful for orientation, especially when you don't yet know which of the five questions to ask.
Be clear-eyed about the limits. A heuristic score is not a crawl. It cannot validate your schema against live search results, assess content quality, or compare you against competitors. Treat the score as a pointer toward which real tool to open next, and be sceptical of any instant tool that presents itself as a complete technical audit — particularly ones that generate urgency before offering to sell you the fix.
Crawlers — Seeing Your Site the Way a Bot Does
Crawling tools walk your site link by link, exactly as a search engine would, and surface structural problems no page-level tool can see: broken internal links, redirect chains, orphan pages nothing links to, duplicate titles across templates, and pages accidentally blocked from indexing.
These issues are invisible from the front end. Your site looks perfect in a browser while a template bug quietly gives forty pages the same title tag. Crawlers are the only practical way to find that on a site of any size, and structural fixes tend to lift many pages at once rather than one.
What No Tool Measures
Every tool above evaluates mechanics. None of them evaluates whether your page is the best answer to the question someone typed — and that is what ranking increasingly depends on.
No audit tool will tell you your article is thin, your claims are unsupported, your competitor's page answers the question better, or your offer isn't compelling. Those judgements require reading your page next to the pages currently outranking you and being honest about the comparison. A green score on a page that doesn't deserve to rank is a well-optimised page that won't rank.
The Order to Run Them
Start with Search Console — establish whether Google can find and index your pages at all. Nothing else matters if the answer is no.
Then analytics, to see whether the traffic you do get behaves like interested traffic. Then a crawler, to catch structural faults affecting many pages at once. Then PageSpeed, to tighten performance once the fundamentals are sound.
Instant diagnostics fit anywhere as a fast orientation, particularly at the very start when you need to know which question to ask.
Run in this order, each tool's output tells you what to check next rather than handing you an undifferentiated list of warnings. Most audit paralysis comes from starting at speed — the most visible metric and, on a site nobody can find, the least consequential one.
Once the tools have told you what is broken, the fix is the real decision: our Web Development service rebuilds what an audit exposes, and our SEO / AEO service owns the search layer afterwards.