A website redesign replaces how a site looks and how it is built while keeping what already works: the pages that rank, the addresses other sites link to and the content customers use. Done in order, it runs from an audit and a URL map through a staging build to redirects, launch checks and several weeks of monitoring in Google Search Console.
Does my website need a redesign or a smaller fix?
It needs a redesign when the problem sits in the structure or the platform, and a smaller fix when it sits in one page, one feature or the content. Rule out the smaller fix first.
| What you see | Usually a smaller fix | Usually a redesign |
|---|---|---|
| Pages load slowly | Resize images, add caching, remove unused scripts. | The theme or page builder is the cause and cannot be trimmed. |
| The site looks dated | A visual refresh on the same platform, with the same addresses. | The layout also fails on phones and the menu no longer fits what you sell. |
| Staff cannot edit it | Training, or an admin screen for one type of content. | Every edit needs a developer, or the platform no longer receives updates. |
| Few inquiries | Rewrite the main pages and test the contact form. | Visitors cannot find your services because the structure is wrong. |
| Security warnings | Update the core, theme and plugins. | Updates break the site because the code is too old to update safely. |
Google's guide to site moves with URL changes advises changing one thing at a time, for example the domain first and the layout later. A refresh that keeps every address carries far less search risk than a redesign that changes them.
What are the steps of a website redesign process?
There are eight steps, and the order matters more than the speed. Google's site move guide follows the same order: prepare, map, redirect, then monitor.
- Audit. Record what works before changing anything: which pages get clicks in the Search Console Performance report, which bring inquiries or sales, and what loads slowly.
- Content inventory. List every page, image and downloadable file with its address, and decide whether each one stays, merges into another page or is retired. Google suggests building the list from your sitemaps, server logs or analytics, the links report in Search Console and your content management system.
- URL map. Write the new address next to every old one, or mark it retired. This sheet drives the redirects, internal links and new sitemap.
- Design. Lay out each page type for phone and desktop, using the content you are keeping.
- Build in staging. Build on a private copy, not the live site. If the copy is hidden from search engines with robots.txt or a noindex rule, note every place that block lives, because it must come off at launch.
- Redirects. Turn the URL map into server-side permanent redirects, each going straight to its final address in one step.
- Launch checks. Test a sample of old addresses, confirm each new page carries a canonical tag pointing to itself, remove the staging blocks, place a real test inquiry or order, and submit the new sitemap in the Search Console Sitemaps report, as Google's sitemap documentation describes.
- Monitoring. Over the following weeks, watch the Page indexing report for "Not found" errors and the Performance report for clicks moving from old addresses to new ones.
What should happen to each old URL in a redesign?
Every old address ends in one of three states: kept, sent with a 301 to its closest equivalent, or answered with a 410 because nothing replaces it. The table maps common cases to the rule in Google's documentation.
| Old URL type | What happens to it | What Google's documentation says |
|---|---|---|
| Page that keeps its content and its address | Kept. It returns 200 as before, with a canonical tag pointing to itself. | Each URL on the new site should carry a self-referencing canonical tag. |
| Page that keeps its content under a new address | 301 to the new address, in one hop. | Permanent redirects such as 301 and 308 show the target in search results, and do not cause a loss in PageRank. |
| Page whose topic now lives on a broader page | 301 to that page, but only if a visitor would find what they came for there. | If a page has a clear replacement on your site, return a 301. |
| Several old pages merged into one | Each old address gets a 301 to the merged page. | Redirecting older URLs to a new page that consolidates their content is acceptable. |
| Page retired with nothing to replace it | 410. Never a redirect to the home page. | If a page is removed with no replacement, return 404 or 410. Many URLs redirected to one irrelevant page, such as the home page, may be treated as a soft 404. |
| Images and PDFs that get visits or links | 301 to the file's new address, or 410 if the file is gone. | Transfer images and downloads, and include them in the URL mapping. |
| Duplicate copies on http, www or another subdomain | 301 to the matching page on the one preferred address. | Pick one preferred address and redirect the other versions to it. |
I use 410 rather than 404 because it says the removal was deliberate. For Google the difference is small: its documentation on HTTP status codes treats every 4xx code except 429 the same way, and previously indexed URLs that return one are dropped from the index. What matters more is not hiding retired pages behind irrelevant redirects, which Google's crawl error guide describes under soft 404s.
When I rebuilt this website in October 2026, I mapped every old URL Google had shown in Search Console: pages that had a direct replacement got a 301, retired pages got a 410, and the old copy of the site on a mail subdomain was redirected to the main domain.
Will a website redesign hurt my SEO?
It can, if old addresses break, if content that ranks disappears or if the new site stays blocked from crawling. Google's site move guide says to expect temporary ranking fluctuation while it recrawls, and that a medium-sized site can take a few weeks or more before the new URLs replace the old ones. Where pages rank afterward is Google's decision, but these steps remove the avoidable causes of a drop.
- Redirect one to one. Each old address goes to its own closest equivalent, not to a category page or the home page. Google's redirect documentation says server-side redirects are the type it is most likely to interpret correctly.
- Keep the titles and content that rank. For pages that get clicks today, keep the topic, the title, the main heading and the substance of the text. Rewriting a page that ranks is a separate decision, made page by page.
- Update internal links. Point menus and links in the text at the new addresses, so nobody passes through redirects. Google also advises sending each redirect straight to its final destination, because chains add delay.
- Submit the sitemap. Google calls a sitemap a hint, not a promise, but it helps the new addresses get found.
- Keep the redirects. Google recommends keeping them for generally at least one year, and from a visitor's point of view, indefinitely.
- Expect fluctuation. Compare clicks over weeks, not days.
What drives the cost of a website redesign?
The cost is driven by the work behind the new look, not the look itself. I give no figure without your scope, and my guide on what a web designer costs covers the numbers.
| Factor | Less work when | More work when |
|---|---|---|
| Page types | A few templates cover the whole site. | Many unique layouts, each designed and built separately. |
| Content | Most pages move across as they are. | Pages need rewriting, or nobody has decided what to keep. |
| Platform | Same platform, new theme. | A move to another platform, with products, posts or customers to migrate. |
| Old URLs | Few pages with readable addresses. | Many addresses, query strings, or several old copies of the site. |
| Features | Pages and a contact form. | A store, bookings, accounts or integrations that must keep working through the switch. |
I quote a redesign the way I quote any build on my web designer and developer page: a fixed price against a written scope. When an old site is too tangled to size up front, a short hourly phase at $55 to $65 per hour comes first.
What mistakes should you avoid in a website redesign?
Avoid the slips that keep a new site out of results or send visitors to dead ends. Google names several of them.
- Launching with the staging block still on. A leftover noindex rule or a robots.txt that blocks everything keeps the new site out of results. Google lists it first among common site move mistakes.
- Sending everything to the home page. Google may treat it as a soft 404.
- Redirects to pages that do not exist. Google says it often sees redirects pointing at wrong, non-existent URLs. Test every rule.
- Forgetting files and copies. PDFs, images and old copies of the site on other hostnames still get visits.
- Changing everything at once. A new domain, platform and design in one launch make any drop hard to trace.
- Losing Search Console verification. If ownership is verified with an HTML file or a meta tag, carry it into the new site.
Finished sites are in my portfolio, and the stages of a project are on how I work. If you want one person to plan and build your redesign, from the URL map to the Search Console checks, my web design and development service starts with a free scoping call of about 30 minutes through start a project.
Last reviewed 12 October 2026. Disclosure: I sell web design and development, so I am not neutral. I am also CTO at ElySpace, a freelance developer for Marmaids LLC, and founder of WHMCSPilot and MagizAI.
