HANDMADE DESIGN / WEB DEVELOPMENT GUIDE
Technical SEO Audit Checklist for Small Business Websites
A technical SEO audit asks a practical question: can search engines discover, render and understand the pages that matter to your business? It should identify problems that block visibility before recommending more content or more links.
This checklist prioritizes issues a small business can verify without spending weeks producing a report nobody uses.
1. Confirm the preferred site version
Decide whether the canonical domain uses www or non-www, and ensure HTTPS is enforced. Alternate protocol and hostname versions should redirect to the preferred URL without unnecessary hops.
A quick check with an HTTP client can reveal loops, 302s where 301 is intended and unexpected 200 responses on duplicate hostnames.
2. Review indexing in Google Search Console
Add the correct domain property. Check the Pages report and inspect the homepage, core services and selected blog posts. Compare indexed pages against pages you actually want in search.
Not every unindexed URL is a problem. Thank-you pages, internal search pages and certain filtered results may be intentionally excluded. Focus on important pages that should appear but do not.
3. Check robots.txt and meta robots
A staging deployment sometimes reaches production with a site-wide block or noindex directive. Review the actual deployed response, not just the development configuration.
A sitemap can help discovery, but it cannot override an intentional block or force Google to index a low-value page.
4. Verify canonical tags
Each indexable page should indicate its preferred URL where appropriate. Watch for old-domain canonicals after a migration, mismatched HTTP/HTTPS variants and a whole site accidentally pointing to the homepage.
Google treats canonical annotations as signals, not guarantees; consistent redirects and internal links reinforce the choice.
5. Inspect JavaScript-rendered content
Some sites load all useful copy after JavaScript runs. Google can render JavaScript, but rendering is an additional step and fragile implementations can hide content or links.
Compare raw HTML with rendered output. Make sure the headline, service description, navigation and important links are accessible. Prefer standard anchor links for navigation, and consider server-side rendering or prerendering when essential content is not reliably exposed.
6. Audit internal linking
Choose several target service pages and ask how easily a visitor can reach them. Important pages should have a clear place in navigation, related content and contextual links. Fix broken links and unnecessary redirect chains.
A cluster is useful when it reflects a genuine topic. For example, a guide on website redesign can link naturally to responsive design, accessibility and website development services.
7. Review response codes and redirects
Export 3xx, 4xx and 5xx responses from a crawl. Keep permanent redirects for moved pages that have relevant counterparts. Return real 404/410 statuses for deleted content without a useful replacement. Do not redirect every old URL to the homepage.
Identify linked 404 pages and prioritize those with real user demand or external references. Not every 404 deserves a replacement article.
8. Measure mobile usability and performance
Google’s Core Web Vitals cover largest contentful paint, interaction responsiveness and layout stability. Optimize the largest real-world issues: oversized hero media, heavy scripts, layout jumps and blocked interactions.
Check mobile navigation, contact forms and sticky elements manually. A site can get a good technical score while still being difficult to use.
9. Verify structured data
Add structured data only where it truthfully describes visible content. For an article, BlogPosting can identify the headline, author and publication date. Do not invent ratings, reviews or FAQs to trigger a special search appearance.
Test generated JSON-LD before publishing and keep dates aligned with the actual page.
10. Measure the outcome
Build a short report with issues, affected URLs, severity, fix owner and verification step. Once major technical blockers are resolved, monitor search impressions, clicks, relevant landing pages and enquiries. A high audit “score” is not a business outcome.
Priority matrix
| Issue | Typical priority | Reason |
|---|---|---|
Important service page noindex |
Urgent | Prevents indexing |
| Redirect loop on homepage | Urgent | Blocks users and bots |
| Broken contact form | Urgent | Lost enquiries |
| Incorrect site-wide canonical | High | Wrong URL signals |
| Missing internal links to service | High | Weak discovery path |
| Minor meta description rewrite | Lower | Usually not a blocker |
| Small decorative image optimization | Lower | Prioritize larger performance issues |
A realistic audit process
First, identify the pages that matter to revenue. Second, verify their accessibility and indexing. Third, fix redirects, canonicals and internal links. Fourth, check performance and usability. Only then develop a content and outreach plan.
For an implementation partner, see Handmade Design SEO services. If you are changing a lot of URLs, use the website redesign checklist alongside this guide.
