Technical SEO Audit: What It Checks, and How to Run One on a Small Site
Updated: Nov 12
By Spencer Capron, founder of Capron Media. Published November 4, 2026.

A technical SEO audit is the part of an SEO audit that ignores your words and checks the machinery: whether Google can reach your pages, read them, and trust that each one is the right version. On a small site you can run most of it yourself with free tools. We ran it on our own site to show you what that looks like.
What is a technical SEO audit?
A technical SEO audit is a check of the parts of your website that decide whether search engines can find, crawl, read and index your pages: robots.txt, your sitemap, status codes, redirects, HTTPS, duplicate pages, speed, mobile layout and structured data. It finds what stops good pages from showing up, before you spend time on the words.
It is one part of a full SEO audit, which also looks at your content, your local results and your competitors.
From Capron Media: the free Lite subscription

Before an audit, get a short, plain read
See what to fix first across your site, on its home page and in its local results. Lite does not include the work on your site. Starter does.
What does a technical SEO audit check?
A technical SEO audit checks about a dozen things, and each one has a free way to look. The table lists what to check, why it matters, and the free tool to use. You do not need all of them on day one; the section on what to fix first, below, puts them in order.
Check | Why it matters | How to check it free |
robots.txt | It tells crawlers which URLs they may access. Google says it is not a way to keep a page out of Google | Open yoursite.com/robots.txt in a browser |
XML sitemap | It lists the pages you want found. Google says a site of about 500 pages or fewer, linked well internally and without many media or news pages to show in search, may not need one | Open the sitemap from robots.txt; check each URL loads |
Indexing | A page that is not indexed cannot appear in results | Search Console, Pages report and URL Inspection |
Status codes | Google may consider a page that returns 200 for indexing; error codes show in Search Console | Search Console, or a free crawler |
Redirects | Old addresses should send people and Google to the new one in one step | A free crawler, or a browser's network panel |
HTTPS | Visitors and Google expect a secure address | Type the http:// address and see if it moves to https:// |
Duplicate pages and canonical tags | One piece of content should have one main address | View the page source and find the canonical tag |
Core Web Vitals | Loading, responsiveness and visual stability, as real visitors experience them | Search Console, Core Web Vitals report; PageSpeed Insights |
Mobile layout | Google uses the mobile version of a site's content for indexing and ranking | Open the page on your phone; PageSpeed Insights |
JavaScript rendering | Google has to run the scripts in a separate rendering step before it sees content they add | View the page source and look for your main text |
Structured data | Markup that describes the page, and must match what is visible | Google's Rich Results Test |
AI crawler access | AI search tools need to be allowed to read the page | Read robots.txt for OAI-SearchBot, Claude-SearchBot, PerplexityBot and others |
How do you do a technical SEO audit, step by step?
To do a technical SEO audit, start with what Google already knows about your site, then work outward: robots.txt, the sitemap, every URL's status, redirects and HTTPS, duplicates, speed, mobile, scripts and markup. Write down each problem as you find it, with the page address, and fix nothing until the list is done.
See what Google has indexed. In Search Console, open the Pages report. Note any page you expected to see that is missing.
Read your robots.txt. Make sure it does not block your whole site or a section you want found.
Open your sitemap. Check that it lists the pages you want found, and only those.
Check every URL's status. Every page in your sitemap should load with a 200 status, not a redirect or an error. A free crawler or Search Console will show you.
Check redirects and HTTPS. Old addresses should move in one step, and the http:// version of your site should move to https://.
Look for duplicates. If the same content lives at two addresses, one should point to the other with a canonical tag or a redirect.
Measure speed. Run your key pages through PageSpeed Insights. Google's good thresholds: the main content loads within 2.5 seconds, the page responds to a tap, click or key press in under 200 milliseconds, and the layout shifts less than 0.1.
Check it on a phone. Read the page on your own phone. Menus, buttons and text should all work without zooming.
Check that your text is in the HTML. View the page source and search for a sentence from the page. If it is not there, it is being added by scripts.
Test your structured data. Run a key page through Google's Rich Results Test, and make sure the markup matches what the page shows.

