Good morning

The Technical Audit Checklist Nobody Teaches

Because it's boring. But it's also the thing quietly breaking your site while you focus on content strategy and keyword research. We cover broken links, orphaned pages, redirect chains, sitemap errors — the invisible problems that compound.

Broken Links
Orphaned Pages
Redirect Chains
Sitemap Errors
Technical SEO audit workspace with multiple monitors showing crawl data

The stuff that breaks sites isn't glamorous

Nobody writes blog posts about redirect chains because redirect chains are not exciting. They don't have a good story arc. They don't make you feel clever for reading about them.

But they slow down Googlebot. They fragment link equity. They confuse users who land on pages that bounce them around before finally arriving somewhere. And they accumulate silently over months of normal site maintenance.

This blog exists to document the unglamorous stuff. The checklist items that get skipped because they feel tedious. The errors that don't show up in your analytics because they happen before users even arrive.

Browse the explainers

What a technical audit actually finds

  • Internal links pointing to 404 pages
  • Pages with no inbound internal links
  • Chains of 3+ redirects in a row
  • Sitemap URLs that return non-200 status codes
  • Duplicate content without canonical tags

Four problems. One afternoon to find them.

Each of these issues has a pattern. Learn the pattern once and you can spot it on any site.

Broken Internal Links

Links that once worked and now return 404. They multiply quietly every time you delete a page or change a URL structure.

Learn more

A broken internal link is a dead end for both users and crawlers. When Googlebot follows a link and hits a 404, it wastes crawl budget and signals that the site isn't well-maintained. Users who click these links bounce immediately.

The tricky part is that most broken internal links weren't broken when they were created. They become broken later, when pages get deleted, URLs get restructured, or CMS slugs change. A link that worked perfectly six months ago may silently return a 404 today.

Read the full guide

Orphaned Pages

Pages that exist on your site but have no internal links pointing to them. Search engines can't find them easily. Neither can your visitors.

Learn more

An orphaned page is technically reachable if you know the URL, but it's invisible to anyone navigating through your site. No menu items, no contextual links, no related content sections point to it. It floats alone.

These pages often represent real effort. Someone wrote that content. Someone uploaded those images. But without internal links, the page gets minimal crawl attention, accumulates almost no internal authority, and rarely ranks for anything meaningful.

Read the full guide

Redirect Chains

When URL A redirects to URL B which redirects to URL C. Each hop adds latency and dilutes the signals passed between pages.

Learn more

A single redirect is fine. Two redirects in a chain is common and usually acceptable. Three or more starts to become a real problem for crawling efficiency and page load speed. Googlebot has a crawl budget — it won't follow infinite redirect chains.

These chains build up over time. A site migration creates redirects. Then a URL structure change adds another layer. Then a domain change adds a third. Before long, you have chains that nobody documented and nobody is monitoring.

Read the full guide

Sitemap Errors

Your XML sitemap probably lists URLs that return 404s, 301s, or other non-200 status codes. This confuses crawlers and wastes their time.

Learn more

An XML sitemap is supposed to be a curated list of pages you want indexed. But most sitemaps are auto-generated and never audited. They accumulate deleted pages, staging URLs, redirect destinations that changed, and pages that have been noindexed.

When Googlebot fetches your sitemap and finds URLs that return errors, it has to decide what to do with that information. At best, it wastes time. At worst, it creates confusion about which version of a page is canonical.

Read the full guide

From zero to clean bill of health in one afternoon

This is the actual sequence. Not a sales funnel. Not a process designed to create dependency. Just the steps.

01

Set Up Screaming Frog

Download the free version. It crawls up to 500 URLs without a license. For most small and medium sites, that's enough to find the major issues. Configure it to follow internal links and check external links too.

02

Run the Crawl

Enter your homepage URL and let it run. For a 200-page site this takes maybe ten minutes. Screaming Frog will follow every internal link it can find, recording the status code of each URL it encounters along the way.

03

Filter by Status Code

Sort by response code. Look at everything that isn't 200. The 4xx errors are your broken pages. The 3xx responses reveal your redirect chains. Export each category to a spreadsheet so you can track fixes.

04

Cross-Reference Your Sitemap

Export your XML sitemap URLs. Compare them against the crawl data. Any URL in your sitemap that returned a non-200 status code is a problem worth fixing. Remove or update those entries.

05

Document and Fix

Work through the list methodically. Update broken internal links. Add contextual links to orphaned pages. Collapse redirect chains so A goes directly to C. Regenerate your sitemap after fixes are in place.

Why Screaming Frog's free version is enough to start

Screaming Frog SEO Spider is not the only crawling tool. But it is the one that most working SEOs actually use. The free version crawls up to 500 URLs per session, which covers a surprising number of real-world sites completely.

The interface is dense. It looks intimidating. But once you understand that you're mostly just looking at status codes and following the "Inlinks" tab to understand where each URL is linked from, the learning curve flattens quickly.

We walk through every relevant filter and export in the plain-English explainers section. No assumed knowledge. No skipping steps because they seem obvious.

See the Screaming Frog guides

A record of what we've learned

Early 2021

First audit, first surprise

Running a technical audit on a client site for the first time and discovering that a site with active traffic had over forty internal links pointing to pages that no longer existed. None of it was visible in Google Analytics.

Mid 2022

The orphaned page problem

Noticing a pattern across multiple sites: pages that had been written, published, and then effectively abandoned because the navigation structure changed and nobody added contextual links. Good content, invisible to crawlers.

Early 2023

Documenting the checklist

Starting to write down the audit steps in a format that could be handed to someone without a technical background. The goal was to make each step reproducible without requiring explanation every time.

Late 2024

This blog

Publishing the checklist publicly and expanding each item into a full explainer. The format shifted from internal documentation to something readable by anyone who wanted to understand what a technical audit actually involves.

2026

Ongoing additions

Adding coverage of search engine patents that relate to crawling behavior, canonical tag handling, and link graph analysis. The patents section exists because the primary sources are more useful than the summaries of them.

What the work actually looks like

Ready to look at what's actually broken?

The plain-English explainers walk through each audit step in detail. No assumed knowledge. No tool subscriptions required beyond Screaming Frog's free tier.