How to Redesign a Website Without Losing Google Rankings (2026 Checklist)

To redesign or migrate a website without losing Google rankings, list every URL that earns traffic or links, keep or improve that content, and 301-redirect each old URL to its closest new match. Then check robots.txt, noindex tags, canonicals and the sitemap on launch day, and watch Search Console for 30 to 90 days.

Key takeaways

• Most traffic drops after a redesign come from changed URLs with no redirect, deleted content, or a leftover noindex tag. All three are preventable.
• Google recommends server-side permanent redirects (301 or 308), one hop to the final page, kept in place for generally at least a year.
• Use Search Console's Change of Address tool only when the domain or subdomain changes. Path changes and HTTPS moves do not need it.

Why do website redesigns lose Google rankings?

Redesigns lose rankings when Google can no longer find what it used to rank. The usual causes are new URLs with no redirects, pages or copy cut during the redesign, a noindex tag left on from staging, content that only appears after JavaScript runs, and internal links that changed or disappeared. Google is not punishing the new design.

Think of each ranking page as an address Google has on file. Change it with no forwarding note, and Google finds a dead end:

• Changed URLs. A new platform or a new menu often means new slugs. Without a redirect, every old link and bookmark breaks.
• Lost content. Designers trim long service pages to make them look cleaner. The words that answered searchers' questions go with them.
• Missing redirects. Teams redirect the top ten pages and forget blog posts, PDFs and images that still pull visits.
• Noindex left on. Staging sites are hidden from search on purpose. If that setting ships to the live site, Google drops the pages. Google's own docs say a noindex rule tells Google to remove the page from results once it is crawled.
• JavaScript-only content. Google indexes the rendered page, and Google notes that server-side or pre-rendering is still a good idea because not every bot runs JavaScript.
• Broken internal links. Google only discovers links built as normal <a> tags with an href. Buttons that navigate with scripts can hide whole sections.

What should you do before the new design goes live?

Before launch, crawl the current site and build a full URL inventory. Record every live page, its traffic and clicks from Search Console, its backlinks, and its title and main heading. This list becomes your redirect map and your proof of what must survive. Skip it and you are guessing.

Pull URLs from more than one place, because no single source has everything:

• A crawl of the live site with any standard SEO crawler.
• The current XML sitemap.
• Search Console's Pages report and the top pages in the Performance report for the last 12 to 16 months.
• Your analytics landing-page report.
• A backlink tool's list of the pages other sites link to.

Put it all in one spreadsheet with one row per old URL. Add columns for clicks, impressions, backlinks, the main search queries, and a "new URL" column you will fill in next. Save a copy of each important page's copy and title tags too. Google's site move guide also says to map images, videos, JavaScript and CSS files, not just pages.

Finally, verify both the old and the new site in Search Console now, including www, non-www and HTTPS versions. You want the data flowing before launch, not after.

How do you build a 301 redirect map that works?

A good redirect map pairs every old URL with the single most relevant new URL and uses a server-side permanent redirect, a 301 or 308. Each redirect should go straight to the final page in one hop. Keep the redirects live for at least a year, and update your own internal links to the new addresses.

Google's guidance on redirects is clear on a few points:

• Use permanent redirects for permanent moves. A 301 or 308 tells Google the new URL should show in results. A 302 or 307 keeps the old URL in results.
• Server-side is best. Google says server-side redirects are the most reliable. JavaScript redirects are a last resort because Google may not see them if rendering fails.
• Avoid chains. Googlebot can follow up to 10 hops, but Google advises redirecting straight to the final page. If you cannot, keep chains to 3 hops or fewer.
• No dumping on the homepage. Do not send many unrelated old URLs to one page. Match by topic.
• Keep them for a long time. Google's site move guide says to keep redirects as long as possible, generally at least 1 year.

Test the map before launch. Run your old URL list through a crawler against the staging site, or right after launch against the live one. Every row should return a single 301 to a page that returns 200.

Which pages should you keep, upgrade or retire?

Keep every page that earns clicks, ranks for useful searches, or has backlinks. Upgrade the best of them with clearer answers and better calls to action, without cutting the content that made them rank. Retire only pages with no traffic, no links and no business value, and redirect them to a close match when one exists.

Sort your inventory into three groups:

1. Keep and protect. Your top pages by clicks. Keep the URL if you can. If the URL must change, keep the topic, the main heading and most of the copy.
2. Keep and upgrade. Pages that rank on page two or three. A redesign is a good time to answer the question in the first paragraph, add an FAQ, and tighten the title tag.
3. Merge or retire. Thin or duplicate pages. Merge similar ones into one stronger page and redirect them all to it. Google says consolidated content can be redirected to a single new page.

Before anyone cuts text in a design review, check the page's search queries. If it ranks for a question, the answer stays.

What should you check on launch day?

On launch day, confirm Google can crawl and index the new site. Check that robots.txt is not blocking it, that no noindex tags shipped from staging, that canonicals point to the new URLs, that the new sitemap is submitted, and that a sample of old URLs redirect in one hop to live pages.

Google's site move guide says to remove any noindex rules or robots.txt blocks that were only for development, give each new URL a self-referencing canonical, and submit a sitemap of the new URLs. Use this table as your launch checklist:

One trap to know: if robots.txt blocks a page, Google never sees its noindex tag. Fix robots.txt first, then look for noindex.

When do you need Google's Change of Address tool?

Use the Change of Address tool in Search Console only when you move to a new domain or subdomain, such as oldname.com to newname.com. You do not need it for HTTP to HTTPS, www to non-www, or new paths on the same domain. Set up the 301 redirects first, then submit the request.

