IQDeskLovable → WordPress Open the converter

Guide

Lovable Site Maintenance After WordPress

Once your Lovable site runs on WordPress, maintenance is four things: keep WordPress, plugins and the theme updated, keep backups, check that forms and pages still work, and edit content in the Site Editor instead of the code. Most of it takes about fifteen minutes a month. The one habit to build early is this: edit the live WordPress site, not the old Lovable project, or the two will drift apart. Below is a routine you can follow and a short list of the jobs that still need a developer.

Decide which site is the source of truth

The day you launch on WordPress, the WordPress site becomes the real site. The Lovable project is now a design reference, nothing more. If you keep editing both, your content will drift and you will not know which page is correct.

Write that decision down somewhere the whole team sees. Then make the practical changes that enforce it.

Keep the Lovable project, though. It is cheap insurance if you ever need to re-convert a page or check how a section looked. If it stays online, point your domain at WordPress and leave the Lovable preview URL as an internal reference.

  • Content changes happen in WordPress: Pages, Posts and the Site Editor.
  • Design tokens (colors, fonts, spacing) live in theme.json in the theme.
  • The Lovable project stays read-only, as a visual reference and a backup of the original design.
  • Your domain points at WordPress. See Lovable custom domain if you have not moved it yet.

The monthly routine

WordPress maintenance is repetitive by design. A short checklist beats a big quarterly cleanup, because small updates rarely break anything and large ones sometimes do.

Run these steps once a month, or after any update notice that mentions security.

  1. Back up first. Use your host's backup feature or a backup plugin. Keep at least one copy off the server. Never update anything without a backup you can restore.
  2. Update plugins, one group at a time, from Dashboard → Updates. Reload the front page after each group.
  3. Update WordPress core when a new version appears. Block themes depend on core for the Site Editor, so staying current matters more than on a classic theme.
  4. Submit a test through your contact form and confirm the message arrives in the real inbox. Form delivery breaks silently more often than anything else.
  5. Click through every page in the main menu, on desktop and on a phone. Look for stacked columns that look wrong and images that fail to load.
  6. Check Search Console for new coverage errors and for pages that lost impressions.

Updating the theme without losing your edits

The converted theme is a normal WordPress block theme. It does not auto-update, because it did not come from the theme directory. That is a feature: nothing will overwrite your work by surprise.

It also means you control when it changes. If you re-run the conversion later — say you redesigned a page in Lovable — you get a fresh theme ZIP. Uploading it over the existing theme replaces template files and theme.json. Edits you made in the Site Editor are stored in the database, not in the theme files, so they survive, but they can also mask the new template. In the Site Editor each customised template shows a Reset option that drops your override and shows the theme file again.

Our advice: before you upload a new version of the theme, note which templates and template parts you changed in the Site Editor. After the upload, check each one and reset the ones that should follow the new design.

If you only changed words and images on a page, you are safe. Page content lives in the page, not in the theme.

  • Template and template part edits are database overrides; reset them in the Site Editor to go back to the theme file.
  • Page content is stored per page and is not touched by a theme update.
  • theme.json is replaced by a new theme ZIP, so re-apply any manual palette edits you made in the file.
  • Child themes are an option if a developer customised the theme heavily. See the WordPress theme handbook for the pattern.

What still needs a developer

Most maintenance is clicking. A few jobs are not, and it helps to know which before you promise a deadline.

Anything that was interactive in Lovable and did not survive the conversion stays a development job. Custom React state, dashboards, API calls, authentication and Supabase-backed features do not become WordPress features on their own. Supported features lists what converts, what is approximated and what is left out, and Lovable Supabase and WordPress covers the data side.

A plugin that breaks a page after an update is also usually a developer job, unless deactivating it fixes things. Deactivate, confirm the page recovers, then decide whether to replace the plugin or get help.

  • Custom interactivity — state, event handlers, dashboards, logged-in screens.
  • Third-party widgets, iframes, canvas and Lottie — these need a block, a plugin or custom code.
  • Performance work beyond caching and image sizes. Lovable site speed in WordPress explains what changes after the move.
  • PHP errors after an update — restore the backup first, then diagnose.

Keep the SEO settings you migrated

The conversion writes per-page titles and descriptions into Yoast, Rank Math or SEOPress when they came from TanStack Start heads. Those values now live in the SEO plugin, not in the code. Edit them there.

Two settings are worth re-checking after any big change. Under Settings → Reading, make sure "Discourage search engines from indexing this site" is unchecked on the live site. Under Settings → Permalinks, confirm the structure has not changed; changing it rewrites every URL.

If you ever change a slug, add a redirect from the old URL. Old links and old rankings point at the old path. Lovable redirects in WordPress covers how to keep them working, and Lovable SEO plugin in WordPress covers the plugin side.

  • Unchecked — "Discourage search engines from indexing this site" in Settings → Reading on production.
  • Stable — the permalink structure. Decide once, then leave it.
  • Redirected — every slug you rename.
  • Reviewed — titles and descriptions after you rewrite a page.

When you redesign in Lovable again

Some teams keep prototyping in Lovable and push the result to WordPress when it is ready. That works, as long as you treat it as a page-level job rather than a whole-site replacement.

Build or redesign the page in Lovable, export it, and run it through the converter. The review screen shows the converted page next to the original inside WordPress Playground, so you can see the difference before anything touches your live site. Conversion, review and the theme download are free, and every account includes two free AI-fix attempts.

Then move only what you need. Copy the pattern for the new page into your live theme, or rebuild that one page in the Site Editor using the converted version as the reference. That keeps your existing templates, menus and SEO fields intact.

Test it on a staging copy first. Lovable staging site explains how to set one up and what to check before you switch.

FAQ

How often should I update a WordPress site converted from Lovable?

Check for updates monthly, and apply security updates as soon as they appear. Always take a backup before updating plugins or WordPress core. After updating, reload the front page and submit a test through your contact form to confirm nothing broke.

Does the converted theme update itself?

No. The theme was generated from your project, so it is not in the WordPress theme directory and it does not auto-update. You update it only when you choose to, by uploading a new theme ZIP. That also means no update will overwrite your work unexpectedly.

Can I keep editing my site in Lovable after moving to WordPress?

You can keep the Lovable project as a design reference, but the live site should be edited in WordPress. Editing both means the two versions drift apart and nobody knows which page is correct. If you redesign a page in Lovable, convert it again and move just that page across.

Will a WordPress update break my converted theme?

It is unlikely, because the theme uses standard block markup and theme.json. Core updates occasionally change Site Editor behaviour, so check your templates after a major release. Keep a backup so you can restore quickly if a page looks wrong.

Do I still need to pay for Lovable hosting after moving to WordPress?

Not for serving the live site, since WordPress serves it. Your Lovable plan still matters if you want to keep editing the project or need the ZIP download, which requires a paid plan. GitHub sync works on every plan, so you can keep the code without hosting there.

Keep reading