SOLUTIONS · RESTRUCTURING AND MIGRATION

Professional redesign without losing rankings.

The company already has a website — but what it shows does not reflect what the business is today. The solution is not to start from scratch ignoring what exists. It is to analyse what works, what does not, and rebuild on that foundation without losing a single position on Google.

01 · APPROACH

Starting from scratch vs rebuilding with preservation.

When a company has been online for years, its website has a history on Google. Indexed URLs, earned positions, organic traffic — even if modest. A poorly executed redesign can destroy all of that in a week. A strategic redesign keeps every valuable URL with its redirect and rebuilds what does not work.

Model A · redesign from scratch
Starting as if the current website did not exist
URLs changed without 301 redirects.
Old content deleted by default.
Platform changed without migrating the structure.
External links that led to the website now return a 404 error.
Organic traffic loss of up to 100% in a week.
Slow recovery — months to regain what was lost.
Model B · this service
Rebuilding with history preservation
Full audit of indexed URLs and external links.
301 migration map before touching a single line of code.
Valuable content kept, transformed or rewritten.
Every old URL redirected to its correct destination.
Zero organic traffic loss during the transition.
Existing rankings preserved + new architecture.
02 · REAL RISKS

What happens when a redesign is done badly.

These are not hypotheses. They are the four most frequent technical causes of ranking loss in a website migration. Each one destroys in a week what took years to build.

Risk 01

URLs changed without redirects.

The new agency changes all URLs without setting up 301 redirects. Google stops finding the pages it had indexed. Organic traffic drops to zero within days.

Risk 02

Deleted content that was ranking.

Old content is discarded which, although poorly presented, ranked for relevant searches. The ranking disappears along with the content. Years of work are lost in a fifteen-minute decision.

Risk 03

Platform change without migrating the structure.

A move from WordPress to another CMS without transferring the URL structure. External links pointing to the website from other sites now lead to error pages. Earned authority is lost.

Risk 04

Visual-only redesign.

The appearance is redesigned but the architecture is left untouched. The website looks better but still fails to reflect what the company is today. Same problem with better packaging — and the same commercial result.

03 · METHODOLOGY

Five phases with a prior audit and subsequent verification.

The process follows the same methodology as a from-scratch project, but with two additional phases: a diagnosis of the current website at the start, and a post-launch verification at the end. Both are specific to the redesign and critical for preserving rankings.

01

Audit of the existing digital presence.

Before proposing what should change, I analyse what exists. What pages exist. Which receive traffic. Which rank for relevant searches. What URLs are indexed on Google. What external links point to the website from other sites. What content has value and what is dead weight. This inventory determines what is preserved, what is transformed and what is discarded.

02

Business analysis.

The same process as in a from-scratch project. Company structure, offering, sectors, regulatory framework, capabilities, competition and digital presence objectives. Because the problem with the old website is almost never purely visual — it is that the company has grown and the web structure has not grown with it.

03

Architecture document with migration map.

The result is a complete architecture document — the same as in a new project — but with an additional component: the 301 migration map. It defines which URLs are kept, which are redirected and where to, which are removed and why, and what new pages are created. In a project with 70 pages in two languages the map can have more than 140 rules — a single missing one is a page Google stops finding.

04

Development on the new architecture.

With the architecture document approved and the migration map defined, development follows the same process as a from-scratch project: proprietary code, structural rankings, native multilingual support, speed, security. The difference is that every technical decision respects what exists and guarantees ranking continuity.

05

Post-launch verification.

After publishing the new website, over the following weeks it is verified that all redirects work, that Google reindexes the new URLs, that there are no traffic drops attributable to the migration and that key positions are held or improve. If an anomaly is detected, it is corrected immediately. A redesign does not end the day it is published — it ends when Google has processed the change.

04 · MIGRATION MAP

Every old URL with a defined destination.

The 301 migration map is the technical piece that ensures no indexed URL is lost in the transition. Every redirect is documented before development starts and is verified after launch. This is what a real project sees during the migration.

What it is
Technical table of 301 redirects.

Every old URL with its corresponding new URL. The 301 redirect tells Google that the page has permanently changed address — and transfers the rankings, external links and authority of the old one to the new URL.

When it is defined
Before development starts.

It is part of the architecture document. Not a single new URL is programmed without knowing which old URL redirects to it. The map is the technical guide for development, not a later formality.

Verification
The 8 weeks following launch.

Search Console monitors which URLs Google reindexes, which 404 errors appear and which positions are held. Any anomaly is corrected before it affects organic traffic.

Without a migration map, organic traffic can drop 80-100% in the first week after the migration. Recovering it takes months — and sometimes it is never recovered.
05 · SIGNALS

Six indicators that your website needs a redesign.

Not every website needs to be rebuilt. But these are the most frequent objective signals that the current digital presence has fallen behind the company that owns it.

01
The company has grown but the website has not.New business lines, new products, new offices or certifications that do not appear on the website. The visitor sees an outdated version.
02
The catalogue is a flat listing.No families, no hierarchy, no datasheets. A buyer cannot find what they are looking for without scrolling for minutes.
03
The certifications are buried.In a downloadable PDF or at the bottom of the company page. In sectors where they are the first selection filter, that is invisible.
04
A single language version.The company exports but the website only exists in Spanish. Or it has an English version made with a machine translator that creates distrust.
05
The platform limits growth.WordPress with plugins that break, builders that do not allow complex structures, templates that constrain the design.
06
The competitor has a better digital presence.And that gives them an advantage in the buyer's perception before the commercial conversation begins.
06 · REAL CASE · MIGRATION EXECUTED

WordPress → proprietary code migration without losing rankings.

ProSilicones64 case

Full migration from WordPress preserving all the history.

The previous website was a static CMS with no product classification, no process documentation and no visible certifications. All existing URLs were mapped, the 301 redirects were configured and the earned rankings were preserved while a completely new architecture was built.

+332%
Organic traffic · 8 weeks
#1
Google · key searches
27
B2B leads · month 2
0
URLs lost
80+
301 redirects
Source: Google Search Console + internal lead system
07 · FREQUENT QUESTIONS

What is asked before hiring.

Will I lose the rankings I already have?
No, if the migration is done correctly. Every URL that changes address is redirected with a permanent 301 rule that tells Google where the new content is. The migration map is defined before development and verified after launch. The goal is to keep everything gained and improve from there.
How long does a redesign project take?
Longer than a new website of the same scope, because it includes the diagnosis phase of the current state and the migration map. The client knows the full timeline before development starts, not after.
Can I do the redesign in phases?
Yes, if the architecture document allows it. A complete structure can be defined and executed in phases prioritised by impact. What matters is that the architecture is fully defined from the start, even if development is approached in stages.
My current website is WordPress. Is it possible to migrate to proprietary code?
Yes. It is exactly what was done with ProSilicones64. The entire existing structure was mapped, every URL was redirected and a new platform was built from scratch on the architecture defined in the analysis. The result was more speed, more security, better rankings and zero plugin dependency. Without losing a single position during the transition.

The redesign is the starting point, not the end.

Once the new website is published, the work continues. Rankings, content, monthly reports, corporate channel management, results monitoring. The redesign builds the foundation — the subsequent management turns it into a tool that generates returns continuously.

Shall we talk about your project?

First conversation with no commitment. The company and its context are understood, and we define which of these services — or combination of them — makes most sense for your case.