Back to blog

Blog article

SEO Site Health Check: What It Covers and How to Run One Clients Can Trust

The Automate Team November 1, 2026

An SEO site health check is a structured check-up of a website that finds problems early, before they cost traffic, enquiries, or sales.

What an SEO Site Health Check Is

An SEO site health check is a structured check-up of a website: a quick, repeatable review that answers one question — is this site in good working order for search engines and visitors, or is something quietly going wrong? It is not a full audit, and it is not a redesign. Think of it like a routine health check rather than a hospital stay: it looks for problems early, before they cost traffic, enquiries, or sales.

For agencies and freelancers, a health check is one of the most useful services to offer, because it is easy for a client to understand and easy to repeat. A client does not need to know what a crawl budget is to understand "your site has three broken key pages and your main service page has no description in search results." A health check turns vague worry about a website into a short, prioritised list.

It is also useful for your own site. Sites drift: pages are added, plugins update, links break, and content goes stale. A regular health check catches that drift while the fixes are still small.

How a Health Check Differs From a Full Audit

The two are often confused, and the distinction matters when you sell or scope the work. A health check is broad and shallow; a full audit is narrow and deep.

Site health checkFull audit
PurposeFind out whether anything is wrong, and what matters mostInvestigate a known problem or prepare a detailed fix plan
ScopeThe whole site, at a summary levelSelected areas, in detail, with evidence per page
TimeUsually under an hour for the checks themselvesSeveral hours to several days, depending on site size
OutputA short, prioritised list with a traffic-light summaryA detailed report with recommendations, evidence, and a fix order
FrequencyMonthly or quarterly, as a routineAt onboarding, before a redesign, or when something breaks

Neither replaces the other. A health check tells you where to look. A full audit tells you exactly what to do once you are looking there. If a health check finds a serious problem — a large drop in indexed pages, for example — that is the trigger for a deeper audit, not a reason to guess at a fix.

What a Good Health Check Covers

A health check that only looks at one thing, such as page speed, is not a health check. A site can load quickly and still be invisible in search, or rank well and still lose visitors to broken pages. Cover these six areas, even briefly, and you will catch most common problems.

1. Can search engines find and index the site?

Check that the important pages are indexable, that there is no accidental "noindex" on key pages, and that the site is not blocking crawlers it should welcome. A single wrong setting here can remove a whole site from search, which is why this check comes first. It is also worth checking that the number of indexed pages looks roughly right for the size of the site: a sudden drop usually means something changed.

2. Are titles and descriptions in place?

Every important page should have a unique, accurate title and a meta description that describes the page honestly. Missing, duplicated, or misleading titles are among the most common findings on real sites, and they are cheap to fix. Read them as a searcher would: would you click this result, and would you land on what you expected?

3. Do the key pages work?

Check the pages that matter most — the homepage, the main service pages, and the contact or enquiry page — for errors, broken links, and missing content. A broken link on an obscure blog post from years ago is a minor issue. A broken enquiry form on the contact page is a lost client. Prioritise by importance, not by count.

4. Is the content thin, duplicated, or out of date?

Look for pages with very little useful content, pages that repeat each other, and pages that describe services or prices the business no longer offers. Thin and duplicated pages rarely rank well, and out-of-date pages damage trust when a visitor does notice them. Note them for rewriting or merging; do not try to fix every page in a health check.

5. Is the site usable on a phone?

Most visitors now arrive on a phone, so check the site on a real phone, not just by resizing a desktop browser. Look for text that is too small to read, buttons that are hard to tap, content that overflows the screen, and forms that are awkward to complete. A site that is hard to use on a phone loses visitors before its content gets a chance.

6. Is the site fast enough to keep visitors?

Slow pages lose visitors, and the effect is worst on mobile connections. You do not need laboratory precision in a health check: load the key pages on a phone connection and note any that feel slow, then record which ones need proper speed work. Speed is a symptom worth investigating, not a single number to chase.

How to Run a Health Check in About 30 Minutes