What did we find when we ran a technical SEO audit on our own site?
We ran these checks on the Capron Media website, capronmedia.com, on October 30, 2026. Most things passed, and we found two problems worth fixing. Here is what we checked, what we saw, and what it means, so you can compare it with your own site.
Check | What we found on October 30, 2026 | What it means |
robots.txt | Loads; lets all crawlers in apart from one blocked crawler and a few minor exceptions, and lists the sitemap | Google and the AI crawlers we checked for are not blocked |
Sitemap | As of October 30, 2026: an index of 7 sitemaps, including blog posts, pages and pricing plans, and 2 sitemaps of member profiles (one empty, one listing a single profile page) | Member profile pages are low-value pages that do not need to be in a sitemap |
Blog URL status | As of October 30, 2026: 94 blog addresses in the sitemap; 92 loaded with 200, and 2 returned a 301 redirect | A sitemap should list final addresses only, so entries like these are worth removing or replacing |
HTTPS | The http:// address redirects with a 301 | Visitors land on the secure address |
Home page speed (lab test) | Performance score 93 out of 100, main content loaded in about 1.6 seconds, no layout shift | Inside Google's good thresholds in a lab test; field data from real visitors is in Search Console |

One lesson from our own run: a sitemap your website builder writes for you can still list pages you would not choose to list. Read it once, whatever builds it.
Technical SEO audit checklist
Here is the short technical SEO audit checklist to copy. Tick each line on your own site, and write the page address next to anything that fails.
robots.txt loads and does not block pages you want found
The sitemap loads, is listed in robots.txt, and lists only pages that load with a 200
Search Console shows your important pages as indexed
No internal link leads to an error page
Old addresses redirect in one step; http:// redirects to https://
Each page has one main address, with a canonical tag that points to itself
Key pages meet Google's Core Web Vitals thresholds
Pages read cleanly on a phone
Your main text is in the page source, not only added by scripts
Structured data passes Google's Rich Results Test and matches the page
AI search crawlers are not blocked in robots.txt
For every item a full audit covers, including content and local results, see our full SEO audit checklist.
What should you fix first after a technical SEO audit?
Fix first whatever stops Google from reaching or indexing your pages, then errors on pages people visit, then anything that sends people or Google the long way round. Speed, markup and polish come after. A slow page that Google can index is a smaller problem than a fast page it cannot.
Order | Problem | Why first |
1 | Site or key pages blocked in robots.txt, or marked noindex | Nothing else matters while Google cannot index them |
2 | Important pages returning errors | Visitors and Google both hit a dead end |
3 | http:// not moving to https:// | Every page is affected at once |
4 | Redirect chains, and redirects listed in the sitemap | Wasted steps for crawlers and visitors |
5 | Duplicate pages without a canonical tag | Google has to choose which version to show |
6 | Core Web Vitals outside Google's thresholds | Affects how pages feel to use |
7 | Structured data errors | Markup that breaks Google's rules can lose its rich result |

How long does a technical SEO audit take?
On a small site, the free checks in this guide fit in one working day, and our own run on October 30, 2026 did. A crawl of a large site, or fixing what the audit finds, takes longer. Run the checks again after any redesign, platform move or big drop in visits.
Three times to re-run it: after a website redesign, after a Google core update hits your visits, and when you change hosting.
Free tools or a paid technical SEO audit?
Free tools are enough to run a technical SEO audit on a small site if you have the time and are comfortable reading the results. A paid audit is worth it when you want every finding explained in plain words, a list of fixes in order, and a report you can hand to whoever makes the changes.
Option | What you get | What it costs | What to check |
Free tools (Search Console, PageSpeed Insights, Rich Results Test) | Raw data on indexing, speed and markup | Your time | Whether you can tell which findings matter |
Desktop crawler software | A list of every URL, status code and redirect | Free tiers and paid plans vary | Whether the free tier covers all your pages |
Agency technical audit | A report, scope set by the provider | Set by each provider | Whether it ends with fixes in order, page by page |
Capron Media (ours) | The SEO Audit, ordered in your portal on a free Lite subscription: a teardown of your site, where to look, what to change, and why | $250, paid once. Delivered in 3 to 5 business days. | A person approves every paid audit before it reaches you, and the report ends with what to do next |
Want to see what to fix first before you pay for anything? Free checks come with a free Lite subscription. A free check reads public data, so there is nothing to connect. If today's free checks are full, yours waits until the next day.
If you would rather have it done for you, see our SEO audit services.
From Capron Media: the free Lite subscription

Want the full audit? Order it in your portal
On Lite you can also order an SEO Audit, from your portal. Lite does not include the work on your site. Starter does.
Related reading: how to run a crawlability test, how search engines crawl websites, when duplicate content matters, how to get your website on Google, and an SEO audit example of a finished report.
Written by Spencer Capron, founder of Capron Media, a Middleborough, Massachusetts SEO service for small business owners. Spencer is HubSpot SEO II certified, holds CompTIA Security+, and has run recurring SEO programs for 30+ small-business clients. He wrote this post in collaboration with our AI agents, and he reviews everything published here.





Comments