Check Your Own Website’s Technical Health: The Owner’s 30-Minute Guide

Underneath every website there is plumbing: the machinery that decides whether Google can find your pages, read them, keep them in its store, and show them to a customer quickly. When the plumbing is sound, nobody notices it. When it is not, the symptoms you find when you check website technical health are odd ones — a service page that never appears on Google no matter how good it is, a site that crawls on phones, reports that say “technical issues: fixed” while nothing you can see has changed.

Technical health is the hardest part of a website for an owner to judge, because none of it shows on the surface. That is exactly why it gets used as fog. The good news: five checks, all free, all doable in your own browser in about half an hour, will tell you more about your site’s real condition than most monthly reports do. No code, no paid tools, and nothing in this guide changes anything — you are only looking, the way a customer or Google would.

This guide is for any business owner, whether you have an SEO provider or not. Work through the five checks, score what you find, and you will know — not guess — whether your site’s plumbing is sound, ageing, or quietly costing you customers. And if you do have a provider, you will finish with five questions they should be able to answer from records they already keep. The process a proper technical fix follows — the one this check effectively grades — is published in full here: how we do technical SEO.

What you need before you check website technical health

Almost nothing: a browser, your website’s address, and about 30 minutes. Unlike a lot of website checks, these five need no accounts and no logins — every one of them looks at your site from the outside, exactly as Google and your customers see it.

Two honest notes before we start. First, some of the numbers below are estimates by design — Google’s own count of your pages is a rough figure, and speed readings move a little from run to run. This check is built for that: it asks you to judge big gaps and clear patterns, never small differences. Second, a healthy score here does not guarantee rankings — plenty else decides those. What it proves is narrower and very valuable: that nothing underneath your site is silently preventing the rest from working.

Check 1: Count what Google holds

Where to go: Open Google and search for site: followed by your website address, with no spaces — for example, site:yourwebsite.com. Google will answer with a rough count (“About X results”) and a list of your pages.

What you’ll see: Google’s store — the index, meaning the list of pages Google has read, kept, and can show in results. A page that is not in this store cannot appear in anyone’s search results, however good the page is. The count is Google’s own estimate, so treat it as a ballpark, not an audit figure.

What “fine” looks like: The ballpark matches the number of pages you believe you have. You have, say, 25 pages — services, locations, about, contact, a few articles — and Google holds something in that neighbourhood, and scrolling the list shows your real pages: your services, your towns, your contact page.

What “worried” looks like — in either direction:

  • Far fewer than you have. Pages you are paying to host, and maybe paying to promote, are not in Google’s store at all. Scroll and check for your money pages by name — if a main service or location page is missing from the list, Google cannot send it a single customer.
  • Far more than you have. Hundreds of results for a 25-page site means Google is storing junk alongside the real pages: old copies of the same page under slightly different addresses, print versions, empty search-and-filter pages your site generates by itself, leftover test pages. Junk copies dilute Google’s attention and can crowd the real page out of its own results.

Either direction of big gap is a finding worth writing down — which pages are missing, or what the extra pages are. Both are fixable, and both are invisible from your homepage.

Check 2: Test your speed on a page that earns money

Where to go: Open Google’s free speed test, PageSpeed Insights, type in the address of one of your service pages — the page a customer lands on to buy from you — and run it. When the results arrive, make sure you are looking at the Mobile tab, not Desktop. Most of your customers, and Google’s own judging, use the phone version of your site.

What you’ll see: Two kinds of information. Near the top, where there has been enough real traffic, sit readings from real visitors’ phones over the last 28 days. Below them is a one-off test run, performed the moment you clicked. Then three headline numbers — Google calls the set Core Web Vitals, and each one has a plain meaning and a published “good” line set by Google:

  • Loading (the test calls it Largest Contentful Paint): how long until the main content — the headline, the main picture — is actually on screen. Google’s line: 2.5 seconds or under.
  • Response (Interaction to Next Paint): you tap a button or a menu, and this is how long the page takes to visibly answer. Google’s line: 200 milliseconds — a fifth of a second — or under.
  • Steadiness (Cumulative Layout Shift): whether text and buttons jump around while the page loads — the reason you have tapped the wrong thing because it moved. Google’s line: 0.1 or under on its movement score.