A health check earns its keep by being repeatable. Use the same steps each time, so this month's results can be compared with last month's, and a new problem stands out.

  • Start with the homepage and the money pages. Open the homepage, the main service pages, and the contact page. Note anything broken, missing, or confusing before you touch any tool.
  • Run an automated scan. Use a tool that checks titles, descriptions, links, status codes, and indexability across the site, and save the output. The scan gives you coverage; your judgement gives it meaning.
  • Check indexability and search appearance. Confirm the key pages can be indexed, and look at how they actually appear in search results — title, description, and any warnings.
  • Test on a phone. Browse the key pages on a phone. Note anything that is hard to read, tap, or complete.
  • Sort findings into red, amber, and green. Red means fix now: broken key pages, missing indexability, a broken enquiry form. Amber means fix soon: duplicated titles, thin pages, slow key pages. Green means healthy, or minor issues that can wait.
  • Write three priorities, not thirty findings. Pick the three fixes that would help the most, explain each in plain language, and say what happens if it is left alone. A client who receives thirty undifferentiated warnings usually fixes none of them.

Reading a Health Score Honestly

Many tools present a single health score, and it is tempting to treat it as a verdict. Resist that. Scores are calculated differently by every tool, they weight things differently, and they cannot know which pages matter to the business. A site can score well and still fail at its job — for example, a fast, technically clean site with an unclear offer and no working enquiry form.

Use the score only as a starting point, and always read the findings behind it. Ask three questions of any health check result: which pages are affected, does it affect visitors or search visibility, and what would fixing it change for the business? If you cannot answer those, the finding is not ready to share with a client.

Be equally careful in the other direction. A low score does not mean a site is broken, and a long list of warnings does not mean a business is failing. Many warnings are minor, many affect pages nobody visits, and some are false positives. The value of a health check is in the triage — separating the few things that matter from the many that do not.

Common Health Check Findings, and What They Usually Mean

  • Missing meta descriptions on key pages. Search engines will invent a snippet from the page content. Sometimes that works; often it picks the least persuasive sentence. Writing a proper description is a small fix with a visible effect.
  • Duplicated titles across many pages. This usually means a template is generating titles automatically and nobody has reviewed them. Each important page deserves its own title.
  • Broken internal links. A few broken links are normal on a large site. A broken link on a main navigation page or a key service page is not, and should be fixed first.
  • Pages indexed that should not be. Thank-you pages, internal search results, and staging pages sometimes leak into search. They waste crawl attention and can confuse searchers.
  • Outdated content on service pages. Old prices, discontinued services, and departed team members are trust problems, not just SEO problems. A health check should flag them even though no tool will.

How Often Should You Run One?

For an active client site, monthly is a sensible default. That is frequent enough to catch regressions — a plugin update that breaks a form, a page that disappears in a redesign — without turning the check into busywork. For a small, rarely changed site, quarterly is enough. For any site, run an extra health check after a redesign, a migration, or a major platform change, and compare it with the check from before the change. That before-and-after comparison is the simplest proof that nothing was lost in the move.

Keep the reports. A single health check is a snapshot; a year of health checks is a story. When a client asks whether their site is improving, a folder of dated checks with the red items shrinking over time is a better answer than any single score.

Offering Health Checks as a Service

A health check makes a good first service for an agency or freelancer, because it is bounded, repeatable, and easy to explain. Scope it clearly: say what the check covers, that it is a summary rather than a full audit, and that the deliverable is a prioritised list with three recommended fixes. Price it as a fixed service, not by the hour, so the client knows what they are buying.

Do not oversell it. A health check finds problems; it does not guarantee rankings, traffic, or sales, and it does not fix anything by itself. Clients who are told honestly what a health check can and cannot do are more likely to buy the follow-up work — because they trust the person who found the problems to fix them.

Try a Health Check on Your Own Site First

The fastest way to learn what a health check feels like is to run one on your own website, where the stakes are low. Start with a free site health check on your own site, work through the six areas above against its findings, and sort the results into red, amber, and green. If the priorities are clear and the evidence is solid, you have a process you can offer to clients with confidence.

When a check finds something worth investigating in depth, turn the findings into a structured document with the report generator, or start at AuditPitch and judge the output on the findings themselves, not the score.