Technical SEO Audit Checklist for Small Businesses (2026)
Most small business SEO problems aren't content problems — they're infrastructure problems. A page can have excellent content and still not rank because Google can't crawl it, can't index it, or can't load it fast enough to care. This checklist covers the technical issues that most commonly suppress rankings for small business websites, in order of priority.
R
Rich NashawatySEO Consultant · 20 years experience · Boston & Nationwide
Fix crawl and indexation issues before anything else — no amount of content or links helps if Google can't access your pages
What technical SEO actually means for small businesses
Technical SEO is the part of search optimization that has nothing to do with content. It's the infrastructure layer — the signals that tell Google whether your site is crawlable, indexable, fast, mobile-friendly, and trustworthy enough to rank.
The reason it matters disproportionately for small businesses is that technical problems are often invisible. A business owner publishing weekly blog posts and building backlinks can be doing everything right on the surface while a single misconfigured robots.txt or accidental noindex tag is silently blocking Google from ranking any of it. These aren't hypothetical scenarios — they're the most common cause of unexplained ranking problems I find when auditing small business sites.
You don't need expensive tools to run a solid technical audit. Google Search Console, PageSpeed Insights, and the Rich Results Test are all free and cover the most impactful issues. What you need is a systematic approach — which is what this checklist provides.
Crawlability and indexation
These are the highest-priority items in any technical audit. If Google can't crawl and index your pages, nothing else matters.
Check for accidental noindex tags
Critical
A noindex meta tag on a page tells Google not to include it in search results. These get added accidentally during development and forgotten. Check your most important pages by viewing their source and searching for "noindex" — or check GSC → Pages → Excluded for pages listed as "Excluded by noindex tag."
Verify your robots.txt isn't blocking important pages
Critical
Your robots.txt file can accidentally block Google from crawling entire sections of your site. View it at yourdomain.com/robots.txt — make sure it's not disallowing your key pages. A Disallow: / line blocks your entire site.
A sitemap tells Google which pages exist and when they were last updated. Without one, Google has to discover your pages through links alone — slower and less reliable. Submit it in GSC once and Google will re-read it automatically.
→ GSC → Indexing → Sitemaps → Submit sitemap URL
Check GSC for crawl errors and coverage issues
Critical
GSC's Pages report shows exactly which of your pages are indexed, which are excluded, and why. Any page showing "Crawled — currently not indexed" or "Discovered — currently not indexed" needs investigation — Google found it but chose not to index it, usually due to thin content or a technical signal.
Broken internal links waste crawl budget and create a poor user experience. GSC flags these under Pages → Not Found (404). Fix by updating the link URL, setting up a 301 redirect, or removing the broken link.
→ GSC → Indexing → Pages → "Not found (404)"
Verify canonical tags are correct
High
Canonical tags tell Google which version of a page is the "master" — preventing duplicate content issues. Check that your canonical URLs match the actual page URL (not pointing to a different domain or www vs non-www variation). View page source and search for "canonical."
Google uses Core Web Vitals as a ranking signal. These measure real-world user experience — how fast your page loads, how stable the layout is, and how quickly it responds to interaction.
Run PageSpeed Insights on your key pages
High
PageSpeed Insights gives you both lab scores and real-world field data. Focus on the mobile score — most local searches happen on mobile. A score below 50 on mobile is a significant ranking disadvantage. The tool tells you exactly what to fix.
→ pagespeed.web.dev — test homepage, main service page, and top blog post
Check Core Web Vitals in GSC
High
GSC's Core Web Vitals report shows real-world data from Chrome users visiting your site — more accurate than lab tests. Look for pages in the "Poor" or "Needs Improvement" categories and prioritize your highest-traffic pages first.
→ GSC → Experience → Core Web Vitals
Ensure images are sized and compressed
High
Oversized images are the most common cause of slow page load times. Images should be sized to their display dimensions (not uploaded at 4000px and displayed at 400px) and compressed. Use WebP format where possible. Free tools: Squoosh, TinyPNG.
Web fonts block page rendering when loaded synchronously. Use the media="print" onload pattern or font-display: swap in your CSS to prevent fonts from delaying the initial page display. This is one of the fastest CLS (Cumulative Layout Shift) fixes available.
These are the basic signals Google reads to understand what each page is about. Missing or duplicate versions of these are surprisingly common even on established sites.
Every page has a unique title tag
High
Title tags are one of the strongest on-page signals for what a page is about. Every page needs a unique title — no two pages should share the same title. Keep them under 60 characters, lead with the primary keyword, and write them for humans first (they appear as the blue link in search results).
→ GSC → Search Appearance → check for duplicate title warnings
Every page has a unique meta description
Medium
Meta descriptions don't directly affect rankings but do affect click-through rate — they're the snippet text in search results. Keep them under 155 characters, include the primary keyword, and write a clear value proposition. Google sometimes rewrites them, but having a good one is worth the effort.
→ View source → search "meta name=description"
One H1 per page, matching the primary keyword intent
Medium
Each page should have exactly one H1 tag — the main headline. It should clearly describe what the page is about and align with the title tag. Multiple H1s or missing H1s are common issues on older or template-built sites.
→ View source → search for h1 tags
Images have descriptive alt text
Medium
Alt text describes images to search engines and screen readers. Descriptive alt text (not keyword-stuffed) helps images rank in image search and contributes to on-page relevance signals. Missing alt text on important images is a missed opportunity.
→ View source → search for img tags without alt attributes
Mobile and HTTPS
Site is fully HTTPS with no mixed content
Critical
HTTPS is a confirmed Google ranking signal. If your site still loads on HTTP — or loads on HTTPS but references HTTP resources (images, scripts) — fix it. Check for the padlock in the browser address bar and look for "Not Secure" warnings. Most hosting providers offer free SSL via Let's Encrypt.
→ Check browser address bar · use Why No Padlock tool for mixed content
Site passes Google's Mobile-Friendly Test
Critical
Google uses mobile-first indexing — it primarily uses the mobile version of your site for ranking. A site that isn't mobile-friendly will rank poorly regardless of content quality. Test with Google's Mobile-Friendly Test tool and fix any issues flagged.
→ search.google.com/test/mobile-friendly
www vs non-www redirects to one canonical version
High
Your site should consistently use either www.yourdomain.com or yourdomain.com — not both. Google treats these as different URLs without a redirect. Set up a 301 redirect from the version you don't use to the one you do, and make sure your canonical tags match.
→ Type both versions in browser and verify one redirects to the other
Structured data and schema
Schema markup helps Google understand your content precisely and can qualify pages for rich results in search — FAQ boxes, review stars, breadcrumbs. It's not a ranking factor directly, but it improves how your results look and can increase click-through rate significantly.
LocalBusiness schema on homepage
High
LocalBusiness JSON-LD on your homepage tells Google your business name, address, phone, hours, and service area in a machine-readable format. This is the schema that matters most for local search. Use Google's Rich Results Test to verify it's parsing correctly.
→ search.google.com/test/rich-results
FAQPage schema on pages with Q&A content
Medium
If a page has a FAQ section, add FAQPage JSON-LD. This can qualify the page for rich results in search — the FAQ answers appear expanded directly in the results page, significantly increasing the visual real estate your result takes up.
→ Add FAQPage JSON-LD to service pages and blog posts with FAQ sections
BreadcrumbList schema on interior pages
Medium
Breadcrumb schema displays the page's location in your site hierarchy in search results — "Home › Blog › Post Title" appears under the URL. It helps users understand site structure and can improve click-through rate on blog posts and service pages.
→ Add BreadcrumbList JSON-LD to blog posts and service pages
What to fix first
Running through this checklist for the first time can surface a long list of issues. Prioritize in this order:
Fix immediately — anything that blocks indexation. Noindex tags on pages you want ranked, robots.txt blocks, missing sitemap. These have the highest potential impact because they may be actively preventing Google from ranking your pages at all. One noindex tag in the wrong place can explain months of unexplained ranking problems.
Fix next — HTTPS and mobile. Both are confirmed ranking signals and both are binary — you either pass or you don't. HTTPS is usually a five-minute fix with your hosting provider. Mobile issues typically require CSS changes.
Fix after — page speed. Speed improvements compound over time and affect every page on your site. Start with the highest-traffic pages and work from the top of the PageSpeed Insights recommendations list.
Layer in over time — schema and on-page signals. These improve existing rankings and click-through rates but won't move the needle until the crawl and indexation foundation is solid.
The monthly habit
Most technical issues don't appear all at once — they creep in with site updates, new content, and plugin changes. Spending 15 minutes in Google Search Console once a month looking at the Pages report and Core Web Vitals catches most issues before they compound.
If you work through this checklist and still can't explain why your rankings aren't moving, the issue is usually one of three things: competitive keyword difficulty (you're targeting terms that require more authority than your site currently has), content quality (the pages that should rank aren't good enough yet), or backlink gaps (competitors have significantly more authoritative links). A technical audit gets the foundation right — but it's the starting point, not the complete picture.
Want someone to run this audit for you?
Book a free strategy call. I'll walk through your site's technical health, identify the highest-priority issues, and give you a specific action list — no agency fluff, no upsell pressure.