React SEO: why your React website might be invisible to Google (and how to fix it)
Is React bad for SEO? Why client-side React sites can look empty to Google and link previews, how to check yours in two minutes, and the fixes that work.

A confession to start: until recently, our own website had this exact problem.
It was built as a client-side React app from a commercial template. It looked fine in a browser, but if you opened the raw HTML you found a single empty <div id="root"></div> and a meta description that read "Web site created using create-react-app". Everything a visitor saw was assembled by JavaScript after the page loaded. To anything that didn't run that JavaScript, the site was blank.
This is the most common React SEO problem we see, and it's easy to miss because the site looks perfect to its owner. This guide explains what's happening, how to check your own site, and how to fix it properly.

Is React bad for SEO?
No. React itself is neutral. Some of the fastest, best-ranking sites on the web use React. The problem is how a React site is rendered.
There are three common approaches:
| Rendering approach | What the server sends | SEO impact |
|---|---|---|
| Client-side rendering (CSR) | An almost empty HTML shell plus JavaScript | Risky: content depends on JavaScript running successfully |
| Server-side rendering (SSR) | Complete HTML for each request | Strong: crawlers see content immediately |
| Static site generation (SSG) | Complete HTML built in advance | Strongest for marketing pages: fast and fully crawlable |
Most "React is bad for SEO" stories are really "client-side rendering is risky for SEO" stories. Create React App, plain Vite React setups and many purchased React templates render on the client by default.
What search engines actually receive
When a browser asks for a page, the server sends back HTML. On a traditional or server-rendered site, that HTML already contains your headings, text, links, title and description. On a client-side React app, it contains almost nothing. The content only appears once the browser downloads, parses and runs your JavaScript bundle.
How Google handles JavaScript
Google can run JavaScript using a recent version of Chromium, but it does so in stages:
- Crawl: Googlebot fetches the HTML. On a client-side app, there's little to see.
- Queue: the page waits for rendering resources. This can take seconds or much longer.
- Render: Google runs your JavaScript and finally sees the content.
- Index: the rendered content is processed and, hopefully, indexed.
That works most of the time, but plenty can go wrong. Scripts may be blocked by robots.txt, a third-party script may time out, an API call may fail, or rendering may simply be deferred. When rendering fails, Google is left with the empty shell, and you rarely find out.
Who doesn't run JavaScript at all
Google is the most capable crawler. Many other important visitors don't render JavaScript:
- Link previews on WhatsApp, LinkedIn, Facebook, Slack and X read only the initial HTML. That's why some links appear as a bare URL with no title or image.
- Many AI crawlers fetch raw HTML and move on, so your content may never reach the AI assistants people now use to research suppliers.
- Other search engines and SEO tools often see exactly what's in the source and nothing more.
If your words only exist after JavaScript runs, a large part of the web can't read them.
How to check your own site in two minutes
You don't need technical tools to find out whether you have this problem.
- View the source, not the inspector. Press Ctrl+U (or Cmd+Option+U on a Mac) on your homepage, then search for your main headline. The browser's Inspect panel shows the page after JavaScript has run, so it hides the problem. View Source shows what crawlers receive first.
- Use Google's own view. In Google Search Console, open the URL Inspection tool for an important page, then View crawled page. Check the HTML and the screenshot. If key content is missing, Google may not be seeing it either.
- Paste your link into a chat. Start a WhatsApp or LinkedIn message and paste your URL. No title, image or description means your meta tags only exist after JavaScript runs.
- Search for a sentence. Copy a distinctive sentence from a deep page and search for it in quotes on Google. If it isn't found weeks after publishing, rendering or indexing is likely failing.

The fixes, from simplest to most involved
1. Generate HTML ahead of time (static generation)
For marketing pages, such as your homepage, services, about page and blog, static generation is usually the best answer. Every page is built into complete HTML when you publish, then served instantly from a CDN.
Next.js, Astro and similar frameworks do this well, and you keep React for the parts that need interactivity. It's what we used when rebuilding our own site, although we went further and generate plain HTML with almost no JavaScript at all.
2. Render on the server (SSR)
For pages that change constantly, such as stock levels, prices, dashboards or personalised content, server-side rendering sends finished HTML on every request. Next.js supports this alongside static pages, so you can choose per page.
3. Pre-rendering services: a stopgap, not a strategy
Pre-rendering tools serve a rendered snapshot to bots while users get the client-side app. They can buy time on a legacy app you can't rebuild yet, but they add a moving part that can drift out of date. Treat them as temporary.
4. Fix the basics whichever approach you choose
- Unique titles and descriptions in the initial HTML for every page.
- Open Graph and Twitter tags so link previews show a title, description and image.
- Real links: use
<a href>links between pages, not click handlers, so crawlers can follow them. - Real URLs: each page needs its own address that works when opened directly.
- Proper status codes: pages that don't exist should return a real 404, not a "not found" message on a 200 page.
- Structured data (JSON-LD) in the HTML for your organisation, services, articles and FAQs.
- A sitemap listing every page you want indexed.
Migrating an existing React site without losing rankings
If your React site already has some traffic, move carefully:
- Inventory every URL the old site serves, including any that rank or have backlinks.
- Keep URLs the same where you can. Where you can't, map each old URL to its new one with a permanent 301 redirect.
- Carry over titles, descriptions and content that already perform.
- Test before launch: View Source on every template, validate structured data and check link previews.
- Watch Search Console for the first few weeks and fix any errors quickly.
We cover the full process in how to redesign your website without losing Google rankings.
What we did with our own site
We rebuilt it as plain HTML generated when we publish. Every page now has its own title, description and structured data. The JavaScript that remains is a few kilobytes for the menu, clocks and filters, and the site works without it. Every old URL redirects to its new home, so nothing that used to rank was lost.
Frequently asked questions
Is React bad for SEO?
React isn't bad for SEO, but client-side rendering can be. If your React app sends an empty HTML shell and builds everything in the browser, crawlers and link previews may see nothing. Server-side rendering or static generation, for example with Next.js, solves this.
Can Google index client-side React apps?
Often, yes. Google renders JavaScript in a second stage after crawling. But rendering can be delayed or fail, and many other crawlers and link previews don't run JavaScript at all, so relying on it is risky for pages that need to rank.
Do I need to rebuild my whole React app to fix SEO?
Not always. Many teams move only their public, search-facing pages, such as the homepage, services, pricing and blog, to static generation, and keep the logged-in app as it is.
Is Next.js good for SEO?
Yes. Next.js can render pages on the server or at build time, so search engines receive complete HTML. You still need the basics right: titles, descriptions, internal links, structured data and speed.
If you suspect your site has the same problem, send us the link and we'll tell you what we see. Or read how we approach Next.js development and technical SEO.
Have a question about your own project? Ask us directly. We reply to every message.


