Website redesign SEO: how to keep your rankings
A website redesign SEO guide: record your old URLs, map and redirect them, keep what ranks, then check Search Console after launch, step by step.
Updated November 1, 2026A redesign loses search traffic for one main reason: pages that Google already ranks disappear or move, and nothing tells Google where they went. Keep the addresses that earn visits, send every old address that changes to its new page with a permanent redirect, keep the words and titles that rank, and watch Search Console for a few weeks after launch. The rest of this guide is how to do each of those, in order.
Why redesigns lose traffic
Google ranks pages, not websites. Each page that brings you visits has an address, a title, some text and links pointing at it from other sites. A redesign can break any of these without anyone noticing:
- The address changes.
/our-services/physiobecomes/services/physiotherapy. The old address now shows an error, and the links other sites gave it point at nothing. - The content changes. The paragraph that answered what people searched for is cut to make the page look cleaner.
- The title changes. A plain, descriptive title is replaced by a slogan.
- Hidden information goes missing. The old site described your business, opening hours and FAQs in structured data; the new template doesn't.
None of this is a reason to avoid a redesign. A faster, clearer site usually helps. It's a reason to record what you have before you change it.
Step 1: Record your old URLs and what they earn
Before anything changes, make a list of every page on your current site and how much each one matters.
- List every address. Your current sitemap (usually at
yourdomain.com/sitemap.xml) lists most pages. A site crawler adds the ones the sitemap misses. Google suggests drawing on sitemaps, server logs, analytics and Search Console's link data, and including images and files too (Google Search Central, site moves with URL changes). - Export your traffic from Search Console. The Performance report shows clicks, impressions, click-through rate and average position, broken down by page and by search query, and it has an export button (Search Console Help, Performance report). Set the date range to the longest you can, open the Pages tab and export it. Then do the same for Queries.
- Note the pages other sites link to. Search Console's Links report lists your most-linked pages. These need a working address after the redesign even if they get few clicks.
- Keep copies. Save each important page's title, description and main text. Once the old site is gone, you can't check what it said.
You now have a spreadsheet: old URL, clicks, impressions, top queries, linked or not. Sort by clicks. The top 20 rows are usually most of your search traffic.
Step 2: Map every old URL to a new one
For each row, write the new address where that content will live. Google's advice is to "map your old site's URLs to the URLs for the new site", starting with the important ones (Google Search Central).
- Best: keep the address. If
/feesis ranking, the new fees page should be at/fees. No redirect needed, nothing for Google to relearn. - Next best: one old page to one new page with the same content, joined by a redirect.
- Merging pages: point each old page at the new page that now covers its content.
- Dropping a page: if nothing replaces it and it earns nothing, let it return a "not found" error. Don't send it to the home page; Google advises against redirecting many pages to an unrelated page like the home page.
Step 3: Set up permanent (301) redirects
A redirect sends visitors and search engines from an old address to the new one. Use a permanent, server-side redirect (301 or 308). Google treats a permanent redirect as "a signal that the redirect target should be canonical", meaning the new page takes the old one's place in results; a temporary redirect (302 or 307) doesn't send that signal (Google Search Central, redirects and Google Search).
Three rules from Google's site-move guide:
- Point straight at the final page. Avoid chains (old page to older page to new page).
- Keep the redirects "for as long as possible, generally at least 1 year."
- Permanent redirects don't lose PageRank, so links to the old address still count for the new one.
Where you set redirects depends on your host. Most site builders, hosting panels and CDNs have a redirects setting. Test a few old addresses in a private browser window after launch: each should land on the right page in one step.
If you're redesigning with Firetend: Firetend doesn't create redirects from your old site's addresses automatically. It reads your old site and moves the content over, but the new pages may live at different addresses. So compare your Step 1 list with the new site's pages before you connect your domain. For any page that earns clicks or links and whose address has changed, ask in a feedback round for the new page to keep its old address (for example "keep /services/teeth-whitening/ as this page's address") before you switch. What Firetend does handle: once your own domain is connected it becomes the main address and every other address, including your-name.firetend.app, redirects to it. See AI website redesign for the whole process.
Step 4: Keep the titles and content that rank
Look at the top queries for each important page. If the old page ranked for "physiotherapy for back pain in Leeds", the new page needs to say that clearly, in its title and its text.
- Titles: keep them descriptive. Under 60 characters (including your site name) avoids being cut off in results.
- Descriptions: 140 to 160 characters, saying what the reader gets.
- Headings and text: keep the sections that answered searchers' questions, even if you shorten them.
- Images: keep descriptive alt text on images that matter.
A redesign is also a good time to improve weak pages. Just do it on purpose, page by page, rather than by accident.
Step 5: Keep (or add) structured data
Structured data is "a standardized format for providing information about a page and classifying the page content" (Google Search Central). It's how search engines read your phone number, address, opening hours, FAQs and articles without guessing. Check the old site's important pages in Google's Rich Results Test, then check the new pages the same way.
Firetend sites generate structured data from their content: LocalBusiness, each location, services, team members, articles and authors, FAQs and breadcrumbs. It stays correct as you edit.
Step 6: Fix internal links
Links within your own site should point at new addresses directly, not through redirects. Google's guide says to "change the internal links on the new site from the old URLs to the new URLs." Check your menu, footer, buttons and links inside page text. If you have links you control elsewhere (Google Business Profile, social profiles, email signatures, ads), update those too.
Step 7: Submit the new sitemap
Submit your new sitemap in Search Console's Sitemaps report, or add a Sitemap: line to robots.txt. Google calls a sitemap "merely a hint", not a guarantee, but it helps Google find the new pages sooner (Google Search Central, build and submit a sitemap). Every Firetend site has a sitemap at /sitemap.xml, rebuilt on each publish, and tells Bing and other IndexNow search engines about changed pages when you publish.
Step 8: Monitor after launch
Expect some movement. For a medium-sized site, Google says "it can take a few weeks or more" before it shows the new addresses instead of the old ones. Larger sites take longer.
For the first four to eight weeks:
- Week 1: open your top 20 old URLs. Each should redirect in one step or still exist. Check Search Console's page indexing report for new "not found" errors.
- Weekly: compare clicks for your top pages with the export from Step 1. A page that drops sharply usually lost its address, its words or its title.
- Monthly: check that the new pages are indexed and the old ones are dropping out.
A short dip that recovers is normal. A page that stays at zero needs fixing, usually with a missing redirect.
A one-page summary
| When | Task | Where |
|---|---|---|
| Before | Export pages and queries | Search Console, Performance |
| Before | List every URL and linked pages | Sitemap, crawler, Links report |
| Before | Map old URL to new URL | Spreadsheet |
| Build | Keep ranking titles and text | Each page |
| Build | Check structured data | Rich Results Test |
| Launch | 301 redirects for changed URLs | Your host |
| Launch | Update internal links | Menu, footer, page text |
| Launch | Submit sitemap | Search Console, Sitemaps |
| After | Compare clicks weekly | Search Console |
For the rest of the project, see the website redesign checklist, and for budgets, website redesign cost.
FAQ
Will a website redesign hurt my SEO?
It can, if pages that rank lose their address, words or title. If you keep or redirect every important address and keep what ranks, a redesign usually doesn't hurt, and a faster, clearer site can help. Expect a few weeks of movement while Google processes the changes.
Do I need redirects if I keep the same domain?
Only for addresses that change. If /about stays /about, nothing is needed. Every page whose address changes needs a permanent (301) redirect to its new page.
How long should I keep 301 redirects?
Google recommends keeping them for as long as possible, generally at least a year. Many sites simply keep them.
Should I redirect every old page to the home page?
No. Google advises against redirecting many pages to an unrelated page such as the home page. Redirect each page to its closest new equivalent, and let pages with no equivalent return "not found".
Does Firetend keep my old URLs?
Not automatically. Firetend moves your content over, but it doesn't create redirects from the old site's addresses. Record your old URLs and check them against the new site before you connect your domain, as in Step 3.
How do I know if the redesign affected rankings?
Compare Search Console clicks and impressions for each important page with your pre-launch export, week by week. Look at pages, not just the site total, so you can see which page lost traffic and why.