Technical SEO Audit Checklist: The 25-Point Check for Small Business Websites

Your website can look perfect and still fail to bring in customers. Before you rewrite a page or spend more on advertising, check the layer underneath: the technical foundations that decide whether search engines can find, read, and trust your site.

A technical SEO audit checklist is a systematic check of that layer. It asks four questions about every important page: can a search engine crawl it, can it index it, does it load well on a phone, and is it the right version of that page? If any answer is no, the page cannot rank. The 25 checks below are ordered by impact.

Before You Start: The Free Toolkit for This Technical SEO Audit Checklist

You do not need paid software. Google Search Console shows your site as Google sees it. PageSpeed Insights tests speed and Core Web Vitals. A crawler such as Screaming Frog, free for up to 500 URLs, collects titles, links, redirects, and indexing rules in one pass. Keep a spreadsheet with one row per check and a pass or fail mark.

Part 1: Can Search Engines Crawl and Index Your Site?

1. Robots.txt is not blocking important pages

Open yourdomain.com/robots.txt. It tells crawlers which parts of your site they may visit, and a stray “Disallow: /” left over from a redesign blocks everything. Pass: no page you want ranked is blocked, and CSS and JavaScript folders are open. Fix: narrow the rule to private areas such as admin folders.

2. Search Console’s Pages report shows your key pages as indexed

In Search Console, open Indexing, then Pages. It lists every URL Google knows about, indexed or excluded, with a reason. Pass: your homepage, service pages, and contact page are indexed. Fix: work through excluded URLs that should be indexed first.

3. No accidental noindex tags on pages that should rank

Check the Pages report for “Excluded by noindex tag” and your content system for a search-visibility setting. In WordPress, one checkbox under Settings, Reading can discourage indexing of the whole site. A noindex tag hides a page from search even though visitors can open it. Pass: only deliberately hidden pages carry the tag. Fix: remove it and request re-indexing.

4. Your XML sitemap lists only live, canonical, indexable URLs

Open your sitemap, usually at yourdomain.com/sitemap.xml, and confirm it is submitted in Search Console and referenced in robots.txt. Pass: every entry returns a 200 status and points to the final canonical version. Fix: regenerate it and strip out anything not live and indexable.

5. Canonical tags point to the page itself

Export every URL and its canonical tag with your crawler. A canonical names the authoritative version of a page when several URLs show similar content. Pass: each important page canonicals to itself over HTTPS. Watch for pages canonicaling to the homepage, to a staging domain, or to a URL that itself redirects. Fix: correct the template setting.

6. Duplicate and parameter URLs are under control

Look for the same content at several addresses: with and without a trailing slash, with www and without, or with tracking parameters. Duplicates split ranking signals between copies. Pass: one version of each page answers and the others redirect to it in a single hop. Fix: pick one URL pattern and redirect the rest.

7. No orphan pages and no pages buried too deep

Use your crawler’s internal-link data to find pages with no links pointing to them, and pages more than three clicks from the homepage. Pass: every important page has several internal links and is within three clicks of the homepage. Fix: link to it from a related page. Our Core Web Vitals guide for small business websites earns its place through internal links from related pages.

8. JavaScript-rendered content is actually visible to crawlers

If your site loads key content with JavaScript, compare the rendered page in Search Console’s URL Inspection tool with the raw source. Pass: the rendered version shows the same key content and links as the browser. Fix: server-side render or pre-render the important content.

Part 2: Site Health, Security, and Status Codes

9. Every important page returns a 200 status

Crawl your site and sort by status code. A page can look fine in a browser and still return an error to a crawler. Pass: every key page returns 200. Fix: restore or redirect broken pages, and check that a custom 404 page still returns a 404 status.

10. Redirects go straight to the final page in one hop

Old URLs should redirect to their replacement, not to another redirect. Chains and loops waste crawl budget and confuse visitors. Pass: every redirect lands on a live page in a single hop. Fix: point each redirect at the final URL and remove the middle steps.

11. HTTPS works on every page with no mixed content

Open key pages and look for a padlock and no warnings. Mixed content happens when a secure page loads an image, script, or style over HTTP. Pass: every page loads over HTTPS and all resources do, too. Fix: update internal links and resource URLs to HTTPS and set a redirect from HTTP to HTTPS.

12. Your site is not carrying a security warning

Check Search Console’s Security issues report and the browser’s address bar. A hacked page, a malware warning, or an expired certificate can push visitors away before they read a word. Pass: no security issues are reported. Fix: remove the compromise, renew the certificate, and request a review.

13. A 404 page helps visitors instead of losing them

Click a broken link on purpose and see what visitors get. Pass: the 404 page explains the problem, links to the homepage and main services, and still returns a 404 status. Fix: replace a blank or server-default 404 with a helpful one.

