## **🔍 What Is the HTTP 413 Error in OTTO SEO?**

When you use OTTO SEO to preview changes on a large WordPress page, you may see an **HTTP 413 (Content Too Large)** error inside the preview window. This error can look alarming, but it does **not** mean your page is broken or that OTTO has failed to process your changes.

The 413 error in this context means one thing: the page you are trying to preview is too large for OTTO's built-in preview window to load. It is a **preview limitation only** and has no effect on your live site or on OTTO's ability to deploy your SEO changes.

## **⚠️ Why This Happens**

OTTO SEO's preview window is a lightweight rendering environment designed to give you a quick visual check of your changes. It has a size limit on the content it can load at one time. Very large WordPress pages — for example, pages with heavyweight page builders, many embedded blocks, large images, or complex layouts — can exceed this limit and trigger the 413 error.

This is **not** caused by:

- Your server's PHP memory limit or upload settings
- A security plugin blocking the request
- A Web Application Firewall (WAF) rejecting traffic
- Any misconfiguration on your WordPress site

You do not need to change any server-side settings to resolve this issue.

## **✅ How Your Changes Are Still Applied**

Even when the preview fails with a 413 error, OTTO SEO continues to work normally in the background. When you deploy changes through OTTO, they are written directly to your WordPress site — the preview window is a separate step and does not control deployment.

In short: **a failed preview does not mean a failed deployment.** Your SEO changes are still live on your site.

## **🛠️ What To Do Instead of Using the Preview**

If you see a 413 error in the OTTO preview, follow these steps to verify your changes were applied correctly:

1. Go to **Left sidebar → OTTO SEO → SEO Automation** (or navigate to **/seo-automation-v3**).
2. Confirm that the changes you intended to make are shown as **deployed** or **active** in the OTTO SEO dashboard.
3. Open your WordPress page directly in a **new browser tab** using your site's live URL.
4. Use your browser's built-in developer tools (right-click → **Inspect** → **Elements** or **View Page Source**) to confirm the SEO changes — such as updated meta titles, descriptions, or structured data — are present in the page code.
5. Optionally, use a third-party tool such as Google's Rich Results Test or a meta tag checker to verify the changes are visible externally.

## **📋 Quick Reference: Preview Error vs. Live Site**

- **413 error in preview window:** The page is too large for the preview to render. This is expected for large or complex pages.
- **Live site deployment:** Unaffected by the preview error. OTTO applies changes directly to your site regardless of preview status.
- **Server-side changes needed:** None. Do not adjust PHP settings, disable security plugins, or modify WAF rules to fix this error.

## **🔄 When To Contact Support**

You should reach out to our team if:

- Your OTTO dashboard shows the changes as **not deployed** or shows an error other than 413 in the preview.
- You have confirmed the changes are deployed in OTTO but they do **not** appear on your live site after a reasonable time.
- You are seeing the 413 error on pages that are not unusually large or complex.

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.