Protect Useful Search Signals During a Website Redesign
Export a baseline of the current site, map every old URL to its new home, keep staging out of search, test redirects and templates before and after launch, agree a rollback plan, and monitor for weeks. Expect some temporary fluctuation — no redesign can guarantee unchanged rankings.
No redesign can guarantee unchanged rankings. Google says to expect temporary ranking fluctuation during a move, and that medium-sized sites can take a few weeks or more before the new URLs replace the old ones. Google: site moves with URL changes
Export a dated baseline.
Once the old site is gone, this evidence is gone too. Tick each export as you save it.
Every old URL needs a decision.
Google recommends mapping old URLs to new ones and using server-side permanent redirects that follow the map. Change a decision or a destination and watch the expected server response update.
| Old URL | Decision | New URL | Expected response |
|---|---|---|---|
| /services/web-design/ | |||
| /about-us/ | |||
| /blog/seo-tips-2019/ | |||
| /web-design-pricing/ | |||
| /old-promo/ | |||
| /contact/ |
Redirect straight to the final destination. Google advises avoiding chains.
Many old URLs sent to the homepage can be treated as soft 404s.
Keep redirects for as long as possible — generally at least one year.
Example URLs are illustrative.
Keep staging private — and know what changes at launch.
The rules that protect staging are the same rules that can hide the new site if they reach production.
Google: robots.txt is not a way to keep pages out of Google — use noindex or password protection. robots.txt introduction · Site moves
- Staging passwordOn — team onlyStill on for staging
- noindex on new templatesOn in stagingRemoved on production
- Development robots.txt blockAllowed in stagingReplaced with final file
- Redirect rulesWritten and testedLive on the old URLs
- AnalyticsTest propertyProduction property
A launch runbook, not a launch day.
Tick items off as your team works through them. The line fills as each stage is completed.
Decide what triggers a rollback before you launch.
Write down the triggers, the action and the owner, and keep a tagged backup of the previous release ready to restore.
Site-wide 5xx errors or blank pages
Restore the previous release from the tagged backup
Developernoindex or robots.txt block live on production
Hotfix the rule immediately, then re-test with URL Inspection
DeveloperRedirects missing or looping on key pages
Re-deploy the tested redirect file; roll back if it can’t be fixed within the agreed window
DeveloperForms or checkout failing
Roll back the affected template or switch to the fallback form
Developer + ownerTracking not firing
Fix tags before judging any traffic change
MarketingWatch the handover for weeks, not hours.
Google describes the expected pattern: indexing of old URLs falls while new URLs rise, with temporary fluctuation along the way.
- Server logs: Googlebot errors and unexpected status codes
- Old URLs returning 404 that still get links or traffic
- Page indexing and both sitemaps in Search Console
- Key-page clicks and conversions against the baseline
- Redirects still live — at least a year
Timing varies by site size; larger sites take longer. Google: site moves
Redesign SEO questions
Straight answers, including what nobody can promise.
Yes. Missing redirects, removed content, development noindex rules left in place, broken internal links or changed templates can all cause pages to lose visibility or traffic.
No one can guarantee that. Google says to expect temporary ranking fluctuation during a move while it recrawls and reindexes the site. Good planning reduces avoidable losses; it does not freeze rankings.
Before design starts. The baseline export and URL map shape the sitemap, templates and content decisions, and are much harder to reconstruct after launch.
Yes, whenever a URL changes or a page is merged. Use server-side permanent redirects to the most relevant new page, and keep them for as long as possible — Google suggests generally at least a year.
Usually not. Google advises against redirecting many old URLs to one irrelevant destination such as the homepage; it can be treated as a soft 404. Redirect to a relevant replacement, or let the page return 404 or 410.
Yes. MTI Tech can build the baseline, URL map and redirect file, run launch QA and monitor the weeks after launch alongside the web development work.
Bring SEO in before the first wireframe.
We build the baseline, URL map and redirect file, run launch QA and monitor the weeks after.