Further down, the report lists “opportunities” — in plain words, that section is the repair list. It names what is holding your page back: pictures far bigger than they need to be, extra code the page insists on loading before it shows you anything, pieces arriving in a wasteful order. You do not need to understand how to fix any of it. You need to know the list exists, because a provider who says they fixed your speed should be able to point at items on it, by name, and tell you which ones they dealt with.

What “fine” looks like: All three numbers inside Google’s lines, on the mobile tab, for a service page — not just the homepage. Homepages are usually the lightest page on a site; a fast homepage proves nothing about the pages customers actually land on.

What “worried” looks like: Any number well outside its line on that mobile reading — loading at five or six seconds against a 2.5-second line, a page that visibly jumps as it loads, taps that take a second to answer. Each slow second is a customer deciding the business feels careless before they have read a word. Write down the three numbers, the page you tested, and the date: those are your before-numbers, and no speed “fix” can be proved without them.

Check 3: Open your own sitemap

Where to go: In your browser’s address bar, type your website address followed by /sitemap.xml — for example, yourwebsite.com/sitemap.xml — and press Enter.

What you’ll see: Your sitemap: the list of addresses your website itself hands to Google, saying “these are my pages — please read these.” It usually looks like a plain list of links. That plainness is fine; it is written for Google’s reader, not for people.

What “fine” looks like: The list loads. The addresses on it are your real pages — your services, locations, articles. Click three or four at random: each one opens a working page, the same page its address promises.

What “worried” looks like: The address itself lands on a “page not found” error, or the list is empty — your site is handing Google no map at all. Or you click addresses from the list and hit dead ends: pages deleted in a redesign months ago, still being offered to Google every day. Or the opposite — your newest service page exists but is nowhere on the list. A sitemap full of dead addresses is your own website directing Google’s reader to nowhere, on purpose, daily. Note which addresses are dead; that list is the finding.

Check 4: Walk the click-path to every important page

Where to go: Start at your homepage, on your computer first and then on your phone. Using only the menus and links on the pages — no typing addresses, no searching — try to reach every service page and every location page you have.

What you’ll see: Your site’s link structure: the web of links that connects your pages to each other. This matters mechanically, not just for tidiness: Google’s reader finds pages by following links, the same way you are doing now. A page that no other page links to is called orphaned — it exists, it may even be in the sitemap, but nothing leads to it, so Google’s reader seldom finds it and visitors essentially never do.

What “fine” looks like: Every service and location page is reachable in a few clicks — three or fewer is a fair working rule — from the homepage, on the computer and on the phone. Check the phone properly: open the menu button and look. Phone menus are often shorter than desktop ones, and pages quietly vanish from them.

What “worried” looks like: A page you can only reach by typing its address because no menu or link leads to it. A whole service missing from the phone menu while it sits proudly on the desktop one. A location page buried under so many clicks that you gave up before reaching it — if you gave up, so does everyone. Write down any page you could not reach by clicking; an orphaned money page earns nothing, however good it is.

Check 5: Check your own stars

Where to go: Search Google for your business name and look at your website’s result — the ordinary blue-link result for your own site. (Stars beside your map listing come from your Google reviews directly; this check is about stars attached to your website result.)

What you’ll see: On some websites, a row of stars and a rating — “4.9”, “based on 212 reviews” — shows right there in the search result. Those details come from schema: hidden notes in a page’s code that tell Google extra facts about the business. Used honestly, the notes repeat facts a visitor can verify. This check verifies one specific fact.

What “fine” looks like: The stars trace to real reviews you can open and count — your Google reviews, or a recognised review platform — and the number and score in the search result match the real ones, near enough. Ask yourself the simple test: can I click through and read these reviews? If yes, your stars are earned.

What “worried” looks like: Stars show, but nobody — not you, not your provider — can show you the reviews behind them. The count matches no platform you have reviews on. Or the provider explains the rating is “in the code” or “part of the SEO package”. That means the rating was typed into the code by whoever built the site: the business awarding itself stars it never earned. The risk is concrete, not theoretical: Google removes stars that do not trace to real reviews, and until it does, every customer who goes looking for those 200 reviews and finds twelve has learned something about the business — from the business’s own search result. Note what you found, and treat this as the most urgent item on the page: it is the one finding that is about honesty, not just plumbing.

Your scorecard: what did you find?

Score each check from what you saw. Be honest rather than kind — the score only helps if it is true.

