Skip to main content
WordPress (self-hosted) is an Available Commerce & Website integration for a WordPress site on your own server or a web host. It signs in to the site’s own REST API with an application password. For a site on WordPress.com, use WordPress instead.

​
What you need

  • WordPress 5.6 or later, served over https.
  • An Editor or Administrator account. An Author account connects, but WordPress only lets it work with its own posts, not pages.
  • The REST API reachable from the internet. Some security plugins turn it off or block application passwords.

​
Connect

1

Create an application password

In WordPress admin, open Users -> Profile and scroll to Application Passwords. Enter Daoco as the name, choose Add New Application Password, and copy the password. WordPress shows it once.
2

Open the WordPress (self-hosted) card

In daoco, open Connections -> Integrations -> Commerce & Website and choose WordPress (self-hosted).
3

Enter the site address, username, and password

Enter your site address, for example https://yoursite.com, your WordPress username, and the application password. Choose Connect. daoco signs in to check them before saving, and tells you if the account cannot publish.
4

Use it from chat

Ask /integration to list your pages, or ask daoco to put a saved page into WordPress.
Do not paste the application password into chat. daoco encrypts it when you enter it in the connection form. To end daoco’s access, revoke the password under Application Passwords in WordPress and disconnect here.

​
Drafts and publishing

daoco always creates new work as a WordPress draft, which visitors cannot see, and returns the edit link. Posts are for dated blog entries; pages are for standing pages such as a comparison, FAQ, landing page, or case study. A page from your page library is sent as saved, with its body converted to HTML. Putting something live is a separate step. Publishing a draft, changing a page that is already live, and taking a page down each change what visitors see, so each one goes through your approval settings. With the default settings daoco asks first and shows you exactly what it will do. Ask for a draft and daoco stops at the draft. Ask for the page to go live and it creates the draft, then requests the publish. After a library page is published, its row under Website -> Pages links to the live address. Choose Check now in the page panel to confirm the live page matches the saved version. daoco does not delete posts or pages, and it does not change themes, plugins, menus, or settings.

​
If the connection fails

  • The username or password was rejected: create a new application password and paste it again. Your normal login password does not work here.
  • No REST route answered: check the site address, and that no plugin has disabled the REST API.
  • The user is not allowed: connect with an Editor or Administrator account.
  • WordPress redirected the request: use the address the error names, for example the www version, as the site address.
  • There is no Application Passwords section: the site must use https, and some security plugins hide it.

​
Current limits

  • SEO plugin fields (Yoast, Rank Math) are not set. The excerpt is, which many themes use as the meta description.
  • Categories, tags, and custom post types are not managed.
  • Scheduling a future publish date is not supported; publishing is immediate.