Technical SEO Checklist for Small Business Websites (2026)

TL;DR: Technical SEO makes sure search engines and AI assistants can find, crawl, render and understand your website. For a small business in 2026, the essentials are: Google Search Console and Bing Webmaster Tools set up, a clean XML sitemap and robots.txt, HTTPS, a fast mobile site that passes Core Web Vitals, one canonical URL per page, unique titles and meta descriptions, structured data, working redirects and no broken links. Most of this can be checked in an afternoon with free tools.

What is technical SEO, and why does it matter for a small business?

Technical SEO is everything about your site's setup that affects whether search engines can access and index it. Great content does not rank if Google cannot crawl it, and it will not be cited by ChatGPT or Perplexity if their search bots are blocked.

Many sites still miss the basics. The 2025 Web Almanac SEO chapter from HTTP Archive, which analyzes millions of websites, found that on mobile:

• Only 48% of sites had good Core Web Vitals
• 67% had a canonical tag
• 67.2% had a meta description
• 84.9% returned their robots.txt file successfully

Fixing these puts a small business ahead of a large share of the web.

The checklist at a glance

A desktop crawler such as Screaming Frog SEO Spider (free up to 500 URLs) covers most of the "site crawler" checks for a small site.

Is your site set up in Google Search Console and Bing Webmaster Tools?

• Verify your domain in Google Search Console. Use a domain property so it covers http, https, www and non-www versions.
• Verify in Bing Webmaster Tools. You can import directly from Search Console. Bing powers Microsoft Copilot, and its AI Performance report shows how often your pages are cited in AI answers.
• Use Search Console's generative AI performance report to see how often your pages are shown in Google AI Overviews and AI Mode. It shows impressions by page, country and device.
• Check both every month for crawl errors, security issues and manual actions.
• From our own setup: Bing let us import our verified site straight from Search Console, and it discovered all 17 URLs in our sitemap the day we submitted it.

Is your XML sitemap clean and submitted?

• Your sitemap should list only pages you want indexed: live, canonical URLs that return a 200 status.
• Remove redirected, noindexed and deleted pages.
• Google's limits are "50MB (uncompressed) or 50,000 URLs" per sitemap, according to its sitemap documentation. Small sites will not get close.
• Google ignores the priority and changefreq fields. It uses lastmod only if it is consistently and verifiably accurate, so do not update it for trivial changes.
• Submit the sitemap in both Search Console and Bing Webmaster Tools, and reference it in robots.txt.

Does your robots.txt let the right bots in?

Your robots.txt file tells crawlers what they may access. A single wrong line can hide your whole site.

• Make sure it does not contain Disallow: / for all user agents after launch. Staging settings left on by mistake are a common cause of sites vanishing from Google.
• Do not block CSS or JavaScript files that pages need to render.
• Allow AI search bots such as OAI-SearchBot (ChatGPT search) and PerplexityBot if you want to be cited in AI answers. Training bots such as GPTBot are a separate choice. Our guide to getting recommended by ChatGPT, Perplexity and Google AI Overviews has the full table.
• Check your CDN or firewall too. Some block AI bots by default regardless of robots.txt.

Remember that robots.txt controls crawling, not indexing. To keep a page out of Google, use a noindex tag and let Google crawl it.

Are your important pages actually indexed?

• Open the Pages report in Search Console and review every reason listed under "not indexed".
• Use URL Inspection on your home page and main service pages. Confirm the Google-selected canonical matches yours.
• Look for accidental noindex tags, especially after a redesign or platform move.
• Thin or near-duplicate pages, such as many location pages with the same text, are often crawled but not indexed. Merge or improve them.
• After a platform move, expect old URLs in the "not indexed" list for a while. When we rebuilt our own site in Webflow, Search Console kept listing a dozen leftover WordPress URLs, such as author pages, date archives and /wp-json/. That is normal: as long as the pages that matter are live at their new addresses, they drop out on their own.

Is your site secure and on one domain?

