Technical SEO checklist for a business website

Technical SEO covers everything that allows a search engine to find, understand and efficiently display your website, regardless of how good the copy is. You can have the best service descriptions in your industry, but if robots.txt blocks your services folder and old URLs return 404 errors, Google won't show them. This technical SEO checklist is ordered by priority: from issues that can wipe out visibility entirely to those that give you an edge over competitors.

Key takeaways

• A page Google cannot index will get no search traffic regardless of content quality, so indexing is always checked first.
• Every piece of content should have one canonical URL, with all other URL variants redirecting to it with a 301.
• Good Core Web Vitals thresholds are LCP within 2.5 s, INP within 200 ms and CLS below 0.1.
• Server-side rendering (SSR) makes content visible in the HTML without executing JavaScript.
• Google Search Console is the essential free tool for monitoring indexing and technical errors.

1. Indexing: can Google see the site at all?

Indexing is the process by which Google stores a page in its index so that it can appear in search results. Start here, because a mistake in this area cancels out every other effort.

• robots.txt doesn't block important sections. robots.txt is a file that tells crawlers which parts of a site they may visit. A classic mistake is a leftover Disallow: / from the staging version.
• Meta robots on important pages doesn't contain noindex.
• The XML sitemap exists, is up to date, lists only URLs that return 200 and is submitted in Google Search Console.
• The staging site is excluded from indexing so it doesn't compete with the live site.
• The page indexing report in Search Console shows no unexpected exclusions of important pages.

2. URLs and duplicate content

The same content available at several addresses dilutes ranking signals. Check that:

• the site runs on HTTPS only, and HTTP redirects to HTTPS,
• one domain version (with or without www) is chosen and the other redirects to it,
• the trailing slash rule is consistent: /services/ or /services, not both,
• every page has a correct canonical tag pointing to itself or to the primary version,
• URLs are short, readable and made of words, not IDs like ?p=123.

3. Redirects and 404 errors

A 301 redirect is a permanent move of an address that sends users and most SEO signals to the new URL. Checklist:

• every change to a page URL has a 301 redirect from the old address,
• there are no redirect chains (A → B → C); each redirect goes straight to its destination,
• internal links point to final URLs, not to redirects,
• the 404 page is helpful, with search or links to key sections, and returns a real 404 status,
• after a redesign, you check Search Console for new 404s on URLs that used to get traffic.

4. Rendering and content accessibility

Google can execute JavaScript, but it does so with a delay and not always completely. The safest setup is one where key content, headings, links and meta tags are present in the HTML returned by the server. A simple test: open "view source" (not developer tools) and check whether you can see your service copy. If the source is nearly empty, the page is rendered in the browser and it's worth considering SSR or static generation.

5. Technical SEO and speed: Core Web Vitals

Core Web Vitals are a set of three Google metrics describing the user experience of a page:

The most common quick wins on business websites:

• compressed images in modern formats such as WebP,
• explicit dimensions for images and embeds so the layout doesn't jump,
• lazy loading for images below the fold, but never for the hero image,
• an audit of tracking scripts and third-party widgets, because every extra script has a cost,
• serving the site from a CDN, close to users.

6. Site structure and internal linking

• Every important page is reachable within three clicks of the home page.
• Each page has exactly one H1, and lower heading levels form a logical hierarchy.
• Breadcrumbs help users and crawlers understand the site structure.
• There are no orphan pages that no internal link points to.
• Link text describes the destination, e.g. "garden design in Leeds", not "click here".

7. Meta tags and structured data

• Every page has a unique meta title (roughly up to 60 characters) and meta description (about 140 to 160 characters).
• Structured data is schema.org markup that tells search engines what a piece of content is. On a business website, start with Organization or LocalBusiness and BreadcrumbList.
• Validate structured data with Google's Rich Results Test.
• Open Graph tags control how a link looks when shared on social media.

8. Language versions and mobile

If the site has several languages, each needs its own URL, its own meta tags and correct hreflang annotations. That deserves a guide of its own, so just one tip here: don't redirect automatically by IP address. For mobile, check that content on phones matches desktop, buttons are comfortably sized and text doesn't require zooming.

9. Monitoring: technical SEO is a process, not a one-off audit

• Review the indexing and Core Web Vitals reports in Google Search Console once a month.
• After every significant change to the site, check for new 404s and exclusions.
• Once a quarter, crawl the site with an SEO crawler to catch redirect chains, missing meta tags and duplicate titles.

Frequently asked questions

Where should I start with technical SEO for a business website?

Start technical SEO by checking indexing: robots.txt, noindex tags and a sitemap submitted in Google Search Console. Only once Google can see all your important pages is it worth optimising speed and structured data.

How often should I run a technical SEO audit?

Run a full technical SEO audit once or twice a year, and always after a redesign or a platform change. Between audits, a monthly review of the Google Search Console reports is enough.

Does technical SEO affect Google rankings?

Yes, technical SEO affects rankings both directly and indirectly, because it governs indexing, speed and how correctly content is interpreted. It won't replace good content, but it lets that content perform fully.

Does a small business website need technical SEO?

Yes, even a small business website needs technical SEO basics, because a single mistake such as a robots.txt block can hide it from Google entirely. With a dozen or so pages, working through the whole checklist usually takes a few hours.

What tools do I need for technical SEO?

For technical SEO basics, Google's free tools are enough: Search Console, PageSpeed Insights and the Rich Results Test. Larger sites also benefit from an SEO crawler that detects issues across all pages at once.

How LessCMS helps with technical SEO

LessCMS handles many items on this checklist out of the box, with no plugins:

• Pages are server-side rendered (SSR) and served from a CDN, and images are automatically converted to WebP.
• The sitemap and robots.txt are generated automatically, and meta titles and descriptions are set per page, entry and language.
• 301 redirects are added in the panel or imported from CSV, and changing a slug automatically creates a redirect from the old URL.

If SEO is your job, see LessCMS for SEO specialists, or go straight to pricing and sign up without a card.