---
title: "Website Audit: What It Is and How to Run One Yourself"
url: https://hostmy.blog/website-audit-wordpress/
date: 2026-11-01
modified: 2026-11-02
lang: en
author: "Aditya Sharma"
description: "A website audit is a structured look at a site that ends in an ordered list of fixes. The six areas to check on a WordPress blog, with commands, and how to plan."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2670-1024x538.jpg
word_count: 1423
---

# Website Audit: What It Is and How to Run One Yourself

A website audit is a structured look at a site to find what is wrong, what is at risk and what to fix first. Done yourself, on a WordPress blog, it takes an afternoon, needs a few free tools, and produces a short list. The point is the list, not the checking, and an audit that ends without an ordered list of fixes has not finished.

This post sets out how to run a website audit on a WordPress blog yourself. It covers what to look at, in what order, with which commands, and how to turn the findings into a plan. It is the general audit, and it is not the same as [the five layer AI SEO audit](/five-layer-ai-seo-audit/). That one works through five layers, from whether a crawler can fetch a page to how fresh it is, to show what an AI crawler receives. This one covers the whole site in six areas, including speed, security, backups and who owns the accounts, none of which appear in those five layers, and it ends with a ranked plan. The two work well together.

## What an audit is, and is not

An audit is a snapshot. It records the state of the site on one day, against a list of checks. It is not a fix, not a monitoring system and not a guarantee. It tells you where the problems are now, so you can decide what to do and in what order. Monitoring, which watches the same things continuously, is the next step.

There is also a difference between an audit for a site you own and an audit before you take over someone else's. We run the second kind before taking on a blog, and the checks overlap. [What we check before taking on a client blog](/what-we-check-before-taking-a-client-blog/) lists the fourteen read-only checks we use, and this post borrows its shape.

## The six areas

| Area | The question | Where to look |
| ---- | ------------ | ------------- |
| Access and indexing | Can search engines reach and index the right pages? | robots.txt, status codes, Search Console |
| Speed | Is the site fast enough for readers and crawlers? | Time to first byte, Core Web Vitals |
| Security | Is the software current and the site clean? | Update lag, core file checks, user accounts |
| Content | Is it worth reading, and is anything stale? | Your top posts, your oldest posts |
| Structure | Does the site hang together? | Internal links, redirects, 404s, sitemap |
| Resilience | Could you recover from a failure? | Backups, restore test, ownership of accounts |

Every check you run belongs to one of these. If a check does not, leave it out.

## Area one: access and indexing

Start here, because nothing else matters if pages cannot be found. Check that robots.txt does not block what you want crawled, that real pages return a 200, that missing pages return a 404, and that no page carries an accidental noindex. Then open the [Page indexing report](https://support.google.com/webmasters/answer/7440203) in Search Console and sort the not-indexed list by reason. Google's help page defines the status like this: "Not indexed: The URL is not indexed, either because of an indexing error, or because of a legitimate reason (for example, if the page is blocked from indexing by your robots.txt file, or is a duplicate page)." So not every entry is a fault, and the reason tells you which ones to chase. For "Crawled - currently not indexed" the same page says: "The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling."

## Area two: speed

Measure the server first, then the page. This prints the time to first byte.

`curl -o /dev/null -s -w "%{time_starttransfer}\n" https://yourdomain.com/your-post/`

Test a post, not only the homepage, because posts carry the images and embeds. Then run Core Web Vitals on the same post. A fast homepage and a slow article template is a common split, which is why you test an article.

I ran that command three times against one of our own posts, https://hostmy.blog/wordpress-abilities-api/, from a Mac on 2 November 2026. It printed 2.07, 1.83 and 2.65 seconds. The three readings differ by 0.8 seconds, so take three and not one. As a control, the same command against a host that does not exist exits with code 6 and prints 0.000000, so a zero means the request failed, not that the site is fast.

## Area three: security and software

Three checks cover a surprising amount, and they are the same three we use before taking on a site.

`wp core verify-checksums
wp plugin list --status=active --format=table
wp user list --role=administrator --fields=ID,user_login,user_email`

The first, [wp core verify-checksums](https://developer.wordpress.org/cli/commands/core/verify-checksums/), is documented as: "Verifies WordPress files against WordPress.org’s checksums." It flags core files that have been changed. The second lists active plugins, so you can see which are abandoned or out of date. The third lists administrators, because old accounts are a quiet risk, because an administrator nobody uses is a login nobody watches. If the plugin list is long, remove what the site does not need, one plugin at a time, and test the site after each one.

## Area four: content

Find your ten most visited posts and your ten oldest. For each, ask whether it is still true, whether it is still the best answer you can give, and whether another post on the site says the same thing. Content that has aged, or that overlaps, drags down the rest. Sort the list by last-modified date to find the aged ones, then update, merge or remove each one.

## Area five: structure

Look at how the site hangs together. Check the sitemap lists only pages that return 200, review the 404s you have, and check that redirects are single hops. Check internal links as well: your best pages should be linked from several relevant places.

## Area six: resilience

The question is whether you could recover. Check that a backup exists, where it is stored, when it was last taken and, most of all, whether anyone has restored it. [The WordPress backup that did not restore](/wordpress-backup/) is the argument for the last part. Check who owns the domain, the host account and the DNS, and who can log in to each. This is the check people skip and later regret.

## Turn the findings into a plan

An audit produces many findings and you can fix only some. Sort them by two questions: how much damage does this do, and how much effort does it take to fix? Do the high-damage, low-effort ones first.

| Finding | Damage | Effort | Order |
| ------- | ------ | ------ | ----- |
| A noindex on live pages | High | Low | First |
| No tested backup | High | Low | First |
| Slow server response | Medium | High | Plan it |
| Stale old posts | Medium | Medium | Next |
| A long plugin list | Low | Medium | Later |

![Grid of damage against effort. A noindex on live pages and no tested backup sit at high damage, low effort and are fixed first. Stale old posts are medium and medium, second. A slow server response is medium damage, high effort, to be planned. A long plugin list is low damage, medium effort, later.](https://hostmy.blog/wp-content/uploads/2026/11/hmb-audit-priority-2670.png)The same five findings placed by damage and effort. The order is the one in the table above.

Write the plan on one page, with the finding, the fix, the owner and a date. A list that lives in your head does not get done.

## How often to repeat it

Run the full audit once a year, and a shorter version every quarter, covering access, backups and accounts. Run the relevant part after any big change, such as a move or a redesign. Between audits, monitoring catches the things that change fast.

## Free tools worth having

You need very little. Search Console shows how Google sees the site, including indexing, sitemaps and security issues. Google's Rich Results Test and the Schema Markup Validator check structured data. The free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) runs 41 live checks of what AI can read on your site, which covers the side the six areas leave out. curl and WP-CLI cover most of the technical checks, as shown above. A speed test on a real article covers the rest. Paid tools can crawl the whole site, and they are useful on a large one, but none is needed for a first audit of a small blog.

## After the audit

Share the plan with whoever will do the work, and put dates on it. Do the first item the same week, so the audit leads to a change. Then put the next one in the diary. The value of an audit is in the repeat: run the same checks each quarter and you can see whether things are getting better, which a one-off never shows.

## Where Host My Blog fits

The audit above is free and you can run it yourself. If you want someone to run it and give you the plan, that is the first step in how we take on a blog, and [our care for bloggers](/for-bloggers/) builds on it. If you would rather do it yourself, the six areas are the whole job.

If you wrote the plan on one page today, which finding would be at the top?