Rebuilding an old WordPress site without migrating its problems

A visual redesign does not automatically fix an aging WordPress installation. The website’s content, users, plugins, rewrite rules and database history can carry the very problems you were trying to leave behind. The safest rebuild treats the old system as an evidence source, not as a clean foundation.

Begin with a reliable inventory

Record the pages, content types, menus, media, taxonomies, redirects and forms actually used by the business. Identify old URLs that attract useful search traffic. A full backup is important for recovery and reference, but it should not be treated as permission to restore every table to production.

Audit the attack surface

Look for unexpected administrator accounts, suspicious scheduled tasks, modified core files, unfamiliar must-use plugins, executable files inside uploads and anomalous published content. Failed login activity alone does not prove compromise, but unexplained public spam or unauthorized posts warrant a serious investigation and credential rotation.

Build clean, migrate deliberately

Install WordPress and maintained dependencies in a fresh environment. Import only vetted content fields and approved media. Replace risky shortcodes and page-builder fragments with native templates or structured blocks. Keep old executable code out of the new site unless it has been independently reviewed.

Protect the search footprint

Map old URLs to appropriate new destinations, preserving relevant pages where possible. Redirect retired routes with intent; do not send every missing page to the homepage. Check canonical URLs, sitemap behavior, robots controls, metadata and broken internal links. Recheck the live site in Search Console after the move.

Test the experience beyond the homepage

A staging review should include keyboard navigation, mobile layouts, editing workflows, contact delivery, media loading, performance, form abuse handling, security headers and recovery procedures. Validate the actual PHP and WordPress versions used by hosting. A static preview and syntax checks are useful, but they are not a substitute for a working staging environment.

Prepare the handover

• Backups and a tested restore procedure
• Administrator access with least privilege and multifactor authentication
• A documented update policy and maintained plugin list
• Redirect manifest and indexation checks
• A content editing guide with ownership responsibilities
• Monitoring for errors, forms and suspicious activity

A rebuild is successful when the team can confidently operate the site months after launch—not simply when the first screenshot looks beautiful.