Google's help page explains what the tool does and its limits:

• You must be a verified owner of both the old and new properties with the same Google account.
• It works on domain-level properties. It does not move subdomains below the one you submit, so cover www and non-www separately.
• Google forwards signals and prefers the new site for 180 days after you start the move.
• Google recommends keeping the old domain registered for at least a year so nobody else can misuse it.
• Do not chain moves (A to B, then B to C), and avoid merging several sites at once.

Google also notes that keeping the same site structure passes signals more directly. That is why changing your domain, design and URL structure all at once carries more risk than changing one at a time.

What should you monitor for 30 to 90 days after launch?

For the first 30 days, check Search Console every few days for crawl errors, unindexed pages and drops in clicks on your top pages. From day 30 to 90, compare clicks, impressions and average position against the same weeks before launch. Fix any 404s, redirect gaps or indexing issues as soon as they show up.

Google tells you to expect temporary ranking swings, and says new URLs on a medium-sized site may take a few weeks or more to appear. A dip in week one is normal. A steady slide in week four is a signal to dig in. Watch these:

• Pages report. Look for spikes in "Not found (404)", "Excluded by noindex" or "Blocked by robots.txt."
• Sitemaps report. Indexed counts for the new sitemap should climb over time.
• Performance report. Compare your top 20 pages and queries before and after. Any page that lost most of its clicks needs a look at its redirect and its content.
• Server logs or crawl stats. Google says the new site will get heavier crawling after a move, so make sure the server keeps up.
• Analytics. Traffic should fall on old URLs and rise on new ones. Leads matter more than visits, so watch form fills and calls too.

How do you move from WordPress to Webflow without losing traffic?

A platform move, such as WordPress to Webflow, is a site move with URL changes in disguise. WordPress often uses date-based or category slugs, while Webflow CMS uses collection folders like /blog/post-name. Map every old URL, rebuild the content in Webflow, add 301 redirects in site settings, and run the same launch checks.

A few platform details matter on this kind of move:

• Redirects live in Webflow's site settings. Webflow's help center says redirects are added under Site settings, Publishing, 301 redirects, and need a paid site or workspace plan. You can import and export them by CSV.
• Use wildcards carefully. Webflow uses capture groups, not full regex. Put specific page rules before broad wildcard rules, because they run in the order they were created. Webflow suggests staying around 1,000 redirects as a best practice.
• Carry over SEO fields. Move title tags, meta descriptions, alt text and structured data, not just the body copy.
• Watch old WordPress extras. Tag pages, author archives, attachment pages and old PDFs in the uploads folder often have links. Redirect the ones that earn traffic.

At Forty-Second Street we build only in Webflow. Whatever platform a site starts on, the URL inventory is always step one.

What does a rebrand that kept its rankings look like?

In our own event venue rebrand case study, a wedding and event venue changed its name, logo and website. Google clicks rose 28% (June 1 to September 27, 2026, versus the same window in 2025, per Google Search Console), and average position improved from 28.8 to 18.1.

The new name started with zero search history. The plan kept the established site's authority and connected the new name to it, so searches for either name led to the venue. In the same period, the new name earned 326 clicks, up from 0.

A name change or redesign does not have to reset your search traffic if the groundwork is done first.

Frequently asked questions

How long does it take Google to settle after a redesign?

Google says to expect temporary ranking swings during a move. For a medium-sized site, new URLs can take a few weeks or more to show up, and larger sites take longer. Plan to watch closely for 30 days and keep monitoring for 90. If traffic is still sliding after a month, look for missing redirects or blocked pages.

Can I redirect every old page to my new homepage?

No. Google warns against sending many unrelated old URLs to one page like the homepage. Each old page should point to the closest new page on the same topic. If you merged several thin pages into one stronger page, redirecting all of them to that single page is fine. A page with no match can return a 404.

Do 301 redirects lose PageRank?

Google's site move guide says permanent redirects do not cause a loss of PageRank. What does hurt is slow redirect chains, redirects to the wrong page, and redirects that get deleted too soon. Point each old URL straight at its final new address and keep the redirects in place for at least a year.

Should I change my domain and redesign at the same time?

Only if you have to. Google's Change of Address help notes that combining a move with a redesign or URL restructure may cause traffic loss, because there is more for Google to re-learn. If you can, change one thing at a time. If you cannot, the redirect map and launch checks matter twice as much.

Is Webflow good for SEO after a migration?

Yes, when it is set up correctly. Webflow lets you add 301 redirects in its site settings and import or export them in bulk by CSV, and you can set titles and meta descriptions page by page. The platform does not save rankings on its own. The URL inventory, redirect map and content you carry over are what protect your traffic.

The bottom line

A redesign should lift your traffic, not erase it. Inventory every URL, keep the content that ranks, redirect each old page to its best match, and check robots, noindex, canonicals and the sitemap before you announce the launch. Then watch Search Console for 90 days. If you want a second set of eyes on your migration plan, Book a free call with Mike, or run the free 60-second check to see where your site stands today.

Sources

• Google Search Central: Site moves with URL changes
• Google Search Central: Redirects and Google Search
• Google Search Console Help: Change of Address tool
• Google Search Central: Block Search indexing with noindex
• Google Search Central: Understand the JavaScript SEO basics
• Webflow Help Center: How do I set up redirects in Webflow?
• Forty-Second Street case study: Event venue rebrand without losing Google

Keep reading

• Why SEO fails on websites that don't convert
• Small business website design strategy
• How much does website design cost in 2026?