# **🔍 Overview**

Search Atlas processes deployment tasks — such as applying SEO improvements across multiple pages — in controlled batches. If you have tried to deploy more than 100 improvements at once, you may have noticed the platform limits your selection. This article explains why that limit exists, how Autopilot handles large queues automatically, and what you can do to work efficiently within the current system.

# **⚙️ Why There Is a 100-Deployment Limit**

The 100-deployment cap per batch is a deliberate safeguard, not a restriction on your total output. Here is why it matters:

- **System stability:** Processing hundreds of deployments simultaneously can overwhelm background task queues, causing jobs to time out, duplicate, or fail silently. The batch limit prevents these cascading failures.
- **Rate-limit protection:** Each deployment triggers publishing actions that are subject to platform-level rate limits. Sending too many at once can saturate those limits and delay all your active projects, not just the current one.
- **Reliable execution:** Smaller, controlled batches complete predictably. You get accurate status updates and can catch errors before they multiply across hundreds of pages.

In short, the limit exists to ensure every deployment you submit actually succeeds — rather than allowing a large batch to partially fail with no clear feedback.

# **📊 How Autopilot Handles Large Queues**

If you are managing a high volume of pages, **Autopilot** is designed to work through your queue automatically without requiring you to manually submit batch after batch. Here is how it works:

1. Autopilot detects pages that are ready for improvement and queues them internally.
2. It submits deployments in sequential batches, respecting system rate limits at each step.
3. Once one batch completes successfully, the next batch is triggered automatically.
4. You do not need to stay logged in or monitor the process — Autopilot runs in the background.

This means that even if you have 500 pages to optimize, Autopilot will work through them in orderly groups, typically in batches of up to 100, until the full queue is processed.

# **🛠️ How to Deploy Improvements in Batches Manually**

If you prefer manual control or need to deploy improvements outside of Autopilot, follow these steps:

1. Go to **Left sidebar → OTTO SEO → All Sites (SEO Automation)** (URL: **/seo-automation-v3**).
2. Select up to **100 pages** using the checkboxes in the page list.
3. Click the deployment action to apply your selected improvements.
4. Wait for the batch to complete and confirm the status updates correctly.
5. Repeat the selection process for the next group of up to 100 pages.

While this requires a few extra steps for large sites, it gives you precise control over which pages are updated and in what order.

# **💡 Tips for Working Efficiently at Scale**

- **Use Autopilot for large sites:** If you consistently need to deploy across hundreds of pages, enabling Autopilot removes the need for manual batching entirely.
- **Prioritize high-impact pages first:** When deploying manually, filter or sort pages by traffic or ranking opportunity so your first batch targets the most valuable URLs.
- **Check active deployment status:** Before starting a new batch, verify previous deployments have completed. Look for the **Active** count on the **OTTO SEO → All Sites (SEO Automation)** page (shown as *Active 20* in the toolbar) to see tasks still in progress.
- **Avoid overlapping batches:** Submitting a new batch while a previous one is still processing can slow both down. Allow each batch to finish before selecting the next group.

# **❓ Frequently Asked Questions**

- **Can the 100-deployment limit be increased for my account?** The limit is applied at the infrastructure level to protect all users on the platform. There is no account-level override available at this time. Autopilot is the recommended solution for large-scale deployments.
- **Will Autopilot skip pages if the queue is very large?** No. Autopilot queues all eligible pages and works through them sequentially. Pages are not skipped — they are processed in the order they are queued.
- **What happens if a batch partially fails?** Failed deployments are flagged individually so you can review and resubmit only the affected pages, without reprocessing the entire batch.

# **🙋 Need More Help?**

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.

# **Additional Notes**

If improvements remain pending and are not being picked up in subsequent runs, contact support — provide your project name, the number of improvements pending, and the date and time of the last deployment run so the team can investigate your project's queue and batch configuration directly.