DESIGN
WEBSITE REDESIGN
- 50+ projects
- from 3 days
- without losing rankings
A refresh of a site that already works and already brings in leads. We keep what performs and rebuild navigation, speed and the mobile version, carrying the URLs across so the search rankings survive.
WHO IS IT FOR?
Three situations where an update pays off faster than a rebuild
- .01
THE SITE LOOKS OLDER THAN THE COMPANY
Built a few years ago: heavy, falling apart on a phone, visually from another era. The company has grown since; the first impression has not. It costs most where you are being compared: a client opens two sites in neighbouring tabs and draws a conclusion in a couple of seconds, without reading either of them.
- .02
THERE IS TRAFFIC AND FEW ENQUIRIES
People arrive, look at the pages and never reach the form. The problem is somewhere in between — in the navigation, in the speed, in the main thing being hidden, or in half the elements being impossible to tap on a phone. Rebuilding blind is dangerous here: without working out where exactly people are being lost, a new design can damage what was working.
- .03
THE SITE SPRAWLED AND THE LOGIC WENT
Sections were added over years, each new one wherever there was room. Nobody understands the structure now, including the people who built it. The problem is almost never the appearance. It is that nobody owned the structure as a whole — and it needs rebuilding, not repainting.
WHAT'S INCLUDED
We do not build below this line
- - A review of the current site and its metrics.01
- - A new structure and navigation.02
- - Custom design, never a template.03
- - Layouts for every device.04
- - Load speed.05
- - Content migration.06
- - Keeping the search rankings.07
- - Launch and the check afterwards.08
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed ships in every project — even the simplest and cheapest one. There are no stripped-down versions.
- FIRST WE LOOK AT WHAT WORKS
A blind redesign can bring down the thing that was bringing in the enquiries. We start with a review: where people leave, which pages bring the traffic, and what must not be touched.
- THE SEARCH RANKINGS ARE THE MAIN RISK
URLs, redirects and structure are worked through before launch, not after. That is what people most often lose when a site is updated.
WHAT'S INSIDE
EVERY PROJECT LOOKS LIKE ITSELF
We do not take ready-made assemblies and we do not bend a business to fit somebody else’s grid. The design is built for the job from scratch: its own composition, its own typography, its own rhythm, its own motion. Which is why no two of our projects look alike — open the portfolio and compare them yourself. With studios that work from templates every project is recognisable from the first screen, and the client notices that too.
DESIGN THAT SURVIVES DEVELOPMENT
A beautiful mockup and a working site are not the same thing, and the difference surfaces during the build: what happens on hover, what on an error, what if there is three times more text, what on a tablet. We write the code ourselves — so we know where a mockup falls apart, and we describe it before a developer has to ask. Whether we build it or your team does, the result will match the picture rather than approximate it.
A SYSTEM, NOT A PILE OF PICTURES
Grid, typography, colour, states, components — built once and reused. A new page is then assembled from parts that already exist rather than drawn again: that is what separates a project you can keep developing from one you will be rebuilding in six months. Plus everything that usually gets forgotten: empty screens, loading, errors, long text, and how all of it looks on the smallest phone there is.
BEAUTIFUL AND FAST IS ONE JOB, NOT TWO
Heavy animation, 3D, a scroll-driven sequence — all easy to draw and hard to keep light. It is usually paid for in speed: the site impresses in a demo and takes four seconds to load for the client. We design the effect and its implementation together — what the browser has to compute, what loads later, what switches off on a weak device. A heavy scene and a slow site are not the same thing, and the second is not compulsory.
CATEGORIES
Three levels of scope. Yours is the one you recognise yourself in
A VISUAL REFRESH
WHEN IS THIS YOUR CASE?
The structure of the site is fine; what has aged is how it looks. The whole base build: a review of the current site and its metrics, a new design, layouts for every device, load speed, content migration, keeping the search rankings, launch and the check afterwards. Nothing stripped out — just without the extras you do not need yet.
REDESIGN WITH THE STRUCTURE
WHEN IS THIS YOUR CASE?
It is not only the look that has to change: the structure grew by itself, the navigation is tangled, pages duplicate one another and part of the content cannot be found at all. We rebuild the structure and the sections, rewrite the logic of the pages, rework the path to an enquiry and put the URLs and redirects in order. Plus analytics, so that after launch you can see what moved in the numbers.
A REBUILD FROM SCRATCH
WHEN IS THIS YOUR CASE?
The site has run out of road technically: a slow engine, somebody else’s platform, code that cannot be extended. We build it again on our own stack, migrate the content, the products, the customers and the history, and keep the URLs and the rankings. It is effectively the development of a new site that keeps everything the previous one accumulated.
FAQ
Answers to the most popular questions
From $1.000 for a visual refresh to $5.000 and up for a rebuild from scratch. The figure depends on the number of pages, on whether the structure has to change, and on whether the site stays on its current platform.
A visual refresh takes 3–10 days. With the structure rebuilt, 5–15 days. A full rebuild, from 7 days. Content migration is quoted separately and depends on the volume.
That is the main risk of a redesign, and it gets closed before launch rather than after. We collect the current URLs, match them against the new structure, set up redirects and keep the pages that bring traffic. A dip of a week or two after the move is normal; the positions recover afterwards. If the site brings you enquiries from search, say so on the first call: the plan will be a different one.
It happens when a site is rebuilt blind — beautifully, but differently. So we start with a review: where people come from, which pages work, where they are lost. What produces results we keep; what gets in the way we change. After launch we compare the numbers — and if something has dropped, we look into it rather than leave it.
By what is already there: in a redesign you have content, traffic, rankings and clients who are used to the site. All of it has to survive — and that is work in its own right, which building from scratch does not involve. If nothing of the old site remains but the domain, the honest thing is to price it as new development.
Yes, if the structure allows it. Usually it starts with the home page and the pages that bring the most traffic: the result shows quickly and the budget is smaller. The rest follows later. But if the problem is the engine or the platform itself, a partial update postpones the question rather than answering it.
Inside the builder, only as far as the builder goes — which is usually the very thing you have already run into. If the platform’s limits are the reason for the update, what you actually need is a move onto code of your own: that is described under the platform migration service.
For the first weeks we watch: how the rankings behave, where people go, what changed in the enquiries. The fixes that follow are part of the work. After that the site can stay on our infrastructure — monitoring, backups, updates.