Redesign
Website redesign and rebuild
Replacing a site that no longer represents the business, without throwing away the search visibility and the links it has accumulated - which is the part most redesigns get wrong.
Problems this solves
- The site was built years ago and now looks older than the business is.
- Traffic dropped after the last redesign and never came back, because URLs changed without redirects.
- The site is slow on mobile and nobody can say which part is responsible.
- New services and products do not fit the old page structure, so they were bolted on as orphan pages.
- Editing anything requires a developer, so content has not been touched in two years.
Who it is for
Businesses with an existing site that already receives traffic and enquiries, and cannot afford a rebuild that quietly resets that to zero.
What is included
Audit before design
What the current site ranks for, which pages produce enquiries, what is orphaned, what is duplicated, and what is technically broken - established before anyone proposes a new layout.
URL and redirect mapping
Every existing URL is mapped to its counterpart on the new site, with a single permanent redirect and no chains. URLs that are working well are kept rather than prettified.
Redesign and rebuild
A new visual system and a hand-written front end, with the content structure reworked around what the business now sells rather than what it sold then.
Post-launch verification
Crawl and indexing checks after go-live, so a redirect that silently returns the wrong status is found in the first week rather than in next quarter's traffic report.
What you receive
- A written audit of the existing site, with the findings ranked by impact
- A complete old-to-new URL map with redirect rules
- A redesigned, rebuilt and deployed site
- Preserved or improved metadata for every page that is carried over
- Updated sitemap, robots and structured data
- A post-launch check covering redirects, status codes, canonical tags and indexing
- A list of what we deliberately did not change, and why
How we work
- 01
Audit
Content, performance, crawlability and current indexing signals, documented.
- 02
Map
Decide what is kept, merged, dropped or redirected, before design starts.
- 03
Rebuild
New design and front end, built against the agreed structure.
- 04
Verify
Launch, then check redirects, status codes and indexing against the map.
Performance, accessibility and search
One-hop redirects only
Every legacy URL reaches its destination in a single permanent redirect. Chains waste crawl budget and dilute the signal that made the old URL valuable.
Measured, not assumed, performance
The old site is measured first, so the new one can be compared against it rather than declared faster.
Structure that stays crawlable
No important page ends up orphaned by the new navigation, and every indexable page is reachable through real links within a few clicks.
What we build with
- React
- TypeScript
- Server-side rendering
- Tailwind CSS
- Headless CMS (optional)
- Redirect mapping
Integrations
- Existing CMS or content export
- Analytics continuity
- Search Console verification
- Forms and CRM handoff
- Existing hosting and DNS
Cost and timeline
We do not publish fixed prices or delivery times, because scope changes both by an order of magnitude. You get both in writing, specific to your project, before any commitment.
What drives the price
- Size of the existing site and how much content is carried over
- How much of the content needs restructuring rather than moving
- Whether the redesign is visual only or a full information-architecture change
- Complexity of the redirect map, especially for stores
- Whether the existing site can be crawled and exported cleanly
- How much new functionality is added alongside the redesign
What drives the timeline
- How quickly content decisions - keep, merge, drop - are made
- Access to the current site, hosting, analytics and Search Console
- Number of templates to redesign
- Whether the launch has to be coordinated with a campaign or a season
- Review turnaround
Related work
- Commerce
Avangard Parts - Automotive Parts Store
A completed automotive e-commerce platform with a bilingual catalogue, fast product discovery and custom administration.
Read the case study - Websites
Planirent - Car Rental Website & Reservation Flow
Custom car rental website and reservation system with card payments, availability logic, and practical operator workflows.
Read the case study
Frequently asked questions
It can, and that is almost always caused by URLs changing without correct redirects, or by content being cut without a decision being made about it. Handled properly - full URL map, one-hop permanent redirects, preserved metadata, post-launch verification - a redesign should not cost you visibility. Nobody can promise it will increase it.
It depends on whether the problem is the surface or the foundation. If the structure and content are sound and the site just looks dated, a redesign is cheaper and safer. If the URL structure, content model or platform is the problem, a rebuild costs less than repeatedly working around it.
Yes, and usually you should. We only change a URL when there is a concrete reason, and when we do, the old one gets a permanent redirect and every internal link, canonical, alternate and sitemap entry is updated to match.
Yes - that is most of this service. We audit what exists before proposing anything, and sometimes the recommendation is a set of targeted fixes rather than a rebuild.
Ready to start?
Tell us about your project and we will come back with a clear, honest plan.
Start a project