14. Server errors and slow responses are under control

Watch for 500 errors, timeouts, and pages that take several seconds to answer. A slow server hurts every other check. Pass: no key page returns a 500 error, and server response time stays well under a second. Fix: check hosting limits, database load, and failing plugins, then re-crawl.

Part 3: Speed, Mobile, and Core Web Vitals

15. Core Web Vitals pass on mobile

Test your homepage and top service pages with PageSpeed Insights and read the Core Web Vitals assessment, not a single lab score. Pass: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Fix: start with images, then JavaScript, then server response. Read our Core Web Vitals guide for the full workflow.

16. Images are sized and compressed for the device

A 4,000-pixel image shown at 400 pixels still costs a visitor the full download. Pass: images are close to their display size, compressed, and in a modern format where possible. Fix: resize and compress, then check the page again. For a deeper pass, see our performance optimization service.

17. The page stays usable while it loads

Watch the page load on a phone: does text jump, do buttons move, does a late banner push content down? Pass: layout is stable and the main call to action is visible and tappable early. Fix: reserve space for images and ads, and keep late-loading elements out of the main content area.

18. Mobile usability passes on a real phone

Open key pages on a phone, not just a resized desktop window. Pass: text is readable without zooming, tap targets are large enough, and forms work. Fix: increase font and tap-target sizes, remove horizontal scrolling, and test the contact form end to end.

Part 4: Content, Links, and Structured Data

19. Titles, descriptions, and headings are unique and descriptive

Every indexable page needs a title, a description, and one H1 that describe that page, not the whole site. Pass: no two key pages share a title, and no title is cut off in search results. Fix: rewrite duplicates, starting with the pages that already get traffic.

20. Internal links guide visitors and crawlers to key pages

Link from related pages to your service pages with anchor text that says what the page is about. Pass: every service page has several internal links, and no important page relies on the main menu alone. Fix: add links from related blog posts and service pages.

21. Structured data matches the visible page

Add LocalBusiness, FAQ, or Article schema only where the page actually shows that information, and test it in Google’s Rich Results Test. Pass: the test shows no errors for the schema you use. Fix: remove schema for content that is not on the page, and correct fields that do not match the visible text.

22. Local signals agree everywhere

Check that your business name, address, and phone number match on your site, your Google Business Profile, and major directories. Pass: the details are identical in all three places. Fix: correct the outlier, starting with the profile, and build your local SEO foundation before chasing broader terms.

Part 5: Tracking, Monitoring, and Next Steps

23. Search Console and Analytics are set up and checked monthly

Confirm Search Console is verified, Analytics is collecting, and someone actually looks at both each month. Pass: both tools show data for the last 30 days. Fix: verify ownership, install the missing tag, and set a monthly review reminder.

24. AI search visibility is on your radar

AI answers now summarize pages, so a page that only targets a keyword can be skipped. Pass: key pages answer a clear question in the first paragraph and back it with specific detail. Fix: add a direct answer at the top, then the evidence below, and keep our AI search optimization service in mind for pages that need a deeper pass.

25. The audit ends with a fix list, not a report

Rank every failure by impact: indexing and security first, speed second, content and links third. Pass: you have a short list with an owner and a date for each fix. Fix: work the list in order, re-check each item, and book a re-audit after the first round. For help with the whole list, see our technical SEO service and SEO services.

Your Fix-First Order (If You Only Have One Week)

If time is tight, fix in this order: indexing blocks and errors first, then redirects and canonicals, then mobile speed, then HTTPS and security, then titles and structured data. That order protects what you already rank for before you try to rank for more.

If you want the audit done for you, request a free quote or start with a free SEO audit to see where your site stands.

Frequently Asked Questions

What is a technical SEO audit?

A technical SEO audit is a systematic check of how search engines crawl, render, and index your website. It covers speed, structure, security, and structured data — the foundations that content and links build on.

How often should a small business run a technical SEO audit?

Run a full audit once or twice a year, and a light check every month. Re-audit after a redesign, a platform change, or a sudden traffic drop.

Do I need paid tools for a technical SEO audit?

No. Google Search Console, PageSpeed Insights, and the free version of Screaming Frog cover most checks in this list. Paid tools help at scale, but they do not replace fixing what the free tools already show.

What is the most common technical SEO problem for small businesses?

Slow mobile pages and thin internal linking. Most small business sites have a few fast pages and many slow, orphaned ones. Fix images, link key pages from the homepage, and re-check in Search Console.

Do Core Web Vitals really matter for a small business website?

Yes: they measure the real user experience, and Google uses page experience as one of many ranking signals. They matter most when two pages are otherwise equal — and they matter to visitors on every page, especially where visitors rely on mobile connections.