Website Redesign Services That Protect Your Rankings

// When should you redesign a website?

A website should be redesigned when its problems are built into the structure and can no longer be fixed one at a time. Looking dated is not enough of a reason on its own; the real test is whether the site is still doing its job. If two or more of the signs below apply at once, a redesign is usually more economical than patching.

• The site scrolls sideways on mobile, text is too small and buttons are hard to tap
• PageSpeed Insights scores below 50 on mobile and the Core Web Vitals report is red
• The stack is outdated; PHP, the theme or libraries cannot be updated without breaking something
• Your brand, logo or services have changed but the site still tells the old story
• Traffic arrives, but enquiries, calls or bookings stay low
• Every small text or image change needs a developer

// Redesign or refresh: which do you need?

If the foundations are sound and the problem is on the surface, a refresh is enough; if the problem is the foundations, you need a redesign. A refresh keeps the existing code and works on design, copy or individual pages; a redesign rebuilds the site. The table shows the criteria we use to decide.

The decision is made in a free review. If a refresh will do, we say so in writing; we do not propose a bigger project than you need.

// What is included in a website redesign?

A redesign is more than a new look; speed, accessibility, structured data and SEO carry-over are all part of the job. The table lists what a standard redesign includes and what sits outside the scope.

// How do you redesign a website without losing SEO?

SEO survives a redesign when every URL that brought traffic or links to the old site has a matching home on the new one. Most post-redesign traffic drops are caused not by the design but by lost URLs and deleted content. That is why we inventory the current site before any design work starts.

• All crawled URLs, pages with impressions and clicks in Search Console, and URLs with external links are listed
• Content that brings traffic is kept or merged into a stronger page; ranking copy is never silently removed
• Every changed URL is 301-redirected individually to its new equivalent; nothing is bulk-redirected to the homepage
• After launch, 404 logs, indexing and impressions are monitored in Search Console

Google's guide to site moves with URL changes covers these steps in detail and recommends keeping redirects for at least a year. If the current site has crawling or indexing problems, we resolve them through technical SEO rather than carrying them into the new build. If the server or domain also changes, the cutover follows our website and hosting migration plan on the same timeline.

A new design should never erase what the old site earned: inventory first, design second.

// How does the redesign process work, and how long does it take?

The process has four steps, and a typical corporate site redesign takes 4 to 8 weeks; page count and when the content is ready matter most. The new site is built on a separate staging environment while the live site keeps running. A backup is taken before launch and the switch happens at a low-traffic hour.

// WordPress or custom software?

WordPress usually suits a site whose content changes often and whose features are standard; custom software suits a site with its own business rules. Because we build both, we decide on neutral criteria:

• Content management — if your team will edit pages and posts themselves, WordPress's admin area is a ready-made advantage
• Custom workflows — bookings, subscriptions or member areas with specific rules run with fewer compromises in custom PHP or Node.js / Next.js
• Maintenance load — WordPress needs regular plugin and core updates; custom software has fewer dependencies but changes need a developer
• Speed and security — the targets are the same on both; what differs is the discipline needed to reach them

For brochure-style business sites, our corporate website page explains the scope in detail. Moving away from closed platforms such as Wix or Squarespace is also a redesign project, because a site on those platforms cannot be exported as files to another server.

// Examples from sites we have built

The standard we aim for in a redesign is visible in sites we have built. Scores were measured with Google PageSpeed Insights against Google's Core Web Vitals thresholds: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1.

• AS Medya — an animated WordPress corporate site for a digital marketing agency. Measured on 4 October 2026: 100 on mobile, 99 on desktop; motion and speed are not mutually exclusive
• Gint Clinic — a premium corporate site in three languages (TR/EN/DE) for an aesthetic surgery clinic; in a multilingual redesign, language structure, URLs and hreflang pairing are planned before design starts
• Ergoterapistimle — a booking-focused corporate site for a children's occupational therapy centre. In a 4 October 2026 stability test (median of 5 runs): 92 on mobile, 99 on desktop

Redesign is part of our web design services; if you have no site yet, you will find our build options there.

// What drives the cost, who leads the work, and when is a redesign unnecessary?

Five variables set the price: page count, whether content is migrated or rewritten, the number of languages, integrations such as bookings or payments, and the number of URLs to redirect. The initial review is free; the quote is fixed after the review and does not go up later. The post-launch bug-fix guarantee and its duration are written into the quote.

Projects are led by Caner Zep Çelik, Founder & Technical Consultant at Zep Bilişim. Since 2020 he has worked across web design, software and search visibility, and has been involved in more than 100 projects. He carries out the inventory, the redirect map and the launch checks himself and does not subcontract the work.

If the site is mobile-friendly, the Core Web Vitals report is green and conversions meet expectations, you do not need a redesign; a refresh of a few pages will do. If the only problem is speed, speed optimisation is cheaper and faster; if it is only the server, a migration is.

// Frequently Asked Questions