Services

Technical SEO and Indexing for JavaScript Applications and Modern Front Ends

This is for teams asking why a React or Next.js site is crawled but not indexed, why rendered HTML is too thin, or why metadata and crawl signals no longer match what search engines need.

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.

Where this fits

  • Rendering, crawlability, metadata, canonical, and sitemap diagnostics.
  • SEO risk review during platform migrations and redesigns.
  • Engineering changes that preserve discoverability after launch.

Common engagements

  • Technical audits before a migration or rebuild.
  • Post‑launch recovery work when traffic or indexing drops.
  • Hands‑on debugging with the existing engineering team.

Related hubs

Related scenarios

  1. 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.

Related project experience

  1. Nando’s

    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.

    Screenshot of the Nando’s website; part of John Kavanagh's development portfolio.

  2. John Lewis
    & Partners

    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.

    Screenshot of the John Lewis website; part of John Kavanagh's development portfolio.

Related technical articles

Also relevant

  1. Secondary service

    Accessibility and usability reviews

    Accessibility, assistive‑technology, and usability reviews for teams that need practical fixes rather than a compliance‑only report.

Send me the details

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.

Send the details
Skip past clients

Previous Clients