How to keep rankings after a redesign
A redesign keeps its rankings when the things search engines rely on stay the same or improve: the URLs, the content on each page, the internal links, and the titles, headings and structured data your templates output. Most redesign traffic losses come from something changing by accident, such as a URL structure that shifted, copy trimmed to fit a new layout, or a staging noindex that shipped to production.
Google's site move documentation notes that any significant change to a site can bring ranking fluctuations while Google recrawls and reindexes it. The aim is to keep those fluctuations short by changing as little as possible that search depends on, and by checking the rest before and after launch.
What a redesign quietly breaks
| What changes | Why it matters | How to catch it |
|---|---|---|
| URL structure | Old URLs lose their signals unless redirected | Compare old and new crawls |
| Page copy | Shorter pages may stop answering the query | Diff the text of top pages |
| Navigation | Pages dropped from menus lose internal links | Count inlinks before and after |
| Title and heading templates | New templates may output generic titles or no H1 | Check page source on each template |
| Structured data | Theme-provided schema may vanish | Rich Results Test on each template |
| Robots and canonicals | Staging settings leak into production | Inspect key URLs after launch |
| Rendering | Content loaded by scripts may not be seen | URL Inspection's rendered HTML |
If the redesign also moves domains or changes the permalink structure, follow the domain move guide or the permalink change guide as well.
Before, during and after launch
- Crawl the live site and save the list. Every URL, its title, H1, canonical, status code and word count. This is your baseline.
- Export your top pages from Search Console. The pages with the most clicks over the last 12 months are the ones you cannot afford to damage.
- Keep URLs where you can. A redesign does not need new URLs. Every URL that stays the same is one less redirect to get right.
- Map every URL that must change to its closest new equivalent, one hop, no chains. The redirect rule generator turns a two-column list into server rules and flags chains. On WordPress, Hydrogen SEO's Redirection Manager takes the same mappings without editing server files.
- Protect staging with a password, not only noindex, so there is no setting to forget at launch.
- Compare staging against the baseline. Titles, H1s, body text on top pages, internal links, schema and canonicals on each template.
- Launch, then test immediately. Load a sample of old URLs and confirm they return 301 to the right place. Inspect the homepage and top pages in Search Console. Confirm robots.txt and the sitemap are the production versions.
- Resubmit the sitemap and request indexing for a handful of the most important pages.
The monitoring window after launch
Watch three reports:
- Pages in Search Console for spikes in "Not found (404)", "Page with redirect" or "Excluded by noindex".
- Performance for your top pages, comparing each week with the weeks before launch.
- Crawl stats for server errors and response time on the new setup.
Google's documentation on hosting changes without URL changes says a temporary drop in crawl rate right after launch is normal, followed by a steady increase over the next few days. Where URLs changed, its site move guide says a medium-sized site can take a few weeks or more for Google to show the new URLs in place of the old ones.
From experience, and not as a promise: a redesign that kept URLs and content usually settles within two to six weeks. One with many redirects can take a few months. A drop that is still growing after a month points to something broken rather than normal fluctuation; go back to the baseline and compare. Keep redirects for at least a year, as Google's site move guide recommends.
Redesign mistakes
- Launching without a crawl of the old site. Without a baseline you cannot tell what changed.
- Redirecting everything to the homepage. Google tends to treat that as a soft 404, and the old pages' signals are lost; see soft 404.
- Trimming copy for the new design. Shorter, prettier pages often stop answering the query they ranked for.
- Switching SEO plugins at the same time and losing custom titles. If you must, use Hydrogen SEO's importer so existing titles, descriptions and redirects come across.
- Removing old blog posts from navigation so they become orphans.
- Chained redirects from earlier migrations; see fixing redirect chains.
Launch-day checklist
- Baseline crawl and Search Console top pages saved.
- Redirect map tested: sample of old URLs return one 301 to the right page.
- No noindex, staging robots.txt or wrong canonical on production.
- Titles, H1s and schema correct on every template.
- Top pages keep their main content.
- Sitemap resubmitted; key pages inspected.
- Weekly checks booked for the next six weeks.
Common questions
Will a website redesign hurt my SEO?
It does not have to. Losses come from changed URLs without redirects, removed content, broken templates or leftover staging settings. A redesign that keeps URLs and content and fixes those risks usually settles within weeks.
How long should I keep redirects after a redesign?
Google's site move documentation recommends keeping redirects for as long as possible, generally at least a year, so it can transfer signals and recrawl links that point to the old URLs.
Should I change my URLs during a redesign?
Only if the old ones are genuinely broken or misleading. Keeping URLs the same removes the biggest source of redesign ranking losses.
My rankings dropped after the redesign. What should I check first?
Check for a noindex or robots.txt block on production, then test old URLs for correct 301 redirects, then compare titles and content on your top pages with the pre-launch crawl.