A Technical SEO Checklist for Small Business Websites

By Michael Mitov. Published October 5, 2026.

Technical SEO decides whether search engines can find, render and understand your pages. You can write the best page on the internet, but if it is blocked, duplicated, buried or painfully slow, it will struggle to rank. This checklist covers the technical foundations in priority order. Work from the top down; the early items cause the biggest problems when they go wrong.

You will need two free tools: Google Search Console for your site and PageSpeed Insights. A crawler such as Screaming Frog (free up to 500 URLs) makes several steps much faster.

1. Can Google reach your pages?

• Robots.txt does not block important content. Visit yourdomain.com/robots.txt. A line reading Disallow: / blocks the entire site and is surprisingly common after a launch.
• No stray noindex tags. Check that key pages are not set to “noindex”. WordPress has a site-wide “Discourage search engines” setting that is sometimes left on after development.
• An XML sitemap exists and is submitted. It should list only pages you want indexed and be submitted in Search Console.
• Important pages return a 200 status. Not redirects, not errors.

2. Are the right pages indexed?

• Review the Pages report in Search Console. Look for important URLs under “Crawled, currently not indexed” or “Discovered, currently not indexed”.
• Search site:yourdomain.com. Unexpected results, such as tag pages, test pages or spam, need attention.
• One version of the site. http and https, www and non-www should all redirect to a single version.
• Canonical tags point to the right URL. Each page should name itself (or its preferred duplicate) as canonical.

3. Is the structure clear?

• Important pages are within three clicks of the homepage. Deeply buried pages are crawled less and rank worse.
• Every page has internal links pointing to it. Pages with no internal links (orphans) are hard for search engines to find.
• URLs are short and descriptive. /website-maintenance beats /?page_id=482.
• Breadcrumbs help both visitors and search engines understand hierarchy.
• No keyword cannibalisation. Two pages targeting the same search compete with each other. Merge or differentiate them.

4. Is it fast enough?

Google’s Core Web Vitals measure real visitor experience. The “good” thresholds are:

Source: Google Search Central and web.dev Core Web Vitals documentation.

• Check the Core Web Vitals report in Search Console for mobile and desktop.
• Compress and resize images. Use WebP or AVIF, at the size they are displayed.
• Remove unused scripts and styles, especially from page builders, sliders and chat widgets.
• Limit web fonts to two families and self-host them.
• Use caching and a CDN. And make sure hosting is not the bottleneck.

5. Does it work on a phone?

• Text is readable without zooming and buttons are large enough to tap.
• Nothing important is hidden on mobile. Google indexes the mobile version of your site.
• Pop-ups do not cover the content as soon as the page loads.

6. Can search engines understand it?

• One H1 per page that describes the page, with logical H2 and H3 headings below.
• Unique title tags and meta descriptions for every important page.
• Structured data (schema) for your business, services or products, articles, FAQs and breadcrumbs. Test it with Google’s Rich Results Test.
• Descriptive image alt text on meaningful images.
• Content is in the HTML. If important text only appears after JavaScript runs, check with the URL Inspection tool that Google sees it.

7. Are redirects and errors under control?

• No redirect chains. A should redirect to C directly, not via B.
• Old URLs from previous versions of the site redirect to their closest new equivalent with a 301.
• Broken internal links fixed and a helpful custom 404 page in place.

8. Is it secure?

• HTTPS everywhere, with no mixed-content warnings.
• No security issues reported in Search Console.
• Software is up to date. Hacked sites lose rankings fast. See the website security checklist.

9. Keep it healthy

Technical SEO is not a one-off job. Plugins add pages, redesigns change URLs and content grows. Re-run this checklist after any redesign, migration or major plugin change, and at least once a year. Turn on Search Console email alerts so you hear about indexing or security problems as they happen.

If you get stuck on any item, especially canonicals, JavaScript rendering, redirects or Core Web Vitals, those are exactly the problems a developer-led technical SEO service is for.

Sources

• Google Search Central: Core Web Vitals and Google Search results
• web.dev: Web Vitals
• Google Search Central: Build and submit a sitemap