Scenario
Traffic Drop After a Redesign or Replatform
Use redesign recovery and technical SEO recovery work to isolate what changed in URLs, templates, rendering, or crawl signals before the organic traffic drop compounds.
Start here when search performance fell after something changed in the platform and the likely cause is technical rather than editorial.
Choose the right technical SEO recovery path when rankings, crawlability, or indexation dropped after a release or migration.
Choose the symptom that best matches the current recovery problem.
Scenario
Use redesign recovery and technical SEO recovery work to isolate what changed in URLs, templates, rendering, or crawl signals before the organic traffic drop compounds.
Scenario
Recover lost visibility after a WordPress‑to‑Next.js migration by tracing the technical gaps in redirects, canonicals, sitemaps, and rendering.
Scenario
Diagnose why Google is not indexing important JavaScript pages before incomplete HTML, unstable metadata, or routing changes keep them out of search.
Scenario
Fix sitemap, robots, and crawl‑discovery failures before important Next.js pages stay hidden, blocked, or stale in search.
Scenario
Fix duplicate URLs, bad redirects, and canonical mistakes before search engines and users keep landing on conflicting versions of the same page.
Capability
Bring in engineering‑led SEO help when Google is not indexing important JavaScript pages because rendering, crawlability, metadata, or migration changes are getting in the way.
Capability
Bring in senior Next.js architecture support when a legacy platform, older front end, or hard‑to‑maintain site needs migration planning, platform rescue, and clearer delivery direction.
Capability
Bring in performance help when page loads feel slow, Core Web Vitals are slipping, or scripting cost is hurting key user journeys.
Capability
Bring in headless CMS consulting when CMS architecture, SEO controls, preview trust, or revalidation decisions are about to lock in operational pain.
Senior software engineer on the UK and Ireland replatform, migrating Nando’s customer‑facing websites from legacy Drupal to a unified headless platform built with Next.js and Storyblok, with a focus on performance, accessibility, and SEO.

Senior developer as part of team 'Findability'. Led the digital implementation of the 'John Lewis & Partners' rebrand alongside new feature development, user journey optimisation, and performance improvements.

Ten practical SEO areas front-end developers can influence, from site speed and semantics to metadata, mobile UX, internal links, and structured data.
GEO and SEO overlap, but they are not interchangeable. This article breaks down where they meet, where they differ, and how websites need to adapt.
Optimising HTML improves SEO, accessibility, and user experience. Here, I explore semantic HTML, clean code, alt text, and other best practices.
Send me the affected page or route, point me at the code if that helps, and tell me what you expected to happen versus what is happening now. If this connects to a Next.js migration, technical SEO drop, performance issue, launch, or platform move, include that context too. I'll come back with the clearest next step.