Technical SEO
that holds up under
core updates.

The £950 entry tier is right for sites under roughly 5,000 indexable URLs on a standard CMS. You get a 20-hour-a-month engagement covering technical fixes, schema, internal linking, Core Web Vitals work, monthly crawl analysis, and a written report. Sites over 5,000 URLs, JavaScript-heavy SaaS, multi-region setups with hreflang, or migrations push scope into the £1,800 to £4,000 tiers. We size the retainer honestly on the first call rather than fitting a square peg.

A general SEO retainer blends technical work, content, and link earning. A technical-only retainer focuses the full monthly allocation on infrastructure: crawlability, rendering, schema, speed, internal link topology, and log-level diagnostics. It pairs well with an in-house content team or a separate content partner, and is the right fit when the technical foundation is the bottleneck rather than word count or link profile.

Yes. JavaScript SEO is one of the most common reasons a technically well-intentioned site fails to rank. We diagnose rendering issues by comparing the initial HTML response, the Googlebot-rendered DOM, and the client-rendered DOM. Most React, Next.js, Vue, and Angular sites we audit have at least one rendering issue affecting indexation. We fix those with the right mix of server-side rendering, static generation, or pre-rendering depending on the stack.

Three layers. First, a site-wide entity graph that links your Organization, WebSite, and Person schemas through stable @id references. Second, template-level schemas for your core page types, usually Article, Product, Service, LocalBusiness, or FAQPage, validated against the current Google rules. Third, page-specific schemas like HowTo, Review, or BreadcrumbList where they fit. Most sites we audit have schema fragments that do not reference each other and do not produce rich results. Fixing that alone often moves click-through rates meaningfully.

Yes, we ingest 30 to 90 days of server logs, segmented by URL pattern and user agent. That tells us which URLs Googlebot is actually requesting, how often, and whether crawl budget is being wasted on faceted URLs, parameter noise, or low-value paginated pages. Log file analysis is the only reliable way to see crawl behaviour. Search Console gives an aggregate, logs give the truth.

We run a migration protocol: full URL inventory, old-to-new mapping, 301 redirect chains minimised to single hops, schema preservation, internal link rebuilding on the new templates, Core Web Vitals validated pre-launch, staging-site indexing controls, post-launch crawl comparison, rank-tracking benchmarks, and 30 to 60 days of post-migration monitoring. Done properly a migration should lift rankings, not harm them. Done poorly it is the single most common reason a site loses 40% of traffic overnight.

Often, yes. On about half our technical retainers we write the specs and your in-house developer or external agency implements them. On the other half we implement directly on WordPress, Next.js, Shopify, or Webflow. Either works. What we will not do is accept responsibility for outcomes when a third party refuses to implement the specified fixes.

A two to three page written note each month, plus a 30-minute call. The note covers what was shipped, what moved in rankings and indexation, what the month-over-month crawl comparison shows, and what is queued next. No 40-slide decks, no vanity dashboards. Search Console and Ahrefs are the source of truth, the note is the interpretation.