Collect current URLs
Combine the sitemap, Search Console data, analytics and a crawl where appropriate. Mark pages with traffic or external links.
Before, during and after
Website redesign without unnecessary search risk
A visual redesign alone does not remove a page from Google. Risk appears when important URLs, content, canonical data, internal links or crawler access change without a controlled plan.
Short answer
Keep working URLs or redirect them directly to equivalent content.
Document current URLs and valuable content. Build and test the new version separately, prepare an accurate URL map, use permanent server-side redirects where needed, and update canonical tags, internal links and the sitemap. Monitor server errors and Search Console after launch.
Written by AI net. Updated 3 October 2026.
Before the redesign
Record the baseline
Without a baseline, you cannot tell what disappeared or changed during the redesign.
Decide the future of each page
Mark every page: keep, update, merge or remove. Removing content and changing its URL are separate decisions.
Create a restorable backup
The backup should cover files and the database. Also confirm the restoration process and access credentials.
Build a staging version
Keep the development copy out of the public index, but remove temporary crawl and indexing blocks before the live launch.
Launch
Describe every change clearly
Google recommends an accurate URL map and permanent server-side redirects when visible URLs change.
Keep the URL where possible
A visual redesign does not require URL changes. An unnecessary change creates extra work for users and search systems.
Redirect to the closest equivalent
Do not send every old service page to the home page when a more relevant destination exists. An irrelevant destination may be treated as a soft 404.
Update the site's own references
Canonical and hreflang links, navigation and contextual links should point directly to final URLs.
Remove launch blocks
Review robots.txt, robots meta rules, HTTP headers and access restrictions. A staging noindex rule must not remain on the live site.
After launch
Monitor the move without promising a fixed recovery time
Processing time depends on the number of URLs, server performance and crawl activity. Search visibility can fluctuate temporarily.
Sitemap and Search Console
Publish the updated sitemap, retain ownership verification and inspect important URLs.
404 and server errors
Monitor logs and reports. Fix missing destinations and broken internal links.
Traffic and enquiries
Compare traffic and conversions on important landing pages with the recorded baseline.
User experience
Core Web Vitals are used by Google's ranking systems, but a good score does not guarantee a ranking. Improve speed primarily for users.
Official sources
What is this guidance based on?
These links open the current Google Search Central documentation.
Site moves with URL changes
Google covers URL mapping, redirects, canonical tags, noindex rules, sitemaps and monitoring as one migration plan.
Open Google's guide ↗Page experience and Core Web Vitals
Google states that good report scores do not guarantee a top ranking and relevant content remains central.
Open the page-experience guide ↗AI net website redesign
URLs and launch are planned before migration.
AI net works with different publishing platforms and custom-built websites. The exact URL map, content migration and required redirects are agreed in the written proposal.
Request a website estimate →