A technical SEO audit helps a small business find the website problems that can prevent search engines from crawling, understanding, and serving its pages. This practical checklist covers the highest-priority checks for crawlability, indexing, redirects, canonical tags, XML sitemaps, robots.txt, HTTPS, mobile usability, and Core Web Vitals, with a simple schedule for repeating the work after launches, redesigns, and platform changes.
Overview
A technical SEO audit is a structured review of how a website works for search engines and visitors. It is not limited to rankings or keyword placement. A page can contain useful content and still underperform if it cannot be crawled, is blocked from indexing, loads unreliably, or has several competing URL versions.
For a small business website, start with issues that affect many pages or prevent important pages from appearing in search. Do not begin by trying to fix every warning in an SEO tool. Separate findings into three groups:
- Critical: Problems that block crawling, indexing, access, or the correct version of a page.
- Important: Problems that affect usability, page performance, internal discovery, or search-result presentation.
- Worth monitoring: Minor warnings that do not currently prevent access or indexing but may signal future maintenance work.
Free tools can provide most of the evidence needed for a first audit. Use a search engine's webmaster tools for indexing and performance data, a browser for HTTPS and mobile checks, and a crawler or site-audit tool for links, status codes, and page-level patterns. The free SEO tools guide for small websites can help you build a practical toolset without collecting unnecessary reports.
What to track
1. Crawlability and indexation
Confirm that search engines can reach the pages that matter to the business: the home page, service or product pages, location pages, key blog posts, contact page, and other pages intended to attract organic traffic.
- Review the site's indexing report for excluded, blocked, redirected, duplicate, and crawled-but-not-indexed URLs.
- Inspect a sample of important URLs individually rather than relying only on a site-wide total.
- Search for a distinctive page URL to check whether the intended page is discoverable, while treating search results as a rough signal rather than a complete index report.
- Check whether staging pages, internal search results, thin archive pages, or private areas are accidentally exposed.
When a valuable page is not indexed, first determine whether the cause is intentional. A page may be excluded because of a noindex directive, a robots.txt rule, a redirect, a canonical pointing elsewhere, or a quality and duplication issue. Fix the cause before requesting another inspection.
2. Robots.txt and XML sitemaps
Open https://example.com/robots.txt in a browser and check that it is available, readable, and not blocking important directories or page paths. Robots.txt controls crawling; it does not reliably remove an already indexed URL. Avoid broad rules copied from another website without understanding what they block.
Review the XML sitemap as a list of preferred, indexable URLs. It should normally contain the canonical versions of pages that return a successful response and are intended for search. Look for redirected URLs, broken URLs, noindex pages, duplicate URL variants, and outdated content. Submit the sitemap through the site's search-console account and monitor whether submitted pages are being processed as expected.
3. Status codes, redirects, and canonical tags
Check internal links and important URLs for HTTP status codes. A successful page should normally return a successful response; deleted pages should return an appropriate not-found or gone response; and permanently moved pages should redirect to the closest relevant replacement. Avoid long redirect chains, redirect loops, and sending every removed page to the home page when a more specific destination exists.
Review canonical tags on pages with similar or alternate URLs. A canonical is a signal about the preferred version, not a substitute for consistent internal links, redirects, or access controls. Confirm that the canonical URL is absolute, uses the preferred HTTPS and hostname format, resolves successfully, and represents substantially the same page.
4. HTTPS, mobile usability, and performance
Visit the site using HTTPS and check for certificate warnings, mixed content, and links that still point to HTTP versions. Confirm that the preferred hostname is consistent and that alternate protocol or hostname versions redirect correctly.
Test important templates on a real phone or a browser's mobile view. Check for horizontal scrolling, clipped buttons, unreadable text, intrusive overlays, broken menus, and forms that are difficult to complete. Technical SEO is closely connected to user experience, so record problems that affect calls, bookings, purchases, or contact submissions.
Use a performance report and field data, when available, to monitor loading and interaction metrics. Pay particular attention to the page's main visible content, layout movement, and responsiveness. Treat performance thresholds as current guidance that can change; use the latest guidance in the testing tool rather than relying on an old screenshot or fixed score target. Improve oversized images, unnecessary scripts, slow hosting, render-blocking assets, and unstable layout elements in that order of likely impact.
5. Internal links and site structure
Every important page should be reachable through normal internal links, not only through the XML sitemap. Check for orphan pages, excessive click depth, broken navigation, and links that use inconsistent URL formats. Use descriptive anchor text that explains the destination naturally. A simple internal linking map can reveal that an important service page receives no contextual links from related articles or the main navigation.
6. Structured data and page templates
If the site uses structured data, validate it on representative templates such as the home page, service page, article, product, or local business page. Mark up only information that is visible and accurate on the page. Treat structured data as a way to describe content, not as a guarantee of enhanced search features. Recheck it after changing themes, plugins, templates, or business details.
Quick troubleshooting table
| Finding | Likely checks | Practical fix |
|---|---|---|
| Important page is not indexed | Noindex, robots.txt, canonical, status code, or internal links | Remove the unintended restriction, correct the preferred URL, add internal links, then request validation |
| Many URLs are excluded | Filters, parameters, duplicate templates, redirects, or intentional exclusions | Classify exclusions before changing settings; correct only exclusions that affect valuable pages |
| 404 errors increase | Recent redesign, deleted pages, broken internal links, or changed slugs | Restore useful pages, add relevant redirects, and update internal links |
| Page performance is weak | Large images, scripts, fonts, hosting, or layout shifts | Compress media, remove unused assets, improve loading order, and retest key templates |
| Canonical is ignored | Conflicting signals, duplicate content, redirects, or an inaccessible canonical URL | Align internal links, sitemap entries, redirects, and canonical tags around one preferred URL |
Cadence and checkpoints
A small website does not need a full technical audit every week. Use a layered schedule:
- Monthly: Check indexing alerts, major coverage changes, manual actions or security notifications, uptime, broken forms, and a small sample of important URLs.
- Quarterly: Review the full technical SEO checklist, crawl key templates, inspect redirects and canonicals, validate the sitemap and robots.txt, and review mobile and performance trends.
- After a launch or redesign: Test before release and again after deployment. Compare URL lists, page titles, status codes, canonicals, internal links, sitemap contents, and analytics or search-console data.
- After a WordPress update: Test navigation, forms, metadata, schema, caching, redirects, and performance. Keep a record of plugin or theme changes so a new issue can be traced quickly. The WordPress SEO compatibility checklist provides a useful recovery workflow.
Keep an audit log with the date, affected URLs, evidence, owner, fix, and retest result. This prevents the same warning from being investigated repeatedly and makes gradual changes easier to interpret.
How to interpret changes
Do not assume that every rise in excluded URLs or every ranking movement represents a technical failure. First compare the change with a known event: a redesign, plugin update, migration, seasonal shift, content removal, tracking change, or search-engine recrawl.
Look for patterns. A single broken page usually calls for a page-level fix. The same issue across hundreds of URLs points to a template, CMS, redirect rule, or hosting configuration. If organic traffic falls, compare affected landing pages with indexing status, impressions, clicks, and recent technical changes. A technical audit can identify access problems, but it cannot by itself explain every change in demand or competition.
Prioritize fixes using three questions: Does the issue affect a valuable page? Does it affect many URLs? Can the fix be verified clearly? Address blocked or incorrect URLs first, then broken user journeys and performance problems, followed by less urgent warnings. After each change, retest the affected URLs and allow time for systems to recrawl before drawing conclusions.
When to revisit
Schedule the next review now rather than waiting for traffic to decline. Revisit this technical SEO audit checklist quarterly, before major campaigns, and whenever the site's platform, theme, plugins, URL structure, domain, hosting, or navigation changes. Review it sooner if important pages disappear from search, error counts rise sharply, forms stop working, or visitors report slow or broken experiences.
For a practical next step, create a spreadsheet with these columns: URL or issue, evidence, priority, proposed fix, date assigned, date completed, and retest result. Start with the five most valuable pages, then expand to templates and site-wide settings. Pair the technical review with a broader free SEO audit checklist for small business websites so that technical findings are considered alongside content, local visibility, and on-page factors.
A recurring audit works best as maintenance, not emergency repair. Track what changed, fix the issues with the widest impact, and keep the checklist current when your CMS, browser tools, or search-console terminology changes.
