Prerendering for Lovable Sites

Prerendering intercepts requests from bots (identified by user-agent) and serves them a fully-rendered HTML snapshot of your page instead of the JavaScript shell a browser would normally execute. Human visitors still get the normal interactive app; crawlers get readable HTML.

Why this matters more than almost anything else

Without it, your headline, body copy, and internal links may not exist as far as many crawlers are concerned, no amount of good content or backlinks fixes a page that's structurally invisible.

How to verify if you need this

• View your page's raw HTML source (not the rendered DOM)
• Check whether your actual text content appears there, or just an empty root div
• If it's the latter, prerendering is your highest-priority fix, ahead of content, ahead of backlinks

Setup approaches

• Managed prerendering services route bot traffic through a rendering service that returns cached HTML
• Edge function rendering for teams comfortable with more configuration
• Static export where possible avoids the problem entirely for content that doesn't change per-user

What to check after setup

Test with Google's URL Inspection tool in Search Console confirm the "rendered HTML" matches what you expect. Recheck after any major site republish, since cache invalidation matters.