Lovable Staging Site: Test Before You Switch

What a staging site is for here

Your Lovable app is live and serving visitors. The WordPress version is new and untested. A staging site lets both exist at the same time, so you can compare them page by page without risk.

The move from Lovable to WordPress is not a database migration. It is a theme install plus a domain switch. That makes staging simple: install the theme somewhere private, look at it, fix it, then repoint DNS.

Three things are worth testing before launch, and each of them is easier on a staging copy than on a live site.

Content — every page from the Lovable app exists, with the right headings, images and links.
Design — colors, fonts, spacing and the header and footer match what theme.json and the patterns produced.
Plumbing — forms send mail, the front page is set, slugs match the old URLs, SEO fields are filled in.

Three places to stage a converted theme

You do not need a complicated setup. Pick the one that matches how far along you are.

The first option costs nothing and needs no hosting account. The other two behave like real servers, which matters once plugins and email are involved.

WordPress Playground, in the browser — the review screen in our converter opens the converted site next to the original inside Playground. Good for a first look at layout and typography. Nothing is saved on a server, so it is not where you test mail or DNS.
A subdomain on your host — something like staging.example.com with WordPress installed. Closest to the real thing, and many hosts offer a one-click staging copy.
A local install — WordPress on your own machine. Fast, private, and fine for theme work. Email and external callbacks are harder to test locally.

Set up the staging site step by step

This is the sequence we recommend when you already have the converted theme ZIP. If you have not converted yet, start with how to convert Lovable to WordPress.

Do step two before step three. A fresh WordPress install is indexable by default, and a staging copy on a public subdomain can be crawled within hours.

Install WordPress on a subdomain, a temporary host URL or a local environment.
Open Settings → Reading and check "Discourage search engines from indexing this site". Save.
Upload the theme under Appearance → Themes → Add New → Upload Theme, then click Activate. Pages are created on activation and the front page is set.
Install the plugins the theme expects — Contact Form 7 if the Lovable app had a form, WooCommerce if it had products, and your SEO plugin: Yoast, Rank Math or SEOPress.
Open the live Lovable site in a second window and walk the two side by side, page by page.
Fix what is off in Appearance → Editor, or send the AI fix agent at it from the review screen.
Repeat the walkthrough after each round of fixes, then move on to the launch checks.

Keeping staging out of Google

Two copies of the same content on two public URLs is not what you want while you test. The checkbox in Settings → Reading is the simplest guard: it asks search engines not to index the site. Respectable crawlers honor it.

It is a request, not a wall. If the staging URL is genuinely sensitive, add HTTP basic auth at the host level, or use a host staging environment that is password protected by default. Local installs are private by nature.

It is also the single most common launch mistake. A site that goes live with the box still checked can sit unindexed for weeks before anyone notices. Make unchecking it the last thing you do.

One more detail. Your live Lovable site stays indexable the whole time, which is correct. You want it serving traffic until the moment the domain moves. What crawlers see on a Lovable app is covered in is Lovable good for SEO?.

What to compare, page by page

Open the Lovable app and the staging site in two windows at the same width. Work through one page at a time instead of skimming the whole site. A list keeps it honest.

Expect close, not pixel identical. The converter produces real WordPress blocks, so spacing and responsive behavior follow WordPress rules. Columns stack on mobile. Some pieces are approximated on purpose: carousels, tabs and modals arrive in their default state, animations in their final state, fixed-height cropped boxes as plain blocks. Supported features lists all of it.

Some things never arrive, and staging is where you decide what to do about them. Custom React state, event handlers, Supabase data, authentication, dashboards, API calls, canvas, Lottie and third-party widgets are not converted. Plan a plugin or a developer for those, or drop them.

Pages — every route from the Lovable app has a WordPress page, with the slug you expect.
Front page — Settings → Reading → "Your homepage displays" points at the right page.
Navigation — the header menu has every item, and every link resolves.
Titles and descriptions — for newer TanStack Start apps these come from each route's head() and land in your SEO plugin. Older React + Vite apps had no per-page meta to copy, so write them now.
Forms — submit one and confirm the mail arrives at a real inbox.
Images — nothing broken, logo in place, aspect ratios sane.
Mobile — resize the window and check the stacked layout on each page.

Going live without a gap

When staging looks right, the switch is mostly DNS. Plan it for a quiet hour and keep the Lovable app running until the new site answers.

If your domain is currently on Lovable hosting, your DNS records move from Lovable to your WordPress host. Propagation is not instant, so some visitors see the old site and some the new one for a while. That is normal and harmless as long as both work. For the record details, check your host's instructions and Lovable's documentation.

Before you touch DNS, run these four checks on staging. After DNS, run them again on the real domain.

Uncheck "Discourage search engines from indexing this site" in Settings → Reading.
Confirm permalinks under Settings → Permalinks, and check that old URLs still resolve. Redirects from public/_redirects are carried over by the converter.
Submit the sitemap your SEO plugin generates to Google Search Console once the domain points at WordPress.
Keep the Lovable project for a few weeks. It is your reference and your fallback if something was missed.

FAQ

Does Lovable have a built-in staging site?

Lovable hosting serves your published app at its own URL, and you can add a custom domain. For anything about preview environments or separate staging URLs on Lovable, check Lovable's documentation at docs.lovable.dev. When you move to WordPress, staging is whatever private WordPress install you choose: a subdomain, a host staging copy or a local install.

Will a staging site hurt my SEO with duplicate content?

Not if you keep it out of the index. Check "Discourage search engines from indexing this site" under Settings then Reading before the staging URL is reachable. For extra safety, put the staging site behind a password at the host level.

Can I test a converted Lovable theme without buying hosting?

Yes. The IQDesk converter's review screen runs WordPress Playground in your browser and shows the converted site next to the original. Conversion, review and the theme download are free, and every account includes two free AI-fix attempts. Playground is right for checking layout and design, not for testing email or DNS.

What happens to my live Lovable site while I test?

Nothing. Converting the code and installing a theme elsewhere does not touch the Lovable project or its hosting. Your live site keeps serving visitors until you change the domain's DNS records.

How long should I keep the Lovable project after launch?

Keep it at least a few weeks. It is the reference you compare against when someone reports a missing section, and the fallback if a page turns out to be incomplete. There is no technical reason to delete it on launch day.

Convert a Lovable site to WordPress All guides