Skip to content

SEO

Technical SEO Checklist: 12 Checks for Any Website

Technical SEO makes sure Google can find, read and store your pages. This technical SEO checklist covers twelve checks you can run on any website, explained in plain language, with the usual fix for each.

4 min read
Technical SEO checklist by LogDart: checklist, code window and speed gauge

In short

  • If Google cannot index a page, nothing else you do for it matters.
  • Speed and mobile use affect both rankings and enquiries.
  • Fix problems in order of how many important pages they affect.
Contents

Content and links get most of the attention in SEO, but none of it helps if Google cannot find and read your pages. This technical SEO checklist covers twelve checks that apply to almost any website. You can run most of them with Google Search Console and a phone.

Can Google find and index your pages?

1. Search Console is set up. Verify your domain in Google Search Console. It is free and shows how Google sees your site.

2. Important pages are indexed. In the Pages report, check that your key pages are indexed. If a page is excluded, the report usually says why.

3. No stray noindex tags. A noindex tag left from development tells Google to keep a page out of results. Check your important pages for it.

4. Robots.txt is not blocking key pages. This file tells search engines where they may go. A wrong line can block whole sections.

5. An XML sitemap is submitted. Your sitemap lists the pages you want indexed. Submit it in Search Console and keep it up to date.

Do your pages load fast and work on phones?

6. Core Web Vitals pass. The Core Web Vitals report shows how fast and stable pages feel to real visitors. Slow loading is often caused by large images or heavy scripts. Our Core Web Vitals guide explains the fixes.

7. Pages work well on a phone. Text should be readable without zooming, buttons easy to tap and nothing wider than the screen. Test on a real phone over mobile data.

8. The site uses HTTPS. Every page should load over a secure connection, with the padlock showing. Old http addresses should redirect to https.

Is your site structure clear?

9. No broken links or redirect chains. Links to missing pages waste visits. Redirects that pass through several steps slow pages down. Fix links to point straight to the final page.

10. One address per page. The same page reachable at several addresses, such as with and without www, can confuse Google. Choose one version, redirect the others and use canonical tags where needed.

11. Clear internal links. Important pages should be linked from your menu, home page or related content, not buried several clicks deep.

Does Google understand what each page is?

12. Structured data where it fits. Structured data describes your business, articles, products or FAQs in a standard format. It helps search engines understand pages and can make results more informative.

How to prioritise fixes

Not every problem matters equally. Start with issues that affect many important pages, such as a template that adds noindex or slows every page. Then fix problems on your highest-value pages: services, products and contact. Leave small issues on old, low-value pages until last.

When to get help

Some fixes are quick settings. Others need a developer, especially speed improvements, redirects during a redesign and structured data. If your website is built on an older platform, some fixes may be easier on a rebuilt site.

Technical audits and fixes are the first part of our search engine optimisation service, and our developers make the changes rather than handing over a list. For more starting points, see our SEO tips.

How we handle this for clients

Our technical audits start in Search Console, because that shows what Google actually sees. We look for the template behind the biggest group of problems, since fixing one template can clear hundreds of pages at once.

Our developers then make the fixes, rather than handing the client a list. We re-check in Search Console after each change and report what moved, so the client sees the effect of the work.

Questions about technical SEO

What is technical SEO?

Technical SEO is the work that helps search engines find, read and store your pages: indexing, sitemaps, speed, mobile use, secure connections, redirects, site structure and structured data. It is the foundation that content and links build on.

How do I know if my site has technical SEO problems?

Set up Google Search Console and check the Pages, Core Web Vitals and Sitemaps reports. They show pages that are not indexed, speed problems and errors. Testing your site on a real phone also reveals many issues.

Does website speed affect SEO?

Yes, as one signal among many. Speed matters more for visitors: slow pages lose enquiries. Google uses real visitor data in its page experience signals, so improvements help both rankings and conversions.

Do I need a developer for technical SEO?

For some fixes, yes: speed improvements, redirects and structured data often need code changes. Others, such as submitting a sitemap or fixing a noindex setting in your CMS, you may be able to do yourself.

How often should I run a technical SEO check?

Check Search Console monthly for new errors, and run a fuller audit at least once a year and after any redesign, platform change or large batch of new pages.

Keep reading