Check🟢 Green — fine🟠 Amber — keep an eye on it🔴 Red — act
1. What Google holds (Check 1)The count roughly matches the pages you have, and your main pages are in the listA gap you can explain — a few minor pages missing, or extra copies you can identifyA main service or location page is missing entirely, or the count is several times your real pages
2. Speed on a money page (Check 2)All three numbers inside Google’s lines (2.5s / 200ms / 0.1), mobile tab, service pageOne number outside its line, or a number only just overTwo or three numbers outside their lines, or loading at double the 2.5-second line or worse
3. Your sitemap (Check 3)It loads, lists your real pages, and the addresses you sampled all workIt loads but is stale — a few dead or deleted addresses still listedIt doesn’t load at all, or many listed addresses are dead, or your main pages are missing from it
4. The click-path (Check 4)Every service and location page reachable in a few clicks, on computer and phonePages reachable but buried deep, or one minor page unlinkedA money page cannot be reached by links at all, or is missing from the phone menu
5. Your stars (Check 5)Stars trace to real reviews you can open and countStars and reviews both exist, but the numbers don’t quite match — worth one questionStars are showing and no reviews behind them can be produced anywhere

Reading your score

Mostly green — sleep fine. Your plumbing is sound: Google holds your pages, they load inside its lines, the map is honest, everything important is reachable, and your stars are earned. There is nothing to fix. Run this check again in about three months — and after any redesign — the way you’d glance at any other part of the business.

Ambers, but no reds — note it, and ask. Nothing here is an emergency, and nothing needs a technician today. But something is drifting — a sitemap going stale, a page slipping outside the speed lines, pages drifting out of the menus. Write down what you found, with today’s date and your three speed numbers, and put the five questions below to your provider in writing, so the answers are on record. Then re-run this check in a month and see which way the ambers moved.

Any red — get it fixed properly. Reds on this page are mechanical problems, not mysteries: a money page Google doesn’t hold, a map handing out dead addresses, an important page nobody can click to. They are all fixable, and none of them fixes itself. Two handling rules: first, the stars red outranks everything — a self-typed rating comes out before any other work, because it is a trust problem, not a performance one. Second, whoever fixes it, insist the work follows the shape of a proper technical process — measured before, fixed in impact order, measured again after, and written into a fix log you can re-check line by line. That process, in full, is here: how we do technical SEO. If the scale is more than you want to manage alone, the free audit at the bottom of this page is where to get a second pair of eyes before you pay anyone.

What good technical work looks like, so you can recognise it

Quiet, measured, and written down. A crawl of every page with its status. Your existing pages, your sitemap and Google’s store laid side by side, with every gap explained. Speed measured per page type — before the work and after it — against Google’s three lines. Fixes ordered by what is costing you customers, not by what is quickest to do. And a fix log: every fix with a date, the address, the problem, what changed, and the before-and-after numbers, kept open until every item closes.

That is the standard to hold any provider to, including us: if they fixed it, they can show you the numbers. Our own process, step by step, is published here — it is the process this check grades: How we do technical SEO.

Five questions to ask whoever does your SEO

Short version — copy, paste, send. Any honest provider answers these from records they already keep. (Our technical process page carries the longer version — what a real fix log contains, and what each answer should look like.)

1. Please send me the fix log for the technical work so far:
   the date, the page address, the problem found, what was
   changed, and the measurement before and after.

2. What were my speed numbers before the work, and what are
   they now — for a service page on a phone, not just the
   homepage?

3. How many pages does my site have, how many are in the
   sitemap, and how many does Google hold in its index?
   Please explain any gap between the three numbers.

4. Which of my pages get no links from any other page on the
   site (orphans), and what is the plan for them?

5. Is there a review star rating anywhere in my site's code?
   If yes, please show me the real reviews it is taken from.

Complete answers that match what you saw in your own check: you almost certainly do not have a problem. A fix claim with no before-numbers, or three counts nobody can reconcile: you have learned something important, and the scorecard above tells you the order to act in.

While you are in checking mode

Technical health is only one of the three things worth checking yourself. The other two guides in this series cover the rest of the picture, in the same plain style, with the same green / amber / red scoring:

  • Your links — who links to you, whether those links help or hurt, and whether any were placed in bulk without your knowledge: Check your own backlinks
  • Your pages themselves — whether each page says the right thing, in the right places, for the searches you want: our on-page self-check guide

And if the worry behind this check is bigger than plumbing — if you suspect a provider built things you would not have approved of — start with the deep guide: Did your SEO agency build spammy backlinks?

Half an hour per guide, once a quarter, and no provider can ever baffle you with a report again.

