How to move a Bubble marketing site to a faster stack without losing your search traffic

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: Bubble is a no-code builder for web apps. If your marketing pages live in a Bubble app and are slow or hard to manage for search, the usual fix is to split: move the marketing pages and blog to a faster site on your main domain, and keep the Bubble app on a subdomain such as app.yourbusiness.com. First test what Google actually sees on your pages. Then map every old address to a new one with permanent redirects, move, and check Search Console for weeks afterward.

Ranjit Bhinge

Your marketing pages run on Bubble, they feel slow or hard to optimise, and you want to move them without losing the traffic you already have.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Short version: do not assume Bubble is the problem. Test what Google sees on your pages first. If the test shows a real problem, or you simply want a faster, easier marketing site, move the marketing pages and keep the app where it is. Most of the risk in a move sits in the redirects, so most of this article is about them.

Why Bubble marketing sites can struggle with search

Bubble, a no-code tool for building web apps, is made for apps where people log in and work with data. A marketing site has different needs: fast first load, simple page content that search engines can read at once, and easy editing by a non-technical team. Reasons teams move their marketing pages:

  • Page content is built in the browser. Forum threads on Bubble SEO (one started in 2021, with a reply as late as April 2024) discuss whether pages that depend on JavaScript are a disadvantage, and one user there reports hundreds of dynamic Bubble pages ranking on Google. Bubble's own help pages say nothing either way about how page body content is delivered, so treat the forum posts as user opinion and test your own pages (next section).
  • Speed. Heavy app code on simple pages can slow the first load. Measure yours: do not rely on a general claim.
  • Editing. Marketing teams want to write and publish a page without opening an app editor.
  • Cost shape. Bubble plans are bought per project and usage is counted in workload units. Its pricing page (November 2026) lists Free, Starter at $32 a month billed annually, Growth at $119, Team at $349, and an Enterprise plan on request, with workload units included per plan (175,000 a month on Starter, for example). Marketing traffic can use units that you would rather spend on the app. See cutting a high Bubble bill.

None of this means a Bubble site cannot rank. Bubble documents the basics: a title, SEO title and description on every page, including dynamic ones, extra tags in the page header, an option to expose an automatic sitemap, a robots.txt file and 301 redirects. The question is what your pages deliver and whether you want to keep fighting for it.

Test first: what does Google see on your pages?

  1. Open Google Search Console, a free tool from Google that shows how your site appears in search.
  2. Paste one of your main marketing URLs into URL Inspection and run a live test.
  3. Look at the rendered HTML and screenshot (both come from the live test, not the indexed version). Does the main text, the headings and the links appear?
  4. Repeat for a blog post or any page with dynamic content from your database.
  5. In Search Console's page indexing report, check that your important pages are indexed and no page is blocked.
  6. Run Google's PageSpeed Insights report on the same pages. Look at the field data section first (real visitors over the previous 28 days), then the lab results, which are a single test under fixed conditions and may differ from field data.

Pass: the text and links appear in the rendered HTML, pages are indexed and field data is acceptable. In that case, you may only need to fix titles, descriptions, the sitemap and speed settings inside Bubble, and moving is optional. Fail: pages show blank or partial content, key pages are not indexed, or field data is poor and you cannot fix it. Then a move makes sense.

Your options

OptionWhat it isGood fitWatch for
Fix inside BubbleComplete titles and descriptions, sitemap, redirects, trim page weightFew marketing pages, tests passLimits of what Bubble exposes
Prerender or proxy service in frontA service that serves a ready-made copy of your pages to crawlersYou cannot move yetAnother bill and another thing to run. Bubble's docs do not cover it, so check the service's own terms
AI website platformA platform where you describe the site and it builds and hosts pagesA small marketing site that your team edits by chatCheck export, redirects, form handling and what you can edit by hand. Compare in moving a site to Ploy
Website builder or CMSA visual builder or a content management system for pages and a blogEditing by non-technical staffPlugin or template lock-in, speed varies
Custom site, for example Next.jsNext.js is a popular framework for building fast sites that send finished pages to the browserContent-heavy sites, special layouts, a link to your appNeeds a developer; plan who edits content

If you are also weighing app builders for the app itself, the library compares them in Bubble alternatives and Bubble vs AI app builders. For moving the app to code, see the cost to move from Bubble to code and Bubble agency or custom code. This article is only about the marketing pages.

