Use a staging copy for an AI-assisted redesign when you want to review layout, content and theme changes before visitors see them. This is particularly important for the full NabWP AI website builder, which can publish generated pages while the build is running.
IN THIS ARTICLE
01 Choose the right starting point
For an established website, create a current backup and a staging copy through the available NabWP tools. For a completely new business site, a separate protected installation may also suit the review process. Confirm the selected site carefully before opening AI website or AI Engineer.
02 Prepare the review environment
- Protect staging access and keep it out of public search indexing.
- Disable or sandbox customer mail, payments, fulfilment and scheduled business integrations copied from production.
- Record the current theme, key pages and business functions that must survive the redesign.
- Give the AI a clear design brief and state which existing content must be preserved.
- Review proposed theme or file changes before approval where the workflow provides that control.
- Test the finished design on desktop and mobile before planning deployment.
Will the full builder preserve my active theme?
The current builder uses Twenty Twenty-Five block patterns and may install and activate that theme. Read the build notice and test the resulting design on the chosen copy. A full build is more extensive than asking the Engineer for a small CSS adjustment.
Can I push the whole staging database to a live store?
Only with a plan that accounts for new orders, users and other live data. Database synchronisation replaces data rather than automatically merging independent transaction histories. Deploy the reviewed scope through an appropriate method, or schedule a controlled final sync when full replacement is genuinely intended.
03 Verify the launch plan
Check navigation, forms, media, accessibility, SEO settings and important integrations. Record which changes live in files and which live in the database. Take a fresh live backup immediately before deployment, preserve current business records and remove staging-only restrictions only from the intended public site. Keep the staging copy isolated after launch so it cannot later send real customer messages or run live payment jobs.