## **🔍 Overview**

If you are sending blog posts to your WordPress site using the Search Atlas OTTO plugin and encountering an **Error 403**, or noticing your website slowing down and content being duplicated, this article will help you identify the cause and resolve the issue quickly.

## **⚠️ What Is Error 403?**

A **403 Forbidden** error means your WordPress site is actively blocking the request sent by the OTTO plugin. This is a permissions or security issue on the receiving server — not a problem with Search Atlas itself. Common causes include:

- **Security plugins** (e.g., Wordfence, iThemes Security, Sucuri) blocking plugin API requests
- **Web Application Firewalls (WAF)** flagging automated POST requests as suspicious
- **Incorrect API credentials** or an expired connection between Search Atlas and your WordPress site
- **IP restrictions** on your hosting server that block external services
- **User role permissions** — the connected WordPress user account may lack sufficient rights (Administrator role required)

## **📉 Why Is My Site Performance Degrading?**

Performance degradation typically occurs when the OTTO plugin repeatedly retries a failed request. Each failed attempt can trigger multiple database writes or cache-clearing routines on your WordPress site, resulting in:

- Increased server load and slower page response times
- Duplicate posts or metadata appearing in your WordPress database
- Excessive entries in your WordPress error logs

Resolving the root cause of the 403 error will stop the retry loop and restore normal site performance.

## **🛠️ How to Fix Error 403 Step by Step**

1. **Check your security plugin settings.** Temporarily disable your security plugin (e.g., Wordfence) and retry sending a post. If it succeeds, whitelist the Search Atlas IP ranges or the OTTO plugin within your security plugin's settings.
2. **Review your WAF rules.** Log in to your hosting control panel or WAF dashboard and look for recently blocked requests from Search Atlas. Add an exception rule to allow traffic from the OTTO plugin.
3. **Reconnect your WordPress site in Search Atlas.** Navigate to **Left sidebar → OTTO SEO → SEO Automation** (URL: **/seo-automation-v3**), find your connected site, disconnect it, and reconnect using fresh API credentials. Ensure the WordPress user account you are connecting has **Administrator** role permissions.
4. **Verify your WordPress REST API is enabled.** The OTTO plugin communicates via the WordPress REST API. Go to your WordPress dashboard and confirm the REST API is not disabled by a plugin or theme. You can test this by visiting **yoursite.com/wp-json/** — if it returns a JSON response, the API is active.
5. **Check for IP restrictions.** Contact your hosting provider and ask whether external API calls from third-party services are blocked. Request that they whitelist Search Atlas outbound IP addresses if necessary.
6. **Remove duplicate content.** If duplicate posts were created during the retry loop, go to your WordPress dashboard, navigate to **Posts → All Posts**, filter by date, and manually delete any duplicates. Consider using a database cleanup plugin to remove orphaned metadata.

## **✅ How to Confirm the Issue Is Resolved**

After completing the steps above, verify that everything is working correctly:

- Navigate to **Left sidebar → OTTO SEO → SEO Automation** (URL: **/seo-automation-v3**) and attempt to publish or update a post to your site
- Confirm the post appears correctly in your WordPress dashboard without duplicates
- Monitor your site speed for 10–15 minutes to confirm server load has returned to normal
- Check your WordPress error logs to confirm no new 403 errors are being recorded

## **🚫 How to Prevent This from Happening Again**

- Always use an **Administrator-level WordPress account** when connecting your site to Search Atlas
- After installing or updating a security plugin, re-verify that the OTTO plugin connection is still working
- Avoid running multiple automated publishing tasks simultaneously to reduce server load
- Periodically review your WAF and firewall logs to catch any newly blocked requests early

## **💬 Still Need Help?**

If you have followed all the steps above and are still experiencing Error 403 or performance issues, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.