Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Website audit: how to run one step by step

Updated · 8 min read

Short answer A website audit is a list of what stops Google or customers from using your site, ranked by damage. A small site takes an afternoon with free tools: Search Console, your phone, PageSpeed Insights, a crawler. Check that Google can reach your pages first, then broken links, security, phone use and speed, then whether each page still tells the truth.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Website audit: what to check, in order

Check in this order. Each row can make the rows below it pointless: a fast page Google can't reach earns nothing.

OrderQuestionFree toolIf it fails
1Can Google show the site at all?Search Console: Manual actions, Security issues, URL InspectionSome or all pages vanish from Google
2Does every link lead somewhere?A crawler, such as Screaming Frog's free versionVisitors and Google hit dead ends
3Is it secure, at one address?Your browser, Search Console's HTTPS reportBrowsers warn visitors away
4Does it work on a phone?Your own phoneGoogle ranks the phone version
5Is it fast for real visitors?Core Web Vitals report, PageSpeed InsightsSlow pages lose callers
6Is the schema markup valid?Rich Results TestRich results may not show
7Is each page still true and useful?Search Console Performance, a spreadsheetOld pages lose searches to fresher ones

Start with Google's own tool. Google says "Third-party tools don't have access to our internal ranking data" and urges owners to use Search Console, "which provides you with key information and data directly from Google Search itself" (Google Search Central: Guidance on third-party SEO tools). A tool's "health score" is a guess about Google, not a reading from it.

How to do a website audit, step by step

Open a spreadsheet with four columns: page, problem, step number, fixed date. Each problem gets the number of the step that found it. Fix low numbers first.

1. Check that Google can show your site

In Search Console, open three things:

  • Manual actions. It shows any manual action against your site and which section it hits; with one, "some or all of that site may not be shown" in results (Google Search Central: How to use Search Console). Any entry goes to the top of your list: see Google manual actions.
  • Security issues. It warns when Google thinks your site "might have been hacked, or used in ways that could potentially harm a visitor" (same page).
  • URL Inspection. Paste your home page and each service page. It shows whether each page is in Google's index. If a page you need isn't, see crawled or discovered, not indexed.

Not set up yet? Start with Search Console for a small business.

2. Find broken links and error pages

Run a crawler: a program that follows every link on your site like Google does. Screaming Frog's free version is "restricted to crawling up to 500 URLs in a single crawl" (Screaming Frog), enough for most service businesses. Sort the results by status code.

  • 404 and other 4xx codes mean "not found". Google says it doesn't index these, and "URLs that are already indexed and return a 4xx status code are removed from the index" (Google Search Central: HTTP status codes). Fix the link, or redirect the old page to its replacement.
  • 5xx codes mean your server failed. Tell your web host or developer.

Fix broken links inside your own menus and buttons first. Customers click those.

3. Check HTTPS and one address

Type your address four ways: with and without "www", with "http" and "https". All four should land on the same https page with no warning. Search Console's HTTPS report shows pages that aren't served securely (Google Search Central: Understanding page experience).

Do it for trust, not rank. Google called HTTPS "a very lightweight signal" when it began using it in 2014 (Google Search Central Blog), and its page experience guide now says that beyond Core Web Vitals, other page experience aspects "don't directly help your website rank higher".

4. Use the site on your phone

Google's own test is gone: "The Mobile Friendly Test and the Mobile Usability report have been retired" (Google Search Central Blog, December 1, 2023). Use your phone instead. It matters because Google ranks the phone version:

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile-first indexing best practices)

On your phone, call from the page, fill in the form and open the menu. If the phone version hides text the desktop shows, Google sees less of your page.

5. Check speed with real-visitor data

Search Console's Core Web Vitals report "shows how pages perform based on real world usage data" (Google Search Central: How to use Search Console). List pages marked Poor. Don't chase a perfect score: Google says good results "doesn't guarantee that your pages will rank at the top" (Google Search Central: Understanding page experience). The pass marks and fixes: Core Web Vitals.

6. Test your schema markup

Schema markup is hidden code that tells Google facts like your hours and address. If you have it, paste each page into the Rich Results Test. Google suggests rechecking after launch because markup "might break after deployment due to templating or serving issues" (Google Search Central: Introduction to structured data). What to include: local business schema.

How to run a content refresh audit

A content refresh audit asks one question of every page: does it still answer its searcher better than anything else? It is step 7, and the one most owners skip.

  1. List your pages with their clicks. In Search Console's Performance report, use Compare and pick "Compare last 3 months year over year" (Google Search Central: Debugging drops in Google Search traffic). Comparing with the same months last year keeps busy seasons from fooling you.
  2. Mark pages that lost clicks, and every page whose prices, services, staff or rules changed since you wrote it.
  3. Read each marked page against Google's questions:
