πŸ› οΈ Restore Accidentally Undeployed Page Schemas

Camilo Aponte

Camilo Aponte

Last updated on Nov 12, 2026

πŸ” What Happened

Sometimes a sitewide undeploy removes page schemas from pages that should still have them. In OTTO, this happens when you use Roll back all on the Page-level schema category, which rolls back every page in that category rather than only the pages you meant to change. Your schemas are not deleted. Their deployment is switched off, so they stop appearing on your live pages. This article explains how to find the affected pages and turn their schemas back on safely.

βœ… Before You Begin

Gather the information you need before making any changes. This will help you restore only what was affected.

  • Site name or domain: Confirm which site was affected.
  • Approximate time: Note when the sitewide undeploy happened, as closely as you can.
  • Intentional undeploys: List any pages you removed schemas from on purpose, either before or after the accidental change.
  • Later updates: Note any schema changes or recoveries made after the incident, so they are not overwritten.

πŸ› οΈ Steps to Restore Schemas

  1. There is no activity or change history in the product that shows the sitewide undeploy event and its time. Use the Page-level schema category instead, and open the Not Deployed tab to see schemas that are currently off.
  2. You cannot see which schemas were active just before the undeploy. In Page-level schema, use the Deployed and Not Deployed tabs to see which schemas are on or off now, and confirm the affected pages against your own list.
  3. Remove pages you meant to keep off. Exclude any page you undeployed on purpose, both before and after the incident.
  4. Check for later recoveries. If someone already restored a page after the incident, leave it as it is.
  5. Redeploy the schemas on your confirmed list. Open each affected schema and choose Deploy this Schema, or select those schemas and use Enable. The button says Enable instead of Deploy until the OTTO SEO Widget is installed and engaged.
  6. Verify the results. Check a sample of restored pages to confirm the schema appears correctly and that pages you meant to keep off remain off.

πŸ›‘οΈ Protecting Intentional Undeploys

Restoring schemas should never undo decisions you made on purpose. Pages removed from schema deployment for valid reasons, such as being retired, being in testing, or having a different markup strategy, should stay undeployed. Always check your records before restoring a page.

🚫 Avoid Blanket Deployments

Do not redeploy schemas across the entire site as a shortcut. A blanket deployment can turn on schemas for pages that were intentionally left off, and it can overwrite recent fixes or custom settings. Restoring only the confirmed list of affected pages is safer and keeps your site accurate.

πŸ’‘ Preventing Future Issues

A few habits can reduce the risk of accidental sitewide changes:

  • Double-check scope before running any action that affects multiple pages.
  • Test on a small set of pages before applying changes sitewide.
  • Keep notes on intentional undeploys so they are easy to find later.
  • Review deployment history regularly, especially after team changes or bulk edits.

πŸ’¬ Getting Further Help

If you need the exact list of affected pages pulled from audit logs or backups, or you are unsure which pages to restore, we can help. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat. To speed things up, include your site name, the approximate time of the undeploy, and any pages you want to keep undeployed.

Was this article helpful?