Redesigning Your Website Without Losing Google Traffic: A 301 Redirect and Migration Checklist

In brief: The most common cause of organic traffic loss in a website redesign is not the design but unmanaged URL and content changes. Addresses change but there is no 301 (permanent) redirect from old addresses to new ones; titles, descriptions and internal links disappear; the sitemap and canonicals are not updated; the test environment is accidentally left indexable, or the live site is accidentally launched with noindex. The solution is a systematic migration plan: 1) inventory the current site, 2) decide which pages to keep, 3) prepare the old-to-new URL mapping and the 301 redirects, 4) verify in a test environment before launch, 5) monitor with Search Console and server logs after launch. Google's own site move documentation explains the same logic.

Last updated: October 2026

A redesign does not look risky, but it is

Months of work go into a new design and a new infrastructure; but to a search engine a site is a structure made of pages, addresses and links. You need to change that structure without breaking it. Common outcomes:

• Because page addresses change, pages that used to rank return “404 – not found” and their rankings disappear.
• Links from other sites (backlinks) point to broken addresses.
• Content is thinned on the new site; paragraphs that answer a search intent are deleted.
• Titles, descriptions and structured data are lost.
• The new site is worse than the old one on mobile or speed.

Most of these can be prevented by planning ahead. Short-term fluctuation can even be normal; but permanent loss is mostly an indication of a mistake.

Before you start the redesign: inventory and decisions

1. Document the current site

First see the real situation you have:

• Full URL list: Take it from the sitemap, a crawling tool (e.g. a crawler like Screaming Frog) and Search Console.
• Pages that get traffic: The pages getting the most clicks and impressions from Search Console and analytics data.
• Pages that get links: Addresses receiving external links (backlinks).
• Title, description, H1 and structured data: The current values for each important page.
• Conversion pages: Which pages your goals such as forms, quotes, carts and phone clicks come from.

This inventory is the answer to “what should we protect?” during the migration.

2. Decide for each page

The golden rule: If possible, do not change URLs. An address that does not change is an address with no redirect risk.

The redirect plan: 301s

What is a 301 and why is it critical?

A 301 says “this page has permanently moved to a new address.” Done correctly, search engines pass signals to the new address and users do not land on a broken page. Google's documentation also recommends server-side redirects for permanent moves.

Prepare a mapping table

Identify a single best new URL for each old URL:

Redirect rules

• Keep them to a single hop. Chained redirects (A→B→C) cost speed and signals; go directly A→C.
• Do not redirect everything in bulk to an unrelated page. Redirecting all old pages to the home page can be treated by Google like a “soft 404.” Choose the page closest in content.
• Think about variants with parameters and trailing slashes too: /page, /page/, ?utm_....
• Make http→https and www/non-www redirects single and consistent.
• Keep redirects in place for at least a year; leaving them permanently is better.

Preserve the technical SEO elements

On the new site check these (and compare them with the old one):

• Title and meta description: Titles of pages that get traffic should not be changed needlessly; if they change, it should be deliberate.
• H1 and heading hierarchy: A single, clear H1 on each page.
• Canonical tag: Each page should point to its own preferred address; a wrong canonical can cause a page to drop out of the index.
• robots.txt and noindex: A noindex/block that is on in the test environment must be removed on live; if it is carried over to live by mistake, the whole site can drop out of the index. It is one of the most common and most expensive mistakes.
• XML sitemap: It should contain the new URLs, not the old ones; resubmit it to Search Console.
• Structured data (schema): Existing markup such as organization, product, FAQ and article should be preserved.
• Hreflang: On multilingual sites, language alternates and self-references must be correct.
• Internal links: Menus and in-content links should point directly to the new addresses (not rely on redirects).
• Image alt text and file names: Some traffic may come from image search too.

For how we manage technical SEO on a modern stack, see our technical SEO with Next.js guide.

Content: improve, don't thin out, when you redesign

Shortening copy in a new design to “look cleaner” is dangerous. If a page answers a particular search intent, the sections that provide that answer should be preserved:

