You can redesign your website without losing search traffic by treating the work as a migration, not just a visual refresh. Before changing the design or platform, record the URLs and search performance you already have. Then preserve valuable pages and their content, redirect URLs that must change, and test the new site before and after launch.
Some search movement can happen after a launch, but avoidable problems—such as missing pages, broken redirects, blocked crawling, or incorrect canonical tags—can make it worse. Use the checklist below to give search engines clear signals about what changed and to help your team spot issues quickly.
1. Crawl and inventory every existing URL
Start with a crawl of the live site. Export every URL you can find, including pages, blog posts, category pages, PDFs, and other files that bring visitors or receive links. Compare the crawl with your XML sitemap, analytics landing-page report, and Google Search Console’s indexed pages and performance reports. No single source is guaranteed to show every URL.
For each URL, record its current status code, title tag, meta description, canonical URL, indexability, and—where possible—organic clicks, impressions, and inbound links. Note the page’s purpose and whether it should stay, be updated, be consolidated with another page, or be retired. This inventory becomes the source of truth for design, content, redirects, and launch checks.
Pay special attention to URLs with search impressions, organic visits, useful backlinks, or a clear business purpose. A page with little traffic today may still answer a buyer’s question or support another important page. Don’t delete a page simply because it looks dated or is absent from the main navigation.
2. Keep URLs where possible and map the rest
If a URL is clear, accurate, and already established, keep it. A redesign does not require changing the site’s address structure. Keeping URLs reduces migration work and avoids making search engines and visitors follow unnecessary redirects.
When a URL must change, create a redirect map before development is complete. Match each old URL to its closest relevant new destination, normally with a permanent 301 redirect. Avoid sending every retired page to the homepage; that gives visitors little context and may not be a useful replacement for the original page.
Include every URL in the map, including pages outside the main navigation. Check for redirect chains, where one old URL redirects through another before reaching the destination, and loops, where URLs send visitors back and forth. Redirect directly to the final destination whenever possible.
Use this short review for each old URL:
- Does the page still serve a useful purpose? Keep its URL if you can.
- Is it being replaced or renamed? Map it to the closest relevant new page.
- Is it being merged into another page? Redirect to that page and retain useful information.
- Is there no suitable replacement? Decide deliberately whether to return a not-found or gone status rather than redirecting to an unrelated page.
- Does the destination load successfully, use the preferred protocol and hostname, and avoid another redirect?
Test the redirect map against the old URL inventory before launch. After launch, test it again on the live site. A spreadsheet is useful only if the redirects are actually implemented and verified.
3. Preserve the content and signals that already work
For pages that attract search traffic, carry over the substance before polishing the copy. Preserve the page’s main topic, useful detail, headings, and answers to buyer questions. You can improve clarity and structure, but replacing a detailed service page with a short generic description may remove information that helped it earn visibility.
Record the title tag and meta description for important pages, then confirm the new versions still describe the page accurately. Keep a clear heading hierarchy and make sure internal links point to the correct new URLs. Links in navigation, related content, and calls to action should not keep sending visitors through redirects.
If a page needs substantial rewriting, keep a record of what changed and why. That makes later investigation more useful: if a page loses impressions after launch, your team can compare the old and new versions instead of guessing. Don’t promise that preserving copy will preserve rankings; it simply avoids discarding useful signals without a reason.
The work should include technical details as well as design and content. In ASAYA’s rebuild of asayamedia.com, the team kept all 154 existing URLs, served full HTML for every page, and fixed conflicting canonical tags on about 100 service pages. You can see the asayamedia.com rebuild case study for the example.
4. Check canonicals, rendering, and structured data
Every indexable page should have a canonical tag that points to the intended preferred URL. Check that the new site does not accidentally canonicalize multiple distinct pages to one address, point canonicals back to the old domain, or produce inconsistent versions with and without a trailing slash. A canonical tag is a signal, not a substitute for redirects when an address has permanently moved.
Check how the page content reaches a search engine. For important pages, confirm the primary content and links are present in the HTML response, rather than appearing only after a browser runs JavaScript. Server-rendered or otherwise fully rendered HTML makes the essential content and links available without relying on client-side behavior. Test the live rendered page as well as the source response.
If the site uses structured data, carry it over only where it remains accurate and supported by visible page content. Validate the markup, check that it describes the correct page, and remove outdated details. Structured data can help search engines interpret information, but it does not guarantee a particular search result or display.
Before launch, check the sitemap and robots.txt. The live XML sitemap should contain the preferred, indexable URLs—not old addresses, redirects, or pages marked noindex. Make sure robots.txt does not block important pages or required assets. A robots.txt rule controls crawling; it is not a reliable way to remove a page from search results.
5. Run a pre-launch checklist on the staging site
A staging site is a place to test the finished build before visitors and search engines encounter it. Keep private staging environments protected from indexing, but plan how that protection will be removed at launch. Before going live, review the site as both a visitor and a crawler.
- Crawl the staging site and check that important pages return successful status codes.
- Compare the new URL list with the old inventory and confirm that every important old URL has a destination or a deliberate retirement decision.
- Test redirects, including old HTTP URLs, alternate hostnames, trailing-slash variants, and common campaign or resource URLs.
- Check page titles, descriptions, headings, canonicals, indexability, and structured data on representative page types.
- Confirm that key page content and internal links are present in rendered HTML and work on mobile.
- Check that the staging noindex or access restriction has a documented removal step for launch.
- Verify analytics and search-related tracking so you can compare performance after launch.
- Prepare a final sitemap and confirm that the live robots.txt will permit crawling of the pages you want indexed.
Test more than the homepage. Include each distinct template, such as service pages, articles, location pages, and contact or conversion pages. A shared template error can affect many URLs at once, so sampling one page type is not enough if the site has several.
6. Check the live site on launch day and monitor it afterward
Once the new site is live, check it on the production domain rather than assuming staging tests carried over. Load key pages, verify redirects, inspect canonicals, and confirm that the intended pages are indexable. Check that no staging block remains and submit the current sitemap through the search console tools you use.
Keep the old URL inventory and redirect map available to the person responsible for launch. Crawl the live site promptly and compare its URLs and status codes with the plan. If a page returns an error, a redirect points to an unrelated destination, or a whole template is blocked, treat that as a priority rather than waiting for routine reporting.
For the following weeks, review Search Console for indexing issues, unexpected exclusions, crawl problems, and changes in clicks and impressions. Compare performance by page and query where possible, not only by total site traffic. Check analytics landing pages and conversion tracking too; a traffic change and a conversion change are related questions, but they are not the same measurement.
If you see a decline, look for patterns before making broad changes. Are affected pages all using one template, sharing a redirect destination, or missing from the sitemap? Did their content or canonical tags change? Search performance can fluctuate, so use evidence from URL inspection, crawls, and page-level reports to distinguish a technical fault from normal variation. Keep a log of fixes and dates so you can assess what helped.
Where to start
Begin with the URL inventory, even if the design work has already started. It gives your team a concrete list of pages to preserve, improve, redirect, and test. If the project includes a new platform, domain, or complex URL structure, bring migration planning into the project early rather than treating it as a final launch task.
ASAYA’s Website Redesign and Migration service starts at $6,500 (six to sixteen weeks). For ongoing search work, Search Engine Optimization starts at $1,600 per month. These are different scopes: a migration focuses on redesign and transition, while ongoing SEO supports continuing search visibility work.
Frequently asked questions
Yes. Search engines need to process changes, and traffic can fluctuate after launch. Careful URL mapping, redirects, and technical checks reduce avoidable problems but cannot guarantee unchanged rankings.
Keep established URLs when they are clear and still fit the page. If a URL must change, redirect the old address to the closest relevant new page and test the redirect after launch.
Check the live site on launch day, then review indexing, crawl issues, clicks, and impressions over the following weeks. Continue monitoring until you can identify whether changes are isolated, template-wide, or part of a broader trend.

Written by
Daniel Lamberth
Founder & Creative Director at ASAYA Media. 15+ years across visual effects, motion, illustration, and software; author of Mastering FLUX.



