π Overview
Sometimes OTTO schema deployment settings change in a way you did not intend. For example, schema may be switched on or off for many pages at once, or a bulk action may run when you only wanted to view deployment counts. This article explains how to confirm what changed, restore the affected pages, and give our support team what they need to help.
β οΈ Common Signs of an Unintended Change
- The number of pages with deployed schema suddenly rises or drops.
- Pages you never selected show a different deployment status.
- Schema you previously deployed no longer appears on your live pages.
- Schema appears on pages where you did not want it.
- A bulk or sitewide action ran when you only meant to read or review data.
π Step 1: Pause Further Changes
Before you try to fix anything, stop making changes. Extra edits make it harder to tell what the original state was.
- Do not run any more bulk Deploy or Roll back actions.
- If a teammate or an automated tool has access to the project, ask them to pause too.
- Note the approximate date and time you first saw the problem.
π Step 2: Identify What Changed
Write down which pages were affected so you can restore them accurately.
- Open the OTTO section for the affected project.
- Go to the schema deployment view and filter by deployment status.
- Compare what you see now with your last known good state. Useful sources are earlier exports, screenshots, reports, or your own notes.
- List the affected page URLs, or their IDs if you have them. If the change was sitewide, note that instead of listing every page.
- Record how many pages were deployed before and after, if you know.
Tip: Check your live site too. Open a few affected pages and review their structured data with a schema testing tool to confirm whether the schema is actually present.
π Step 3: Restore the Previous State Yourself
For a small number of pages, you can usually fix the problem directly.
- Select the pages that should have schema deployed and redeploy them.
- Select the pages that should not have schema and click Roll back, then confirm with Undo Deployment.
- Wait a few minutes, then refresh the deployment view to confirm the status updated.
- Clear any site or CDN cache if you use one, so the live pages show the latest version.
If the change affected a large number of pages, or you cannot tell what the original state was, skip to the next section and ask our support team for help.
β Step 4: Verify the Result
- Check that the deployed page count matches what you expect.
- Spot-check several restored pages on your live site.
- Confirm that pages meant to stay without schema are still without it.
- Re-check after 24 hours to make sure nothing reverted.
π¬ When to Ask Support for Help
Contact support if any of these apply:
- Many pages were affected and you cannot restore them one by one.
- You do not know the original deployment state.
- The change seems to have come from a bulk or sitewide action you did not request.
- Pages still do not match the expected state after you redeploy or undeploy them.
Our team can review deployment history on our side and, where records allow, work to restore the affected pages to their state before the change. They can also look into why the action ran. Because the available history can vary by case, restoration depends on what records exist for your project.
π What to Include in Your Message
The more detail you share, the faster we can help. Please include:
- Project or domain name affected.
- Date and time (with time zone) when you first noticed the change.
- Affected page URLs or IDs, or a note that the change was sitewide.
- What you were doing when it happened, such as viewing deployment counts, running a bulk action, or using an assistant or automation.
- The state you expect, such as which pages should be deployed and which should not.
- Screenshots or exports showing the before and after, if you have them.
- Who else has access to the project, if anyone.
If an automated assistant or tool appeared to start a change on its own, say so and describe what you asked it to do. This helps our team trace the cause.
π‘οΈ How to Prevent This in the Future
- Export or screenshot your deployment status before running any bulk action.
- Review the number of pages selected before you confirm a deploy or undeploy.
- Use filters to limit actions to the pages you intend to change.
- When you only need counts, use read-only views or reports instead of action buttons.
- Limit project access to the people who need it, and tell your team before making large changes.
- Check your deployment status after every large update.
β Quick FAQ
Will undeploying schema harm my site? No. Removing schema returns pages to how they were without it. It may affect how rich results appear in search over time.
How long until restored schema shows on my site? Usually within a few minutes, though caching can delay it.
Can I get an exact list of affected pages? Our support team can help identify them from the records available for your project. Sharing your own list as well speeds up the review.
π Need More 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.