Skip to main content

Getting this error when trying to reconnect Wordpress, no idea what it means. Any help would be greatly appreciated.

Error parsing response. We got: "<!DOCTYPE html> <html> <head> <meta charset="utf-8"> <meta name="viewport" content="width=de"

Hi @swishsalescoaching,

Welcome to the Zapier Community! Happy to help here.

There are several plugins that block Zapier's attempts to connect to WordPress. I recommend disabling security-related plugins like JetPack and test yout connection following the systematic disabling of the plugins. 

Here is a list of the ones that can be an issue:

Jetpack, Wordfence Security, iThemes Security, WP Rocket, JWT Auth, WP-SpamShield, WP Content Copy Protection & No Right Click, Limit Login Attempts Reloaded, SiteGuard WP Plugin, IP Geo Block, WPS Hide Login, reCaptcha by BestWebSoft, Profile Builder.

Although there are many other plugins that could also cause such an error, based on my research, one customer pointed out that disabling the Yoast SEO function 'REST API: Head endpoint' did the trick for them. Here's how to disable it: https://yoast.com/help/how-to-disable-or-enable-the-rest-api-endpoint-in-yoast-seo/ 

When you get a chance, can you give this a shot and let me know how it goes?


Hey @swishsalescoaching 

Welcome to the community!

Sorry to hear about the bother with this!

This error can be one of two things, an issue with permalinks or a plugin conflict

1. Sometimes the type of permalink used on the WordPress installation can cause trouble. To change the permalink type:

  • In your WordPress site, go to Settings, then click Permalinks.
  • Click any permalink option other than "Plain" (this is the default option).
  • Click "Save Changes".

2. Unfortunately, there are many plugins that block Zapier's attempts to connect to WordPress which generally leads to an error like this!

Our standard recommendation is to try disabling security-related plugins like JetPack and test your connection. When you get past the error you can re-enable the plugins one by one to identify the cause.

Although there are many other plugins that could also cause such an error, one of our customers pointed out that disabling the Yoast SEO function 'REST API: Head endpoint' did the trick for them. Yoast is a very popular plugin, so this could be a good one to start with. 

Here's how to disable it: https://yoast.com/help/how-to-disable-or-enable-the-rest-api-endpoint-in-yoast-seo/

If none of that does the trick then it would be worth opening a ticket with support, this way we can take a closer look and help get to the bottom of this!