- 01
Market
Saudi Arabia
- 02
Written for
Head of Digital, CTO
- 03
Decision
Modernise an ageing website without risking what it has already earned
- 04
Languages
EN · AR
The method
Audit, triage, stabilise, then replatform — the order that keeps the site whole
Each step exists to make the next one smaller and safer. The build is deliberately last, because a rebuild scoped before the audit is a rebuild scoped on folklore.
Audit what actually exists
Every URL, its traffic, the queries it earns, the links pointing at it, and the integrations the site quietly holds — forms feeding a CRM, feeds other systems read, scripts a department added years ago. The inventory always surprises its owners. An evidence-backed inventory instead of an assumed one.
Decide keep, migrate or retire — per page
Traffic and business value make the call: pages that earn stay and move; pages that once mattered are retired with redirects to their successors; duplicates and orphans are retired outright. The rebuild shrinks with every honest decision. A triage list that is the project’s real scope.
Stabilise the information architecture
The target structure and every URL’s fate — kept, moved with a one-to-one redirect, or retired to a successor — are fixed before code, because search engines and visitors forgive a new design far more readily than a maze of moved addresses. A redirect map agreed and testable before anything ships.
Replatform in increments behind it
Sections move to the new stack one at a time — the old and new serve together under one architecture — and each increment is verified against the map before the next begins. A launch night never happens, because nothing waits for one. A modernisation delivered as reversible slices.
The triage
Most of an old website has not earned a place on the new one
A site that has grown for eight or ten years is mostly sediment: campaign pages for campaigns nobody remembers, three near-identical descriptions of the same service written in different eras, event pages for events long past, documents uploaded once and linked never. The audit routinely finds that a large share of URLs receive almost no visits, and that a small core carries nearly all the traffic and all the rankings. Migrating the sediment costs real money — every page moved must be rebuilt, retranslated and retested — and it buys nothing but bulk.
Retirement, done properly, is not loss. A retired page redirects to the page that now owns its subject, so a visitor following an old link and a search engine holding an old ranking both arrive somewhere better, and the authority the old page gathered concentrates on its successor instead of evaporating. The pages that keep earning are treated with the opposite care: moved one-to-one, verified after the move, watched afterwards. Triage is what lets the modernisation spend its budget where the site actually lives.
The routes
Big-bang relaunch, incremental replatform, or patching in place — what each route risks
Three honest options exist, and each is right somewhere. The comparison is about what each one puts at stake, because the cost of a modernisation is dominated by what goes wrong, not by what goes right.
| Option | Risk to search standing and old links | When the organisation feels improvement | How mistakes surface | What it demands of your team | Best for |
|---|---|---|---|---|---|
| Big-bang relaunch | Everything changes at once — every mapping error goes live the same night. | Nothing improves until launch day, and everything is supposed to. | In production, all together, under launch pressure. | A long freeze, then a scramble. | Small sites with little to lose in search. |
| Incremental replatform | One section’s worth at a time, verified before the next moves. | The worst section improves first, within weeks. | In one slice, reversible, while the rest stands. | Steady involvement, no freeze, no launch night. | Established sites whose traffic and rankings are worth protecting. |
| Patching in place | None today — the risk accrues as the platform ages past repair. | Small relief per patch, on a declining foundation. | As mounting fragility — each fix harder than the last. | Little now; an unplanned rebuild eventually. | Buying a year on a site already scheduled for replacement. |
Our role
What the modernisation carries over and which farewells stay your decision
- 01
The audit, before any commitment
The inventory, the traffic evidence and the integration map are produced first and belong to you — they are worth having even if the modernisation waits a year.
- 02
The machinery of a safe move
Redirect maps generated and tested rather than hand-written, parity checks that compare old and new pages before traffic shifts, and monitoring that watches the rankings of moved pages after each increment.
- 03
Increments that stand alone
Each slice ships complete — migrated content, working redirects, verified integrations — so the project can pause between increments without leaving the site half-moved.
Which pages the business still believes in, and which it is ready to retire, are calls only you can make; we bring the evidence that informs them and the machinery that makes either answer safe to execute.
Common questions
What buyers ask
Does modernising the website mean redesigning it as well?+
They are separable, and separating them is often the point. Modernisation as we run it changes the platform, the structure and the content inventory; the visual design can move with it, after it, or not at all. Holding the information architecture stable is what makes this possible — because the structure does not move, a new design can ship on the new platform section by section, or the existing design can be reproduced first and refreshed later once the foundation is safe. Deciding the two questions independently keeps each one honest: the platform is judged on engineering grounds, the design on brand and conversion grounds.
What happens to the search standing of pages we decide to retire?+
Each retired URL redirects permanently to the page that now owns its subject — not to the homepage, which search engines treat as a soft deletion. Done that way, the visitor following an old link lands somewhere genuinely useful, and most of the authority the old page accumulated transfers to its successor rather than disappearing. What we do not do is promise the transfer is lossless; no honest supplier can, because the receiving page is judged on its own merits too. The discipline is one-to-one mapping, no redirect chains, and monitoring afterwards so any page that slips is seen and addressed rather than discovered in a quarterly report.
Can the website stay fully live while it is being modernised?+
Yes — that is the reason for the incremental route. The old and new platforms serve together behind one address scheme: a routing layer sends each section to whichever generation currently owns it, so a visitor moves between old and new pages without noticing a seam. Each increment shifts one section, is verified, and can be pointed back at the old platform if something surfaces. The cost of this safety is that two systems run in parallel for the duration, which needs a little operational attention — a modest price against the alternative, which is taking the site through a single cutover that has to be right everywhere at once.
In this cluster
Plan the first increment
A modernisation plan built on your own inventory: what stays, what moves, what retires, and the first increment that ships without touching the rest.
Start the conversation
