Website Redesign: How to Decide, Plan and Protect Traffic

Key takeaways

A redesign is worth it when the site gets in the way of the business: it is hard to update, slow, awkward on phones, or no longer describes what you sell. If only the look is dated, a refresh is often enough.
Know which job you are buying. A redesign changes how the site looks and is organized, a rebuild replaces how it is made, and a migration moves it to a new host, domain or platform. Many projects are a mix.
Search traffic is protected by planning, not luck: list every old URL, map each one to its new home, and use permanent (301) redirects, which Google recommends keeping for at least a year.
Keep the domain, hosting, analytics and Search Console in your own name before the project starts, and give the agency access rather than ownership.
Budget and timing vary widely. Clutch’s review data shows most web design projects cost under $10,000, while larger projects pull the average far higher.

A website redesign is a planned change to how your site looks, how it is organized and often how it works, done to fix problems that cost you customers or time. You need one when the site no longer does its job: visitors cannot find what they need on a phone, you cannot update it without help, it loads slowly, or it describes a business you no longer run. You probably do not need one if the site works and only the colors and photos feel tired; a refresh of the visual layer costs less and carries less risk.

This guide walks through the decision from the owner’s side of the table. It covers the signs that point to a redesign, the difference between a redesign, a rebuild and a migration, how to keep the search traffic you already earned, how to keep control of your accounts while someone else does the work, what to put in the brief, what it tends to cost and how long it takes, and what to check once the new site is live.

Signs you need a redesign (and when a refresh is enough)

The best reason to redesign is a business reason. A site that looks dated but still brings in calls and form submissions is not urgent. A site that looks fine but quietly loses people on phones is. Here are the signs I would take seriously.

It is hard to use on a phone. Google finished moving to mobile-first indexing in 2023, which means it looks mainly at the mobile version of your pages when it indexes them. If text is tiny, buttons are cramped or menus break on a phone, both visitors and search engines are seeing your weakest version.
It is slow. Google’s Core Web Vitals guidance asks for the main content to load within 2.5 seconds, for the page to respond to taps in under 200 milliseconds, and for layout shift below 0.1. A site that misses all three by a wide margin usually needs more than a coat of paint.
You cannot update it yourself. If changing opening hours or adding a service means emailing a developer, the site is costing you time and money every month.
It no longer matches the business. New services, a new area, a new audience or a new price point all change what the site needs to say and how it should be organized.
The structure is a maze. Pages added over the years with no plan, duplicate pages, and menus that nobody can explain are signs the architecture needs rethinking, not just the design.

A refresh is enough when the structure and the content still make sense and the problems are mostly visual: new photos, updated colors and fonts, a cleaner home page, tightened copy. A refresh usually keeps the same URLs, which removes most of the search risk. My advice is to ask for a refresh quote alongside a redesign quote, so you can see the difference in cost and scope side by side.

Redesign vs rebuild vs migration

These words get used loosely, and the confusion shows up later in the invoice. It helps to name the job precisely before you ask anyone for a price.

Job	What changes	Typical example	Main risk
Refresh	Look and feel only	New theme styling, photos, home page copy	Low, URLs stay the same
Redesign	Look, layout, navigation and often content	New page structure, merged or split pages	URL changes that lose search traffic
Rebuild	How the site is made	Old custom code replaced with a standard WordPress build	Features or content lost in the rebuild
Migration	Where the site lives or its address	New host, new domain, new platform, or new URL structure	Broken links, lost rankings, email downtime

In practice, a small business project is often a redesign plus a migration: for example, moving from a website builder to WordPress and changing the page structure at the same time. That is fine, but it raises the stakes. Google’s own site move guidance suggests changing one thing at a time where you can, so that if something goes wrong you know what caused it. If you are changing platform, domain and structure all at once, you need a stricter plan and closer monitoring after launch.

If your project involves moving the site anywhere, read the guide to website migration, which explains the four types (host, domain, platform and structure) and how each one affects search.

Protecting your search traffic