Frequently asked questions

My homepage score is fine. Isn’t that enough?

No — and this is the most common false comfort in the whole subject. Your homepage is usually the lightest page you own: one template, often fewer pictures, no booking form, no gallery, no map. Your service pages are built from different templates and carry different loads, and they do not perform alike. They are also the pages that matter: customers searching for what you sell land on the service page, not the homepage — and Google judges the page they land on. A fine homepage score next to a six-second service page is a fast front door on a house whose shop floor is under water. That is why Check 2 sends you to a money page, on the mobile tab, on purpose.

PageSpeed gives me different numbers every time I run it. Which one is true?

Both, because they are two different kinds of number, and the report shows both. The readings near the top — where your site has enough traffic to have them — come from real visitors: actual phones, on actual networks, collected over the last 28 days. That is the record Google judges you by, and it changes slowly. The numbers further down come from a test run: the moment you click, the tool loads your page once, on a test phone under test conditions. Run it at a busy moment or on a different day and that single run wobbles — the way one timing of a delivery run wobbles against the month’s average. So judge by the real-visitor record where it exists, and by the range of a few runs where it doesn’t — never by one run, good or bad, and never by a single score quoted in a sales report.

Can I fix these things myself?

Honestly split. The check itself needs no one — that is the point of it. Of the fixes: some are genuinely owner-sized. Adding a missing menu link, or linking a service page from a relevant article, is ordinary editing in most website systems. Spotting dead sitemap entries and wrong details costs nothing but attention. The rest needs a developer or a competent provider: speed work (the repair list in Check 2 is mostly code and file work), removing a typed-in star rating from the code, fixing forwarding chains and page templates, and most index problems beyond a missing link. The valuable owner skill is not doing the plumbing — it is the one this guide builds: knowing what to ask for, and being able to check afterwards whether it was actually done.

How often should I repeat this check?

About once a quarter is plenty for most businesses — half an hour, and the picture changes slowly. Check sooner after anything big: a redesign, a new theme or website system, a hosting move, or a pile of new pages. Those are the moments pages fall out of Google’s store, drop out of menus, and slip outside the speed lines without anyone noticing — ordinary life, not sabotage, is the commonest cause of technical decay.

Rather have it checked for you?

The check above tells you whether a problem exists. If you scored a red — or you would simply rather an experienced eye went through it — send us your website and we will check it the way this guide describes: what Google holds, how your money pages load on a phone, what your sitemap and menus are really doing, and what we would fix first, in plain English, with the before-numbers attached. Free, no obligation, and no panic sold with it.

Start your free local SEO audit


🖨️ PRINT THIS — the one-page technical health check

This is the print version of the guide above. Print it, keep it by the computer, and run the check once a quarter — and after any redesign. You need: a browser and your website address. About 30 minutes.

Google’s three speed lines (from Check 2 — write your service page’s mobile numbers beside them)

  • Loading: 2.5 seconds or under — yours: ________
  • Response to a tap: 200 milliseconds or under — yours: ________
  • Page steadiness (movement score): 0.1 or under — yours: ________

The five checks

  • 1. Count what Google holds — Search site:yourwebsite.com. Count roughly matches your pages, main pages present = fine. A money page missing, or hundreds of extra pages = not fine.
  • 2. Speed on a money page — pagespeed.web.dev, a service page, Mobile tab. All three numbers inside the lines above = fine. Any well outside = not fine.
  • 3. Open your sitemap — yourwebsite.com/sitemap.xml. Loads, lists real pages, sampled addresses work = fine. Error page, or dead addresses listed = not fine.
  • 4. Walk the click-path — From your homepage, reach every service and location page by links alone, in a few clicks — on the phone menu too. A page no clicks reach = orphaned = not fine.
  • 5. Check your stars — Stars beside your website result must trace to real reviews you can open and count. Stars nobody can show you the reviews for = typed into the code = not fine.

Your colours

  • 🟢 Mostly green — sleep fine. Nothing to do. Check again in about 3 months.
  • 🟠 Ambers, no reds — write down what you found, ask your provider the five questions from the guide, in writing, and re-check in a month.
  • 🔴 Any red — get it fixed properly, with before-and-after numbers and a fix log. A red on Check 5 (stars) comes out first — that one is about honesty, not speed.

Date checked: ____________ Next check due: ____________

Full guide, with the deep version of every check: rankautomateagency.com/guides-check-your-websites-technical-health/