A redesign can improve credibility, usability and lead generation, but it can also disrupt organic search if URLs, content, links or technical settings change without a migration plan. SEO should be part of the project from the start, not a repair task after launch.
1. Record a baseline before design begins
Use analytics and Search Console to identify landing pages with organic traffic, conversions, valuable backlinks and consistent impressions. Export the current URL list and record titles, meta descriptions, canonical URLs, indexability and internal links. This baseline helps identify what changed after launch.
2. Audit content and page purpose
Classify each URL as keep, improve, consolidate, redirect or retire. Consider traffic, backlinks, business relevance and whether another page genuinely replaces it. Do not delete a page just because it looks old, and do not migrate every thin page without review.
3. Map URL changes and redirects
Create a mapping from each changed old URL to its closest relevant destination. Use permanent redirects for pages that have moved permanently. Avoid redirect chains and do not send unrelated URLs to the homepage. Track old URL, new URL, reason and verification result in one migration sheet.
4. Preserve on-page signals
Review title tags, H1 headings, meta descriptions, canonicals, image alt text and structured data in the new templates. Do not assume a theme or CMS migration preserves every setting. Test rendered pages as well as editor previews, especially when a page builder or JavaScript is involved.
5. Protect navigation and internal links
Update navigation, breadcrumbs, footer links, contextual links and calls to action to point directly to preferred URLs. Make sure key service pages remain discoverable and that the new architecture reflects how visitors look for information.
6. Test the staging site
Check status codes, canonicals and robots directives.
Test desktop and mobile layouts.
Verify forms, menus, search and checkout where relevant.
Confirm analytics and conversion tracking.
Check image loading, performance and structured data.
Ensure staging restrictions will not remain on production.
Test important user journeys end to end. A design can look correct while a contact form or tracking event is broken.
7. Launch with a controlled checklist
Confirm HTTPS, redirects, robots, canonicals, sitemap and analytics at launch. Inspect a sample of high-value URLs in Search Console. Keep the redirect map and rollback plan accessible to the people responsible for the site.
8. Monitor after launch
Track crawl errors, indexing, organic landing pages, impressions, clicks and qualified leads. Compare results with the baseline while accounting for seasonality and normal fluctuation. Investigate concentrated drops on migrated templates rather than assuming every movement was caused by the redesign.
Migration checklist
Phase
Essential task
Before design
Export URLs and record search and conversion baselines
During build
Preserve content purpose, metadata and page accessibility
Before launch
Test redirects, mobile journeys, forms and analytics
Launch day
Verify HTTPS, robots, canonicals and sitemap
After launch
Monitor indexing, traffic, leads and crawl errors
Common mistakes
Changing URLs without a redirect map.
Deleting content before checking its value.
Leaving staging noindex rules on production.
Assuming a visually attractive design is automatically usable or fast.
Failing to test mobile forms and tracking.
Keep a simple URL migration map
For example, if an old service page moves from /old-web-design/ to /services/web-development/, record the old URL, destination, redirect type and test result. Update internal links to the new destination rather than leaving them to pass through the redirect. If a page has no direct replacement, decide whether its content belongs in another page or whether it should be retired.
Assign an owner for launch-day checks and define who can roll back a release if critical forms, navigation or indexing controls fail. This is especially important when the redesign changes the CMS, URL structure or hosting setup.
Frequently asked questions
Will a redesign always reduce rankings?
No. Outcomes vary. A well-managed redesign can preserve important signals, while changes to content, URLs and technical setup can affect performance.
Should every old URL redirect to the homepage?
No. Redirect to the closest relevant replacement. If none exists, retire the page appropriately.
Plan the redesign around business goals
A redesign should improve the customer experience as well as preserve search visibility. Feed Flow’s web development services and UI/UX design services are relevant when a project needs both technical implementation and a clearer user journey.
