Key takeaways
- List every URL that gets traffic or links before anyone touches the design.
- Map each old URL to its closest new page and use server-side permanent redirects (301 or 308).
- Keep redirects for as long as possible, generally at least one year, as Google recommends.
- Keep the content that ranks. A prettier page with half the text is a different page to Google.
- Block the staging site, and remember to unblock the live one on launch day.
- Some ranking movement is normal for a few weeks. Monitor daily for the first month.
Why do redesigns lose traffic?
Redesigns lose traffic when Google can no longer find what it used to rank. The usual causes are changed URLs without redirects, deleted or shortened content, a staging noindex left on the live site, new menus that drop internal links and missing titles or schema. The design itself is rarely the problem. The migration is.
Google treats a redesign that changes URLs as a site move. Its guide to site moves with URL changes describes the whole process: prepare the new site, map old URLs to new ones, redirect, and monitor. Everything below follows that guide, plus what I have learned doing it in practice.
Step 1: inventory every URL
Before design starts, build the list of pages you cannot afford to lose. Combine three sources: a full crawl of the current site, the pages with clicks in Search Console over the last 12 months, and the pages that other sites link to. Add your top landing pages from Analytics. Save titles, meta descriptions, H1s and word counts, so you can compare later.
How do you build a redirect map?
Put every old URL in a spreadsheet and write, next to each one, the new URL that best matches its content. Services go to the same service, articles to the same article, deleted products to the closest category. Only pages with no equivalent and no traffic should return 404. Review the map before development, not after launch.
| Old URL | New URL | Action |
|---|---|---|
| /services/ac-repair.html | /ac-repair/ | 301 to the same service |
| /blog/2019/furnace-tips | /blog/furnace-maintenance-tips/ | 301 to the updated article |
| /team-old/ | /about/ | 301 to the closest page |
| /promo-summer-2021/ | None | 410 or 404, if it has no traffic or links |
Avoid the shortcut of sending every old URL to the home page. Visitors land somewhere that does not answer their search, and search engines lose the page-by-page match that let you rank.
Which redirects should you use?
Use server-side permanent redirects, 301 or 308, from each old URL straight to its final new URL in one hop. Google recommends keeping them for as long as possible, generally at least one year. Avoid JavaScript redirects, temporary 302s for permanent moves and chains where one redirect leads to another before the final page.
Redirects are also the strongest way to tell Google which URL is the main one. Its guide to canonical URLs lists redirects and rel="canonical" as strong signals. After launch, update internal links to point to the new URLs directly, instead of relying on redirects forever.
Step 2: keep content parity
The new page for each important URL should keep the substance of the old one: the same topic, the main headings, the text that answered the search, the FAQs, images with alt text, titles and structured data. Designers often cut text to make pages look clean. If a service page ranked because it explained prices, process and service areas, the new version needs that too. Improve the content if you like, but do not quietly remove what was working.
Step 3: block staging, then unblock it
Google advises blocking the test site from crawling, with robots.txt or noindex, and removing those blocks when the new site goes live. Both halves matter. An indexed staging site creates a duplicate of your business. A live site that keeps the staging block disappears from Google. I also protect staging with a password, so no one outside the team sees it.
Launch day checklist
- Remove noindex and staging robots.txt rules from the live site.
- Test a sample of redirects from the map, including your top 20 pages by traffic.
- Crawl the new site: no 404s from internal links, no redirect chains, one canonical per page.
- Titles, meta descriptions, H1s and structured data are in place on every key template.
- Submit the new sitemap in Search Console and keep the old one submitted for a while.
- Check the phone number, forms and analytics events: leads must keep being recorded.
- Use URL Inspection on the home page and main service pages and request indexing.
- If the domain changed, use the Change of Address tool in Search Console.
Submitting both sitemaps is a trick from Google's own guide: at first the new sitemap shows few indexed pages and the old one many, and you can watch the numbers swap as Google processes the move. Just remember that a sitemap helps discovery but does not guarantee indexing.
What should you monitor in the first 30 days?
Watch indexing, errors, rankings for your main pages and, above all, leads. Check Search Console and your crawler daily in the first week, then weekly. Compare clicks per page against the pre-launch baseline, not just site totals. Any page that lost most of its clicks usually points to a missing redirect or missing content.
| When | What to check | Where |
|---|---|---|
| Day 1 | Live site indexable, redirects working, forms and calls tracked | Browser, crawler, URL Inspection, GA4 |
| Days 2 to 7 | New 404s, server errors, pages excluded from the index | Search Console Pages report, server logs |
| Week 2 | Clicks and position for your top 20 pages versus baseline | Search Console Performance, filtered by page |
| Week 3 | Old sitemap indexed count going down, new one going up | Search Console Sitemaps |
| Week 4 | Leads from organic search versus the same period before launch | GA4, call tracking, CRM |
Is a traffic dip after launch normal?
A small, temporary dip is normal. Google says rankings may fluctuate while it recrawls and reindexes, and that a medium-sized site can take a few weeks or more to settle, while larger sites take longer. A sharp drop on specific pages that does not recover is not normal and usually has a fixable cause.
When that happens, go back to the redirect map and the content comparison for the pages that lost traffic. In most cases the fix is a missing redirect, a noindex, or content that was cut.
Planning a redesign
I build fast, interactive websites through my web design and development service, and every build includes the migration plan above. If another team is building your site, I can handle the SEO side as a technical SEO project: URL inventory, redirect map, staging review and launch monitoring. Before you commit, it is worth reading do I need a new website for SEO? and running the technical SEO checklist on your current site.
The rest of my approach is on the SEO consultant home page. See pricing, or book a free 30-minute call to review your redesign plan before launch.
Frequently asked questions
How long should I keep redirects after a redesign?
Google recommends keeping them for as long as possible, generally at least one year. I usually leave them in place indefinitely.
Can I change my URLs to make them cleaner?
Yes, if each old URL redirects to its new equivalent. Change URLs only when there is a real benefit, because every change adds migration risk.
Should I redesign and change domain at the same time?
It is safer to do one big change at a time, so you can tell which one caused any drop.
Will a new design improve my rankings by itself?
Not by itself. Rankings follow content, links, relevance and technical health. A redesign helps when it improves those, not just the look.
What if my traffic already dropped after a redesign?
Compare old and new URLs for the pages that lost clicks. Missing redirects and cut content are the usual causes, and they can often be fixed.
