- Load content from WordPress — list and read posts, pages, and related fields your account can access
- Build dynamic pages and layouts driven by CMS content instead of hard-coding copy in the repo
- Show blogs, marketing sections, and resource pages that stay up to date when editors publish in WordPress
- Combine WordPress content with the rest of your app — for example, sync or display selected posts alongside your own data
- Automate publishing workflows — for example, create or update drafts when you describe that behavior in chat (within what the API allows for your site)
Common use cases & example apps
| Example app | Example prompt | Description |
|---|---|---|
| Marketing and landing pages | Use WordPress and build a marketing site where the homepage and key sections load titles, body, and images from my WordPress site. | Ship pages powered by CMS content. The app fetches posts or pages from WordPress and renders them as components so editors can update copy and media without changing app code. |
| Blog and editorial sites | Use WordPress and build a blog that lists recent posts and shows each post’s content, featured image, and excerpt. | Run a blog backed by WordPress. The app loads post lists and detail views from the API and reflects new publishes from the WordPress dashboard. |
| Resource or help center | Use WordPress and build a help center where each article is a WordPress page with search and categories. | Centralize articles in WordPress. The app queries pages or posts and builds navigation and article views from your CMS structure. |
| Product or listing-style content | Use WordPress and build a catalog-style page that shows items I maintain as posts (or custom content) with filters. | Present structured listings from WordPress. The app reads entries and fields exposed by the API and renders filters and cards based on your content model. |
| Event and announcement pages | Use WordPress and build a page that loads upcoming events from WordPress and sorts them by date. | Highlight time-based content. The app fetches posts or pages that represent events and orders them using dates you store in WordPress. |
| Editorial or publish workflows | When I submit this form, create a draft post on WordPress with the title and body I provide. | Turn submissions into drafts. The app creates or updates content through the API so editors finish work in WordPress. |
How WordPress connections work
- One connection is tied to the WordPress.com user who completes sign-in.
- That user’s visible sites and allowed actions follow WordPress.com’s rules and the scopes granted at authorization.
- You can create multiple connections (for example, separate accounts or environments) and link different projects to different connections where your workspace setup allows it.
How to connect WordPress.com
Workspace admins and owners can connect Linear. When a connection is created, WordPress.com becomes available across all projects in the workspace.Prerequisites
- A WordPress.com account that can access the target site or sites
- Lovable workspace admin or owner role
Set up your WordPress connection
Open the WordPress connector
Go to Settings → Connectors → Shared connectors and select WordPress.com.
Name the connection
In Display name, choose a clear name (for example,
WordPress Marketing or WordPress Staging).Use WordPress in a project
In chat, describe what you want using plain language and mention WordPress when it matters. For example:FAQs
Is this WordPress.com or WordPress.org?
Is this WordPress.com or WordPress.org?
The connector is built around WordPress.com. Self-hosted WordPress sites are a different product; they may still work with some WordPress.com or Jetpack flows depending on your setup, but you should assume this integration targets WordPress.com unless your site is explicitly connected in a way WordPress.com’s API supports.
Who pays for WordPress.com?
Who pays for WordPress.com?
WordPress.com billing, plans, and any API-related limits are between you and WordPress.com. Lovable does not replace your WordPress.com subscription or quotas.
Who can create or delete the connection?
Who can create or delete the connection?
Workspace admins and owners add and remove WordPress connections. Other roles may still use the connector in projects when your workspace and project permissions allow it.
Are my WordPress tokens visible in my project?
Are my WordPress tokens visible in my project?
No. With gateway-based connectors, credentials stay in the gateway. Your project does not store the OAuth tokens in plain view. See Gateway-based connectors.
Can each visitor to my app sign in with their own WordPress account?
Can each visitor to my app sign in with their own WordPress account?
The shared connector represents the connection you configured at the workspace level, not per-end-user WordPress login. If you need each user to authenticate to WordPress individually, you typically design a custom auth or API flow in your app rather than relying on this shared connector alone.
What if authorization fails or a site is missing?
What if authorization fails or a site is missing?
Limitations & troubleshooting
- API coverage depends on WordPress.com, your site type, and permissions granted at connect time. Not every WordPress admin task is available through the API.
- Gateway limits apply per connector and project as described in Gateway-based connectors.
- If something works in the WordPress.com dashboard but not in your app, check whether the action is exposed to the API for your site and account.
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.