Connecting your WordPress site allows Blaze to author and post blog content automatically.

In this article, we will walk through how to:

Download link

Use this link to download the zipped plugin and save it somewhere that's easy to access. ❌ You do not need to unzip the file. ❌
​

Login to your WordPress admin panel (usually at https://your-wp-site.com/wp-admin) using WordPress site administrator login credentials.

Navigate to "Plugins" on the left navigation bar, then click on "Add New Plugin" at the top of the page.

Click "Upload Plugin".

Upload the zipped plugin you downloaded earlier in Step 1, then click "Install Now".

Click the "Activate Plugin" button to activate Blaze and complete the installation process.

Go to User > Profile > Scroll down to the Application Password section of page.

Give your Application Password a name.

Click Add Application Password.

Copy your Application Password.

Click "Set Up your Account" on the WordPress card.

Next, fill out the form with your WordPress credentials.

Then, click Connect Account to save the integration.

You should be taken back the integration page. WordPress should be now located in the "In your Content Plan" section with a green icon next to it. This indicates that its connected correctly.

Select Content Plan from the side bar. Then click Adjust Defaults then Channels. Scroll down to Blog. Enable it if not enabled and adjust the amount of content you want Blaze to generate by default. Click Save as Default to confirm your changes.

As Blaze executes your content plan it will generate content. You will see Blogs appear on your calendar that are automatically generated.

They will automatically get posted to your WordPress site when that date and time comes to pass. Up until then you can review edit and optimize the blog.

With any blog open navigate to the Prepare to Publish section. Click on Configure Blog Metadata

With the Configure Metadata panel open you can adjust the following items:

Confirm that your permalinks are not "Plain" permalinks, but rather what WordPress refers to as "Pretty" permalinks.

On the WordPress dashboard, go to Settings → Permalinks Screen. You can choose one of the permalink structures or enter your own in the “Custom structure” field using the structure tags (Reference: Permalink documentation from Wordpress).

Some security plugins like JetPack, WP Cerber Security will require you to whitelist Blaze IPs. Reach out to support via chat or email support@blaze.ai if you need to whitelist Blaze for your WordPress site.

Some CDN settings will also require you to whitelist Blaze or complete a security challenge. We have seen this with some customers who are using Cloudflare, for example, to deliver content globally. Reach out to support via chat or email support@blaze.ai if you need to whitelist Blaze for your WordPress site.

Wordfence

If you are using the Wordfence plugin and want to use an application password, you will need to enable application passwords in the Wordfence settings.

Do this by going to your WordPress Dashboard → Side Menu → Wordfence → All Options → Disable WordPress application passwords checkbox is not ticked (i.e., application passwords need to be enabled and not disabled).

You may also be able to whitelist Blaze's URL. See here for more details from WordPress's forum.

Jetpack

Jetpack Protect (official WordPress module) will occasionally block some AWS IPs you can either allowlist the IP listed in the error, disable Protect altogether, or if try and allowlist all AWS us-east-1 IPs.

Once you do that, try reconnecting your WordPress account to see if this resolves the issue.

If you have a firewall enabled please double-check that it allows Blaze to connect as well.

This can happen if the authenticated user does not have an appropriate role. Please review WordPress' details on Roles and Capabilities as you will need an authenticated user who at least has an Editor role to post as other authors.

In order to connect to WordPress, you must have XML-RPC functionality turned on. This is turned on by default in WordPress 3.5+. If you're having issues connecting, go to Settings > Writing > Remote Publishing and check the checkbox.

You may also receive this error if your WordPress installation is secured and not publicly available. Unfortunately, the installation must be publicly accessible to work with Blaze.

Also, we're unable to provide IPs to allowlist as our IPs are not static - they rotate because we use AWS. If you'd like, you should be able to allowlist a block of IPs from AWS to make this work. You would just need to make sure the list you're allowing is the us-east-1 IP range.

AWS provides a list of their IP address ranges at https://ip-ranges.amazonaws.com/ip-ranges.json.

Additionally, Blaze's calls will always include the header User-Agent: Blaze, so this may be an alternative when allowing a whole range of IPs isn't feasible.

You may also be able to white URL. See here for more details from WordPress's forum.

This error could mean that you're using the wrong Base URL in the login screen. If you're using http: try using https:. If you're using www.example.com try using it example.com.

If you continue to get this error, then it's likely because the XML-RPC is being blocked on the WordPress site. It's most likely being blocked by a plugin, the hosting provider, or a security setting. To fix, try disabling a your plugins one and a time, then try reconnecting to WordPress account to see if you can isolate the problem plugin.

If not, it might be a back-end change that needs to be made by your hosting provider or website developer. We recommend reaching out to them and asking them to update the XML-RPC settings for you. You can send them this link for more information: https://codex.wordpress.org/XML-RPC_Support

If your provider/developer wants to allowlist access to us, you can let them know that we use Amazon's AWS products for our server infrastructure, so they'll need to allowlist their IP list from the us-east-1 region. You can find that range list here: https://ip-ranges.amazonaws.com/ip-ranges.json.