• Every page should load over HTTPS with a valid certificate.
• Pick one version (for example, https://www.example.com) and 301 redirect all others to it in a single hop.
• Check for mixed content warnings, where an HTTPS page loads images or scripts over HTTP.

Does your site work well on mobile?

Google now crawls and indexes the mobile version of websites. It announced in October 2023 that the move to mobile-first indexing was complete, as reported by Search Engine Journal. That means:

• The mobile version must contain the same content, headings, links and structured data as desktop.
• Text must be readable without zooming, and buttons must be easy to tap.
• Pop-ups must not cover the main content on arrival.

Does your site pass Core Web Vitals?

Core Web Vitals measure real users' experience of loading, responsiveness and visual stability. Google is clear about their role: "Core Web Vitals are used by our ranking systems," according to its page experience guidance, which also states:

"Google's core ranking systems look to reward content that provides a good page experience."

The "good" thresholds, measured at the 75th percentile of real visits, are set out on web.dev:

Check your scores in PageSpeed Insights and the Core Web Vitals report in Search Console. Focus on the field data from real users, not only the lab score.

Are your canonical tags, titles and meta descriptions in order?

• Every indexable page should have a self-referencing canonical tag, unless it is a deliberate duplicate.
• Each page needs a unique title tag with the main topic near the start. Google sets no length limit, but it cuts long titles to fit the screen, so keep the important words in roughly the first 60 characters.
• Write a unique meta description that genuinely summarizes the page and answers "why click this?". There is no official length, though around 150 characters usually displays in full. Google often writes its own snippet from your page text, so clear answer sentences in the body matter too.
• Use one H1 per page and a logical H2 and H3 structure. Phrasing H2s as questions can help both search snippets and AI answers.

Is your structured data valid and accurate?

• Add Organization (or LocalBusiness) markup on the home page with your name, logo, URL, contact details and social profiles.
• Add BreadcrumbList for site structure, Article or BlogPosting for posts, and Product or Service where relevant.
• Test with Google's Rich Results Test and the Schema Markup Validator.
• Make sure the markup matches the visible text on the page. Google's AI features guidance lists this as a best practice.

Structured data does not need special AI versions. Google says there is "no special schema.org structured data that you need to add" for its AI features.

One change to know about: Google stopped showing FAQ rich results for every site from 7 May 2026, according to its Search Central updates log, and HowTo rich results were dropped earlier. FAQ sections are still worth having for readers and AI answers, but do not add FAQ markup expecting extra space in search results.

Have you fixed redirects, broken links and orphan pages?

• Run a crawl and fix internal links that point to 404 pages or redirects.
• Avoid redirect chains. Each old URL should redirect straight to its final destination.
• Find orphan pages, which no other page links to, and link to them from relevant content.
• After any redesign, map every old URL to a new one with 301 redirects. If you are weighing a platform change, our Webflow vs WordPress comparison covers what to plan for.

Are your images optimized?

• Serve images at the size they are displayed, in WebP or AVIF where possible.
• Lazy-load images below the fold, but never the main hero image.
• Write descriptive alt text for meaningful images. It helps accessibility and image search.
• Use descriptive file names, such as webflow-website-redesign-example.webp.

Should you add an llms.txt file?

It is optional. The 2025 Web Almanac found llms.txt on just 2.1% of mobile sites, and Google says you do not need AI text files to appear in its AI features. Its July 2026 guide to optimizing for generative AI goes further: Google Search itself does not use llms.txt. Add one if your platform makes it easy, but finish the checklist above first.

How often should you run this checklist?

• Monthly: Search Console and Bing Webmaster Tools reports, Core Web Vitals, new 404s.
• Quarterly: full site crawl, structured data tests, robots.txt and sitemap review.
• Every launch or redesign: the whole list, before and after go-live.

How Nimbus can help

Nimbus Web Solutions runs technical SEO audits and fixes for small and mid-sized business websites in the US, UK and Europe, on Webflow, WordPress and custom builds. We give you a prioritized list in plain English, fix the issues, and set your site up for both search engines and AI assistants. See our SEO services or ask for an audit.

Sources

• HTTP Archive, Web Almanac 2025: SEO
• Google Search Central, Understanding page experience in Google Search results
• web.dev, Web Vitals
• Google Search Central, Build and submit a sitemap
• Google Search Central, AI features and your website
• Search Engine Journal, Google completes switch to mobile-first indexing, October 2023
• Microsoft Bing, Introducing AI Performance in Bing Webmaster Tools, February 2026
• Google Search Central, Optimizing for generative AI features on Google Search, July 2026
• Google Search Console Help, Generative AI performance report
• Google Search Central, Search Central updates log