Services

Fix JavaScript Pages Not Indexing, Rendering and Metadata Problems

Use this page when a React or Next.js site is crawled but not indexed, key content only appears after JavaScript runs, or rendered HTML and metadata do not match what search engines need.

Diagnose why Google is not indexing important JavaScript pages before incomplete HTML, unstable metadata, or routing changes keep them out of search.

Typical symptoms

  • Pages are published but not indexing reliably or at all.
  • Search engines are seeing incomplete, inconsistent, or delayed content.
  • Metadata or rendered page state does not match the intended output.

Likely causes

  • Important page data is not available early enough in the rendered output.
  • Link discovery or metadata generation is inconsistent across templates.
  • Rendering assumptions changed during a migration or framework update.

What I look at first

  • Quick check: inspect the raw HTML and metadata on the affected templates before comparing them with the hydrated browser state.
  • How content becomes visible to bots on priority routes.
  • Whether the issue is rendering, crawl discovery, or URL management.

How I help fix this

  • Separate rendering issues from crawl and URL problems quickly.
  • Identify the templates and page types that need the first fixes.
  • Support engineering changes that improve indexable output without guesswork.

When to bring me in

  • Bring me in when the issue is clearly technical and broad SEO guesswork is wasting time.
  • Bring me in when rendering, metadata, and indexing problems are overlapping on important routes.

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

Related services

  2. Capability

    Technical SEO for JavaScript Applications

    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.

  3. Adjacent 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.

Questions teams usually ask

Does this include metadata and Open Graph problems?
Yes, when those issues are tied to the same rendering or indexing failure. The point of this page is to diagnose what bots can actually see and process, not to treat metadata in isolation.
How is this different from crawlability debugging?
Crawlability work is about discovery and route access. This page is for the rendering and indexing side of the problem, where the content or metadata a crawler sees is incomplete, unstable, or delayed.

Show me what's not working

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