SEO

A technical SEO checklist for business websites

Content cannot outrun a broken foundation. Before commissioning more articles or building links, it is worth confirming that search engines can reach, understand and trust your existing pages. This checklist covers the technical basics in the order we usually review them.

1. Can search engines reach your pages?

Start with access. If a page cannot be crawled, nothing else about it matters.

  • robots.txt does not block important sections or resources such as CSS and JavaScript
  • No stray noindex tags left over from a staging site or redesign
  • An XML sitemap exists, lists only canonical indexable URLs and is submitted in Search Console
  • Important pages are reachable through normal internal links, not only through search boxes or scripts
  • Server responses are healthy — no long chains of redirects, no frequent 5xx errors

2. Is the right version of each page indexed?

Sites often expose the same content at several URLs: with and without www, with and without a trailing slash, with tracking parameters, over HTTP and HTTPS. Search engines have to guess which is the real one.

  • One canonical version of the site, with all others redirecting permanently (301)
  • A self-referencing canonical tag on each page
  • Parameterised and filter URLs handled deliberately, not left to multiply
  • Thin or duplicate pages consolidated or removed from the index
  • Search Console indexing report reviewed for “discovered — not indexed” and excluded pages

3. Is the site fast where it matters?

Google evaluates real-user performance through Core Web Vitals: loading (LCP), layout stability (CLS) and responsiveness (INP). Test on a mid-range phone on mobile data, not on a developer machine.

  • Hero image optimised, correctly sized and not lazy-loaded above the fold
  • Images in WebP or AVIF with width and height set to prevent layout shift
  • Fonts self-hosted and loaded with a sensible display strategy
  • Third-party scripts audited and deferred or removed where possible
  • JavaScript payload kept small, with code split by page
  • Compression and long-lived caching enabled for static assets

4. Is each page clear about what it is for?

Every indexable page needs a unique purpose that a search engine — and a person — can grasp in seconds.

  • A unique, descriptive title tag and meta description on every page
  • Exactly one H1 that states the page’s subject, with a logical H2 and H3 hierarchy beneath it
  • Descriptive URLs that are short, lowercase and stable
  • Descriptive alt text on meaningful images (and empty alt on purely decorative ones)
  • Breadcrumbs that reflect the site structure

5. Is it usable on mobile?

Google indexes the mobile version first. A page that hides content on mobile, or has tap targets too small to use, is being judged on that experience.

  • Responsive layout with no horizontal scrolling at 320px width
  • Content parity between mobile and desktop versions
  • Tap targets large enough and spaced apart
  • Readable text without zooming

6. Is structured data present and accurate?

Schema markup helps search engines and answer engines understand entities and page types. It must match what is visible on the page — inaccurate markup is worse than none.

  • Organization and WebSite markup on the site, LocalBusiness where a real location exists
  • Service, Product or SoftwareApplication markup on the relevant pages
  • Article markup on blog posts, with real author and dates
  • FAQPage markup only for FAQs actually shown on the page
  • BreadcrumbList markup matching the visible breadcrumbs
  • Validated with a structured data testing tool

7. Does internal linking reflect what matters?

Internal links tell search engines which pages are important and how topics relate. Pages that generate enquiries should not sit five clicks deep with a single link to them.

  • Important service and product pages linked from the main navigation and from relevant content
  • Descriptive anchor text rather than “click here”
  • No orphan pages with zero internal links
  • Related content linked contextually within articles
  • Broken internal links fixed

8. Security and housekeeping

HTTPS everywhere, with valid certificates and no mixed content, is a baseline expectation. Custom 404 pages should return a genuine 404 status and help visitors move on.

  • HTTPS enforced sitewide with HSTS where appropriate
  • No mixed content warnings
  • A helpful 404 page that returns a 404 status code
  • Removed or changed URLs redirected, not left to error

How to prioritise

Fix access and indexation problems first, because they block everything. Then address speed and mobile experience, then structure and markup, then internal linking. Content improvements come last — not because they matter least, but because they work best on a sound foundation.

Frequently asked questions

How often should a technical SEO audit be done?

A full audit annually and after any redesign, migration or platform change, with lighter monthly checks of Search Console for new errors.

Do I need structured data on every page?

No. Use it where it accurately describes the page: organisation and website markup sitewide, and specific types for services, products, articles and FAQs.

What is the single most common technical problem?

Slow, heavy pages — especially oversized hero images and excessive third-party scripts — followed by duplicate URLs with no clear canonical.

Can I do this myself?

Much of it, yes, using Search Console and Lighthouse. Implementation is where it usually stalls, which is why we do it for clients rather than only reporting on it.

Next step

Want us to run this against your site? See our SEO services or request a technical review.

Keep reading

Related articles

Next step

Want this applied to your business?

Reading about it is one thing. If you want to know what it would take in your specific situation, send us a short brief.

Start Your Project WhatsApp