You already have a site. That changes the job completely: the risk is no longer building the wrong thing, it is destroying something that was quietly working. Most redesign damage is self-inflicted and entirely avoidable.
A website redesign is replacing a site that already exists, and the defining constraint is everything the old site had that you cannot afford to lose. Rankings, indexed pages, inbound links, the URLs people bookmarked and printed on things. A redesign that ignores those does not just fail to help. It sets you back.
This is what separates it from web design, where nothing exists yet and there is nothing to break, and from website development, which is the build itself. In a redesign, the migration is the project. The design is the easy part.
Nobody sets out to lose their traffic. It happens the same handful of ways, every time.
The new system prefers a different URL pattern, so every page moves. The old addresses now return a 404. Every link anyone ever built to you, every bookmark, every ranking attached to those addresses: gone, silently. The site looks great. The phone stops ringing. It usually takes a couple of months for anyone to connect the two.
A page with eight paragraphs answering real customer questions looks cluttered in a design mockup. It gets cut to two lines and a photo. The design improved. The reason the page ranked was those eight paragraphs, and it is now gone. This is the quietest failure of the lot, because the page still exists so nothing looks broken.
Decisions about what to keep get made on taste rather than on which pages earn clicks. If you are not looking at Search Console before you start, you are choosing what to delete at random and calling it editorial judgement.
The in-progress copy was left crawlable, and now Google has two versions of your site and no idea which is real. Alternatively the reverse: the blocking rule from staging shipped to production, and the new site is invisible. We have seen the second one sit unnoticed for weeks. Both are in the launch checklist because both are common.
Launch is when you start watching, not when you stop. Redirect errors and crawl problems surface over the following weeks. If nobody is looking at the reports, the site degrades and the first signal is a bad quarter.
We will talk you out of this if the facts point that way. It costs us a project and saves you a great deal more.
Every URL, what is indexed, which pages earn clicks, what links point where. This happens before any design conversation, because it decides what the redesign is allowed to touch.
The pages doing real work get protected. Their URLs, their content, their substance. Anything cut is cut on evidence, not on how it looked in a mockup.
One for one, written down, before the build. If a URL has no new home, that is a decision to make deliberately rather than a 404 to discover later.
301s in place at the moment of switchover, not the following week. Blocking rules removed. Sitemap regenerated and submitted.
Crawl errors, redirect problems, indexing, traffic. Movement in the first weeks is normal. A cliff is not, and the difference matters. This is why Search Console is not optional.
We treat a redesign as a migration with a design attached, not a design with a migration attached. That ordering is the whole difference between a redesign that helps and one that quietly costs you a year.
It can, and this is the single most common way redesigns go wrong. Rankings are attached to specific URLs and the content on them. Change the URLs without redirecting, or strip out the text that was doing the ranking because it looked wordy, and you can lose visibility that took years to build.
It is avoidable. Every old URL gets mapped to its new home with a 301 redirect, the content that earns traffic is kept, and Search Console gets watched afterwards rather than everyone walking away. Some movement during a migration is normal and settles. Losing a page because nobody mapped it is not normal, it is negligence.
Start by working out what is wrong, because "it looks dated" and "it does not bring in work" are different diagnoses with different fixes. If the site converts fine and just looks old to you, you may be the only person who cares. If nobody can find it, a redesign changes nothing, because that is a technical SEO or local SEO problem and a fresh coat of paint does not touch it.
We wrote a diagnosis walkthrough: outdated business website. It will tell you honestly whether the site is the problem.
Often, yes, and when it is possible it is usually the right call. Keeping URLs removes the largest risk in the whole project for free. URLs only need to change when the structure was genuinely wrong: pages nested under categories that made no sense, or a URL pattern that fights the way the site is now organised.
The rule is simple: change URLs when there is a real reason, not because the new system prefers a different pattern. If they must change, they get mapped and redirected, one for one.
Check before you delete. This is where redesigns quietly bleed. That page you think is filler may be the one bringing in a third of your search traffic, and you will not know until it is gone. Search Console data tells you which pages actually earn clicks.
Some content genuinely should go: pages about services you stopped offering, duplicates, anything untrue. But that decision should follow the data, not a designer's preference for a shorter page.
Not reliably, and anyone assuming so is guessing. A redesign adds work a new build does not have: auditing what exists, mapping URLs, deciding what content survives, planning the migration, and verifying nothing broke afterwards. What it saves is having existing content and a known audience.
The honest answer is that it depends on the state of what you have. The same cost factors apply either way: what a small business website costs.
Design and build a site that explains your business and brings in enquiries.
The build itself: structure, code, forms, and the systems behind the pages.
Decide whether to refresh, rebuild, or leave it alone.
The crawling, indexing and structure work search engines depend on.
See how Google actually crawls, indexes and ranks your pages.
What to verify before and after a site goes live.
Send us the URL before you commit to anything. We will tell you what is worth keeping, what is actually wrong, and whether a redesign is the right spend at all.