Back to journal
Digital

Technical SEO: what your web developer should be doing that most are not

Most conversations about SEO focus on content and keywords. Write more blogs. Use the right phrases. Get backlinks. This advice is not wrong, but it is incomplete. Because all of it sits on a foundation of technical SEO, and if that foundation has cracks, the content work above it will underperform no matter how good it is.

After two decades in enterprise IT, I approach SEO with the same structured rigour I brought to banking systems. You start with the infrastructure. Then you build on top of it.

Here is what technical SEO actually involves, and what your developer should be ensuring from day one.

Site speed is a direct ranking factor. Google has been explicit about this for years. A website that loads in under two seconds will rank above an equivalent website that takes four seconds. The most common causes of slow loading are unoptimised images, too many third-party scripts, poor hosting and unminified CSS and JavaScript. Every image on your website should be compressed without visible quality loss. Your hosting should be on a server geographically close to your primary audience. Your code should be clean and lean.

Mobile-first is not optional. Google indexes the mobile version of your website first. This has been true since 2019. If your website is not fully responsive, if text is too small to read on a phone, if buttons are too close together to tap accurately, or if content behaves differently on mobile than on desktop, your rankings will suffer. Every page of your website should be tested on actual mobile devices, not just browser simulations.

HTTPS is a baseline requirement. An unsecured HTTP website sends trust signals to both Google and your visitors that are actively harmful. Every website must have a valid SSL certificate and serve all pages over HTTPS. This is not advanced SEO. It is a minimum standard that no developer should be leaving unimplemented in 2025.

Structured data helps Google understand your content. Structured data, also called schema markup, is code added to your website that explicitly tells Google what your content is about. Person schema, LocalBusiness schema, Service schema, BlogPosting schema. When Google can read your structured data, it can display rich results in search, including star ratings, event dates, FAQ answers and other enhanced formats that dramatically increase click-through rates from search results.

Crawlability means Google can actually read your site. Your robots.txt file tells search engine crawlers which pages to index and which to ignore. Your sitemap.xml tells them where all your pages are. Internal linking helps them understand the structure and relative importance of your content. If your important pages are not being crawled and indexed, they cannot rank. This sounds basic but I regularly audit websites for clients where significant pages are accidentally blocked from crawling.

Core Web Vitals are Google ranking signals. Largest Contentful Paint measures how quickly the main content of a page loads. Cumulative Layout Shift measures how stable the page layout is as it loads. Interaction to Next Paint measures how quickly the page responds to user interaction. Google measures these for every page of your website and uses them as ranking signals. You can check your scores using Google Search Console and PageSpeed Insights. If your scores are poor, your developer needs to address them.

Technical SEO is not glamorous. It does not produce the visible, shareable results that a viral blog post does. But it is what makes everything else work. A website with strong technical foundations will consistently outrank a technically weak competitor even with equivalent content, because Google can trust it, read it, and deliver it to users confidently.

When I build websites for clients, technical SEO is not an add-on. It is built in from the first line of code. Because there is no point building something beautiful that Google cannot find.