Before starting another NabWP AI website build, decide which previously generated pages should be replaced and preserve any edits worth keeping. The replacement option can move earlier AI-generated pages to the WordPress bin, including content you may have refined after the first build.
IN THIS ARTICLE
01 Inventory the existing work
List the pages from the previous build and note which contain approved text, custom blocks, media or working forms. Record their public URLs and menu use. Create a current files-and-database backup and consider exporting important content as an additional reference.
02 Choose the build strategy
- Use a staging or separate review site when the live website must remain unchanged.
- Open the new build flow and read the Replace the pages AI built last time option.
- Remember that this option is on by default in the current workflow; set it deliberately for your intended outcome.
- If retaining old pages, plan how new pages and navigation will be reviewed to avoid confusing duplicates.
- Review any theme-change notice and start the new build only on the intended website.
- Compare the new result with the preserved content before deleting anything permanently.
Does replacement affect only untouched AI text?
Do not assume that manual improvements exempt a page that was originally generated by the builder. The replacement workflow targets the previously generated pages. Preserve valuable edits before approving replacement rather than relying on the builder to distinguish which paragraphs you changed.
Can I recover pages from Trash?
WordPress Trash can provide a recovery opportunity when the pages remain there, but it is not a permanent backup. Restored pages may also need their slugs, menus and homepage relationships reviewed. Keep the independent backup for a more complete recovery option.
What if I only want to improve one page?
Use normal WordPress editing or the focused writing or Engineer workflow appropriate to that change. A complete new build can alter the theme and site-wide presentation and may be unnecessary for a narrow revision.
03 Verify the final structure
Check for duplicate pages, broken old URLs, lost form settings and menus pointing to binned content. Preserve useful redirects when public URLs change. Review every generated claim and placeholder, then back up the accepted version before deploying it to a live site with current customer data.