AI-built apps ยท November 2026
Short answer: a Lovable app is a React app, not a WordPress theme, so there is no button that turns one into the other. What people usually want is one of four things: the app and the WordPress site under the same name, the app inside the WordPress hosting they already pay for, a site their team can edit in WordPress, or a blog written in WordPress that shows up inside the app. Each is below, with the steps and the seven things that most often break on the way.
Lovable's own documentation says apps created from May 13, 2026 use
TanStack Start, which "runs server code", while older apps use React + Vite and "build to static files". This
decides almost everything below. To check: open package.json in Lovable's code view (or in your
GitHub copy). If @tanstack/react-start is listed under dependencies, it is the newer kind. If not, it
is the older, static kind. You can also ask Lovable in the project chat which stack the project uses.
Why it matters: ordinary WordPress hosting runs PHP for WordPress and serves files. It can serve the older kind (plain files). The newer kind needs a host that runs a Node server, which most shared WordPress plans do not offer.
| Route | What you get | Works with | Good when |
|---|---|---|---|
| 1. Side by side | WordPress stays at yoursite.com, the app lives at
app.yoursite.com, with links between them. | Both kinds of app. | Almost always. Each tool keeps doing what it is good at, and nothing is rebuilt. |
| 2. A folder on your WordPress hosting | The app at yoursite.com/app/, served
from the same hosting as WordPress. | The older, static kind only. | You want one host and one bill, and the app is already built. |
| 3. Rebuild the pages in WordPress | A WordPress site that looks like your Lovable design, editable by your team in the WordPress editor. | Any, but only the look moves. | It is a marketing site with no logins or database, and non-developers must edit it. |
| 4. WordPress behind the app | Posts written in WordPress, shown inside the Lovable app. | Both kinds of app. | You want a blog or news section without building an editor. |
app. Leave the records that point to WordPress alone.https://app.yoursite.com to the allowed redirect addresses
(in Supabase: Authentication, URL Configuration). Then link from the WordPress menu to the app.npm install.vite.config.ts add base: '/app/' (the folder name,
with both slashes). If the app uses React Router, give the router the same base:
<BrowserRouter basename="/app">.VITE_ values (for example its Supabase address
and public key) in a .env file, then npm run build. Lovable's guide is plain about it:
variables starting with VITE_ "are embedded at build time, not runtime".dist into a new folder app next to WordPress's
files (usually in public_html), with your host's file manager or SFTP. Do not overwrite WordPress's
own index.php or .htaccess.app, so a refresh on any page of the app loads the
app instead of WordPress's "page not found":
FallbackResource /app/index.html
If your host ignores that line, use the longer form:
RewriteEngine On
RewriteBase /app/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /app/index.html [L]
This is for Apache and LiteSpeed hosts, which most WordPress plans use. On Nginx, the host's panel
needs a rule that sends unknown addresses under /app/ to /app/index.html.https://yoursite.com/app to the login provider's allowed redirect addresses, then test
as a new user: sign up, log out, log in, refresh on an inner page.Use the Lovable site as the design and build the same pages with a block theme or a page builder. Copy the text, images and colours across; ask Lovable for the exact colour codes and fonts it used. Be clear about what does not come along: sign-ups, accounts, payments and anything stored in the app's database stay in the Lovable app. If the site has those, use route 1 for the app and rebuild only the public pages. Keep old addresses working: if a page moves, add a 301 redirect from its old address so search engines and old links follow.
A WordPress site has a public list of its posts at
https://yoursite.com/wp-json/wp/v2/posts (WordPress's REST API; 10 posts at a time unless you pass
per_page). Ask Lovable to "show the latest posts from this address, with title, date and a link", and
the app reads them from WordPress. Your team keeps writing in WordPress as before.
If the browser blocks the request, either WordPress must allow your app's address to read it, or the app fetches the posts from its server or a backend function instead of the browser. Some security plugins switch this list off; check the address in a browser first.
index.php, and /app/dashboard is not a real file. The
app's own .htaccess (route 2, step 5) takes those addresses back./assets/... files. The app was built
for the root of a site but uploaded into a folder, so it looks for its files in the wrong place. Set
base: '/app/', build again, upload again.VITE_ values were missing when you built, so
they were baked in empty. Setting them later on the server changes nothing for this kind of app: put them in
.env and build again.www if you use both), and change the site
address there if the old one is gone..output directory" that is started with node .output/server/index.mjs. Use route 1: keep
it on Lovable or on a host that runs Node, under a subdomain.index.html. Exclude /app/ from the cache, or clear it after every upload.
Vite gives the files in assets new names when they change, so index.html is the one file
that must never be kept old.In a private browser window, on a phone as well as a computer: (1) open the app's address and sign up as a brand-new user. (2) Go two pages deep and press refresh. (3) Log out and back in with every sign-in button you show. (4) Do the main task from start to finish, payment included. (5) Go from a WordPress page to the app and back, and check the links work both ways. If all five hold, the seven problems above are not in your app.
This is a checklist, not a study: we have not counted how often each problem happens. Read on November 21, 2026: Lovable's FAQ and its guide to hosting outside Lovable (the two kinds of app, the build output, build-time variables, redirect addresses), Vite's build guide (the base path), Apache's mod_dir documentation (FallbackResource) and WordPress's REST API reference (the posts list). The rest (caching, frames, testing as a new user) is general engineering practice. Lovable, WordPress and hosts change their menus often, so check their pages if something here does not match what you see. Urgisoft is not affiliated with Lovable, WordPress, Automattic or Supabase.
A blank page after publishing: six causes. Login and Supabase errors: seven causes. Stripe payments not working: seven causes. Six security checks you can run yourself. Health app? What HIPAA needs from an AI-built app. Deploy to Vercel or Netlify. Base44 bug fixing. Replit app bug fixing. Fix AI-generated code: seven common problems. Convert a Lovable app to iOS: three routes and seven traps. Lovable app not showing in Google? Seven fixes. Slow on phones? Our demo shop, measured before and after: 14.5 s to 1.4 s. Not sure which problem you have? A ten-minute check.
We fix apps made with Lovable, Bolt, Base44, Replit, Cursor and other AI builders, and get them working live: the blank page after a move, the login that sends people to the old address, the refresh that shows "not found", the page that is slow on a phone, and we tell you in plain words what was wrong. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from $150. No fix, no charge. We never ask for your password. Rebuilding a whole site as a WordPress theme is not part of the gig.
See the gig on Fiverr