DEV Community

John Medina
John Medina

Posted on

You Vibe-Coded Your SaaS Landing Page — Google Can't See It

Look, I get it. You used Lovable or Bolt, shipped a beautiful landing page in 3 hours, and felt like a god. The UI is slick, animations are butter.

But it's been 3 weeks and you have 0 organic traffic.

Here is why: you shipped a Client-Side Rendered (CSR) React app. Google hates those.

I was digging into indexation stats recently. Google takes about 9x longer to index JS-heavy pages. If your site exceeds their rendering budget, indexation drops by up to 40%.

When Googlebot hits your vibe-coded site, it sees a blank HTML file and a massive JS bundle. It has to queue it for rendering, parse the JS, execute it, and only then sees the content. Most indie devs don't realize this until their Search Console stays flat for months.

Vibe-coding tools default to SPA (Single Page Application) architectures because they're easier to generate and feel faster to the user. But for a landing page? It's SEO suicide.

If you want organic users, you need SSR (Server-Side Rendering) or SSG (Static Site Generation). When Google hits the URL, the HTML needs to be there instantly.

I built LLMeter (open-source LLM cost tracking) using Next.js on Vercel specifically for this reason. SSR out of the box. No waiting for Googlebot to execute JS. It just indexes.

If you're stuck with a CSR landing page right now:

  1. Prerender.io is an option, though it's a band-aid.
  2. Rebuild the marketing pages in Next.js/Astro. Keep the CSR app for the actual dashboard on a subdomain (app.yoursaas.com).

Don't let the AI tools trick you into bad architecture. Ship fast, but make sure Google can actually read it, tbh.

Check out LLMeter if you're dealing with LLM API costs

Top comments (0)