A redesign is the project we are asked for most, and the one with the most risk. Not because design is hard, but because one wrong step can destroy search positions your site built over years.
When a redesign is justified
- The site fails on mobile. If Search Console shows most visitors arrive on phones and the site is not built for small screens, that is a business problem, not aesthetics.
- It loads slowly. If Core Web Vitals are in the red, a rebuild on a modern stack can fix performance in one go. See how page speed affects sales.
- Traffic is there, conversion is not. Usually information architecture, call-to-action placement or trust signals.
- The platform is unsupported. A years-old WordPress with plugins nobody updates is a security risk. See when to replace WordPress.
- The brand changed, the site did not. A mismatch erodes trust.
When it is not needed
“A more modern look” is not enough. If the site converts, loads fast and ranks well, a visual overhaul can break all three. Smaller steps often do the job: a new hero section, speed optimisation on the current theme, A/B tests of call-to-action text, structured data. If the problem is narrow, the fix should be narrow too.
What you can lose in the move
- Search positions. Google has indexed specific URLs. If URLs change without 301 redirects, the new pages start from zero.
- Speed. Heavier images, extra scripts and unoptimised fonts can make the new site slower than the old.
- Conversion. Users know the old layout; conversion often dips in the first weeks even when the new site is better.
- Technical SEO data. Backlinks to old URLs lose value without correct redirects. Canonical URLs, structured data and the sitemap matter equally.
A safe migration checklist
Before launch
- Full export of the old site’s URLs
- A mapping table: every old URL to its new URL
- 301 redirects implemented on the server (not in JavaScript)
- Canonical URLs checked on all new pages
- Sitemap.xml updated; robots.txt checked
After launch
- Submit the new sitemap in Google Search Console
- Check crawl errors over the next two to three days
- Compare PageSpeed Insights with the old site
- Manually test the 20-30 most important URLs for working redirects
First month
- Watch traffic in Search Console weekly
- If a position drops sharply, check the redirect to that page first
How we run it
We start with an audit, not a design: what works on the old site and must not be broken (analytics, Search Console, Core Web Vitals, URL structure, backlinks). Then information architecture: which pages stay, merge or go, which defines the URL structure and the redirect list. Design runs in parallel with the technical specification. We build with Laravel, Vue.js and Inertia.js, avoid launching on a Friday evening, and monitor the first week. Post-launch SEO checks are part of the same migration, not a separate project.
Audit before you decide
If you are unsure whether you need a redesign, start with an audit of technical state, search positions, speed and conversion issues. Often the result is a set of targeted changes instead of a full rebuild. See our web development service or describe your situation.
