How to Revert Deployed Patches

Overview

If a deployed meta tag or schema script causes indexing errors or layout shifts, CrawlSage allows you to instantly revert the update. The Rollback feature restores the original metadata backup stored in our database, returning your headers to their pre-audit state.

Prerequisites

• A deployment marked as Applied or Verified.

Step-by-Step Guide

1. Open your **Optimizations** dashboard and click on **Deployment History**.
2. Locate the verified code patch you wish to revert.
3. Click the **Rollback** or **Revert Fix** button on the card.
4. Confirm the action in the verification modal pop-up.
5. CrawlSage dispatches a delete payload to your CMS API. The plugin deletes the optimization entry and restores the original backup.
6. The Validation Bot runs an immediate check to confirm the rollback is live on the DOM.

Expected Result

The fix status in your history table changes to Rolled Back. The original meta tags and schema configurations will be active on the target site headers.

Common Mistakes

• Deleting plugin before rollback: If you uninstall the WordPress plugin before clicking rollback, CrawlSage will be unable to remove the tags. Always trigger rollbacks before disconnecting integrations.

Troubleshooting

• Rollback fails with "API Key Invalid":

  Your workspace session credentials have refreshed. Re-authenticate in settings and try triggering the rollback command again.

Related Guides

• Understanding the Deploy Pipeline
• How the Validation Bot Works