Modernize the website without losing what already works: content, authority, links, and brand recognition.
The redesign of the existing site includes an analysis of the current situation, a new structure, visual refreshment, better mobile display, preservation of important links and a clearer path to contact.
For companies whose site looks outdated, doesn't show good service, works poorly on the phone, or doesn't bring enough inquiries even though it already has content and visits.
Enter the address and in half a minute you get the actual measurement from Google — the same test we use before suggesting anything.
The score is a Google Lighthouse measurement for mobile. A lower score does not mean the website is bad; it identifies specific technical opportunities for improvement.
We publish the range so you can understand the likely budget before a call. The final proposal depends on scope, functionality, and how much content is ready.
The same pricing logic as the full calculator, with a shorter path to an indicative range.
Redesign advice is often vague. These are measurable outcomes from real projects, using Google Search Console and Lighthouse data rather than estimates.
The WooCommerce store moved from Elementor to custom templates and ACF. Core Web Vitals changed from Failed to Passed in real-user CrUX data. Google Search performance improved by 33% in clicks and 25% in impressions, while the average position moved from 8.1 to 5.1. Rankings were not lost; they improved.
Bilingual site with B2B section and reservations. The mobile performance rating went from 29 to 99. The most sensitive part was not the design, but the fact that no reservation was lost during the transition, because the system was in use all the time.
The redesign also included a move from a .com to a .rs domain, one of the highest-risk technical changes because the site identity changes for search engines. The result was a 99/100 mobile Lighthouse score and a 1.0-second Speed Index; the previous version had never scored above 76.
All three case studies were published with a full description of the scope of work and technologies used.
Every migration guide correctly says to set up 301 redirects, but that is rarely where the difficult mistakes happen. The real risks are in details that a checklist does not reveal.
Almost every site has addresses that no one from the company considers important, which bring stable traffic — an old article, a FAQ page, a description of a service that you no longer actively sell. If the plan is made according to the current menu, they disappear. That's why the list is made from Search Console by the actual views, not by how the site looks.
In addition to products and categories, there are filters, variations, search pages and pagination. When switching from one system to another, it can easily happen that the structures do not match and addresses that did not exist before are generated. It doesn't bring down the site, but it dilutes what Google clearly understood before.
When a domain is changed, not only the content but also the identity is transferred: redirects must be complete and permanent, both domains are logged into the Search Console, and the old one does not shut down until the transfer is confirmed. We did this on the SaiMai project and it is the only part of the redesign that does not tolerate improvisation.
Even when the migration is done correctly, Google needs time to revisit and understand the new site. An honest framework of expectations looks like this.
Ranking fluctuations and a modest drop in impressions are common while new URLs are indexed. That alone does not mean the migration failed. Persistent sharp declines, 404 errors on previously valuable URLs, or pages disappearing from the index are the real warning signs.
Before launch, we record the baseline: which URLs earn impressions and clicks, and at which positions. After launch, we monitor crawl errors, indexing, and those same URLs. Without a baseline there is nothing reliable to compare, which is why many redesigns cannot prove whether they helped or harmed performance.
If a dated-looking website still generates enquiries and the real problem is speed or unclear messaging, a full redesign is an expensive answer to a smaller problem. Performance work or content restructuring may be the more honest recommendation. Redesign makes sense when the structure is holding the site back, not merely when the visuals feel old.
Not when every traffic-generating URL is inventoried before launch and permanently redirected to the correct new destination. On Buba u autu, the average position improved from 8.1 to 5.1 and clicks increased by 33% after redesign. Losses occur when migration decisions are based on visual structure instead of Search Console data.
A visual refresh of the existing structure usually takes two to three weeks. A redesign with a new page structure and content takes four to eight weeks. Ecommerce or booking-system redesigns take eight to sixteen weeks because the cutover must be planned without interrupting live operations.
Yes. The new version is built separately and launched only after validation, so the existing website continues receiving visits and enquiries. For live booking or order systems, the cutover is planned so no transactions are lost during the change.
Content that attracts traffic is retained and migrated because it is the reason the site ranks. Its presentation may change, but it is not discarded. Obsolete pages with no visibility can be retired, with redirects to the closest relevant destination instead of simply disappearing.
A redesign preserves the existing domain, valuable content, and earned rankings, building on what already works. A new website on a new domain starts without that history. If the current domain has authority or traffic, redesigning it is almost always the safer choice.
Konkretni projekti iz ove usluge — šta je bio problem, šta smo uradili i šta se promenilo.
Lighthouse 99/100 on mobile and Speed Index 1.0 s — previous version of the site did not exceed 76
Full case studyMobile Lighthouse performance improved from 29 to 99, with migration completed without losing bookings
Full case studyCore Web Vitals from Failed to Passed (CrUX), +33% clicks and +25% views in Google Search, average position from 8.1 to 5.1
Full case studyThe same four steps regardless of the service — to know where the project is at all times.
We first establish what the website must deliver: enquiries, sales, trust, better performance, easier maintenance, or a migration without losses.
We plan the pages, content, and user journey so visitors understand the offer quickly and can contact you easily.
We build a clear interface, a fast user experience, and a WordPress admin area that does not require a developer for every change.
Before launch, we test the mobile layout, forms, performance, page URLs, redirects, analytics setup, and every critical user flow.
Services are often combined — redesign with performance work, a store with maintenance.
Send a short project description, the current website link if one exists, and the goal you want to achieve. We will respond with the best next step.