Technical SEO Checklist: 42 Checks for Small Sites

You’ve written good content, your service pages look great and you’ve built a few links. But some pages still don’t show up on Google, rankings slip for no clear reason or Search Console is full of warnings you don’t understand.

That’s usually a technical problem. This technical SEO checklist covers what I check first on small and mid-sized business websites: crawling, indexing, speed, mobile, structure and structured data, in plain language you can act on.

Quick answer: A technical SEO checklist makes sure Google can crawl, index and understand your site. Check robots.txt, your XML sitemap and noindex tags, fix redirects and broken links, use HTTPS, set canonical URLs, pass Core Web Vitals, make pages work well on mobile, add structured data and monitor Search Console regularly.

What Technical SEO Covers

Technical SEO is everything that helps search engines access and understand your pages, separate from the words on the page and the links pointing to it. Think of it as the foundation. Great content on a site Google can’t crawl properly won’t rank.

For most small business sites, a handful of issues cause most of the damage: blocked or noindexed pages, messy redirects, slow mobile pages and duplicate URLs. The checklist below is ordered roughly by how often I find each problem.

1. Crawling

Google has to reach your pages before it can rank them.

• Robots.txt loads at yoursite.com/robots.txt and doesn’t block important pages or folders
• CSS and JavaScript files aren’t blocked
• Every important page is linked from at least one other page
• Main navigation uses normal HTML links, not only JavaScript clicks
• No long redirect chains (A to B to C)
• No internal links pointing to 404 pages or redirected URLs
• Server errors (5xx) are rare in Search Console’s Crawl Stats

One common mix-up: Google’s robots.txt guide says robots.txt is not a mechanism for keeping a web page out of Google. To keep a page out, use noindex or password protection.

2. Indexing

Crawled doesn’t mean indexed. Check that the right pages are in Google and the wrong ones aren’t.

• Search Console’s Page indexing report shows your key pages as indexed
• No important pages have a noindex tag by mistake
• Thin or useless pages (tag archives, test pages, old demo content) are noindexed or removed
• Each page has a self-referencing canonical tag, or a canonical to the preferred version
• Only one version of the site is live: https and either www or non-www, with the others redirecting
• Filtered or parameter URLs don’t create hundreds of duplicate pages

If pages sit in “Discovered, currently not indexed,” my guide on fixing Discovered – currently not indexed explains the usual causes.

3. XML Sitemap

A sitemap tells Google which pages you care about.

• An XML sitemap exists and is submitted in Search Console
• It lists only indexable, canonical URLs that return 200
• It updates automatically when you publish or remove pages
• Lastmod dates are accurate, or left out

Google’s sitemap documentation says a single sitemap is limited to 50MB uncompressed or 50,000 URLs. It also says Google ignores the priority and changefreq values, so don’t spend time tuning them.

4. Site Speed and Core Web Vitals

Speed affects both rankings and leads. Google’s Core Web Vitals targets, measured at the 75th percentile of page loads, are:

• Core Web Vitals report in Search Console shows “Good” URLs on mobile
• Images are compressed, correctly sized and served as WebP or AVIF
• The main hero image isn’t lazy-loaded
• Unused plugins, scripts and fonts are removed
• Caching and a CDN are set up
• Image and video sizes are set to avoid layout shifts

If INP is your weak spot, my guide on how to improve INP score walks through the fixes.

5. Mobile Experience

Google mainly uses the mobile version of your site for indexing and ranking, so mobile problems are ranking problems.

• The same main content appears on mobile and desktop
• Text is readable without zooming
• Buttons and links are easy to tap
• No pop-ups cover the main content on mobile
• Phone numbers are clickable

6. Site Structure and URLs

A clear structure helps both users and search engines.

• URLs are short, readable and use hyphens
• Important pages are within three clicks of the home page
• Each service and location has its own page
• Breadcrumbs are used on deeper pages
• Old URLs that changed have 301 redirects

Planning a new site? My website redesign checklist and website migration SEO checklist cover redirects in detail.

7. On-Page Technical Elements

These live in the code of every page.

• Every page has a unique title tag and meta description
• Each page has one clear H1
• Images have descriptive alt text
• The site uses HTTPS with no mixed-content warnings
• The html lang attribute is set correctly

8. Structured Data

Structured data helps Google understand who you are and what’s on the page.

• LocalBusiness or Organization schema on the home or contact page
• Article or BlogPosting schema on blog posts
• Breadcrumb schema if you use breadcrumbs
• No errors in Google’s Rich Results Test

For service businesses, see my guide to schema markup for local business.

How Often to Run This Technical SEO Checklist

Run the full technical SEO checklist once when you start, then after any redesign, migration, theme change or plugin update that affects templates. Between those, a monthly 15-minute check in Search Console catches most new problems: indexing drops, Core Web Vitals warnings and crawl errors.

Frequently Asked Questions

What is included in a technical SEO checklist?

A technical SEO checklist covers crawling, indexing, XML sitemaps, site speed and Core Web Vitals, mobile experience, site structure and URLs, redirects, HTTPS, canonical tags, on-page code like titles and headings, and structured data. The goal is to make sure Google can find, understand and rank your important pages.

How often should I do a technical SEO audit?

Do a full audit when you start working on SEO, then after any major change like a redesign, migration or new theme. For most small business sites, a quick monthly check in Search Console is enough between full audits. Larger sites that publish often may need a deeper review every quarter.

Can I do technical SEO myself?

Many checks are simple, like reviewing Search Console, checking robots.txt, submitting a sitemap and fixing broken links. Speed optimization, redirect mapping and structured data can need developer skills. Start with Search Console reports and fix the clear errors first, then get help for anything that touches code or server settings.

What tools do I need for technical SEO?

Google Search Console and PageSpeed Insights are free and cover the most important checks. A crawler like Screaming Frog, free for up to 500 URLs, helps find broken links, redirects and missing tags. Google’s Rich Results Test checks structured data. You don’t need expensive tools to start.

Does technical SEO matter for small websites?

Yes. Small sites have fewer pages, so a single noindexed service page or broken redirect can cost a big share of your traffic and leads. The good news is that small sites are faster to audit and fix, often in a few hours.

Final Thoughts

Technical SEO isn’t glamorous, but it decides whether your content gets a fair chance to rank. Work through this technical SEO checklist, fix the biggest problems first and keep an eye on Search Console every month.

If you’d prefer an expert to do it, my SEO audit and technical SEO service covers every check here with a prioritized fix list, or you can send me a message for a quick review.