• Do not delete the main text and headings of pages that get traffic.
• Keep content formats such as Q&A, tables and lists.
• Do not remove trust signals such as the update date and author information.
• When adding new content, produce content that adds value (answers the user's question).

To be visible in AI-assisted search too, you can read our GEO guide on the importance of content structure.

Speed and user experience: the new site should not be slower than the old

A new design often brings more images, animations and scripts. If speed and usability fall, rankings and conversions will be affected too. Before launch:

• Measure page speed on mobile and desktop (Lighthouse, PageSpeed Insights).
• Serve images at the right size and in modern formats; lazy-load off-screen images.
• Reduce unnecessary third-party scripts.
• Test mobile usability on real devices.

As a ready starting point, our free Website Review tool gives a quick first look at the technical and SEO status of both your old and your new site.

Launch day and after: step-by-step checklist

Before launch (in the test environment)

• The mapping table for all old URLs is ready and tested (bulk check with a sample list)
• 301 redirects are single-hop, with no loops
• The test environment is hidden from search engines (noindex/password), and this will be removed when moving to live
• The new sitemap is ready, robots.txt is correct
• Title, meta description, H1, canonical and structured data have been checked
• Analytics and conversion tracking (form, phone, cart) work
• Speed and mobile tests have been done
• Forms, payments and email notifications have been tested

On launch day

• Verify that the live site has no noindex and no robots block
• Try the important old URLs one by one: do they go to the right new page with a 301?
• Submit the new sitemap to Search Console
• Check SSL/HTTPS and www/non-www redirects
• Verify that data flows in analytics

4–12 weeks after launch

• Monitor the Pages (indexing) and Crawl stats reports in Search Console; fix 404 and redirect errors
• Track ranking and click changes on the 20–50 pages that get the most traffic
• Find old addresses returning 404 in server logs and add redirects
• Check that old addresses that receive external links are redirecting
• Monitor speed and Core Web Vitals data

Small fluctuations in the first weeks after launch can be normal; but if there is a steady, clear drop, the most likely causes are missing redirects, a wrong canonical/noindex or lost content.

9 common mistakes

1. Moving to the new site without producing a URL inventory
2. Redirecting all old addresses to the home page
3. Creating redirect chains and loops
4. Carrying the test environment's noindex setting to the live site
5. Changing the text and title of pages that get traffic without reviewing them
6. Not updating the sitemap and Search Console
7. Breaking hreflang and canonical counterparts on a multilingual site
8. Not testing the new site's speed and mobile experience
9. Not monitoring after launch

Redesigning with Aktaş Digital

In redesign projects we plan first to protect the existing organic presence: a URL inventory, a redirect table, a technical SEO check, speed targets and post-launch monitoring are standard parts of the project. On modern stacks (e.g. Next.js) we build a strong base for speed and technical SEO; we covered the process in our corporate website development guide and the choice of stack in WordPress or Next.js.

To see the state of your current site, you can try our Website Review tool, and for a redesign plan you can write to us through our quote form. If you are planning new systems alongside the redesign (e.g. web applications), we can include them in the same plan.

Frequently Asked Questions

Is losing rankings in a redesign inevitable?

No. In a well-planned migration (URLs are kept or mapped correctly with 301s, content and technical elements are preserved) you do not have to suffer permanent loss. Short-term fluctuation can happen; but with regular monitoring, problems are caught early.

How long does the effect of a 301 redirect take?

The time it takes search engines to crawl the new addresses and process the signals varies with the number of pages and how often the site is crawled. A duration cannot be guaranteed, which is why monitoring matters. Keep redirects in place for a long time (at least a year).

What should I do if I am also changing my domain name?

A domain change is a more sensitive migration than a URL change. Redirect from every address on the old domain to the new ones with a 301, use the Search Console “Change of address” tool and follow the steps in Google's site move documentation.

What should I do instead of deleting old pages?

If a page has value, update the content and keep it; if a similar page exists, merge and 301; if it is truly worthless, you can return 404 or 410. Look at traffic, links and conversion data when deciding.

How do I hide the test environment from search engines?

Password protection is the safest route; noindex can also be used. What matters is making sure the setting is removed when going live. Blocking with robots.txt alone does not always prevent indexing.

What should I look at in Search Console after the redesign?

Look at the errors and exclusion reasons in the Pages (indexing) report, crawl stats, the sitemap status, the Core Web Vitals report and the change in clicks/impressions against the previous period in the performance report.

Conclusion

A successful website redesign means launching the new design while preserving the value the old site earned. Produce the URL inventory, decide which pages to keep and move, prepare the 301s, preserve technical SEO and content, watch out for the noindex mistake when going live and monitor regularly after launch. The first thing you can do today: put all your site's URLs and your 50 pages with the most traffic into a table.