Connecting a WordPress site

WordPress sites connect through the WordPress REST API with a username and an Application Password. Nothing needs to be installed for standard publishing. This guide walks through preparing WordPress, connecting the site and checking the settings afterwards.

Before you start

• You are an Owner or Admin of the company in Accounts, or of its agency.

• You have administrator access to the WordPress site, or someone who does can create the Application Password.

• The REST API is reachable: open https://your-site.com/wp-json in a browser. You should see a JSON response that includes wp/v2.

Step 1: Choose the WordPress user

The platform publishes as this user. Use a user who can create, edit and delete posts, for example with the Editor or Administrator role.

Tip: Create a dedicated user such as "UP-TO-DATE publisher". You can then revoke its access without affecting a real person, and posts are clearly attributed.

Step 2: Create an Application Password

1. Sign in to WordPress as that user, or as an administrator editing that user.

2. Go to Users > Profile (or edit the user) and scroll to Application Passwords.

3. Enter a name, for example "UP-TO-DATE", and add a new application password.

4. Copy the generated password. WordPress shows it only once.

If the Application Passwords section is missing, a security plugin or the host has turned it off. It must be available for the connection to work.

Step 3: Open Connect a Site

1. In Accounts, go to Companies > open the company > Websites tab.

2. Click Connect a Site. If the company already has sites, click Connect New Site.

3. Under Select your CMS, choose WordPress. It is selected by default.

Step 4: Fill in the fields

Step 5: Test the connection

1. Click Test Connection.

2. The test checks that /wp-json lists wp/v2, creates a draft called "Test Post" and deletes it again. WordPress may keep that draft in the Trash.

3. When it passes, you see "Test connection successful! Credentials are valid."

The test always uses the standard posts endpoint. It does not check the custom post type.

Step 6 (optional): Enable ACF support

After a passed test, an ACF Support section appears. Tick Enable ACF Support if the site uses the Advanced Custom Fields plugin for its posts, then define which fields the platform fills in the editor that appears. Leave it off for standard posts.

Step 7: Connect

1. Click Connect.

2. The window closes and the site appears in the company's Websites list.

Step 8: Check the settings

1. Go to Websites > open the site > Edit connection.

2. In Edit Site Settings, check the WordPress settings:

   • Post Type: make sure it shows your custom post type if you use one. If it shows posts, enter the right value here.

   • Blog Slug Prefix: the URL part before the post slug, for example blog for /blog/my-post. Leave it empty for none.

   • Multilingual Plugin: None, WPML or Polylang.

3. Click Save Changes.

To change the username, Application Password or site URL later, use the same window. Leave App Password blank to keep the current one.

Multilingual sites

Ask the UP-TO-DATE support team for the plugin files. In WordPress, upload them with Plugins > Add New > Upload Plugin and activate them. The handler endpoints only accept users with the edit_posts capability. See Connecting a website: the connection handler step by step.

Common errors

Related articles

• Connecting a website: the connection handler step by step

• Required technical access (before you start)

• Testing whether the connection works correctly

• Troubleshooting: website connections and crawls