All Collections
Billing & Account Management
Configuring WordPress Security to allow Content at Scale<>WordPress Integration
Configuring WordPress Security to allow Content at Scale<>WordPress Integration

Checking for plugin conflicts is your first line of defense when a plugin isn't performing as expected.

John Pratt avatar
Written by John Pratt
Updated over a week ago

Many Content at Scale users have website security. In some cases, security plugins' settings can block or limit plugin access for the Content at Scale<>WordPress Integration (plugin) to your WordPress site, especially if the plugin requests are mistaken for potentially harmful traffic.

Since our plugin uses JSON for its plugin requests, you can adjust your security plugin's settings to allow our Content at Scale<>WordPress integration to perform as expected.

How do I make sure my security plugin is allowing Content at Scale access to my website?

Here's how to accomplish this for three different popular security plugins:

Cloudflare:

  1. Log in to your Cloudflare Account: Visit the official Cloudflare website and enter your credentials to log in.

  2. Select your Site: Once you're logged in, you'll see a list of websites associated with your account. Select the WordPress website you want to configure.

  3. Navigate to the Firewall tab: After selecting your website, you'll be taken to your dashboard. From there, click on the Firewall tab.

  4. Set up a Firewall Rule: Within the Firewall section, click on "Firewall Rules". Click on "Create a Firewall rule". In the rule settings, you can add your own conditions. For example, you can set the "Field" to "URI Full", "Operator" to "contains", and "Value" to "/wp-json/" (which is the default prefix for WordPress REST API requests) or ".json" if your plugin sends requests to specific JSON files. Then choose an action like "Allow".

  5. Save and Deploy: After setting up your desired rule, click on "Deploy" to activate the rule.

Wordfence Security:

  1. Log into WordPress: Visit your WordPress website and log into your WordPress Dashboard.

  2. Go to Wordfence Settings: In your Dashboard, navigate to "Wordfence" on the left-hand side, then select "All Options".

  3. Check Firewall Rules: Under the "Firewall Options", there's a section called "Whitelisted URLs". This is where you can allow access to certain URLs.

  4. Whitelist API Access: Click "Add" to add a new whitelisted URL. Set "URL" to your API's URL (e.g., "/wp-json/") and set "Param Type" to "URL". Set "Param Name" to the parameter the plugin uses, if any. Leave "Allow Reason" blank or enter a note for your own reference. Then click "Add" to save the URL.

  5. Save Changes: Scroll down and click "Save Changes" to apply your new settings.

Sucuri Security:

  1. Log into WordPress: Visit your WordPress website and log into your WordPress Dashboard.

  2. Go to Sucuri Settings: In your Dashboard, navigate to "Sucuri Security" on the left-hand side, then select "Firewall (WAF)".

  3. Whitelist API URL: On the WAF page, find the "Whitelisted URLs" section. Click "Add Whitelisted URL". Set the "Path" to your API's URL (e.g., "/wp-json/"), and set "Permitted Methods" to "POST, GET" or whatever methods your plugin uses.

  4. Save Changes: Click "Add Whitelisted URL" to save the URL.


This should allow Content at Scale's JSON API requests through the firewall.

Remember to be careful when configuring these settings, as overly permissive rules can potentially expose your website to security threats. It's recommended to only allow the specific paths and methods needed for the plugin to function.

These steps are generalized, you may need to modify them based on the specifics of the plugin and how it interacts with the API.


If you have additional questions, need more resources, or would like to provide valuable feedback, don't hesitate to reach out to our dedicated Support team.

Did this answer your question?