See what is there
List the pages, posts, media, metadata, and special files before deciding what the new site needs.
Migration work
A site migration is not a copy and paste job. Before the new design goes live, you need to know which pages, articles, images, and routes still matter, and what should happen to the rest.
A careful migration
A visible redesign is only part of the job. The route plan needs to cover what stays, what gets rewritten, what redirects, and what can safely be retired.
That matters most for older blogs. An article may need a full rewrite before it belongs in search again, but losing its route by accident is not a useful migration strategy.
List the pages, posts, media, metadata, and special files before deciding what the new site needs.
Keep worthwhile articles and routes. Rewrite, redirect, or retire the pages that no longer fit.
Create the new pages, bring over approved media, and test the routes, metadata, and visual result.
Launch when the redirects, sitemap, headers, and public URLs have a known outcome.
Every known public URL gets a planned outcome before the new site becomes public.
Images and logos are reviewed with their pages, then kept locally where they belong.
Canonical URLs, sitemap entries, redirects, and relevant category pages are reviewed as part of the build.