"Does the content provide original information, reporting, research, or analysis?" (Google Search Central: Creating helpful, reliable, people-first content)
"After reading your content, will someone leave feeling they've learned enough about a topic to help achieve their goal?" (same page)
  1. Decide for each page: keep, update, merge with a similar page, or delete. Google calls deleting "a last resort" (Google Search Central: Core updates). When to merge or delete, and how to redirect: update, merge or delete old pages.
  2. Change real content, not just the date. Google lists changing dates "to make them seem fresh when the content has not substantially changed" as a warning sign (Google Search Central: Creating helpful content).

Will a website audit protect you from Google updates?

Not directly. Core updates "don't target specific sites or individual web pages" (Google Search Central: Core updates). No checklist makes a site immune. What an audit can do is make you ready to read an update calmly.

Google ran core updates in March and May 2026, and the November 2026 core update began on November 10 and was still rolling out on November 16 (Google Search Status Dashboard). Google's own view of them:

"In general, most sites don't need to worry about core updates and may not even realize one has happened." (Google Search Central: Core updates)

To be ready:

  • Keep a baseline. Search Console holds 16 months of data; for longer, Google points to its API or bulk exports (Google Search Central: Debugging drops). Export your Performance report after each audit.
  • Don't edit mid-update. Google says wait until the update finishes, then compare a week after with a week before it started (Google Search Central: Core updates).
  • Ignore small moves. For a drop like position 2 to 4, Google says "There's no need to take drastic action" (same page). After a large drop, see traffic dropped after a core update.

What to skip in a website audit

Common audit itemWhat Google says
Treat HTTPS as a big ranking boostIt was "a very lightweight signal" in 2014 (Google Search Central Blog); keep it for trust
Run the Mobile-Friendly TestRetired December 1, 2023 (Google Search Central Blog)
Build an XML sitemap no matter whatA site of "about 500 pages or fewer" with good links "might not need a sitemap" (Google Search Central: Learn about sitemaps)
Chase a 100 speed scoreA perfect score "just for SEO reasons may not be the best use of your time" (Google Search Central: Understanding page experience)
Trust a tool's site-wide "SEO score"Third-party tools don't see Google's ranking data (Google Search Central)

Example

A plumber with a 40-page site (US dollars)

The crawl finds the "Water heaters" menu link returns a 404 after a redesign. That's step 2, fixed first with a redirect. Speed shows two Poor pages, step 5, fixed next. The content audit flags a 2021 page quoting a $1,200 heater install the plumber now prices at $1,800. It's rewritten with today's price; the date changes because the content did.

A dental clinic during the November update (Canadian dollars)

Clicks dip 8% on November 12. The update is still rolling out, so the clinic changes nothing, exports its Performance report, and plans the comparison for a week after Google marks the update finished.

An accountant with 120 blog posts

The year-over-year compare shows 30 posts lost most of their clicks. Ten cover tax rules that changed: updated. Eight repeat each other in pairs: merged with redirects. Two describe a service the firm dropped: deleted.

FAQ

How long does a website audit take?

For a site under 500 pages, the free tools above cover it in an afternoon. The content refresh audit takes longer, since someone has to read each marked page.

How often should I audit my website?

Google sets no schedule. Search Console emails you when it finds new issues (Google Search Central: How to use Search Console). Do a full audit after a redesign, a platform move or a large traffic drop.

Do I need a paid audit tool?

Not for a small site. Search Console, PageSpeed Insights, the Rich Results Test and a free crawler cover the checks above. Paid crawlers mainly help past 500 pages.

Technical audit vs content audit: what's the difference?

A technical audit checks whether Google and visitors can reach and use your pages (steps 1 to 6). A content audit checks whether what those pages say is still right and useful (step 7).

Different for you?

Keep learning

NextHow to do an SEO audit: technical, on-page and off-pageA step-by-step SEO audit for a small business site with free tools: technical, on-page, off-page, local, international and AI search checks, in fix order.

Do it yourself

SEO checklist: 10 steps to rank higher with the site you haveAn SEO checklist for an existing website: 10 steps in priority order, the free Google tool for each, and how to tell when a step is done.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: How to use Search Console
  2. Google Search Central: Guidance on third-party SEO tools
  3. Google Search Central: How HTTP status codes affect Google's crawlers
  4. Google Search Central: Understanding page experience
  5. Google Search Central Blog: HTTPS as a ranking signal (August 7, 2014)
  6. Google Search Central: Mobile site and mobile-first indexing best practices
  7. Google Search Central Blog: Mobile-Friendly Test retired (update of December 1, 2023)
  8. Google Search Central: Introduction to structured data
  9. Google Search Central: Learn about sitemaps
  10. Google Search Central: Creating helpful, reliable, people-first content
  11. Google Search Central: Debugging drops in Google Search traffic
  12. Google Search Central: Google Search's core updates and your website
  13. Google Search Status Dashboard: Ranking incident history
  14. Screaming Frog: SEO Spider