## **🔍 Overview**

If your OTTO SEO suggestions are not deploying to your WordPress site, or if the Atlas playbook returns a **403** or **400** error during preview, this article explains what may be happening and what to have ready when you contact our team for assistance.

## **⚙️ What May Be Causing This**

OTTO deployment and playbook preview errors on WordPress trial sites can stem from a number of underlying causes, including plugin connectivity issues, caching conflicts, or an incomplete site authorisation. Because these errors often require backend investigation to diagnose correctly, our support team will need to look into the specifics of your setup directly.

## **📋 What to Have Ready When You Escalate**

To help our team resolve your issue as quickly as possible, please gather the following before reaching out:

- The **exact error message** you are seeing (e.g., 403 Forbidden, 400 Bad Request, or any other on-screen text).
- The **name of your WordPress project** or trial site as it appears in Search Atlas.
- The **timestamp** of when the error first occurred or the most recent occurrence.
- A brief description of the action you were taking when the error appeared (e.g., running a playbook preview, deploying suggestions, scanning the site).
- Any caching or third-party plugins you have active on the WordPress site (e.g., WP Rocket, Google Tag Manager).
- Screenshots of the error if available.

Having this information ready will allow our team to investigate your specific configuration without delays.

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.