Preserve a recoverable copy before changing a SitePad theme, removing pages or rebuilding shared components. Screenshots help document appearance, but a recovery plan also needs the site's editable content and any supporting data.
01 Prepare a recovery point
- Identify the exact SitePad installation, website directory and associated database if the installed version uses one. Ask support to confirm the required components when they are unclear.
- Record the live domain, page list, menu structure, form settings and connected services. Keep passwords separately in an approved password manager.
- If the control-panel SitePad plugin provides a Backup action, use it for the correct site and confirm that the operation completes. Availability depends on the installed integration.
- Where that action is absent, use the hosting account's supported backup process for the relevant files and database. Confirm what the selected backup actually includes.
- Download or retain a copy outside the installation being changed. Label it with the site, date and purpose, and check that it can be read.
- Confirm how restoration would be performed and whether it replaces current data. Use a separate test location when a restore rehearsal is available.
- Make the planned changes in manageable stages and verify the public site after each significant update.
Common questions
Is a published HTML copy enough?
It may help preserve visible content, but it may not preserve the editable project, database or working forms. Match the backup to the installed SitePad version and recovery goal.
Can I restore only the header?
That depends on the available recovery tools. Keep a content copy before editing, and ask about selective recovery before replacing the whole site.
When should I delete the old backup?
Keep it until the changed site has passed its checks and the agreed retention period has elapsed. Protect copies containing contact or customer data.