A technical SEO audit is the diagnostic step behind every sensible SEO plan. Its job is to find the issues that affect crawlability, indexation, architecture and site quality — the problems that quietly stop good content and good services from being found — instead of producing a long, undifferentiated list of low-impact warnings.

Whether you run the checks yourself or pay someone to do them, the value of an audit lies in the priorities it sets. This checklist works through the main areas in the order an auditor usually covers them, so you can make a first pass over your own site, make sense of a report you have been given, or judge whether an audit you are quoted for is genuinely thorough.

The audit checklist at a glance

1. Crawl the website and identify discoverability problems

Start by establishing what URLs exist, how they are linked, and which important pages are hard to reach. A crawl of the whole site, compared against the XML sitemap and the pages search engines already know about, usually reveals the first problems: broken internal links, unnecessary URL parameters, duplicate paths to the same content, orphaned pages with no internal links pointing to them, and key pages buried so deep in the structure that crawlers — and visitors — rarely reach them.

2. Compare crawlable URLs with indexation

A page can exist without being indexed, and a page can be indexed that you would rather keep out of search results. The two lists rarely match, and the differences are where the problems sit. Review indexability, noindex directives, robots.txt controls, canonical tags and sitemap inclusion together rather than in isolation. Watch in particular for valuable pages accidentally excluded — a leftover noindex tag from a redesign is a classic — and for test, staging or thin duplicate pages that have been indexed and are diluting the site’s quality signals.

3. Review status codes, redirects and canonicals

Important pages should return the status code you expect: live pages 200, moved pages a single clean redirect, genuinely removed pages a proper 404. Redirect chains and loops waste crawl effort and slow visitors down; soft 404s — error pages that return a 200 status — mislead everyone. Canonical tags should point each page to its preferred version, consistently. Migrations and redesigns deserve extra attention, because older URLs often still carry links and search history, and http/https or www/non-www duplicates can split signals between two versions of the same site.

4. Check site architecture and internal linking

Priority services should be easy to reach through the navigation and through contextual links inside related content. A clean hierarchy — homepage, then a services hub, then dedicated service pages — helps visitors and crawlers understand how the site fits together. Look for important pages that sit more than a few clicks from the homepage, sections linked only from a footer, and anchor text that gives no clue about the page it points to. For the content and on-page side of those pages, review our On-Page SEO Austin service.

5. Test performance and Core Web Vitals

Core Web Vitals measure three things about real visitor experience: how quickly the main content loads, how promptly the page responds to interaction, and how stable the layout is while loading. Test performance on representative templates — the homepage, a service page, a blog post — rather than a single page, and test on mobile first. The usual causes of poor scores are large unoptimised images, unnecessary JavaScript, heavy plugins and third-party scripts loaded on every page. Performance matters beyond rankings, too: a slow page loses visitors before any SEO work has the chance to help.

6. Validate structured data

Structured data should describe what is actually on the page, using types that accurately fit the content — a local business, a service, an FAQ where the questions genuinely appear. More schema is not automatically better; inaccurate or inflated markup can make a site ineligible for the rich results it was aiming at. Test the main templates with a validation tool, separate genuine errors from minor warnings, and check that the names and details in the markup match what visitors see on the page itself.

7. Re-crawl after fixes

Technical work is not complete when a task is marked done. Once the fixes are implemented, re-crawl the site, test the priority URLs directly, and confirm in Search Console that the changes are visible to search engines — that excluded pages are being picked up, duplicates are consolidated, and errors are clearing. Some changes register within days; others only show their effect once the affected pages have been re-crawled, so build a validation step and a short monitoring period into the end of every audit rather than treating the report as the finish line.

Common issues an audit usually finds

The same handful of problems turns up on small-business websites of every kind. None of them is dramatic on its own, but together they quietly hold a site back:

• Pages from an old design still indexed alongside their replacements
• Long redirect chains left behind by a redesign or a change of domain
• Duplicate versions of the site — www and non-www, or http and https — both reachable
• Oversized images uploaded at full camera resolution, slowing every page on mobile
• Important service or location pages missing from the main navigation
• Test or staging pages left open to indexing
• An XML sitemap that still lists redirected or deleted URLs
• Structured data copied from a template that describes a different business

How long an audit takes — and what you should receive

How long an audit takes depends mostly on the size and complexity of the site and how much history it carries. A small business website is a far quicker job than a large catalogue or a site that has been through several redesigns, and an honest auditor will say so rather than quote a fixed number of hours for every site. What matters more than the timetable is what lands in your hands at the end. A proper audit usually includes a findings list ordered by priority and likely impact, a plain-English explanation of why each issue matters, the specific fix recommended for each one — including which fixes need a developer and which are simple settings changes — and a validation pass after the fixes, confirming the problems are actually resolved. A report that is just an automated tool export, with no priorities or explanations, is not really an audit. If you would rather have the work done for you, our technical SEO service in Austin covers the audit itself and the fixes that follow from it.

Need help applying this to your website?

This guide explains the framework. If you want a prioritised review of your own site, start with the relevant service page or request an audit.

Request a Free SEO Audit →