Why rankings drop after a redesign
Google ranks individual pages, not websites. When a redesign changes page addresses without redirects, removes content that was ranking, rewrites titles and headings, or launches with search engines still blocked, Google loses the signals it used to rank those pages. The site looks better, but to Google it is partly a new site.
- Changed URLs with no 301 redirects, so old links and rankings point at error pages.
- Removed or heavily trimmed content on pages that were bringing in traffic.
- New titles, headings, and internal links that no longer match what people search for.
- A staging setting that blocks search engines, left on after launch.
- A slower site, especially on phones, because of heavy images, scripts, or a page builder.
Step 1: Benchmark before you touch anything
Record where you stand so you can measure the result. In Google Search Console, export the pages and queries that brought in clicks over the last few months. From your analytics, note the pages that bring in leads or sales. Crawl the current site to capture every URL, title, meta description, and heading.
This list tells you which pages carry the site. Those pages keep their address, their core content, and their focus through the redesign, even if everything around them changes.
Step 2: Keep URLs, or map every redirect
The safest redesign keeps every URL exactly as it is. When the structure has to change, build a redirect map: every old URL in one column, its new URL in the next, and a permanent 301 redirect for each one. Redirect to the most relevant new page, not to the homepage, which Google tends to treat as a soft error.
Do not forget addresses that only exist outside your navigation: old campaign landing pages, PDFs, and images that other sites link to. The links report in Search Console and your crawl will surface most of them.
Step 3: Preserve what ranks
A new layout can present the same information better, but the substance of your best pages should survive. Keep the text that answers the searcher’s question, the headings that match it, and the title and meta description, unless you have a clear reason to improve them. Keep internal links pointing at your important pages, because they tell Google which pages matter most.
If you consolidate several thin pages into one stronger page, redirect each old page to it. If you add new service or location pages, write each one for its audience instead of copying a template, so Google sees them as useful rather than as duplicates.
Step 4: Build on staging, safely
Build the new site on a staging address that search engines cannot index, behind a password or a noindex setting, so Google never sees two copies of your site. Then make removing that block an explicit item on the launch checklist. Launching with noindex still on is one of the most common and most damaging redesign mistakes, and it is easy to miss because the site looks perfectly normal to visitors.
Step 5: Run the technical checks
Before launch, go through the new site page type by page type:
- Each page has one clear H1, a unique title, and a meta description.
- Canonical tags point at each page’s own final URL.
- The XML sitemap lists the new URLs, and robots.txt does not block anything important.
- Structured data, such as your business details and FAQs, carries over and validates.
- Core Web Vitals hold or improve: images are compressed and sized, and scripts are kept to what each page needs.
- The site works with a keyboard and a screen reader, and text has enough contrast.
Questions to ask whoever builds it
Whether you hire an agency or a freelancer, or do the work in-house, these questions show quickly whether search has been planned for:
- Will every current URL keep working, and where is the redirect map?
- How will the staging site be kept out of search results, and who removes that block at launch?
- Which pages will change their content, and why?
- How will speed on phones be measured before and after?
- Who watches Search Console after launch, and for how long?
Clear answers to all five are a good sign. Vague answers to the first two are the biggest warning.
Step 6: Launch, then monitor for 4 to 8 weeks
Launch on a quiet day, then test the redirect map against the live site right away. Submit the new sitemap in Search Console and request indexing for your most important pages. Over the following weeks, watch the pages report for spikes in not-found errors, compare clicks for your benchmark pages, and fix any missed redirect quickly.
Some fluctuation in the first two to four weeks is normal while Google recrawls. A steady drop on specific pages usually points to a specific cause: a missing redirect, lost content, or a changed title. The benchmark from step one is what lets you find it.
For an example of a redesign focused on mobile shoppers and checkout, see the Bikerevier case study. If you are planning one, my website redesign service follows this process from benchmark to post-launch monitoring, and the migration checklist covers changing platforms at the same time.