The traffic a site earns from Google is tied to its URLs. When a redesign changes those URLs and nothing tells Google where the pages went, the old addresses return errors, and the rankings they held start to disappear. This is the most common way redesigns go wrong, and it is almost entirely preventable.

Build a URL map before anything else

Start with a complete list of the URLs on your current site. Pull it from your sitemap, from Google Search Console and from a crawl of the site, and add any page that gets traffic or links from other sites. Then, in a spreadsheet, give every old URL a destination on the new site: the same address, a new address, or the closest relevant page if the content is being merged. Google’s guidance on moving a site with URL changes puts this mapping at the start of the process for a reason. It is also where you will spot pages that nobody planned to keep but that still bring in visitors.

Use permanent redirects, and keep them

Each old URL that changes should send visitors and search engines to its new address with a server-side permanent redirect, which means a 301 or 308 status code. Google explains that permanent redirects tell it to show the new address in search results, while temporary ones keep the old address. Google recommends keeping redirects for as long as possible, generally at least one year. Avoid chains where one redirect points to another and then another; send each old URL straight to its final destination.

Launch cleanly and tell Google

Before launch, make sure the development site’s “do not index” settings are switched off on the live site, and submit an updated XML sitemap in Search Console. If the domain itself changes, Google provides a Change of Address tool in Search Console; it needs a 301 redirect from the old home page to the new one and verified ownership of both properties, and Google says it keeps forwarding signals for 180 days. Expect some movement in rankings: Google notes that visibility can fluctuate temporarily during a move, and that for a small to medium-sized site it can take a few weeks for most pages to be picked up at their new addresses.

Ask whoever builds the new site to send you the finished URL map and the redirect list before launch day, not after. Reading through it takes an hour and is the single best check you can make as an owner, because you know which pages bring in customers.

Keep ownership of your accounts during the project

A redesign is the moment many owners discover they do not actually control their own website. The domain was registered by a former developer, the hosting is on the agency’s account, and the analytics property belongs to someone who left years ago. Sort this out before the project starts, not in the middle of it.

The domain should be registered in your name, with your email address as the registrant contact. Under ICANN’s rules, the registered name holder is the one entitled to move the domain to another registrar. Registrars can also apply temporary transfer locks after certain changes, so fixing the paperwork at the last minute can stall a migration.

The same principle applies to everything else. Hosting should be on an account you own and pay for. In Google Search Console, you should be a verified owner; Google’s help pages explain that delegated owners and users lose access if all verified owners are removed. In Google Analytics, you should hold the Administrator role, which is the role that can add and remove users. The agency then works through access you grant, and when the project ends you remove it. If you want to know how that arrangement works in practice, the page on how we work sets it out.

What to put in the brief

A good brief does not need to be long. It needs to be specific about the business, honest about the problems, and clear about what must not break. I would include the following.

What the site is for. The two or three actions that matter most: calls, quote requests, bookings, purchases.
What is wrong now. The specific problems, with examples. “Our booking form does not work on iPhones” is more useful than “the site feels old.”
What must survive. Pages that bring in traffic or leads, integrations you depend on (booking, payments, email signup), and anything legally required.
Who updates it afterward. If you or your staff will edit the site, say so, because it changes how the site should be built.
Access and ownership. A list of every account involved and who holds it today.
Constraints. Budget range, deadline and any dates you cannot launch on, such as your busiest season.
What is out of scope. New copywriting, photography, logo work or SEO are often assumed by one side and not the other.

For a full step-by-step list to work from, use the website redesign checklist, which runs from the first audit through to the checks after launch.

How long it takes and what it costs

There is no single honest number for either, because a five-page brochure site and a hundred-page site with a shop are different projects. What I can do is point to data from people who track real projects and explain what moves the price.

Clutch, which collects verified reviews of web design projects, reports in its pricing guide (updated September 21, 2026) that most web design projects cost less than $10,000, that the average project cost is about $38,000, and that the average project runs around seven months. That average is pulled up by large projects, so treat the “under $10,000” figure as the more realistic picture for a small business site. Clutch also lists typical agency rates in the United States at $100 to $149 per hour. Freelance marketplaces sit lower: Upwork reports a median of about $21 per hour for web designers worldwide, with typical rates of $15 to $30.

