A redesigned website can launch successfully while leaving important URLs, content and search signals behind. Visitors follow an old link and reach the wrong page. A useful service page disappears. Preview settings accidentally stay active on the public site.

I help you prepare the SEO side of a WordPress migration before release. That includes a rebuild on WordPress, a domain or URL change, or a move to a headless frontend. The work connects the existing site's important pages to the proposed site, with explicit decisions about what stays, moves, merges or retires.

You receive a usable migration plan, agreed implementation where included, and a record of the checks around launch. I work with your designer or developer so the search requirements become concrete release tasks.

A typical first engagement covers one existing WordPress site, one target environment, up to 200 inventoried URLs and an agreed priority verification sample. Before quoting, we identify page types, integrations, languages and who owns the content, redirects and deployment.

Allow 5–10 business days for preparation and preview verification once access, the proposed structure and a usable target environment are ready. The launch date and verification window are scheduled separately. This is migration planning and launch support; building the replacement site or transferring all content and media requires its own scope.

A source URL inventory assembled from the available site, exports, sitemaps and search evidence, with gaps marked.

A reviewed old-to-new URL map, including pages that need a deliberate removal or consolidation decision.

Priority content and template checks covering important headings, metadata, internal links, canonical output and indexability settings.

Redirect implementation in the agreed configuration, or precise deployment instructions when your developer owns that layer.

A release checklist, launch checks for the agreed URL sample, and a handoff recording completed work, exceptions and rollback responsibilities.

For a large nutrition site, I reconstructed legacy URLs from Wayback/CDX and Search Console evidence, implemented approved redirect mappings, and validated their destinations and host/protocol behavior. That work informs how I plan URL coverage before a migration.

Inventory: Establish the available source pages and the site's commercially important routes.

Map: Agree each affected URL's destination or retirement, with the content owner resolving ambiguous cases.

Prepare: Check the preview, implement agreed rules and assign remaining launch tasks.

Verify: Check the approved release, document exceptions and hand over follow-up priorities.

The existing and proposed URLs, WordPress access or exports, available search data, the target environment, proposed navigation, and the migration date. Identify the person approving content decisions and the developer or host controlling redirects and deployment.