Briefing

Vibe-Coding Tools Create SEO Suicide for Landing Pages

seo
by John Medina · Vercel Google Search

Switch your landing pages to SSR or SSG so Googlebot can index content immediately, rebuild them in Next.js or Astro, and keep the CSR dashboard on a subdomain.

What to do now

Switch your landing pages to SSR or SSG, rebuild them in Next.js or Astro, and keep the CSR dashboard on a subdomain.

Summary

Vibe-coding tools ship landing pages as client‑side rendered React apps, which Googlebot sees as a blank HTML file plus a massive JS bundle. Google takes up to nine times longer to index such pages, and if the rendering budget is exceeded, indexation can drop by 40%. The default SPA architecture is convenient for developers but disastrous for SEO. SSR or SSG solutions like Next.js on Vercel deliver instant HTML, allowing Googlebot to crawl content immediately. For those stuck with CSR, options include Prerender.io as a quick fix, or rebuilding marketing pages in Next.js or Astro while keeping the dashboard on a subdomain.

The article demonstrates how LLMeter was built with Next.js for instant SSR and highlights the pitfalls of relying on Vibe‑coded SPAs for SEO‑critical pages.

Key changes

  • CSR React apps cause Googlebot to see blank HTML and large JS bundle, delaying indexation up to 9×
  • Indexation drops by up to 40% if rendering budget is exceeded
  • SSR/SSG delivers instant HTML, improving indexation speed
  • Next.js on Vercel offers SSR out of the box
  • Prerender.io is a band‑aid but can be used
  • Rebuild marketing pages in Next.js or Astro; keep CSR dashboard on a subdomain
  • Vibe‑coding tools default to SPA architecture
  • Google hates JS‑heavy pages

Affects

none

Customer impact

Analyzing matches…

Ask about this story

Impact on an agency? Which customers? Compare historically Risks of waiting