Technical SEO basics UK businesses actually need

Why technical SEO comes first

If Google can't reach a page, or has been told not to index it, nothing else you do on that page matters. Technical SEO is about removing those blocks. For a small business site with a few dozen pages, it's usually a short job. The trouble is that it's easy to break things during a redesign or a plugin update and not notice for months.

The five things that matter most

1. Google can crawl your pages

Crawling means Google's bots can fetch your pages by following links. Two common problems stop it.

• A blocking robots.txt file. Sites in development are often set to block all bots, and that setting sometimes survives launch. Check yours by visiting your domain followed by /robots.txt. Google's robots.txt introduction explains what the rules mean.
• Pages with no links to them. If a page is only reachable through a search box or a form, Google may never find it.

2. Google is allowed to index them

A "noindex" tag tells Google to keep a page out of results. It's useful for thank-you pages and admin areas, and a disaster on your main service pages. Many website builders have a "hide from search engines" tick box. Make sure it's off for pages you want found.

Search Console's Page indexing report shows which pages are indexed and why others aren't.

3. One address per page

The same page can often be reached several ways: with and without "www", with and without a trailing slash, over http and https. Pick one version and redirect the others to it. Google's guide to consolidating duplicate URLs covers the options, including canonical tags.

4. HTTPS everywhere

Every page should load over HTTPS with a valid certificate. Most hosts provide one free. Browsers mark plain http pages as "not secure", which puts people off filling in your enquiry form.

5. It works well on a phone

Google uses the mobile version of your site for indexing, as its mobile-first indexing guidance explains. If your mobile layout hides content or drops sections, Google may not see them either.

Helpful extras

These are worth doing once the basics are solid.

• An XML sitemap. A list of the pages you want indexed, submitted in Search Console. Most platforms create one automatically. See Google's sitemaps overview.
• Reasonable speed. Compress images, avoid piling on plugins and choose decent hosting. Our Core Web Vitals guide goes into detail.
• Proper redirects. When you remove or rename a page, send visitors and Google to the closest replacement with a permanent redirect. Google's redirects documentation explains the types.
• A useful 404 page. When someone hits a dead link, help them find what they wanted rather than showing a blank error.
• Structured data where it fits. Marking up your business details or products can help search engines understand them. It isn't required to rank.

What you can usually ignore

Plenty of technical SEO advice is aimed at sites with millions of pages. For a small business, these rarely matter:

• Crawl budget. Google says it's mainly a concern for very large or fast-changing sites. Its crawl budget guide is written for sites with roughly a million or more unique pages, or ten thousand plus that change daily.
• Perfect audit scores. Tools flag hundreds of minor warnings. Many make no practical difference.
• Exotic markup. You don't need every schema type you've read about.

A real-world check you can run today

Pick your three most important pages and do this for each:

1. Search `site:` followed by the page's address. Does it appear? 2. Paste the address into Search Console's URL Inspection tool. Does it say the page is on Google? Is the canonical the one you'd expect? 3. Open the page on your phone over mobile data. Does it load in a reasonable time and show everything the desktop version shows? 4. Type the address with "http://" instead of "https://". Does it redirect to the secure version?

If all four pass, your technical basics for those pages are in decent shape.

When to get help

Get a second pair of eyes before a redesign, a platform change or a domain change. Those are the moments when technical problems most often appear, and they're far cheaper to prevent than to fix. Our migration checklist is a good starting point.

Also get help if Search Console shows a sudden drop in indexed pages, or a manual action or security issue message. Those need investigation rather than guesswork.

Keep an eye on it

Technical problems rarely announce themselves. A plugin update adds a noindex tag. A developer changes a URL. A certificate expires. A monthly look at Search Console's indexing and Core Web Vitals reports catches most of these before they cost you enquiries. Set a recurring reminder and keep a short note of anything that changes.