Technical SEO Audit Checklist: 40 Checks for Small Business Websites

A technical SEO audit answers one question: can search engines find, crawl, render, understand and index your website without obstacles? If the answer is no, no amount of content or link building will deliver the results you expect. This checklist is the technical part of the process we run on every site before we work on content. It complements our on-page SEO audit checklist, which covers titles, headings and content.

This article is part of our complete guide: SEO for Small Business: The Complete Guide (2026).

You will need Google Search Console, a website crawler (many have free versions for small sites), Google PageSpeed Insights and a browser. Work through each section in order; earlier issues often cause later ones.

Section 1: Crawling and access (checks 1–7)

1. Robots.txt is accessible and correct. It loads at /robots.txt, does not contain Disallow: / for all user agents, and lists the sitemap. See Blocked by robots.txt.
2. CSS and JavaScript are crawlable. Google needs them to render pages.
3. No important pages blocked by robots.txt. Check the robots.txt report and URL Inspection.
4. Server responds reliably. Check Settings › Crawl stats for host status issues and average response time.
5. No firewall or bot protection blocking Googlebot. Look for 403 or 429 errors in Search Console. Allow verified search engine bots.
6. Login or password protection is off on public pages.
7. Crawl depth is shallow. Important pages are reachable within three clicks of the homepage.

Section 2: Indexing (checks 8–15)

8. Search engine visibility is on. In WordPress, “Discourage search engines” is unticked.
9. No accidental noindex on key pages. See Excluded by noindex.
10. XML sitemap exists, is submitted and contains only indexable 200 URLs. See sitemap guide.
11. Every indexable page has one correct self-referencing canonical. See canonical issues.
12. Page indexing report reviewed. Note the main reasons for non-indexed pages. See the report explained.
13. Key pages are indexed. Inspect the homepage and top service pages.
14. Thin archives, attachment pages and internal search results are noindexed or removed.
15. No unexpected pages in the index. A site: search shows no spam, staging or test pages.

Section 3: URLs, redirects and status codes (checks 16–22)

16. One preferred domain version. http, https, www and non-www all redirect in a single hop to the preferred version.
17. No redirect chains or loops. See Page with redirect.
18. Internal links point to final URLs, not redirects.
19. No broken internal links (404s).
20. Removed pages with value are redirected to relevant replacements.
21. No soft 404s on important pages. See soft 404 errors.
22. URLs are short, readable and lowercase, with hyphens rather than underscores or parameters.

Section 4: Site architecture (checks 23–26)

23. Clear hierarchy: homepage, main categories or services, then detail pages.
24. No orphan pages. Every indexable page receives at least one internal link. See internal linking.
25. Navigation is crawlable HTML, not only JavaScript-generated or image-based.
26. Breadcrumbs on deeper sites, with BreadcrumbList structured data.

Section 5: Speed and Core Web Vitals (checks 27–31)

27. Core Web Vitals report in Search Console shows mostly “Good” URLs on mobile.
28. LCP under 2.5 seconds on key pages: optimise hero images and server response.
29. INP under 200 ms: reduce heavy JavaScript and third-party scripts.
30. CLS under 0.1: set image dimensions and avoid late-loading banners.
31. Caching, compression and modern image formats are enabled. On WordPress, see LiteSpeed speed guide.

Section 6: Mobile (checks 32–33)

32. Content parity: the mobile version shows the same important content, links and structured data as desktop. Google indexes mobile first.
33. Usable layout: readable text, tappable buttons and no horizontal scrolling.

Section 7: Security (checks 34–37)

34. HTTPS everywhere, with a valid certificate and no mixed content warnings.
35. No security issues or manual actions reported in Search Console.
36. CMS, theme and plugins updated; unused plugins removed. See our WordPress security checklist.
37. Security headers in place, such as HSTS, X-Content-Type-Options and X-Frame-Options.

Section 8: Structured data and international (checks 38–40)

38. Valid structured data for Organization or LocalBusiness, breadcrumbs, articles and products where relevant, with no errors in Search Console enhancement reports. See local business schema.
39. Language declared in the HTML lang attribute.
40. Hreflang correct for multilingual or multi-country sites, pointing to canonical URLs with return links.

How to prioritise what you find

An audit typically produces a long list. Rank issues by impact and effort:

• Critical: anything stopping key pages from being crawled or indexed (robots.txt blocks, noindex, wrong canonicals, server errors, hacks).
• High: issues affecting many pages, such as redirect chains, duplicate content, poor Core Web Vitals on templates, or orphaned money pages.
• Medium: broken links, soft 404s, missing structured data.
• Low: cosmetic issues on low-traffic pages.

Fix critical issues immediately, then work through high-impact template-level fixes, because one change to a template can fix hundreds of pages.

Turning the audit into an action plan

An audit is only useful if it leads to changes. For each issue, record four things: what is wrong, which URLs or templates it affects, how to fix it, and who will do it. Group fixes by where they happen. Settings changes (robots.txt, SEO plugin options, redirects) can often be done in an afternoon. Template changes (headings, canonical output, image sizes) may need a developer. Content changes (thin pages, duplicates) take longer and belong in a content plan. Agree a date to re-crawl the site and recheck Search Console after the fixes, so you can confirm each issue is resolved rather than assuming it is. Keep the audit document: next time, you can compare results and see whether old problems have returned.

How often to run a technical audit

Run a full audit before and after any redesign or migration, and at least once or twice a year. Check Search Console monthly for sudden changes in indexing, Core Web Vitals or security, which often signal a new problem. See redesign without losing SEO.

Technical SEO on website builders

On Wix, Squarespace and Shopify, many technical items are managed by the platform, so your audit focuses on indexing settings, redirects, duplicates, speed choices and structured data. On WordPress you control everything, which means more to check and more to fix. See SEO for Wix websites.

Our experience

This checklist reflects issues we have actually found and fixed on client sites in our case studies, from leftover noindex tags and hacked spam pages to redirect chains after redesigns. Projects such as Powersports Software and M10 News show how technical fixes unlock content that was already good.

Related guides and services

• On-page SEO audit checklist: a page-by-page checklist for titles, headings, content and links.
• Page indexing report explained: every status in Search Console in plain English.
• Google not indexing all pages: why only part of your site is indexed.
• Blocked by robots.txt: how to read and repair a robots.txt file safely.
• Google indexing fix service: we diagnose and fix pages Google will not index.

Get expert help

We run this full technical audit on your site, prioritise the issues by impact, fix them and confirm the results in Search Console. Start with our SEO services, browse real client results in our case studies, or contact us for a free, no-pressure review of your website.

Frequently asked questions

What is the difference between technical and on-page SEO?

Technical SEO ensures search engines can crawl, render and index the site. On-page SEO optimises the content and HTML of individual pages.

How long does a technical SEO audit take?

For a small business site, typically one to three days including prioritised recommendations.

Can I do a technical audit myself?

Yes, using this checklist, Search Console and a crawler. Fixes may need developer help.

What tools do I need?

Google Search Console, a crawler, PageSpeed Insights and a structured data testing tool.