Technical SEO Checklist for Small Business Websites

Technical SEO is the foundation everything else stands on. You can write excellent content and earn great reviews, but if Google can’t crawl your pages, indexes the wrong versions, or finds a slow and broken site, that work won’t deliver what it should.

The word “technical” puts many business owners off, but most of the checks are straightforward. You don’t need to fix everything yourself; you just need to know what to look for and what to ask your developer.

This checklist covers the technical issues we find most often on small and mid-sized business websites, roughly in order of importance, with free tools to check each one.

The free tools you’ll need

• Google Search Console: shows how Google sees your site, which pages are indexed and what errors it finds. Our Search Console guide explains the key reports.
• PageSpeed Insights: speed and Core Web Vitals for any page.
• A crawler: Screaming Frog SEO Spider’s free version crawls up to 500 URLs and shows titles, status codes, redirects and more.
• Google’s Rich Results Test: checks structured data.
• Your own phone: still the best test of what visitors experience.

1. Can Google crawl your site?

Google discovers pages by following links and reading your sitemap. Check:

• robots.txt (at yoursite.com/robots.txt) isn’t blocking important sections. A single line like Disallow: / blocks the whole site — a common leftover from development.
• XML sitemap exists, lists your important pages, excludes redirected or noindexed pages, and is submitted in Search Console.
• Internal links reach every important page. Pages with no links pointing to them — “orphan pages” — are hard for Google to find and value.
• Navigation is made of real links, not only JavaScript actions that crawlers may not follow.

2. Are the right pages indexed?

In Search Console’s Pages report, check that your key service, product and article pages are indexed. Then look for problems in the other direction — pages that shouldn’t be in Google:

• Thank-you pages, internal search results and login pages
• Thin tag and archive pages generated automatically by your CMS
• Staging or test copies of the site
• Old, outdated pages with no value

Use a noindex tag for pages that should stay out of search results. Search site:yourdomain.com on Google to get a rough picture of what’s indexed.

3. One version of every page

The same page can often be reached at several addresses: with and without www, with http and https, with and without a trailing slash, or with tracking parameters added. Google may treat these as duplicates and split signals between them.

• Pick one preferred version of your domain and permanently redirect (301) all others to it.
• Make sure every page has a canonical tag pointing to its preferred URL.
• Check product variations, filters and sorting options don’t create thousands of near-identical URLs.

4. HTTPS everywhere

Your whole site should load over HTTPS with a valid certificate. Check that HTTP addresses redirect to HTTPS, that the certificate renews automatically, and that pages don’t load images or scripts over plain HTTP, which triggers “not secure” warnings.

5. Broken links and redirects

Crawl your site and look at status codes:

• 404 errors on internal links: update the links or redirect the missing pages.
• Redirect chains where one redirect leads to another: link directly to the final URL.
• Temporary (302) redirects used for permanent moves: change them to 301s.
• Soft 404s: pages that say “not found” but return a normal status code, which confuses search engines.

6. Titles, descriptions and headings

• Every page has a unique, descriptive title, ideally under about 60 characters
• Meta descriptions summarise the page and encourage clicks
• Each page has one H1 that describes its main topic
• No duplicate titles across many pages, a common CMS problem

A crawler lists all titles and descriptions in one table, making duplicates and missing ones easy to spot.

7. Speed and mobile experience

Google indexes the mobile version of your site, so the mobile experience is what counts. Check that content, links and structured data are the same on mobile as on desktop, text is readable without zooming, and buttons are easy to tap.

For speed, check Core Web Vitals in Search Console and PageSpeed Insights. Our guide on why websites are slow on mobile covers the usual fixes: images, plugins, caching and hosting.

8. Structured data

Structured data (schema markup) describes your business, products, articles and other content in a format search engines read easily. At minimum, most businesses benefit from Organization or LocalBusiness markup, breadcrumbs, and Product markup for stores. Our schema markup guide explains what to add and what to avoid.

9. JavaScript-heavy sites

Websites built entirely with JavaScript frameworks sometimes show content only after scripts run. Google can render JavaScript, but it can be slower and less reliable, and other search engines and AI tools may see less. Use Search Console’s URL Inspection to view the rendered page, and confirm the important text and links are present. Server-side rendering or static generation avoids most of these problems.

10. Images

• Descriptive file names and alt text
• Compressed, correctly sized images in modern formats
• Width and height set to prevent layout shifts
• Important images loaded as normal images rather than only as CSS backgrounds

11. Site structure and internal linking

How pages link to each other tells Google which pages matter most and how topics relate. A clear structure also helps visitors find what they need.

• Keep important pages close to the homepage. Key services and categories should be reachable within two or three clicks.
• Link related pages to each other. A blog post about a topic should link to the matching service page, and the service page can link back to helpful guides.
• Use descriptive anchor text. “Our website maintenance plans” tells Google more than “click here”.
• Use breadcrumbs on deeper pages to show their place in the structure.
• Avoid huge, flat menus that link to everything equally; prioritise.

12. Language and location signals

If your site has versions for different languages or countries, use hreflang tags so Google shows the right version to the right people, and give each version its own URL. If you only serve India, make sure your contact details, currency and content make that clear. Our guide to Hindi and English websites covers language setup.

13. Check after every major change

Many technical problems are introduced by accident: a plugin update that changes URLs, a new theme that removes structured data, a developer who forgets to remove a noindex tag after launch. After any significant change, recrawl the site, check that key pages are still indexable, test forms and tracking, and watch Search Console for new errors over the following weeks. A ten-minute check can save months of lost traffic.

How to prioritise what you find

A first audit can produce a long list of issues. Not all are equally important. A sensible order is:

1. Anything blocking indexing of important pages: robots.txt mistakes, accidental noindex tags, broken canonical tags.
2. Security and HTTPS problems.
3. Broken pages and redirects affecting pages with traffic or links.
4. Duplicate content on a large scale.
5. Speed and mobile issues on key templates.
6. Titles, descriptions and structured data.
7. Minor warnings from tools, which often matter little.

Fixing the top three categories often produces visible improvements faster than working through hundreds of minor warnings.

How often to check

Run a full crawl and review this checklist every three to six months, and after any redesign, migration or major plugin change. Check Search Console monthly for new errors.

If you’d like a professional technical audit, contact us. We’ll crawl your site, prioritise every issue by impact and explain the fixes in plain language, so your developer — or our team — can work through them.