Lovable and WordPress work together in one of two ways. Either the Lovable app reads and writes your WordPress content through Lovable's WordPress connector (WordPress as a headless CMS), or the two simply live side by side: WordPress on yoursite.com, the Lovable app on app.yoursite.com. What doesn't work is putting a Lovable app inside WordPress as a theme or a page. Lovable builds a React app, not PHP templates, and there's no export to WordPress.
Most founders who search for this already have a WordPress marketing site with a few years of blog posts and some rankings, and a new product built in Lovable. The question is how to join them without breaking either. We checked Lovable's self-hosted WordPress docs on November 13, 2026.
What the connector actually does
You create an Application Password in WordPress (Users > Profile, scroll down), then add a "WordPress (self-hosted)" connection in Lovable's Connectors with the site URL, the username and that password. Lovable checks it against the users/me endpoint before saving. From then on your app can list posts, pages and custom post types, upload media, read categories, tags and users, and call REST routes that plugins add. It can also write: the docs' own example prompt is a form that creates a draft post on your WordPress site.
Requirements are short and one of them bites. HTTPS, WordPress 5.6 or later, a user with the right role, and non-plain permalinks. If your site still uses ?p=123 style URLs, every call fails with rest_no_route and the error doesn't tell you why. Settings > Permalinks, pick anything but Plain. On a site with years of posts that changes every URL, so do it with redirects, not on a Friday.
WordPress.com sites need a different connector, and WooCommerce has its own too. The self-hosted one won't touch plugins, permalinks, hosting or SSL for you.
The catch: one WordPress account for everyone
This is the part to think about before you click Save. The connection is one shared WordPress account. There's no per-user login. Whatever role that account has, your app has, for every visitor who can reach the feature that calls it.
We've seen people paste in their own admin password, because it was the first one they had. Don't. If a Lovable-built form can create drafts, then anyone who finds that form can create drafts, and with an Administrator's Application Password the app could also delete pages and read every user's email address through the REST API. Make a separate WordPress user for the app with the lowest role that does the job: Contributor if it only creates drafts for review, Author if it publishes, never Administrator. And if the app only shows published posts, it may not need a password at all, since /wp-json/wp/v2/posts is public on a default install.
Revoke the password in WordPress the day you stop using it. Lovable won't rotate it for you, and if you revoke it, the connection in Lovable has to be updated before anything works again.
Also put a rate limit or a login in front of any feature that writes. Spam bots love a public form that turns into WordPress posts.
Three setups, and which one we'd pick
1. Side by side (most people should stop here). WordPress keeps yoursite.com, the blog and the rankings. The Lovable app goes on app.yoursite.com via Lovable's custom domain setup. The "Log in" and "Start free" buttons on WordPress link to the app. Nothing is shared except the domain, nothing can break the other side, and your SEO stays where it was earned. It's boring and it's right for 80% of cases.
2. Headless: Lovable front, WordPress content. The Lovable app becomes the public site and pulls posts from WordPress through the connector. Your editors keep the WordPress admin they know. This makes sense when the product and the content really need to be one experience, say a marketplace with editorial guides on the same pages.
Check two things first. Can Google see the posts? Older Lovable projects are single-page apps that build the page in the browser, which is the problem in our Lovable SEO post. Newer projects render on the server, but only if the WordPress content is fetched on the server too. Open a post, view source, and search for a sentence from the article. If it isn't there, Google mostly isn't reading it either. And keep the old URLs: WordPress links like /2024/05/some-post/ need to land on the same post on the new site, or need a 301, or the rankings go.
3. Move off WordPress completely. Copy the posts into the app and shut WordPress down. Fine for a site with 15 posts and no traffic. For anything with real search traffic it's a migration project, not a weekend, and it gets you nothing setup 1 doesn't, unless you're trying to drop the WordPress hosting bill and plugin updates.
Embedding the Lovable app in a WordPress page with an iframe, which people also try, is the worst of all of these. Auth cookies get blocked as third-party in Safari, the page scrolls inside a page, and Google indexes an empty frame.
Where it goes wrong after launch
The connector itself is fine. What breaks is the stuff around it. Someone updates a security plugin on WordPress that disables Application Passwords or the REST API for "hardening", and the blog section of the app goes blank. A host puts the WordPress site behind a bot challenge, and calls from the app start getting HTML instead of JSON. Neither shows up in Lovable's preview, because nothing changed in Lovable.
So if the app depends on WordPress, monitor the WordPress side: a simple uptime check on /wp-json/wp/v2/posts?per_page=1 catches both.
If you want the app launched next to an existing WordPress site with the domain, auth and redirects done properly, our Lovable to production service starts at $500 and takes 5 to 7 days. Or just tell us about your setup and we'll say which of the three fits.
Originally published on lovable2live.com. Aakash Verma, software developer and founder of Lovable 2 Live.

Top comments (0)