Take your SPA anywhere.

You moved for control. Don't lose SEO in the switch.

You shipped on a builder because it was fast. Now you need things it can't give you — custom domains, your own pricing, build-time flexibility, git access, a proper deploy pipeline. Moving hosts usually means re-solving SEO from scratch: pre-rendering, sitemap, schema, cache warmup, the works. RndrKit is the one piece of the stack that doesn't have to change. Point us at your new origin and your indexed pages stay indexed.

1. STEP_01

   Step 1 — Export your code.

   Get your source out of the builder you started on. Every major SPA builder ships a code-export path — we won't re-document their flows, we'll just point you at them.

   Lovable export docs →Bolt export docs →Replit export docs →
2. STEP_02

   Step 2 — Deploy to your new host.

   Push the exported repo to Cloudflare Pages, Vercel, Netlify, or your own server. Your new origin is whatever hostname serves your SPA after deploy — that's the URL RndrKit will fetch from.

   Cloudflare Pages →Vercel →Netlify →
3. STEP_03

   Step 3 — Point RndrKit at your new origin.

   In the dashboard, add your domain (the public address your visitors use), paste your new origin URL into the Origin URL field, and pick a delivery path — Proxy (simplest) or Cloudflare Worker (edge-fast). That's the only RndrKit-side work.

   Connect any SPA →
4. STEP_04

   Step 4 — Verify indexing.

   Run a bot-user-agent smoke test on a few pages, open Google Search Console, and use URL Inspection to request re-indexing on your top-traffic URLs. Google usually refreshes the cache within a week.

   Smoke-test your site →Google Search Console →

No cold start. No ranking reset.

• [OK]Already-indexed URLs stay indexed — same paths, same canonical, same content.
• [OK]Your sitemap and schema transfer unchanged. RndrKit serves what your SPA renders; it doesn't rewrite your meta.
• [OK]The cache warms on first bot render, so top-traffic URLs are ready before Google checks back.
• [OK]Rankings persist through the DNS cutover — bots see pre-rendered HTML the moment the record propagates.
• [OK]Switching delivery paths later (Proxy ↔ Worker) doesn't touch indexing — it's the same HTML either way.

Will I lose rankings?

No — that's the whole point. Your URLs don't change, your content doesn't change, and your schema / sitemap travel with you. RndrKit serves search engines the same pre-rendered HTML from your new origin, so rankings carry through the DNS cutover.

Do I need to change my domain?

No. Keep the domain your visitors and Google already know. You just re-point DNS: a CNAME record to rndrkit.io (for most providers) or an A record to our ingress if your DNS doesn't support apex CNAMEs. The hostname your customers type stays identical.

What if I want to keep my AI builder and just add RndrKit?

That works too — and it's the most common starting point. Leave your app on Lovable, Bolt, Replit, or wherever. Add RndrKit in front and we pre-render the version bots and crawlers see. You only need this migration guide if you've decided to move the host itself.

How long does this take?

Typically an afternoon. Export and redeploy are usually the longest part and depend on your build pipeline. The RndrKit side — add domain, set origin URL, point DNS — takes about five minutes. Re-indexing happens on Google's schedule once DNS propagates.