Not sure what you need? That's fine. Let's figure it out together

Technical SEO

The behind-the-scenes work that makes everything else possible. If Google can't crawl, index and understand your site properly, nothing else matters.

Technical SEO is one part of a broader SEO strategy. It's the foundation that content and links build on.

The invisible problems that tank your rankings.

Your site might look perfectly fine to visitors. But underneath, there could be dozens of issues that Google sees and you don't. Slow page loads. Crawl errors. Duplicate content confusing the indexer. Pages Google can't even find. Mobile experience that's technically passable but practically painful.

These aren't the kind of problems your web designer will flag. They don't show up in Google Analytics. They just quietly erode your rankings, drip by drip, until you're wondering why your traffic has flatlined while competitors pull ahead.

The frustrating part is that you could have brilliant content and a solid link profile, and technical issues will still hold you back. It's like having a great engine in a car with the handbrake stuck on — all that effort, going nowhere.

How I fix what's broken under the bonnet.

Methodical, thorough, and hands-on. I don't just hand you a list of problems — I fix them.

Comprehensive audit

I crawl your entire site the way Google does, flagging everything from broken links and redirect chains to orphaned pages and thin content. You get a clear picture of what's wrong, what matters most, and a prioritised plan for fixing it.

Site speed & Core Web Vitals

Page speed is a ranking factor and a user experience factor. I dig into render-blocking resources, image optimisation, server response times, layout shifts, and everything else that affects how fast your pages load and how stable they feel.

Crawlability & indexation

If Google can't find your pages, they can't rank them. I'll sort out your robots.txt, XML sitemaps, internal linking structure, canonical tags, and anything else that controls how search engines discover and index your content.

Concrete outcomes, not just a report.

Technical SEO shouldn't end with a PDF you never read. Here's what you actually walk away with.

Full technical audit

A comprehensive crawl of your site covering indexation, crawl budget, site architecture, duplicate content, redirect chains, broken links, and every other technical factor that affects your rankings. Prioritised by impact, not alphabetical order.

Site speed optimisation

Hands-on work to improve your Core Web Vitals and page load times. That means image compression, code minification, lazy loading, server-side improvements, and anything else that's slowing your site down.

Schema markup implementation

Structured data that helps Google understand your content and can earn you rich results in search — review stars, FAQs, breadcrumbs, product information, and more. Implemented properly, tested, and monitored.

Ongoing technical monitoring

Technical issues don't just happen once. New pages get added, plugins get updated, things break. I run regular crawls and monitor your site's technical health so problems get caught and fixed before they affect your rankings.

Things people usually ask about technical SEO.

Technical SEO covers everything that affects how search engines crawl, index, and render your website. Think of it as the infrastructure your content sits on. It includes site speed, mobile-friendliness, URL structure, internal linking, sitemaps, structured data, HTTPS, and dozens of other factors. If any of these are broken or suboptimal, it puts a ceiling on how well the rest of your SEO can perform.
Honestly, most businesses don't know until someone looks. Technical issues are usually invisible to visitors and won't show up in basic analytics. Some warning signs: pages that load slowly, a drop in organic traffic with no obvious cause, pages not appearing in Google despite being published, or Google Search Console flagging errors. The only way to know for certain is a proper technical audit.
No. The audit itself is just a diagnostic — I'm crawling and analysing, not changing anything. When it comes to implementing fixes, I work methodically, test changes in staging where possible, and prioritise low-risk, high-impact improvements first. I'll always explain what I'm doing and why before making changes, and I'll have a rollback plan for anything significant.
I'd recommend a thorough audit at least once a year, with lighter monitoring in between. If you're regularly adding new content, updating your CMS, or making design changes, more frequent checks are sensible. The reality is that technical issues accumulate gradually — a redirect here, a broken link there — and catching them early is far cheaper than untangling months of compounded problems.

Not sure what's going on
under the bonnet?

Let's find out. A technical audit will show you exactly where things stand and what needs fixing.

Let's have a chat