Technical SEO Audit Checklist for Small Business Websites
9 min read
A small business website can have excellent content and still struggle in search because of technical problems that visitors never see. Pages blocked from indexing, slow templates, broken redirects and duplicate URLs quietly limit how much search engines can find, understand and show. Fixing them is often more practical and affordable than writing yet another blog post or adding more pages.
This checklist walks you through a technical SEO audit in a sensible order: tools first, then crawling and indexing, structure, speed and mobile, and finally on-page technical elements. You don't need to be a developer, and most checks use free tools. By the end you should have a short, ranked list of fixes you can act on, and you can work through it at your own pace.
What a technical SEO audit covers
Technical SEO is the work that helps search engines access, interpret and trust your website. It sits underneath content and links. If a page can't be crawled, or loads so slowly that visitors leave, good writing has little chance to perform. An audit checks each of these foundations in turn and records what's working and what isn't.
Run an audit when you launch or redesign a site, when you migrate to a new domain or platform, when traffic drops without an obvious reason, and at least once a year as routine maintenance. Small sites change more than owners realize, through plugins, new pages and edits that nobody tracked. Many owners only discover technical faults after enquiries fall, so a scheduled review is cheaper than reacting later. Put the date in your calendar like any other maintenance task.
Keep expectations realistic. A technical audit removes obstacles but doesn't guarantee rankings, since search results depend on competition, content quality, relevance and many other factors. Use it to make sure nothing on your own site holds back pages that deserve to rank. The fixes support other marketing too: faster, cleaner pages help paid campaigns and email traffic convert better, as well as the organic visitors who arrive from search engines.
Set up the tools you need
Start with Google Search Console, which is free and shows how Google sees your site. Verify your domain, submit your sitemap, and review the Pages report for indexing problems, the Performance report for queries and clicks, and the Experience reports for speed and mobile issues. Bing Webmaster Tools gives a similar view for Bing. Make sure the person doing the audit has full access, because several of the most useful reports are hidden from limited users.
Add a crawler to see your site the way a search engine bot does. Desktop crawlers such as Screaming Frog have a free version suitable for small sites, and several online tools provide basic crawls too. A crawl lists every URL with its status code, title, headings and links, which makes patterns easy to spot. Free tools usually cap how many pages they crawl, which rarely matters for a site with a few dozen or a few hundred pages.
Use Google PageSpeed Insights for speed checks and GA4 to confirm that organic traffic is being recorded correctly. Put findings in a simple spreadsheet with columns for the URL, the issue, how serious it is, who will fix it and the date completed. Share the sheet with whoever manages your website so nothing gets lost in email threads, and update it as each item is done instead of at the end.
Check crawling and indexing
Begin by asking whether search engines can reach your important pages. Open yourdomain.com/robots.txt and make sure it doesn't block key sections by mistake. A single stray line, often left over from a development version of the site, can stop crawlers from visiting entire folders, so read it carefully. Check the sitemap line at the bottom of the file too, since it gives crawlers a direct route to the pages you most want found, and confirm the address it points to still works.
Next, look for accidental noindex instructions. They can appear as a meta robots tag in the page code or as an HTTP header, and some content management systems add them through a setting such as discouraging search engines from indexing the site. Use Search Console's URL Inspection tool to confirm how Google sees a given page. Look at pages that redirect or return errors as well, because an important page that quietly returns a different status code won't be indexed the way you expect.
Then review the Pages report in Search Console. Look at why pages are excluded, such as duplicate content, crawled but not indexed, or blocked by robots.txt. Some exclusions are normal, but important service and product pages should appear in the indexed list. Click into each reason group and sample several URLs. When a whole folder is excluded for the same cause, that usually points to a single setting or template problem that's simple to correct once you find it.
- Robots.txt allows crawling of important pages and points to your sitemap
- No unintended noindex tags on pages you want found
- XML sitemap lists only live, canonical, indexable URLs and is submitted in Search Console
- Canonical tags point to the preferred version of each page
- Only one version of the site resolves: https with or without www, not both
Review site structure, URLs and redirects
A clear structure helps both visitors and crawlers. Important pages should be reachable within a few clicks from the homepage, and each should be linked from at least one other page. Pages with no internal links, often called orphan pages, are hard for search engines to discover and tend to get little attention. A flat, logical structure with clear categories also makes it easier to spread internal links to pages that deserve more visibility.
Check URLs for consistency. Short, readable addresses that describe the page are easier to manage than long strings of parameters. Watch for duplicate versions created by trailing slashes, capital letters, tracking parameters or filters, and use canonical tags or redirects so each page has one preferred address. Pick one rule and apply it everywhere, including internal links, the sitemap and canonical tags, so every signal points the same way and search engines don't have to guess.
Review status codes in your crawl. Pages returning 404 that still receive links or traffic should be redirected to a relevant replacement. Redirect chains, where one redirect leads to another, waste crawl effort and slow visitors, so point old URLs straight to the final destination with a permanent 301 redirect. Use temporary 302 redirects only when a move really is temporary. After a redesign, run your old URL list through a crawler to confirm that every important address lands correctly.
Fix broken internal links
Broken links frustrate visitors and send crawlers to dead ends. Your crawl report lists internal links that lead to 404 pages. Update each link to the correct page, or remove it if the content no longer exists. Check navigation menus and footers first, because a single broken link there can appear on every page of the site.
Test speed, Core Web Vitals and mobile usability
Page experience affects both visitors and search performance. Google's Core Web Vitals measure loading (Largest Contentful Paint), responsiveness (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). Search Console reports them using real visitor data when your site has enough traffic, and PageSpeed Insights shows both field data and lab test results. Treat the thresholds Google publishes as guides, and focus first on templates used by many pages, since one fix there improves the whole site at once.
The usual causes of slow small business sites are oversized images, heavy themes, too many plugins, unoptimized fonts and third party scripts. Compress and resize images, serve modern formats where possible, enable caching, and remove tools that nobody uses. Hosting quality matters too, especially for sites that respond slowly even when pages are light. Test again after each change, because speed problems often hide behind one another and fixing one can reveal the next bottleneck in line.
Mobile usability deserves its own check because most searches now happen on phones. Open key pages on a real device and test menus, forms and buttons. Make sure the viewport is set correctly, text is readable without zooming, and tappable items aren't too close together. Content should be the same on mobile as on desktop.
Audit on-page technical elements
Use your crawl to review the elements that tell search engines what each page is about. Every indexable page should have a unique title tag and a meta description written for people, one clear H1 heading, and a logical order of subheadings. Missing, duplicated or very long titles are among the easiest issues to find and fix. Start with the highest traffic pages, because titles and descriptions there influence how many people click through from search results.
Check that your site uses HTTPS everywhere, with no mixed content warnings caused by images or scripts loading over HTTP. Review image alt text for descriptive, accurate wording, and confirm that images are compressed. Where it fits your business, add structured data such as Organization, LocalBusiness or FAQ markup, and test it with Google's Rich Results Test. Don't add markup that doesn't match what's visible on the page, since misleading structured data can make search engines ignore it or, in serious cases, take action against the site.
For local businesses, confirm that your name, address and phone number match across the site and your Google Business Profile. Keep contact details as readable text instead of images, and give each location or service its own page where it genuinely differs, so each page has a clear purpose. Consistent details build trust with people and search engines alike, and a quick search through your pages and listings will show whether they match.
- Unique, descriptive title tags and meta descriptions on every page
- One H1 per page and a logical heading order
- Descriptive alt text on meaningful images
- HTTPS with no mixed content errors
- Valid structured data where relevant
Prioritize fixes and keep the audit alive
An audit can produce a long list, and not every item deserves immediate attention. Rank issues by impact and effort. Anything that blocks indexing of important pages comes first, followed by broken redirects and slow templates, then on-page tidy ups. Quick wins can be done in a single afternoon while larger projects go into a schedule.
After fixing an issue, verify it. Use the URL Inspection tool to request reindexing of key pages, re-crawl the site to confirm errors are gone, and watch the Pages and Performance reports over the following weeks. Search engines take time to reprocess changes, so be patient before judging results. Keep a dated record of changes, which helps you connect later movements in traffic to specific fixes instead of relying on memory or assumptions.
Dynamic Growth is automated software. Its SEO Audit scans your URL and ranks the technical and on-page issues, and its Whole-Site Crawl goes through pages across the site, which suits the broken link and redirect checks above. You fix the issues yourself. Schedule a repeat audit every six to twelve months.
Frequently asked questions
How often should a small business run a technical SEO audit?
A full audit once or twice a year is enough for most small sites. Run an extra one after a redesign, migration or sudden traffic drop. Between audits, glance at Search Console monthly for new indexing errors, speed warnings or manual action notices so you can fix problems before they grow.
Can I do a technical SEO audit without a developer?
Yes, for most checks. Search Console, PageSpeed Insights and a free crawler show you what needs attention, and many fixes such as titles, redirects and image compression can be made in a content management system. You may need a developer for server settings, theme code or complex structured data.
What is the difference between crawling and indexing?
Crawling is when a search engine bot visits a page and reads it. Indexing is when the search engine stores that page so it can appear in results. A page can be crawled but not indexed, for example if it is thin, duplicated or marked noindex, so check both steps.
Do I need an XML sitemap for a small website?
A sitemap isn't mandatory for very small, well linked sites, but it's quick to set up and helps search engines discover pages. Include only live, indexable, canonical URLs, submit it in Search Console, and keep it updated automatically through your platform or an SEO plugin.
Which technical issues should I fix first?
Start with anything that stops important pages from being crawled or indexed, such as robots.txt blocks and noindex tags. Next fix broken pages and redirect chains, then major speed and mobile problems. Cosmetic items such as slightly long meta descriptions can wait until the serious issues are resolved.
More from the blog
- Website Monitoring: What to Check Every Week (Beyond Uptime)
- Website Audit Checklist: 25 Checks Before You Spend on Marketing
- How to Read an SEO Audit Report and Decide What to Fix First
- Broken Link Checker: How to Find and Fix Broken Links on Your Website
- AI Search Optimization: How to Check Whether AI Assistants Mention Your Brand
- Website Speed Test: How to Read Your Results and Speed Up Your Site
- SSL Certificate Checker: How to Check Your Certificate and Fix Common Errors