How I scope a WordPress rebuild without breaking the live site.

Before estimating the rebuild, I crawl the public site and list its important URLs, templates, content types, forms, analytics, tracking events, redirects, files, accounts, plugins, integrations, and hosting dependencies. I also record what is already working so the new build does not remove useful behavior by accident.

Not every page has the same risk. I identify how visitors discover services, request a quote, purchase, log in, reset a password, download information, book a call, or contact support. Those paths become explicit acceptance tests rather than assumptions hidden inside a page list.

Some content and URLs should stay. Some templates only need cleanup. Other parts need a new structure. Ideas that are useful but not required for launch move into a later phase. This keeps the first release focused while protecting valuable pages, data, and search intent.

The new site is built on a protected staging environment with its own database and files. Production remains the source of truth until the agreed content freeze or final synchronization window. Search engines are blocked from staging, and staging email, payment, and automation behavior is controlled so test activity cannot reach real customers.

A rebuild can fail even when the design looks good. I map old URLs to new destinations, protect important page copy and metadata, plan structured content and media migration, account for orders or user records that change during development, and verify canonical tags, schema, sitemap output, analytics, and internal links before launch.

The definition of done covers responsive layout, browsers, forms, notification delivery, accounts, checkout where relevant, integrations, accessibility basics, page speed, redirects, indexing controls, backups, security checks, and monitoring. The person authorized to launch and the condition for rollback are named before the release window.

The final scope explains the business goal, page map, reusable templates, features, integrations, content ownership, migration work, technical constraints, acceptance criteria, risks, launch sequence, and later opportunities. That gives the business a document it can approve and gives development a plan it can estimate responsibly.