Replit and SEO: Why Businesses Are Accidentally Destroying Their Google Rankings

Replit and SEO: Why Businesses Are Accidentally Destroying Their Google Rankings

Picture this. A business owner gets a shiny new website built. It looks brilliant — fast, modern, clean design. They're delighted. They pay the invoice. They wait for the enquiries to roll in.

Three months later, they're ranking for nothing. Their old WordPress site used to bring in ten leads a week. This one? Two. Maybe.

Their developer shrugs. "The site's working fine."

And technically, they're right. The site works perfectly — for humans. For Google, it's practically invisible.

This is the story playing out right now, quietly, across thousands of small businesses in the UK. And it's almost always caused by the same thing: a developer who built a React app without understanding what that means for SEO.

The Rise of the Vibe-Coded Website

Tools like Replit, Lovable, Bolt, and a dozen others have made it faster than ever to build a website. You describe what you want, an AI builds it, you deploy it. Half a day's work. Sometimes less.

These are genuinely impressive tools. I use Replit myself — this very website was built on it. But there's a catch that almost nobody warns new users about, and it's costing businesses real money in lost rankings.

The default output of most AI website builders — including Replit — is a React application using client-side rendering. And if you don't know what that means, you probably haven't heard the alarm bells going off yet. You will.

The Difference Between a Website and a Web App (in Plain English)

Here's the thing most developers won't take five minutes to explain.

A traditional website — WordPress, hand-coded HTML, Squarespace — works like a restaurant that serves you a finished meal. You ask for the page, the server sends back complete, ready-to-read HTML. Every word, every heading, every paragraph is right there in the response. Google's crawler (Googlebot) reads it instantly and indexes it immediately.

A default React app — the kind Replit and most AI builders produce — works more like a flatpack kit. You ask for the page, the server sends back an almost empty box with assembly instructions inside (JavaScript). The browser has to run those instructions to build the page you actually see. It looks identical to the human eye. But Googlebot? It receives something like an empty shell with just a blank container div and no actual content inside it.

No text. No headings. No body copy. Nothing to index.

This is called Client-Side Rendering (CSR) — the page is rendered in the browser, not on the server. And it's the default for almost every React app built with Vite, Create React App, or the AI tools that use them under the hood.

How Googlebot Actually Works — The Two Waves

Google does eventually render JavaScript. That's the line developers use to wave away the problem. "Google can handle JavaScript now." And they're not wrong — technically.

But what they don't tell you is how Google handles it: in two separate waves, and the second one is painfully slow.

Wave 1 — The instant crawl. Googlebot visits your page and reads the raw HTML it receives. If that HTML contains your content (as it does with WordPress or a properly built SSR site), it gets indexed right away. If the server sends an empty container with no content, there's nothing useful to index.

Wave 2 — The JavaScript rendering queue. If Wave 1 finds JavaScript-only content, Google adds the page to a secondary rendering queue. This queue is managed by Google's Web Rendering Service (WRS), which has limited capacity. Pages in this queue can wait days. Sometimes weeks. New pages on brand new sites can sit invisible in Google for over a month.

So when a business replaces their WordPress site with a Replit React app, they move every single page from Wave 1 (instant) to Wave 2 (whenever Google gets around to it). Their existing rankings — built up over months or years — can evaporate almost overnight.

What People Are Actually Saying

I've seen this exact conversation play out in forums more times than I can count now.

On the Replit Community Forum, users report submitting their sites to Google Search Console and running SEMrush reports, only to find their pages simply aren't being indexed despite being live and publicly accessible. Threads specifically about SEO for Replit-hosted websites are full of developers discovering — after the fact — that their React app has a fundamental indexing problem nobody warned them about.

On the Google Search Central Community, there's a thread titled: "Facing Issues in SEO for a Website built on React JS as it only supports CSR with no webcache." It's not a one-off complaint. It's a well-worn pattern.

The most telling symptom is a Google Search Console status that reads: "Crawled – Currently Not Indexed." Google found the page, visited it, decided there wasn't enough content to index, and moved on. For a CSR React app, this is almost inevitable on the first crawl — because on that first visit, there genuinely isn't any readable content in the HTML response.

As SEO resource optimizer.team documents directly: "If you see an empty shell with no real content in the HTML, Google has to render JavaScript before it can index your content. This works but is slower and less predictable — new pages can take days or weeks to appear."

Why This Matters More Than Most Developers Admit

Rankings are not a vanity metric for small businesses. They are leads. They are phone calls. They are sales.

If your plumbing business ranks third for "emergency plumber Stirling" and you move to a new site that drops you off page one, you don't just lose SEO bragging rights — you lose a steady stream of customers who will never know you exist.

The cruel part is the delay. CSR sites often look fine in Google Search Console for weeks after launch. Pages appear to be crawled. Then slowly, quietly, rankings slip. By the time the business owner notices, Google has already demoted them and established new competitors in those positions.

A developer who charges £800 for a React app built without SSR may have just cost their client tens of thousands in lost business over the following year. They'll never connect the dots.

The Fix: SSR — The Best of Both Worlds

Here's the good news. This problem is entirely solvable. You don't have to choose between a modern, fast website and one that Google can actually read. You just need Server-Side Rendering (SSR).

SSR means the server renders your React components to complete, content-filled HTML before sending it to the browser. Google receives a fully-formed page — exactly like WordPress — and indexes it immediately. Then JavaScript loads in the browser and makes the page fully interactive. The user gets a fast, modern experience. Google gets readable HTML. Everyone wins.

This process is called hydration — the server sends the finished HTML, and then JavaScript "hydrates" it to make it interactive. It's the best of both worlds: the SEO-friendliness of a traditional site, the performance and flexibility of a modern React app.

There are several ways to implement SSR properly:

• Next.js — the most popular React framework with SSR built in by default. An excellent choice for most business sites.
• Vite + Express SSR — the approach I use on this website. React rendered on the server via Vite's SSR mode, served through an Express/Node.js server. Fully custom, no framework lock-in.
• Remix — SSR by default, excellent routing, strong SEO fundamentals baked in.
• Astro — fantastic for content-heavy sites; sends pure HTML with optional JavaScript islands where you need interactivity.

What to Ask Your Developer — A Checklist

If you're having a website built, or reviewing an existing one, here's what to check before signing off:

The Comparison Nobody Shows You

The Takeaway

Replit is a remarkable platform. The websites and applications you can build on it — when done correctly — are genuinely world-class. Fast, scalable, fully custom, with no plugin bloat and no monthly platform tax.

But "built on Replit" doesn't automatically mean "good for SEO." The platform doesn't enforce SSR. The AI doesn't always implement it. And developers who use it as a shortcut to build client websites without understanding server-side rendering are handing their clients a beautifully wrapped problem.

The result is a growing number of small businesses sitting on modern, invisible websites — paying for something that's costing them more in lost rankings than it ever saved in build time.

If you're commissioning a website right now, ask the questions above. If your developer can't answer them clearly, that clarity is itself an answer.

And if you already have a site that's losing rankings and you suspect CSR might be the culprit — get in touch. I'll look at it, tell you exactly what's happening, and fix it properly.

Lewis Cowan — The Bee Seen Company, Dunblane.