A site health audit you can hand to a client: sections, scoring, a sample and next steps
Short answer: A client-ready site health audit is a short report, usually two to five pages, that checks speed, search visibility, broken pages, mobile use, trust basics and forms, scores each area in plain words and ends with a ranked fix list. You can build it free with Google's PageSpeed Insights (a free page speed test), Google Search Console (a free tool that shows how your site appears in search) and the free version of Screaming Frog (a desktop site crawler that stops at 500 pages). An AI workflow in Ploy (an AI marketing platform that builds and runs websites) can draft one, but a person must check it before the client sees it.
A client asks, "Is my website OK?" You can run tools all day, but a screenshot of a score is not an answer. What they need is a page they can read in five minutes and act on.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The direct answer: hand over a report with six short sections, one clear score per section, and a fix list ordered by effort and impact. The tools produce the data. Your job is to turn it into decisions. If the report is only a printout of tool output, the client will not read it.
This page gives you the section layout, a scoring scheme you can reuse, the free tools and their limits, a sample, and a test plan. It also shows where Ploy fits as one way to draft the report, and when you should not use it.
This page may contain affiliate links from which Blur Studio earns commissions.
What a client wants from an audit
A business owner wants three answers: is it broken, is it costing me customers, and what do I do first. They do not want to learn what Core Web Vitals are. So write the top of the report for the owner and put the detail at the back for whoever fixes things. If you already do a monthly routine, our website health after launch page covers what to monitor between audits. This page covers the document you hand over.
The six sections
- Summary (half a page). Overall status in one word (healthy, needs work, urgent), the three biggest issues, and the first fix.
- Speed and stability. Whether key pages pass Google's Core Web Vitals (three measures of loading, responsiveness and layout shift), from PageSpeed Insights.
- Search visibility. What Google Search Console says about indexing: how many pages are indexed, and which are not found, redirected or crawled but not indexed.
- Broken pages and links. 404 errors (page not found) and broken internal links, from Search Console and a crawler.
- Mobile and usability. Whether a visitor on a phone can find the phone number, read the text, tap a button and finish the main action.
- Forms, trust and basics. Does the contact form arrive in the inbox, is the site on HTTPS (secure connection), are the privacy page, address and reviews visible.
Add a one-page appendix with the raw numbers and dates so a developer can reproduce each finding.
Free tools and their limits
| Tool | What it is | What it gives you | Limit to know |
|---|---|---|---|
| PageSpeed Insights | Google's free page speed test | Field data (real visitors, previous 28 days) and lab data (one simulated load) | Field data needs enough visits; lab data is a single test |
| Lighthouse | An open-source auditing tool from Google, built into Chrome | Scores for performance, accessibility, SEO and more | A simulated load on your machine; results vary run to run |
| Google Search Console | Google's free tool that shows how the site appears in search | Indexing, not found pages, soft 404s, redirects | Needs ownership verification by the site owner |
| Screaming Frog SEO Spider | A desktop program that crawls a site like a search engine | Broken links, redirects, missing titles | The free version crawls up to 500 URLs; the paid licence is listed at £199 a year, in pounds, as of November 2026; check the page |
| Looker Studio | Google's free dashboard builder | Shows your numbers on one shareable page | Free to use; it displays data and does not write the findings for you |
On Core Web Vitals, Google says a page passes when the 75th percentile of INP, LCP and CLS are all Good: INP (how fast the page reacts to taps and clicks) at 200 milliseconds or less, LCP (how fast the main content shows) at 2,500 milliseconds or less, CLS (how much the layout jumps) at 0.1 or less. If there is not enough INP data, LCP and CLS decide. Do not tell a client that a perfect Lighthouse score will raise their rankings. It will not be a promise anyone can keep. Lighthouse is a diagnostic, not a ranking button.
Paid options exist. Semrush is a paid search marketing subscription with site checking and reporting tools; its price page showed SEO at $139 a month ($117.33 billed annually), Starter at $199 and Pro+ at $299 a month as of November 2026, with no currency named, so check the vendor page. A freelancer or agency can run the audit by hand and quote per site. See Semrush alternatives for the other tools in that class.
A simple scoring scheme you can reuse
Do not invent a score out of 100 with weights nobody can explain. Use a traffic light plus a short reason. This scheme is mine, not an industry standard, so tell the client that.
| Status | Meaning | Example rule |
|---|---|---|
| Green | Fine, nothing to do now | Key pages pass Core Web Vitals; no new 404s this month |
| Amber | Fix in the next month | One key page fails LCP; 5 or fewer 404s with no visits |
| Red | Fix this week, it is costing leads | Contact form does not arrive; the home page is not indexed; the site is not on HTTPS |
Then rank the fix list with two columns: effort (small, medium, large) and impact (low, medium, high). Fix small-effort, high-impact items first. Keep the rules written down so next quarter's report is scored the same way.
How to run the audit, step by step
- Get access. Ask the client to add you as a user in Search Console, or ask for the verified property. Without it you cannot see indexing data.
- Pick five key pages. The home page, the main service page, the contact page, the most visited blog or landing page, and the page ads send people to.
- Run PageSpeed Insights on each, on mobile first. Note whether it passes and which of the three measures fails. Record the date.
- Open the Search Console Page indexing report. Count pages in each status, and list the "Not found (404)", "Soft 404", "Page with redirect" and "Crawled, currently not indexed" groups.
- Crawl the site. With the free Screaming Frog, note whether the site has more than 500 URLs. If it does, label the crawl as partial in the report.
- Test the contact form. Submit it, and confirm the message arrives where the client reads it. Check spam too.
- Use the site on a phone. Try to find the phone number and complete the main action with one hand.
- Score each section, write the summary last, and rank the fix list.
A sample report page (made-up numbers)
This sample shows the level of detail. All findings and numbers are invented.
| Section | Status | Finding | First fix |
|---|---|---|---|
| Speed | Amber | Home page passes; service page fails LCP on mobile (3.4 seconds, as of the run date) | Compress the hero image |
| Search visibility | Amber | 42 pages indexed, 6 "Crawled, currently not indexed", all old tag pages | Merge or remove thin tag pages |
| Broken pages | Green | 2 new 404s, both with no visits | Leave as is or add redirects |
| Mobile and usability | Red | Phone number is not tappable on mobile | Make it a click-to-call link |
| Forms and trust | Red | Contact form email lands in spam | Set up proper sending for the form |
Summary: "The site loads well and is found by Google, but two issues are likely costing enquiries: the phone number cannot be tapped on phones and the contact form emails land in spam. Fix those two this week." That is a report a client acts on.
Drafting the report with Ploy, one option
Ploy is an AI marketing platform from Ploy, Inc. You chat with an AI agent that builds and updates pages and hosts the site. It runs reusable workflows called Ploybooks, and Ploy's changelog lists a new "website health and usability audit" Ploybook on 19 October 2026. Ploy's docs also say you can ask the agent to run a Lighthouse audit. Google Analytics 4 and Search Console connect on every plan, including Free (the integrations docs, updated 30 October 2026, say so; the pricing page's Google row covers Google Workspace tools from Starter, so check the card in your account). See Ploybooks explained for how a Ploybook works.
The vendor facts, as of November 2026 on ploy.ai/pricing: Free is $0 with 500 AI credits a day up to 2,000; Starter is $50 a month ($480 billed yearly) with 4,000 credits a month; Pro is $300 a month ($2,880 billed yearly) with 24,000 credits a month; Enterprise is by quote and adds done-for-you Ploybook setup. Credits do not roll over, and Ploy does not publish a credit cost per run. Ploybooks can run on demand or on a schedule; new schedules end after 90 days by default.
The limits matter for audits. Coverage is reported per run, so read what a given run actually checked, for example how many pages, and do not describe it to a client as a complete audit unless it was. AI output needs human review before it reaches a client. Always check the findings that drive a Red status by hand.
Ploy's agency setup is one organization per agency with one workspace per client. See Ploy for agencies. It has no described white label option, so the report you hand over should carry your own branding and be written by you.
What goes wrong
- Tool output as a report. A list of 80 warnings with no ranking. Rank or cut.
- Chasing a perfect score. A client asks for 100 on every tool. Spend effort where visitors and leads are.
- Partial crawls presented as full. The free Screaming Frog limit is 500 URLs.
- One-off data. A single Lighthouse run varies. Run key pages more than once or rely on PageSpeed Insights field data when it exists.
- No access. Without Search Console access you are guessing about indexing.
- Quality control gaps. Check the basics with the quality control checklist for AI-built websites before declaring a site healthy.
Test plan: is your report good enough
- Pass: a client who is not technical can say, after five minutes, what the biggest issue is and who will fix it. Fail: they ask what Core Web Vitals are before they get to the point.
- Pass: a second person can repeat your findings from the appendix and get the same result. Fail: they cannot.
- Pass: the report is scored by the same rules next quarter. Fail: the rules changed and numbers cannot be compared.
- Pass (AI draft): every Red or Amber finding in the draft matches what you see by hand. Fail: any invented page, number or cause.
When not to use Ploy for this
Skip Ploy if you only audit a handful of sites a year, since the free Google tools and your own time cover it. Skip it if the client sites are on another platform and you have no reason to move them, since a Ploy audit workflow is useful mainly inside Ploy. Skip it if you need a branded, white-label client portal; for that, see white label reporting and agency client portal software. Pick a paid SEO suite when you need ongoing rank tracking and backlink data, which a health audit does not cover.
How I'd approach this
I would run the first audit by hand on one friendly client, using only free tools, and write the report in the six-section layout. Only after that would I try an AI draft, for example a Ploybook in Ploy on its Free plan, and compare its findings with mine line by line. If the draft matches and saves real time, I would keep it as a first pass and still check every Red item by hand. For a rolling check between audits, see a weekly website report that writes itself.
If you need a custom version, with AI agents that use your business knowledge, connections to your CRM and calendar, a half-built flow finished, or ongoing care, Blur Studio builds that. See what the business work includes.
First-week plan. Day 1: get Search Console access and pick five key pages. Day 2: run PageSpeed Insights and the Search Console indexing report. Day 3: crawl the site and test the form and the phone experience. Day 4: score each section and rank the fixes. Day 5: write the summary last, send the report, and book a short call to agree the first fix. Also read how to check if your website has SEO problems for the search side in more depth.
Related guide: How to Show a Client Site Errors and Broken Pages.
A closely related page covers the same ground from another angle: Search Console and GA4 in One Place: Options.
Questions people ask
What should a website audit report include for a client?
A one-word status and top three issues, then short sections on speed, search visibility, broken pages, mobile use, and forms and trust, each with a traffic-light score and a ranked fix list. Add an appendix with raw numbers and dates so a developer can repeat each check.
What free tools can I use for a site audit?
PageSpeed Insights for speed, Lighthouse for a wider diagnostic, Google Search Console for indexing and not found pages, and the free version of Screaming Frog for crawling up to 500 URLs. Looker Studio is free for turning the numbers into a shareable page.
How long should the report be?
Two to five pages for a small business site, with the summary on page one. Longer reports are rarely read. Put detail in an appendix.
Can Ploy run a site audit for me?
Ploy's changelog lists a website health and usability audit Ploybook, and its docs say the agent can run a Lighthouse audit. Runs use AI credits, coverage is reported per run, and the output needs human review before a client sees it. See Ploybooks explained.
How much does Ploy cost for this?
Ploy's plans, as of November 2026, are Free at $0, Starter at $50 a month, Pro at $300 a month and Enterprise by quote. Ploy does not publish a credit cost per run, so test one audit before you plan a batch. See Ploy pricing.
How often should I audit a client site?
A full audit each quarter is usually enough for a small site, with a lighter monthly check in between. Re-audit after any redesign, move to a new platform or big content change. See keeping your website fresh.
Does a high Lighthouse score improve rankings?
Do not promise that. Lighthouse is a diagnostic for finding problems, not a ranking switch. Focus on whether real visitors have a fast, usable site and whether the pages that bring leads pass Google's Core Web Vitals.
Do I need the client's permission to audit their site?
Public pages can be tested with free tools, but Search Console indexing data needs the client to give you access. Get written agreement on scope, and tell the client what you will do with the data. Check local law for anything beyond that.
More in this topic: Websites: simple stats and reports for owners and clients (9 guides) →