A technical SEO audit checks whether search engines can reach, read and index the pages on your website. This technical SEO audit checklist is written for the owner or marketer of a small website, roughly 500 pages or fewer, who wants a clear list of checks to run in one sitting.
You do not need a paid tool or a developer to start. You need Google Search Console and a browser.
This guide walks you through fifteen checks, each with a “done when” line so you know when to stop, then shows the order in which to fix what you find. Keep this technical SEO checklist open and tick each check off.
A site can have excellent content and still lose search visibility if search engines cannot reach it. A site audit finds the cause before you spend more on content or ads, and it protects search engine visibility for every page on your site.
Technical problems are quiet. A stray noindex tag, a broken redirect or a blocked page does not announce itself, and the first sign is usually a drop in traffic.
A technical SEO audit asks one question: can search engines find, read and index your important pages?
Every check below answers a version of that question. Search engines crawl your pages by following links, read what they find, and decide which pages to keep in the index. A problem at any of those three stages keeps a page out of search results, whatever its quality.
Google’s own guidance on generative AI features makes the same point. To appear in those features, a page must be indexed and eligible to be shown in Google Search with a snippet.
So the technical basics also decide whether you can show up in AI answers. Our guide to being found in search and AI answers explains the wider picture.
What you need before you start
Three free things are enough for a small site, and any SEO tool you add later is a bonus:
- A Google Search Console account with your site verified. Our Library entry on Search Console explains what it is, and the walkthrough on setting up Search Console, analytics and AI search tracking covers the setup.
- Access to your website admin, so you can see your SEO settings, redirects and sitemap.
- A crawler or site audit tool is optional. For a site under 500 pages, a free crawler can list broken links and redirects in minutes, but Search Console and a browser cover most of the audit.
What a small site can skip
Many technical SEO checklists include extras written for large online stores. A small site does not need most of them. Google says its crawl budget guide is for sites with 1 million or more unique pages, or 10,000 or more pages that change daily.
If that is not you, keeping your sitemap current and checking the Page indexing report is adequate. The section on what to skip below lists the rest.
Run these fifteen checks in one sitting
The first five checks confirm that search engines can get in. The middle five check what they find once inside. The last five check the details that decide how your pages appear. Work through them in order, and note each problem in a simple list rather than fixing as you go.
1. Verify your site in Google Search Console
Search Console is where Google reports what it sees on your site. Without it, you are auditing blind. Verify the version of your site that people actually visit, then open the reports used in this checklist: Page indexing, Sitemaps, Core Web Vitals and the HTTPS report.
If you want a second view, Bing Webmaster Tools is the free equivalent for Bing, and Google Analytics shows what visitors do once they arrive.
While you are there, check that your inquiry form or booking button is recorded as a key event in your analytics. A technical fix is only worth making if you can see its effect on the visits that matter.
Done when you can open the Page indexing report for your site without a permission error.
2. Check that your site answers on one secure address
Type four versions of your address into a browser: with and without www, and with http and https. All four should end up on one https version. Google lists redirecting several URLs to one preferred URL as a standard use of redirects.
HTTPS also appears on Google’s self-check for page experience, which asks whether pages are served in a secure fashion. If the Search Console HTTPS report lists pages that are not secure, fix the mixed content or the certificate first.
Done when all four address versions land on one https address and the browser shows no security warning.
3. Read the Page indexing report and fix crawl errors
The Page indexing report shows which pages Google can index and why others are left out. Your goal, in Google’s words, is to get the canonical version of every important page indexed. You should not expect every URL to be indexed, and a page marked duplicate or alternate is usually a good sign.
Open each reason under “Why pages aren’t indexed” and look at the Source column. Google says you can generally fix only issues where the source is “Website”. Crawl errors such as server errors (5xx), not found (404) and redirect errors deserve attention when they affect pages you want visitors to find.
Compare how many pages are indexed with how many pages you expect. A ten-page business site with several hundred indexed pages has a duplicate problem, and a site with half its indexed pages missing has an access problem. Only pages in the Google index can appear in results.
New content can take a few days to appear, so do not panic over a page published yesterday.
Done when every page you care about is either indexed or has a written reason it is not.
4. Test your key pages with the URL Inspection tool
Pick the pages that earn or should earn inquiries: the home page, each service page and your contact page. Paste each address into the URL Inspection tool at the top of Search Console. It shows whether Google has indexed the page, which canonical Google selected, and what the page looks like when Google renders it.
Run a live test if you changed something recently. The tool also lets you request indexing for a URL, which is useful after you publish or fix a page.
Done when each key page shows as indexed, or you know exactly why not.
5. Review your robots.txt file and noindex tags
Your robots.txt file tells crawlers which URLs they may access, and Google describes it as a way to avoid overloading your site, not a mechanism for keeping a page out of Google.
Open yourdomain.com/robots.txt and check that it does not block pages, scripts or styles you want crawled. Crawler rules are read by all major search engines, so one careless line can hide your entire site from them and from other search engines.
Then look for accidental noindex rules. A noindex meta tag or X-Robots-Tag header drops a page from Google Search results. A common mistake is a “discourage search engines” setting left on after a site launch. If you rebuilt your site recently, our guide to launching a new website without losing search traffic covers this trap.
One more trap: if a page is blocked in robots.txt, crawlers never see its noindex tag, and the URL can still appear in results. To hide a page, leave it crawlable and use noindex.
Done when robots.txt blocks only pages you chose to block, and no important page carries a noindex rule.
6. Check your XML sitemap
An XML sitemap lists the pages you want search engines to find, and it helps crawlers discover them. Our Library entry on the sitemap explains the idea.
Google notes that a site of about 500 pages or fewer, properly linked, might not need a sitemap, but a new site with few links pointing to it usually benefits from one.
Most website platforms generate a sitemap automatically. Open it and check three things: it lists only live pages that return a normal response, it leaves out pages you have set to noindex, and it is submitted in the Search Console Sitemaps report.
Google’s limits are 50 MB uncompressed or 50,000 URLs per sitemap, which a small site will not reach.
Done when the Sitemaps report shows your sitemap as successful and the pages in it are the pages you want indexed.
7. Fix broken links and redirect chains
Broken links send visitors and crawlers to a dead page. Google’s crawling documentation explains that Search Console reports errors for status codes in the 4xx and 5xx range, and for failed redirections.
Your page indexing report shows the ones Google found. A crawler will find the rest, including broken internal links and broken links to external links on other sites.
To fix broken links, either restore the page, update the link to the right destination, or redirect the old address to the closest relevant page. Do not redirect everything to the home page.
If multiple pages link to the same dead address, fix them together, and check your older blog pages too. Update internal links to point straight at the new address, so visitors and crawlers do not rely on the redirect.
Check redirects as you go. Use permanent redirects (301 or 308) when a page has moved for good, because Google treats them as a signal that the new address should be the one shown in results.
Temporary redirects (302 or 307) are for short-term moves. Avoid redirect chains, where one redirect leads to another. Googlebot follows up to ten hops, but every extra hop slows the visitor.
Look for soft 404s too. Google describes these as pages that return a normal “success” response while the content says the page is missing or is empty.
Done when no important page returns an error, and each redirect goes straight to its final destination in one step.
8. Eliminate duplicate content and set a canonical tag on every page
Duplicate content happens when the same page can be reached on several URLs, such as with tracking parameters, with and without a trailing slash, or on a test copy of the site.
Search engines then have to guess which version to show, and link equity gets split across multiple URLs. Thin content pages that repeat each other add to the problem.
Google says that when you do not choose, it picks the version it considers best. You can guide it. Google lists redirects and rel=”canonical” annotations as strong signals, and sitemap inclusion as a weak one.
Two rules from the same page: do not use robots.txt for canonicalization, and do not point to different canonical URLs using different methods.
On a small site, this check is short. Look for printer pages, parameter URLs, tag and category archives that repeat your posts, and old staging copies. Point each to one preferred address with a canonical tag, or noindex the ones that add nothing.
Done when each important page has a single preferred URL, and your sitemap and canonical tags agree.
9. Check Core Web Vitals, including interaction to next paint
Core Web Vitals measure real-world user experience on three things. Largest Contentful Paint measures loading, and Google advises that it should occur within 2.5 seconds.
Interaction to Next Paint measures responsiveness, with a target under 200 milliseconds. Cumulative Layout Shift measures visual stability, with a target under 0.1. Google lists all three on its Core Web Vitals page.
According to web.dev, a page passes when it meets all three targets at the 75th percentile of page loads. Open the Core Web Vitals report in Search Console. It uses real user data and lists only indexed URLs. A small site may see “No data available” because not enough visitors have been measured yet.
In that case, paste your key pages into PageSpeed Insights at pagespeed.web.dev for a single-page test. The usual causes on small sites are oversized images, too many scripts and plugins, and layouts that jump as they load.
Compress the hero image on your landing pages, remove plugins you do not use and set image sizes in your page code. Site speed improvements help every visitor, whether or not they affect Google rankings.
Slow server response time is another common cause, so ask your host about it if page speed stays poor on every page. Mobile users on slower connections feel these delays most, and slow pages cost you site visitors before they read a word.
Done when your main pages meet the three targets, or you have a short list of the pages and causes that do not.
10. Confirm the mobile version shows the same content as the desktop version
Google uses the mobile version of your content for indexing and ranking, which it calls mobile-first indexing. Google recommends responsive design, which serves the same HTML on every device and avoids most mobile problems.
Test a few mobile pages on real mobile devices, not only a resized desktop browser, and compare them with the desktop pages.
If your site is responsive, check three things on a phone. First, nothing important is hidden on mobile that appears on desktop. Second, primary content does not wait for a tap or swipe to load, because Google does not load content that needs interaction. Third, the same robots meta tags apply on both versions.
Done when your key pages show the same headings, text and links on a phone as on a computer.
11. Audit internal links and find orphan pages
Internal links are links from one page of your site to another. They are how crawlers move around your site and how visitors find what they need. A page with no internal links pointing to it is an orphan page, and crawlers may not find it.
Google says it can generally only crawl links that are an a element with an href attribute. Menus and buttons built from scripts without a real link may not be followed.
Check that your main navigation uses real links to your service pages and other site pages, and use descriptive anchor text that tells the reader and Google what the next page is about. For image links, the alt text works as anchor text, and it also helps screen readers describe the page.
To find orphan pages, compare your sitemap with the pages a crawler reaches from the home page. Anything in the sitemap that the crawler never reaches needs a link from a related page.
Aim for every important page to be reachable within a few clicks of the home page. This is the heart of good site architecture: a clear structure where related pages link to each other, and where you update internal links whenever you add or remove a page.
Done when each important page has at least one internal link from a relevant page, and your menus use real links.
12. Review your URL structure
Google asks for simple, readable addresses. Its guidance on URL structure recommends descriptive words over long ID numbers, and it warns against using URL fragments (the part after a hash sign) to change the content of a page.
Check that your addresses are short, lowercase and consistent. A page at /services/seo-audit reads better, and ages better, than /index.php?id=3482. Do not change working addresses just to tidy them. If you must change one, redirect the old address to the new one.
Done when your main page addresses use readable words and none depends on a fragment to load content.
13. Review title tags and meta descriptions
Each page needs its own title tag, because the title is often the main thing people use to decide which result to click. Titles and descriptions are part of basic on page optimization, and they help search engines understand a page’s content at a glance.
Google’s advice on title links is to give every page a title in the title element, keep it descriptive and concise, and avoid vague words such as “Home” or repeated boilerplate across pages.
Meta descriptions work differently. Google primarily builds snippets from the page content and sometimes uses the meta description when it describes the page better. So write a short, accurate description for your key pages, but do not expect Google to always show it.
A crawler or your SEO plugin can list missing and duplicate title tags in one pass. Fix the pages that earn inquiries first, and treat page titles and meta tags as final page optimization after the checks that decide whether a page is indexed at all.
Done when every key page has a unique, descriptive title tag and a meta description that matches its content.
14. Validate structured data and schema markup
Structured data is code that labels the facts on a page so search engines can read them without guessing. Google says it uses structured data to understand a page and that it can enable rich results. Our Library entry on schema markup explains it in plain language.
For a small site, the useful types are usually organization, local business, article and FAQ details, depending on what you publish. Most platforms add structured data markup through a plugin.
Test your key pages with Google’s Rich Results Test and fix any errors it flags. Valid markup can make a page eligible for rich snippets, though Google does not promise them. Keep the markup consistent with what the page actually shows.
If you run a business people visit, the local SEO checklist covers the local business markup in detail.
Done when the Rich Results Test passes for your key pages with no errors.
15. Check that search engines and AI crawlers can reach your content
Open your robots.txt again and look for rules that name specific crawlers. Some site owners block AI crawlers on purpose, and that is a legitimate choice. The mistake is blocking them by accident through a plugin or a copied template, then wondering why your brand never appears in AI answers.
Google says that optimizing for its generative AI features is, from its perspective, still SEO. It also tells site owners to follow crawling best practices, to reduce duplicate content, to follow JavaScript SEO guidance if their site uses it, and to provide a good page experience. Every earlier check in this list supports that advice.
If your site renders its main content with JavaScript, use the URL Inspection tool from check 4 to confirm the rendered page contains your text and links.
Done when robots.txt reflects a decision you made on purpose about each crawler, and your rendered pages show their main content.
Fix what you find in this order
An audit produces a list, and a list needs an order. Fix anything that blocks crawling or indexing first, because nothing else matters if a page cannot be indexed. Then fix what wastes the effort of crawlers, then what slows visitors, then the details.
This table shows the order. The sample findings are an illustration of a typical small business site, not a client result.
| Priority | Finding | Why it comes here | Check |
|---|---|---|---|
| 1 | Noindex tag on the service pages | Pages cannot appear in results at all | 5 |
| 1 | Robots.txt blocks the blog folder | Crawlers cannot read the pages | 5 |
| 2 | Four address versions, no redirects | Splits links and signals across duplicates | 2, 8 |
| 2 | Sitemap lists deleted pages | Sends crawlers to dead ends | 6, 7 |
| 3 | Broken links and redirect chains | Wastes crawl effort and loses visitors | 7 |
| 3 | Orphan pages with no internal links | Pages are hard to discover | 11 |
| 4 | Slow hero image, layout shift | Hurts visitors on phones | 9, 10 |
| 5 | Missing title tags and structured data | Reduces rich result eligibility and click appeal | 13, 14 |
After each fix, use the validate option in the Page indexing report where it is offered, so Google rechecks the pages. Then wait. Google says new content can take days to be indexed, so judge your fixes after a few weeks, not a few hours.
Skip these parts of a technical SEO checklist until your site is bigger
Longer technical SEO checklists include items that matter only at scale. For a small site, they cost time without paying it back.
Crawl budget is the amount of crawling Google will spend on your site. Google’s guide says that if your site does not have many rapidly changing pages, you do not need it.
Log file analysis, which reads server log files to see how crawlers visit, helps large sites find wasted crawling. International SEO and hreflang tags matter if you serve several countries or languages, and not if you serve one.
On page SEO, such as keyword targeting and page copy, and off page SEO, such as link building, belong to separate efforts, and paid SEO software is optional at this size. A backlink from a trusted site helps, but it is not a technical fix, so it sits outside this audit.
Skipping these is not laziness. It is how you keep the audit short enough to repeat.
Repeat a short version of this audit every quarter
Technical problems come back. A plugin update changes your robots rules, a redesign drops your redirects, or a new page lands with a noindex tag from a template. A full audit once a year will miss all of that.
Instead, run a ten-minute version each quarter: open the Page indexing report, scan the Core Web Vitals report, check your sitemap status, and click through your main navigation on a phone. Our guide to maintaining your search presence lays out a full quarterly routine.
Run the full fifteen checks again after any redesign, platform move or change of web address.
Where the audit ends and the next job starts
A clean technical audit removes obstacles. It does not create demand. Once search engines can reach and index your pages, the next questions are whether your pages answer what people search for and whether other sites mention you.
If you want the full playbook for being found, the ebook Be Where They Look walks through search and distribution for brands that want visitors from the right places. Each Wednesday, the Ground Truth newsletter sends one practical idea on search and brand growth.
FAQ
What is a technical SEO audit?
A technical SEO audit is a review of the behind-the-scenes parts of a website that affect how search engines crawl, index and display it. It covers indexing, redirects, speed, mobile access, links and structured data. The aim is to find and fix problems that stop good pages from being found.
How long does a technical SEO audit take for a small website?
For a site of around 500 pages or fewer, the fifteen checks above fit into one working session, because most problems show up in Search Console and a quick crawl. The fixes can take longer, especially redirects and speed work, so keep the audit and the repairs separate.
How often should I run a technical SEO audit?
Run the full checklist after any redesign, platform move or change of web address, and a shorter ten-minute check each quarter. Technical issues often appear after plugin updates, template changes and new page launches, so regular light checks catch more than one large annual audit.
Do I need paid tools for a technical SEO audit?
No. Google Search Console is free and covers indexing, sitemaps, Core Web Vitals and HTTPS. PageSpeed Insights and the Rich Results Test are free as well. A crawler helps find broken links and orphan pages faster, and some are free for small sites, but they are optional.
Does technical SEO matter for AI search?
Yes. Google says a page must be indexed and eligible to appear in Search with a snippet before it can appear in its generative AI features. Crawlable pages, clean redirects and a good page experience support both search results and AI search answers, so a clean audit is the base for any AI search work.