In brief: Website redesign is planned according to signs that the website cannot do its job, rather than a number of years. A website that is difficult to use on mobile, slow to open, impossible to update, running on an old PHP version or failing to represent the brand properly deserves a redesign regardless of age. If two or more checklist items apply, consider redesigning; search traffic is protected through a URL map and 301 redirects.
Website redesign is planned according to signs that the website cannot do its job, rather than a calendar date. A website that is difficult to use on mobile, slow to open, impossible to update, running on an old PHP version or no longer representing the brand correctly deserves a redesign regardless of its age. The answer to “when should a website be redesigned” is therefore not a number of years, but how many items are checked in the following checklist.
The article first examines the signs individually, then distinguishes situations where repair is sufficient from those requiring redesign. Based on Google’s site move guide, it explains how URL mapping and 301 redirects prevent the loss of search traffic, the greatest concern during corporate website redesign. The final section covers redesign stages, monitoring after launch and factors determining the budget.
When should a website be redesigned? A signs checklist
If two or more of the following items apply to the existing website, redesign should be considered. A single item can often be resolved through repair; when several occur together, the problems generally stem from the same outdated infrastructure.
- Broken mobile layout: Text remains too small, the menu does not open, forms cannot be completed on a phone, or the page scrolls sideways.
- Slow-loading pages: Especially on mobile connections, the homepage and service pages load late, and images settle into place afterward.
- Infrastructure that cannot be updated: Theme or plugin updates break the website, so updates have been postponed for months.
- Old PHP version: The hosting dashboard warns that the version needs upgrading, but the website does not work on the new version.
- Content that cannot be edited independently: A developer is needed every time a phone number or price needs changing.
- Appearance inconsistent with the brand: The logo, colors, service list or company name has changed, but the website still presents the old version.
- Unmeasurable conversions: Nobody knows how many inquiries come through forms, WhatsApp or phone calls.
- Security history: The website was previously hacked and cleaned, but the old components responsible for the vulnerability remain in place.
This list is a starting point rather than a scoring system. A redesign decision made without distinguishing root problems from their consequences can carry the same issues into the new design. For example, slow speed and an unupdatable theme often share a cause; seeking separate solutions wastes time.
Timing matters alongside the signs. The question of when to redesign a website cannot be considered independently of the business’s busy sales or quotation periods; scheduling the transition during a relatively quiet period reduces the impact of possible disruptions. If the announcement date of a new service, branch or campaign is known, plan the redesign backward from that date.
Mobile experience: Google evaluates the website as seen on a phone
A website with mobile problems affects not only visitors but search visibility, because Google uses the smartphone-crawled version for indexing and ranking. Google calls this approach mobile-first indexing and asks that mobile content be equivalent to desktop content.
A common situation on older websites is mobile presentation being a separate layer added afterward. Some desktop text is hidden on phones, tables become unreadable, and clickable elements sit too close together. In a structure built from the start with responsive design, content comes from a single source; there are no differences in text, headings or structured data between mobile and desktop.
Fixing mobile issues with patches is possible if the theme permits it. If the theme depends on an old page builder and every correction breaks something elsewhere, redesign is the less risky path.
Slow speed: Which measurements signal a need for redesign?
Whether slow speed requires redesign becomes clear by examining why Core Web Vitals values are poor. According to Google’s web.dev resource, a good experience requires the largest content’s display time (LCP) to be 2.5 seconds or less, interaction response time (INP) 200 milliseconds or less, and visual shift score (CLS) 0.1 or less; assessment uses the 75th percentile of visits. Measurement methods and how values are improved are explained in detail in the article on website speed optimization and Core Web Vitals .
Causes such as uncompressed images, missing caching or weak hosting do not require redesign; optimization resolves them. If slowness comes from a heavy page builder loading dozens of files on every page, interdependent plugins or an old theme framework, optimization offers limited gains. In that case, the speed issue is structural and should be resolved together with rebuilding.
Infrastructure that cannot be updated and old PHP versions: The security side
A website that cannot be updated continues carrying known security vulnerabilities; this is the technical reason with the greatest weight in the redesign decision. In PHP’s official support schedule, every version receives two years of active support followed by two years of security-only support. At the end of this period, the version reaches end of life and no new security patches are published; the current table can be followed on the PHP supported versions page .
The picture is similar on the WordPress side. WordPress.org’s server requirements page gives PHP 8.3 or higher as the recommended version; it states that older versions are not officially supported and may expose the website to security vulnerabilities. The problem begins when a theme written years ago or a discontinued plugin produces errors on the new PHP version, leading the owner to remain on the old version to keep the website working.
There are two ways out of this cycle. If incompatibility is limited to one or two components, replace those components and move the website to the current version. If the theme, page builder and most critical plugins are no longer developed, corporate website redesign is a more consistent decision in terms of both security and maintenance cost.
Page contents
Brand changes and unmeasurable conversions
When the brand changes or it is impossible to measure whether the website brings inquiries, redesign is undertaken for business rather than technical reasons. A new logo, new service area, merged companies or a changing target audience affect not just the website’s visuals but its page structure.
On the measurement side, the problem is generally infrastructure. On older websites, successful form submissions do not open a separate page, WhatsApp and phone buttons are untagged, and Google Analytics 4 is either absent or lacks defined key events. Whether advertising or SEO work is effective on such a website can only be discussed through guesswork.
In the new structure, forms, calls and message clicks are set up to be measured from day one. This also allows the question “has the website improved” to be answered with data after redesign.
Repair, partial redesign or full redesign?
Not every complaint requires a website from scratch; the right decision depends on which layer contains the problem. The following table shows common situations and which approach usually makes more sense:
| Situation | Approach usually sufficient |
|---|---|
| Infrastructure is current; only images and text are outdated | Content and image updates |
| Speed problems stem from images, caching or hosting | Speed optimization, changing servers if necessary |
| A single plugin or theme component is incompatible with the new PHP version | Component replacement and version upgrade |
| The homepage and service pages are outdated; other pages are sound | Partial redesign: Redesigning priority templates |
| Mobile layout, speed and update problems exist together | Full redesign while preserving content and URLs |
| The brand, service structure and audience have changed | Full redesign with a new page plan |
The website’s role over the next few years is also considered when deciding. If plans include e-commerce, a multilingual structure or an appointment system, repairing infrastructure unable to support them will require a second redesign shortly afterward. Partial redesign is a reasonable middle path for businesses wanting to spend their budget gradually. However, putting a new design over old infrastructure leaves security and speed problems in place.
Let us evaluate the existing website together
Share the website address and current problems through WhatsApp to discuss whether repair or redesign makes more sense. If redesign is needed, the scope is clarified, the proposal is sent the same day, and the schedule is settled in the same conversation.
How is SEO loss prevented during redesign? URL mapping and 301 redirects
The fundamental action protecting search traffic during redesign is linking each old address to its new equivalent with a permanent (301) redirect. Google’s guide to site moves with URL changes recommends preparing a map matching old and new URLs before migration and using server-side permanent redirects. If addresses will not change at all, redirects are unnecessary; preserving every possible URL exactly is the safest approach in a redesign.
If URLs will change, prepare the transition in this order:
- Address inventory: List all important URLs from the sitemap, the pages report in Search Console and landing pages in Analytics.
- Mapping: Choose the closest matching new page for each old address; seek a direct equivalent rather than redirecting everything to the homepage.
- Redirects without chains: The old address goes directly to the final address; do not build chains from A to B and B to C.
- Updating internal links: Change links in menus, footers and text to the new addresses instead of relying on redirects.
- Page-level tags: New pages contain self-referencing canonical tags and correct titles and descriptions; robots.txt permits crawling of the new structure.
- Sitemaps: Submit the new sitemap through Search Console; the guide also recommends keeping the old sitemap for a while.
Google asks that redirects remain in place as long as possible, generally at least one year, and explicitly states that temporary ranking fluctuations may occur during migration. If addresses and the server will change together, plan the process alongside the WordPress website migration steps; DNS, email records and SSL are also part of transition day.
Stages of corporate website redesign
Corporate website redesign begins with examining the existing website and ends with monitoring after launch; design is the middle step in this process. Designing without knowing which existing pages bring traffic and inquiries may unknowingly delete the most valuable content.
In the first stage, collect the page inventory and measurement data and separate content to preserve from content to rewrite. In the second, prepare the new page plan and complete URL mapping accordingly. Design and setup take place in a separate testing environment without touching the live website; content transfer, forms and measurement tags are tested there.
On launch day, activate redirects, submit the new sitemap and check old addresses individually through sampling. The new website’s page structure, packages and setup process are explained separately on the corporate web design page.
What is monitored in the first weeks after launch?
Redesign does not end on launch day; checks in the first weeks catch missed redirects before they turn into lost traffic. The pages report in Search Console shows old addresses returning 404 errors and new pages that are not indexed.
According to Google’s guide, processing most new addresses on medium-sized websites can take several weeks, and longer on large websites. During this period, a gradual exchange in indexed page counts between old and new sitemaps is expected. Forms actually sending email and phone and WhatsApp clicks appearing in Analytics are also tested on day one.
If updates, backups and minor corrections are not handled regularly after launch, the new website reaches the same point as the old one within a few years. Work requiring continuity can be planned through annual WordPress maintenance and updates .
Common mistakes in website redesign and the correct method
Most losses during redesign come from an unplanned transition rather than the design itself. Common mistakes and their alternatives are as follows:
- Deleting pages that bring traffic: An old article appearing to receive few visits may bring inquiries for a particular search; look at the data before deleting.
- Redirecting all old addresses to the homepage: A redirect without an equivalent does not take visitors where they want to go; select the closest matching page for each address.
- Leaving the test environment open to indexing: The prelaunch copy can become a second website competing with the live website in Google; protect the test environment with a password.
- Forgetting the “block search engines” setting on launch day: If this WordPress setting is enabled during testing and not disabled at launch, the website is not crawled.
- Not transferring measurement codes: If Analytics and conversion tags are not installed on the new website, the impact of redesign cannot be compared.
- Leaving domain and hosting access with a third party: Redesign is also an opportunity to put accounts in the business’s name.
What determines the cost and duration of a website redesign?
The website redesign budget depends on page count, the amount of content to preserve, whether URLs change and additional functions. Onur Freelance does not apply a fixed package price for website redesign; the existing website is reviewed and a business-specific price is provided. The preliminary assessment is free, and the proposal is shared the same day. To compare packages for new websites built from scratch, see the web design prices page.
If text and images are ready, a redesigned corporate website is completed and handed over in an average of 5-7 business days. No fixed figures are given for additional work such as migration, speed optimization or measurement setup; a precise proposal is prepared after reviewing the existing website. Mobile compatibility, SEO infrastructure and an SSL certificate are standard in the new setup; domain and hosting accounts are opened in the business’s name, and dashboard use is demonstrated at handover. Maintenance after launch is optional, with a monthly fee ranging from 500 to 2,000 TL.
The item that extends the timeline most is generally content. Preparing text, images and corporate information at the beginning shortens the schedule; if content will be written alongside the redesign, this is discussed as a separate step in the plan.
Let us make the redesign decision with data
Use the same number to ask whether redesign is needed, plan a safe transition with URL mapping or start the new website immediately. WhatsApp and phone are available between 09:00 and 21:00.
Related guides
Frequently asked questions
How many years should pass between website redesigns?
There is no fixed number of years; redesign timing depends on signs such as mobile problems, slow speed, infrastructure that cannot be updated or brand changes, rather than the website’s age. If several signs appear together, redesign is considered.
Will Google rankings fall when the website is redesigned?
Permanent losses can be prevented if URLs are preserved or each old address redirects to its new equivalent with 301. Google says temporary ranking fluctuations may occur during migration; Search Console is therefore monitored after launch.
How long should 301 redirects be kept?
Google recommends keeping redirects in place as long as possible, generally at least one year. If external links point to old addresses, keeping redirects longer also prevents lost visitors.
Why is using an old PHP version risky?
PHP versions receive two years of active support followed by two years of security-only support, after which patches are no longer published. WordPress.org also states that versions whose official support has ended can expose the website to security vulnerabilities.
Is existing content preserved during redesign?
Yes, content bringing traffic and inquiries is preserved and transferred to the new design, updated if necessary. Decisions about which content to preserve are based on Search Console and Analytics data.
Can only the design be changed instead of a full redesign?
If the infrastructure is current and secure, a visual refresh or partial redesign may be sufficient. If themes and plugins cannot be updated, changing only the appearance will not resolve speed and security problems.
How long does corporate website redesign take?
For corporate websites with content ready, the redesign schedule averages 5-7 business days. If URL changes, migration or additional functions are involved, the schedule is finalized after reviewing the scope.
Does the website go offline during redesign?
It does not need to; the new website is prepared in a separate testing environment, and the old website continues working until launch day. The transition takes place on a planned day with redirects and DNS settings.
Call us
Call us for detailed information.
Let us call you!
Share your phone number and let us call you!
Our other services
- › Corporate web design
- › E-commerce website development
- › SEO optimization
- › WordPress website development
- › Google Ads management
- › WordPress speed optimization
Service areas
- › Web design in Sakarya
- › Web design in Tekirdağ
- › Web design in Bursa
- › Web design in Beşiktaş
- › Web design in Şişli
- › Web design in Tuzla
- › Web design in Ümraniye
- › Web design in Kadıköy
- › Web design in İstanbul
- › Web design in Ankara
- › Web design in Ataşehir
- › Web design in Üsküdar
- › Web design in Kartal
- › Web design in Maltepe
- › Web design in Pendik
- › Web design in Kocaeli
- › Web design in İzmir
- › Web design in Antalya