Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Technical SEO: The Twelve Things Worth Checking
Web Development

Technical SEO: The Twelve Things Worth Checking

A prioritised technical checklist for business sites, from the things that break rankings outright to the ones that barely register.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Four things break rankings outright: blocked crawling, broken indexing directives, duplicate content without canonicals, and pages that fail on mobile. Everything else is optimisation. Check those four first, quarterly, and you avoid nearly every self-inflicted disaster.

Most technical SEO is triage, not optimisation

Technical SEO gets sold as a long list of improvements. In practice it is mostly about not being broken. A site that is crawlable, indexable, unique and usable on a phone has cleared the bar that most competitors trip over.

The list below is ordered by consequence. The first four can remove you from search results entirely. The rest are worth doing and will not save you if the first four are wrong.

Tier one: the four that break everything

  1. Crawlability. Check robots.txt does not block what you want indexed. A disallow line copied from staging is the most common catastrophic error in this field.
  2. Indexability. Check meta robots and headers on real pages, not in theory. A noindex left over from a rebuild is the second most common.
  3. Canonicalisation. One URL per piece of content. Watch for parameters, trailing slashes, http and https, and www and non-www all serving the same thing.
  4. Mobile usability. Indexing is mobile-first. If your mobile rendering hides content, that content is effectively gone.

Tier two: the ones with real but bounded impact

  • Site structure. Every important page reachable within three clicks of the homepage.
  • Internal linking. Genuinely the most underused lever most sites have — relevant links with descriptive text between related pages.
  • XML sitemap. Current, accurate, no 404s or redirects in it.
  • Page speed on real devices, particularly layout stability.
  • Structured data where it fits: organisation, article, FAQ, product. Correct, not decorative.

Tier three: worth doing, rarely decisive

Image alt text, heading hierarchy, breadcrumbs, hreflang for genuinely multilingual sites, and open graph tags for how links look when shared. All good practice. None will rescue a site with a tier-one problem, and none will make a thin page rank.

If someone proposes a six-month technical programme without having checked the four tier-one items in week one, ask why.

The audit rhythm that prevents surprises

Once a quarter, spend an hour: crawl the site, check index coverage, confirm robots directives, and compare landing-page traffic against the previous quarter to catch quiet declines.

After every deployment that touches templates, routing or hosting, check indexability. Most catastrophic SEO incidents are deployment accidents, not algorithm changes, and they are visible within a day if anyone looks.

What technical work cannot fix

A technically flawless site with nothing worth reading will not rank. If your pages do not answer the question better than the ones currently ranking, no amount of schema will change the outcome.

That is worth saying plainly because technical work is measurable and content work is not, which makes it tempting to keep doing the measurable thing long past the point of usefulness.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How often should we run a technical audit?

Quarterly for a stable site, and after any significant deployment or platform change. The quarterly one takes an hour if nothing is wrong, which is the point.

Does structured data improve rankings?

Not directly in most cases, but it can affect how your result is displayed, which affects clicks. FAQ and article markup are cheap and worth having; exotic markup for its own sake is not.

Should we worry about crawl budget?

Only if you have hundreds of thousands of pages. For a typical business site the concept is a distraction — your pages are being crawled adequately.

Our traffic dropped suddenly. Where do we look first?

Robots.txt, meta robots, and whether anything was deployed in the previous week. In our experience the large majority of sudden drops on business sites are self-inflicted technical changes, not penalties.

Keep reading

More on Web Development

Start here

Want the four tier-one checks run on your site?

It takes us under an hour and we will tell you plainly whether anything is broken. No report full of colour-coded scores you did not ask for.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →