Technical SEO
Making the site properly crawlable, renderable and fast, so the pages you already have get seen, understood and indexed instead of quietly ignored.
Overview
Technical SEO is the part nobody sees and everything depends on. Search engines have a finite budget for crawling your site; if that budget is spent on parameter variations, duplicate paginated pages and redirect chains, your actual content gets visited rarely and updated slowly.
The modern version of this work is mostly about rendering and speed. Sites built as single page applications frequently serve search engines a shell with no content, and Core Web Vitals problems suppress pages that would otherwise rank. Neither shows up in a content audit.
Who this is for
- Sites where a large share of pages are excluded from the index
- JavaScript-heavy applications whose content may not be rendering for crawlers
- Companies planning a replatform or recovering from one that went badly
How we approach technical seo
The specific pieces of work a typical engagement covers. Scope is agreed up front — nothing here is a surprise line item later.
Crawl and index analysis
Full crawl compared against what search engines actually have indexed. The gap between the two is where the problems live.
Rendering verification
Checking what a crawler sees rather than what your browser shows. Client-rendered content is often invisible to indexing and nobody notices for months.
Core Web Vitals
Largest contentful paint, interaction latency and layout stability, fixed in the code rather than masked with a caching plugin.
Canonical and duplicate handling
Parameters, pagination, filtered views and near-duplicate pages resolved so authority consolidates instead of splitting.
Structured data
Schema implemented and validated for the page types that can earn richer results, and left off the ones that cannot.
Migration planning
Redirect mapping, pre-launch checks and post-launch monitoring. Migrations are where most catastrophic organic losses actually happen.
From first call to measured result
The same sequence every time, so you always know what happens next.
Crawl
Full technical crawl plus log file analysis where available, which shows what search engines really request rather than what we assume.
Prioritise
Rank findings by expected traffic impact against development effort, so the engineering time goes where it pays.
Implement
Work with your developers or make the changes ourselves, with each fix verified rather than assumed after deployment.
Monitor
Ongoing indexation and performance monitoring, so regressions are caught in days rather than at the next quarterly review.
Outcomes, not deliverables
A pile of artefacts isn't progress. These are the changes the work is meant to produce — and what we report against.
Pages that finally get seen
Fixing indexation often raises traffic without a single new page being written.
Faster site, better conversion
Core Web Vitals work improves rankings and conversion rate at the same time, which makes it unusually easy to justify.
Migrations that do not cost you a year
Properly mapped redirects and pre-launch checks are the difference between a quiet replatform and a twelve month recovery.
Crawl budget on the right pages
Removing waste means important pages are visited and refreshed far more often.
Common questions about Technical SEO
The things people ask before they get in touch. If yours is not here, ask us directly.
How do we know if we have a technical SEO problem?
The clearest signal is a large gap between pages submitted and pages indexed in Search Console. Other tells are important pages not appearing for their own brand-plus-product query, and organic traffic dropping sharply on the date of a release.
Does our JavaScript framework hurt SEO?
It can. Search engines render JavaScript but do it on a delay and not always completely. Server rendering or static generation removes the risk entirely. If you are on Next.js or similar with server rendering enabled, you are usually fine, and we verify rather than assume.
How much of this needs our developers?
Most of the meaningful fixes touch templates or infrastructure, so yes, developer time is needed. We write tickets in a form engineers can pick up, with the reasoning included so they can push back where our fix conflicts with something we cannot see.
We are replatforming. When should you be involved?
Before the URL structure is decided, which is usually earlier than people expect. Being brought in the week before launch means redirect mapping under time pressure, which is exactly how migrations go wrong.
Thinking about Technical SEO?
Tell us what you are trying to change. If we are not the right fit we will say so, and point you somewhere better.
Looking at the wider picture?
Technical SEO usually sits alongside other work in Search & Organic Growth. Browse the full area to see what it connects to.