A new website should bring you more visitors, not fewer. Yet many businesses see their Google traffic drop after a redesign, sometimes by half, and it can take months to recover. Almost always, the cause is not the new design. It is something that got lost in the move.
The good news: a relaunch that is planned properly usually keeps its rankings, and often improves them. Here is the checklist to follow.
Why rankings drop after a redesign
Google ranks individual pages, at individual addresses (URLs). Each one has a history: the searches it appears for, the links pointing to it from other sites, the way visitors behave on it. When a relaunch changes or deletes those addresses without telling Google where the page went, that history is lost. To Google, the new page is a stranger.
The most common causes of a drop are:
- Changed URLs without redirects.
/our-servicesbecomes/services, and the old address now shows an error page. - Removed or thinned content. A page that ranked well is merged, shortened or cut because it “didn’t fit the new design”.
- Lost titles and descriptions. Carefully written page titles are replaced with defaults.
- A blocked site. The “don’t index this” setting used during development is still switched on after launch.
- Weaker internal links. The new navigation no longer links to pages that used to be prominent.
- Slower pages. Heavy images and video added without care.
Every one of these is avoidable.
Before you change anything: record where you stand
You can only protect what you have measured. Before design starts, record:
- Your top pages. In Google Search Console, open Performance, set the date range to the last 12 months and export the pages and queries. These are the pages you must not lose.
- Every URL on the current site. A crawler such as Screaming Frog (free up to 500 URLs) lists every page, image and document, with titles, descriptions and status codes.
- Your backlinks. Search Console’s Links report shows which of your pages other sites link to. Those pages carry extra weight.
- A traffic baseline. Note visits and enquiries per month from your analytics, so you can compare honestly after launch, allowing for seasonal swings.
Plan the new structure around what works
A redesign is a good moment to tidy up, but be deliberate:
- Keep URLs that work. If an address does not need to change, don’t change it. This is the single most effective way to keep rankings.
- Keep the content that ranks. You can redesign a page completely. Just keep the substance that answers the searcher’s question, and improve it rather than shortening it.
- Merge thin pages thoughtfully. Three weak pages on the same topic can become one strong one, as long as all three old addresses redirect to it.
- Carry over titles and meta descriptions, then improve them where they are weak.
Build a redirect map
A redirect map is a simple spreadsheet: every old URL in one column, its new address in the next. Each old page gets a 301 redirect (a permanent redirect) to the single most relevant new page.
A few rules:
- One to one where possible.
/old-pageshould go to its true replacement, not to the home page. Redirecting everything to the home page is treated by Google much like a missing page. - No chains. A to B to C slows visitors down and wastes crawling. Point A straight at C.
- Include images and PDFs that receive traffic or links.
- Only remove pages on purpose. If a page truly has no replacement, a 404 or 410 status is acceptable. Just make sure it is a decision, not an accident.
Build and test on a staging site
Build the new site at a separate, private address and keep it out of Google while you work, using password protection or a noindex tag. Before launch, check on staging:
- Every redirect from your map, tested in bulk (most crawlers can do this from a list).
- No broken internal links.
- Titles, descriptions and headings on every important page.
- Structured data (for example your business details) still valid in Google’s Rich Results Test.
- Page speed on a phone. Google’s Core Web Vitals give clear targets: the main content should load within 2.5 seconds (LCP), the page should respond to taps within 200 milliseconds (INP), and the layout should not jump around (CLS below 0.1).
- Mobile layout on real phones, not only in a desktop browser.
Launch day
- Switch the site live and remove the staging block: no
noindextags, and arobots.txtthat allows crawling. - Activate the redirects and test a sample of old URLs in a private browser window.
- Submit the new XML sitemap in Search Console.
- Use URL Inspection in Search Console to request indexing of your most important pages.
- If the domain itself changed, also use Search Console’s Change of Address tool.
- Check that analytics, contact forms and booking links work, by actually sending a test enquiry.
The weeks after launch
Some movement in rankings during the first weeks is normal while Google recrawls the site. What matters is the trend. For four to eight weeks:
- Check Search Console’s Pages report for new errors and fix any missing redirects you find.
- Compare your top pages and queries with your baseline export.
- Watch enquiries, not only traffic. A clearer site often converts better even before rankings move.
If a key page drops and stays down, compare old and new: has content, a heading or an internal link gone missing? It is usually something specific and fixable.
Your quick checklist
- Export top pages, queries and backlinks from Search Console
- Crawl the old site and save every URL
- Keep URLs that don’t need to change
- Keep and improve content that ranks
- Map every old URL to its new home with a 301 redirect
- Test redirects, links, metadata and speed on staging
- Remove the staging block on launch day
- Submit the sitemap and request indexing
- Monitor for four to eight weeks
A beautiful new site that nobody finds helps no one. If you are planning a relaunch and want help doing it safely, let’s talk.