Check my websiteGuidesAbout
Fecto / Guides / React SEO problems

React SEO problems

React isn’t bad for SEO; a React app that renders only in the browser is, because its HTML arrives with an empty root element and the text appears after scripts run. Google renders JavaScript, but the AI search bots and most other crawlers read the HTML as served, so check what your page looks like without JavaScript.

Free, about ten seconds, no account.

Is React SEO friendly?

React decides what HTML exists; where that HTML is produced is up to the framework around it. With a server framework such as Next.js, React Router in framework mode or TanStack Start, each page arrives with its text. With a plain client-side setup, such as the Vite React template, the server sends one HTML file for every URL and React fills it in after loading.

Google handles that second case reasonably well: it renders the page and indexes what appears. Fecto’s rule for main text reflects this and isn’t applied to Googlebot. The engines that feed AI answers are another matter, which is why the same React site can rank on Google and be invisible to an assistant.

The other React-specific problems come from writing everything as components: tags set from an effect, navigation done with click handlers, redirects done with navigate(). They work for a person with a browser and fail for anything that reads the HTML.

Common causes, and the fix for each

An empty root element

Fecto check read.main-text-needs-js · Main text is in the HTML

The scan reads the page without running scripts. If the main text isn’t there, the fix is to prerender the routes that matter (most build setups can emit static HTML per route) or move them to a server-rendering framework. Your agent picks the smaller change for your setup and re-runs the check on the built output.

Titles set from an effect

Fecto check index.meta-tags · Title and description

Libraries that set document.title after mount leave the served HTML with the template’s title. React 19 can render <title> and <meta> from components, but in a client-only app that still happens in the browser. The tags have to be in the HTML the server sends, so this goes with prerendering.

Links that are divs with onClick

Fecto check act.faux-controls · Real links and buttons

Google only follows <a> elements with an href. A card that navigates with a click handler is invisible as a link to crawlers and unreachable by keyboard. Swapping it for your router’s link component fixes both.

Text locked in images and canvas

Fecto check read.little-text · Enough text to understand the page

Hero sections built from images, animations or canvas often carry the only sentence that says what you do. If the page has only a few sentences of real text, an assistant can’t describe you. Put the sentence in HTML and keep the visual.

Redirects done in a component

Fecto check read.redirect-hygiene · Clean redirects

A home page that calls navigate() on mount looks like a blank page to a crawler that doesn’t run scripts. The check flags script-only and meta-refresh redirects; a server redirect replaces them.

Let your agent do it

Your agent reads how the app is built before proposing anything, so a Vite app gets prerendering added rather than a framework migration it didn’t ask for. Each change is one pull request with the check results attached.

Claude CodeClaude appCodexCursor

No coding agent yet? Install the Claude app, sign in, then come back and choose Claude app.

Set it up by hand
curl -fsSL https://fecto.ai/install | sh

Then tell it

Use Fecto to check and fix my site.

Don’t rewrite the app to fix SEO

Moving a working React app to a new framework is weeks of risk. Prerendering the handful of public pages usually passes the same checks, and the logged-in app can stay client-side.

What it costs

You pay only when the result shows up on your site: +20% more visits or enquiries is $30, +50% is $60, double is $100, and anything below +20% costs $0. Never more than $100 a site a month.

Questions

Do I need Next.js for SEO with React?

No. You need the public pages’ HTML to carry their text, titles and links. Next.js is one way; React Router’s framework mode, TanStack Start or build-time prerendering of a Vite app are others. Pick the one closest to what you already run.

Does react-helmet still work?

It sets tags in the browser, so in a client-only app the served HTML keeps the template’s title. With server rendering it can work, but React 19 handles <title> and <meta> in components itself, without a library.

Will Google index my React SPA?

Usually, given time: Googlebot renders JavaScript and indexes what appears. The cost is elsewhere. AI search bots and link previews read the raw HTML, and Fecto’s main-text check is aimed at them.

Can I fix this without touching the app’s logic?

Often, yes. Prerendering runs at build time for the routes you list and writes HTML files next to the bundle; the app takes over in the browser as before. Pages that need a signed-in user stay client-only, which is what you want anyway.

Related guides

  • Single page app SEO
  • Next.js SEO
  • Vibe coded website SEO issues
  • Lovable SEO
  • Bolt.new SEO
  • All guides

Checked against Google Search Central: JavaScript SEO basics on 18 November 2026.