The split: marketing site on the main domain, app on a subdomain

Decide, page by page, which side each belongs to:

  • Marketing site: home page, service pages, pricing, about, blog, guides, landing pages, contact. Everything a stranger finds from search.
  • App: sign-in, dashboards, account pages, anything behind a login.

The app moves to a subdomain such as app.yourbusiness.com and the marketing site takes the main domain. A "Log in" link in the header joins them. Logged-in pages should not be indexed. The marketing site no longer shares Bubble's code, so app changes cannot slow it, and app traffic does not touch your marketing site. Moving the app itself is a separate project and often can wait.

Build the redirect map

This step protects your traffic. Google's site-move guidance (read it in full before you start) says to list old addresses, map each one to its new address, and use permanent server-side redirects, code 301 or 308.

  1. List every old URL. Sources: Bubble's sitemap (if you turned on the exposed sitemap, each database item of a dynamic page type counts as a page), Google Search Console's performance report, your analytics, and a crawl of the live site. Include blog posts and landing pages.
  2. Rank them. Mark the pages with the most clicks, links and leads. Those must be perfect.
  3. Decide the new address for each. Keep the same path where you can: the fewer changes, the lower the risk. The more you change at once (structure, text and design), the harder it is to tell what caused a drop, so change as little as you can.
  4. Write one row per old URL: old address, new address, status code, notes.
  5. Pages with no match: redirect to the nearest related page, not always the home page. Google says not to redirect many old pages to one irrelevant page. If a page is truly gone, a not found or gone response is correct.
  6. Avoid chains. Send each old address straight to its final address. Google says to send old addresses straight to the final address and, if that is not possible, keep chains to about 3 hops and never more than 5.
  7. Check query strings and case. Bubble's redirect fields use full addresses with the protocol, match exactly unless you use wildcards, and carry query strings over. Your new host may behave differently, so test.

Where the redirects live matters. Once your main domain points at the new host, Bubble no longer answers requests for old addresses. So the new host must hold the redirects for every moved address, and any address that stays on Bubble, such as the app on its subdomain, needs its own rules. A sample row:

Old addressNew addressCodePriority
/services/web-design/services/web-designnone (same path)High
/blog/old-post-title/blog/old-post-titlenoneMedium
/pricing-v2/pricing301High
/dashboardapp.yourbusiness.com/dashboard301Low

The migration, step by step

  1. Record a baseline. Export Search Console performance by page for the last 3 months, a list of indexed pages, a crawl of titles and descriptions, and your current conversions.
  2. Build the new site on a test address and keep it out of search with noindex (a tag that tells search engines to skip a page). Copy titles, descriptions, headings, text, images with their alt text, internal links and structured data across.
  3. Check the new site: every important page, forms, tracking, and mobile view.
  4. Prepare the domain. Google advises verifying every version of the old and new site in Search Console, such as www, non-www, HTTP and HTTPS. A common extra step, which is my habit and not in Google's page, is to lower the DNS time-to-live, the time other systems keep your address cached, a day or two ahead of the change. See custom domain, DNS and SSL setup and pointing a domain without breaking email.
  5. Export what you need from Bubble before you cancel anything: content, your page text, images and any data you want to keep. Check Bubble's current export options for your plan.
  6. Launch. Remove the test noindex. Confirm the live site has a robots.txt that allows crawling and a sitemap that lists only new pages. Switch the domain.
  7. Test redirects the same day, in batches, with a script or a crawl tool, and spot-check with URL Inspection.
  8. Submit the new sitemap in Search Console and remove the old one. Update links in your email signature, profiles and ads.
  9. Keep the redirects. Google's site-move page says at least a year. Its Change of Address page says at least 180 days, and longer if you still get search traffic to the old addresses. Use the longer. Change of Address in Search Console applies to moves from one domain or subdomain to another, not to moving pages within the same site, http to https, www changes, or a change of host with the same addresses. If your main domain stays the same, you do not use it.
  10. Keep your Bubble plan as long as the app needs it. Cancel only what you replaced.

After the move: what to check and when

Google says to expect ranking to move around for a while, and for a medium-sized site it can take a few weeks or more before new addresses show. So do not judge on day two.