The things that move the price are predictable: the number of page templates, how much content needs to be rewritten or moved, integrations such as booking or e-commerce, whether the platform is changing, and how much of the old site’s search traffic needs to be protected. The guide to website redesign cost goes through each of these and explains how to compare quotes fairly.

As for time, a simple redesign that keeps the platform and the content can be done in weeks. A project that rewrites content, changes platform and remaps URLs takes longer, and most of the delay usually comes from waiting for content and approvals rather than from the build itself. If you are moving away from a website builder, budget extra time for content that has to be moved by hand.

Moving platforms during a redesign

Many owners decide to redesign at the same time as leaving a website builder. That is a sensible moment to do it, since the pages are being reworked anyway. It does mean checking early what the old platform lets you take with you. Wix, for example, states in its help center that a Wix site cannot be exported to another host and that blog posts cannot currently be exported to other platforms, while contacts and store products can be exported as CSV files. The step-by-step guide on how to migrate from Wix to WordPress explains what that means in practice and how to keep your URLs and rankings.

If your platform choice is still open, the comparison of the best website builder for small business is a good place to start. A builder like Squarespace can be the right call for a simple site that you want to manage yourself, and there is no reason to move just for the sake of it.

For any migration, a checklist keeps the risky steps from being skipped. The website migration checklist covers the work before, during and after the move, including DNS, email and redirects.

What to check after launch

Launch day is not the finish line. The first few weeks are when broken redirects, missing pages and tracking gaps show up, and they are much cheaper to fix early.

Redirects. Test a sample of old URLs, starting with the pages that brought in the most traffic, and confirm each one lands on the right new page in a single step.
Search Console. Check that the new sitemap has been processed and watch the page indexing report for spikes in “not found” errors.
Forms and calls. Submit every form and click every phone link on a real phone. Confirm the messages arrive where they should.
Analytics. Make sure tracking is installed on every template and that conversions are still recorded.
Speed and phones. Run the main templates through a Core Web Vitals check and look at them on an actual phone.
Crawling rules. Make sure robots.txt does not block search engines or the crawlers AI assistants use to find sources. OpenAI, for instance, states that sites which block its OAI-SearchBot will not appear directly in ChatGPT search answers.
Email. If DNS changed, send and receive a test email from your business address.

After the first month, compare traffic and leads with the same period before the redesign. Some movement is normal while Google processes the changes, but a steep drop on specific pages almost always points to a redirect or indexing problem that can be found and fixed. Ongoing checks like these are part of regular website maintenance, which is worth setting up as soon as the new site is live.

Getting help with a redesign

If you would like someone to handle the redesign, the redirects and the move while you keep ownership of everything, the website redesign and migration page explains how we approach it.

Frequently asked questions

How often should a small business redesign its website?

There is no fixed schedule. Redesign when the site stops serving the business: it is hard to update, slow, poor on phones, or out of step with what you sell. If the structure still works, a lighter refresh is often enough.

Will a website redesign hurt my Google rankings?

It can if URLs change without redirects. If every old URL is mapped to a new one with a permanent 301 redirect and the new site is crawlable, rankings usually settle after a period of temporary movement, which Google describes as normal during a move.

Should I redesign and change platforms at the same time?

It is often efficient, because the pages are being rebuilt anyway. Google recommends changing one thing at a time when possible, so if you combine them, plan the URL map carefully and monitor closely after launch.

Who should own the domain and hosting during a redesign?

You should. Both should be in your name and paid from your account, with the agency given access. Fix ownership before the project starts, because changes to a domain’s registration details can take time to process.

How long should I keep redirects after a redesign?

Google recommends keeping them for as long as possible, generally at least one year. In practice there is little reason to ever remove them, since old links on other sites keep pointing to the old addresses.

Website Redesign