You redesign a website without losing your Google rankings by recording everything the old site ranks for before you start, keeping the URLs that perform or redirecting every one of them with a permanent 301 redirect to its closest new page, carrying over the content, titles and internal links that earned those rankings, testing the new site with search engines blocked, and monitoring Google Search Console closely for several weeks after launch. Done carefully, a redesign is an opportunity to rank higher. Done carelessly, it is the most common reason established businesses suddenly lose their search traffic.
The short version
- Benchmark first. Export rankings, traffic, top pages and backlinks before anything changes
- Map every old URL. Each one should stay the same or 301 redirect to the most relevant new page
- Keep what ranks. Preserve the content, titles and headings of high-performing pages unless you are deliberately improving them
- Test before launch. Crawl the staging site, check redirects, tags and speed, and keep staging out of Google
- Watch after launch. Monitor Search Console, fix errors fast and expect a short period of fluctuation
Why redesigns lose rankings
Google ranks individual URLs. Each one has built up signals over time, including the searches it matches, the links pointing to it, its click history and its position in your internal linking. When a redesign changes or deletes URLs without redirects, those signals are thrown away. Google finds 404 errors where pages used to be, links from other sites lead nowhere, and the new pages start from scratch.
Other common causes include content being cut or rewritten without its key phrases, titles and headings replaced with generic marketing copy, staging-site noindex tags or robots.txt blocks going live, internal links removed in a new navigation, slower page templates, and JavaScript-heavy builds that hide content from crawlers.
Phase 1. Before you design anything, benchmark
Capture a full picture of how the current site performs, so you know what to protect and can measure the result.
- Export Search Console data. Queries and pages for the last 12 to 16 months, with clicks, impressions and positions.
- Export analytics. Top landing pages by organic traffic and conversions.
- Crawl the current site with a crawler tool to record every URL, its status code, title, meta description, H1, canonical and internal links.
- List pages with backlinks, because those carry authority from other sites.
- Record rankings for your most important search terms.
- Save the sitemap and any existing redirects.
Mark your most valuable pages, the ones that bring the most organic traffic, conversions or links. These need the most care.
Phase 2. Plan the new structure with SEO in mind
A redesign is a chance to improve structure, as long as changes are deliberate.
- Keep URLs that work. If a URL ranks well and still fits the new structure, keep it exactly as it is. The safest redirect is the one you never need.
- Group content logically. Make sure every service, product and location has a clear page, and that related pages link to each other.
- Do not merge or delete high-value pages casually. If two pages compete for the same search, merging them can help, but redirect the old one to the new one.
- Keep important pages close to the homepage, within two or three clicks.
- Plan for new pages that target searches the old site missed.
Phase 3. Build a complete redirect map
The redirect map is the heart of a safe migration. It is a spreadsheet listing every old URL and the new URL it should go to.
| Old URL | New URL | Redirect type | Notes |
|---|---|---|---|
| /services.html | /services/ | 301 | Hub page |
| /seo-services | /services/seo-management/ | 301 | High traffic, keep title |
| /blog/2019/10/seo-tips | /blog/how-to-improve-seo/ | 301 | Merged into updated guide |
| /old-promo | /offers/ | 301 | Closest equivalent |
| /test-page | none | 410 | No value, remove |
Follow these rules when you build it.
- Use 301 redirects for permanent moves. A 302 tells Google the move is temporary.
- Redirect each page to its closest new equivalent. Mass redirects to the homepage are treated like soft 404s and lose the page's value.
- Avoid chains. Each old URL should reach its final destination in one hop. Update old redirects so they point directly to the new URLs.
- Cover variations, including http and https, www and non-www, trailing slashes and old file extensions such as .html and .php.
- Include images and PDFs that receive traffic or links.
Phase 4. Carry over the content and on-page SEO
Design can change freely. The words that rank deserve more care.
- Keep the substance of high-performing pages, including the sections and phrases that match what people search. Improve them, but do not cut what made them rank.
- Carry over title tags and meta descriptions for top pages, or improve them deliberately.
- Keep one H1 per page with the main topic.
- Preserve internal links between related pages, and add more where the new structure allows.
- Carry over structured data, image alt text, canonical tags and hreflang tags.
- Keep the content in the HTML. If the new site uses a JavaScript framework, make sure pages are rendered on the server or pre-rendered.
Phase 5. Test everything on staging
Build the new site on a staging environment that search engines cannot index, protected by a password or a noindex rule, then test thoroughly.
- Crawl the staging site and compare titles, H1s, canonicals and status codes with the old crawl.
- Test every redirect in your map and confirm each returns a single 301 to the correct page.
- Check speed and Core Web Vitals on key templates, on mobile.
- Validate structured data with Google's Rich Results Test.
- Check robots.txt and meta robots for the production version, so nothing is accidentally blocked.
- Test forms, tracking and analytics so you do not lose conversion data at launch.
The most expensive launch mistake. Staging sites are usually blocked from search engines with noindex tags or robots.txt rules. If those settings go live with the new site, Google drops pages from its index. Make removing them an explicit launch checklist item, and check the live site within minutes of launch.
Phase 6. Launch day
- Launch at a quiet time for your business, early in the week, so your team can respond quickly.
- Put redirects live at the same moment as the new site.
- Remove staging blocks, check robots.txt and meta robots on the live site.
- Submit the new XML sitemap in Search Console and keep the old one available briefly so Google discovers the redirects.
- Run your free SEO check on the live site immediately.
- Spot-check your top twenty old URLs to confirm they redirect correctly.
Phase 7. Monitor for the next eight weeks
Expect some movement as Google reprocesses the site. Watch closely and fix problems fast.
- Search Console Pages report for spikes in 404s, excluded pages or redirect errors.
- Performance report comparing impressions and clicks with the benchmark.
- Rankings for your key search terms.
- Analytics for organic landing pages and conversions.
- Server logs or crawl stats to confirm Google is crawling the new URLs.
A short dip of a few weeks is common even in well executed migrations. A drop that keeps deepening after four weeks usually points to missing redirects, lost content or a technical block, and should be investigated immediately.
Want a website or app that actually brings in customers?
We design and build fast, search-ready websites and mobile apps from scratch, or rebuild the ones you have so they rank and convert
Who should be involved
A safe redesign needs more than designers and developers. Bring in whoever owns SEO from the first planning meeting, along with the person responsible for analytics and tracking, and someone who knows which pages bring in leads or sales. Agree who signs off the redirect map and who checks Search Console after launch. Many ranking losses happen because each team assumed another was handling redirects or tags.
Use the redesign to rank higher
A redesign done with SEO in mind can lift rankings well above where they were. Use it to give every service and location its own page, fix slow templates, add structured data across the site, tidy internal linking, merge thin duplicate pages into strong ones, and rewrite introductions so each page answers its main question in the first paragraph. Because Google recrawls the whole site after a launch, improvements made during a redesign are picked up faster than piecemeal changes.
Changing domains or platforms
Domain changes and platform moves carry more risk than design changes, because every URL changes at once.
For a domain change, redirect every old URL to its equivalent on the new domain, keep the redirects in place for at least a year and ideally permanently, use the Change of Address tool in Google Search Console, update links you control on social profiles, directories and partner sites, and keep the old domain registered.
For a platform change, such as moving from one CMS or e-commerce platform to another, pay special attention to URL patterns, which often change by default. Product, category and blog URLs may need custom rules or redirects. Check that the new platform supports the redirects, canonical tags, structured data and speed you need before committing.
Signs your redesign went well
- Impressions and clicks return to the benchmark within a few weeks and then grow.
- No unexpected rise in 404s or excluded pages in Search Console.
- Key search terms hold or improve their positions.
- Core Web Vitals improve thanks to the new templates.
- Organic conversions rise because the new design makes the next step clearer.
Redesign SEO checklist
- Benchmark rankings, traffic, top pages and backlinks.
- Crawl the old site and keep a copy of the data.
- Plan the new structure, keeping URLs that work.
- Build a complete one-to-one redirect map.
- Carry over content, titles, headings, internal links and structured data.
- Test staging thoroughly, with search engines blocked.
- Launch with redirects live, staging blocks removed and a new sitemap submitted.
- Monitor Search Console and analytics daily for two weeks, then weekly for two months.