Capture the working site first
Keep a dated backup of the current site and record its public URLs. For a WordPress installation, include the database, uploads, theme files, plugin list, and relevant configuration. A static export contains public pages but does not replace a database backup or preserve editing workflows. Confirm the restoration method before changing the live site.
Decide what stays and what moves
Create a mapping with old URL, new URL, content owner, and verification status. Keep useful paths where possible. When a page moves, plan a permanent redirect to its closest equivalent. Do not send every missing article to the homepage. Separate deleted material from content that is merely awaiting review.
Rebuild around real content
Move a long article, an image-heavy page, and a form or worksheet into a staging copy first. Check navigation, headings, canonical URLs, image descriptions, and internal links. Replacing a live WordPress site with static HTML also changes how search, comments, logins, and forms work; identify each of those services explicitly.
Verify the release before switching traffic
Compare the planned URL list with the generated pages. Test CSS and image paths, check the verification token, and open representative pages on a narrow screen. Preserve a rollback copy. A local file preview verifies layout and links differently from an HTTP server; it cannot establish redirects, response headers, or status codes.
Check live behavior after launch
Request the homepage, an old article path, a new guide, the sitemap, the verification file, and a deliberately nonexistent URL. Confirm that missing pages return HTTP 404. Review server logs and indexing reports after recrawling. Keep a record of corrections so a later rebuild does not reintroduce the same problem.
Further reading
For installation-specific migration steps, use the official WordPress documentation and confirm the procedure against your own backup and staging environment.
Primary reference:
WordPress migration handbook