WhenCheckPassFail, then do this
Day 1Top 20 old URLs redirect to the right new pageAll return a permanent redirect once, to the right placeFix the rule, retest
Day 1robots.txt and meta tagsNo block, no leftover noindexRemove it now
Week 1Search Console: new pages discovered, errorsPages appear and are indexedInspect URLs, resubmit sitemap
Weeks 2 to 6Clicks by page, against the baselineBack near baseline, or risingCheck 404s, chains, canonicals, content you changed
Week 4PageSpeed field dataImprovedFix largest image and scripts first

If clicks fall and stay down, work the diagnosis list in rankings dropped after a website migration.

A worked example, with made-up numbers

A coaching business has 25 marketing pages and 40 blog posts on Bubble. Its app, a booking and client area, has 600 users. The plan: put the 65 marketing pages on a new site, keep the app on the app subdomain.

  • Old URL list: 65 marketing addresses plus 6 app pages that stay on Bubble.
  • Same path kept for 58 addresses, so no rule is needed for them beyond the move itself.
  • 7 addresses change (for example an old pricing page), so 7 redirect rows, each one hop.
  • The 10 pages with the most clicks are checked by hand on launch day.

The numbers are invented. The method is the point: keep paths the same, redirect the few that change, and check the best pages by hand.

Who should not move yet

  • You have a handful of pages, they are indexed, and the test passes. Fix titles and speed in Bubble instead.
  • Your whole product is the app and the marketing is one page.
  • You cannot name who will edit the new site. A faster site nobody updates is worse.
  • You are about to redesign the content too. Move first, redesign later, so you can tell the causes apart.

How I'd approach this

I would test first, split second, and redesign last. Measuring what Google sees takes an afternoon and decides whether you are solving a real problem. If you move, I would keep the paths as close to the originals as possible and spend the time on the redirect map and the checks.

First-week plan: day one run URL Inspection and PageSpeed on five key pages and save the results. Day two export your Search Console baseline and list every URL. Day three decide the split and the new stack, and who will edit it. Day four draft the redirect map for the top 20 pages. Day five get two written quotes or a build plan, and ask each builder how they handle redirects, forms and your content editing. Decision rule: if the test passes, fix in place. If it fails and you have more than a few dozen pages, move the marketing side.

If you want the marketing site rebuilt on a faster stack and connected to your app, Blur Studio builds that custom version, including finishing a half-built move and looking after it afterward: see what that includes.

Questions people ask

Is Bubble bad for SEO?

No blanket answer is supported. Bubble documents titles, descriptions, a sitemap, robots.txt and redirects. Test your own pages with Search Console's URL Inspection and PageSpeed Insights, and decide from what you see.

Does Bubble render pages on the server?

Bubble's own help pages do not say. Forum users discuss JavaScript rendering, but those are user posts and some are old, so they are opinion, not Bubble's position. Run a live test in URL Inspection on your pages to see the rendered text.

Should I move the whole app or just the marketing pages?

Often just the marketing pages. The app can stay on a subdomain while you decide about it separately. For app costs see the cost to move from Bubble to code.

How do I redirect old Bubble URLs to a new site?

Make a map of old to new addresses and set permanent redirects on the new host, since Bubble stops answering once your domain points elsewhere. Go straight to the final address with no long chains, and keep the redirects for at least a year.

Will I lose rankings when I move?

Expect movement for a few weeks or more. Careful redirects, the same page content and a clean sitemap reduce the risk. If clicks stay down, follow the migration ranking fix list. Nobody can promise a result.

What is the best Bubble alternative for a marketing site?

It depends on who edits it. An AI website platform or a website builder suits small teams, a CMS suits content-heavy sites, and a custom Next.js site suits special needs. The options table above compares them. For the app side see Bubble alternatives.

Can I keep my Bubble app and use a different site for marketing?

Yes. Put the app on a subdomain such as app.yourbusiness.com, and link to it from the new site. Forms and sign-ups on the new site can send data to the app. See connecting a marketing site to your own app or database.

What should I export from Bubble before I leave?

Your page text and images, any data you want to keep, your sitemap and a list of URLs, and the settings for redirects. Check Bubble's current export options for your plan, and keep the app plan active while the app still runs there.

More in this topic: Websites: custom builds, portals, lead capture and site care (9 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…