Strategy-led redesign and migration

Website Rebuild

A strategy-led rebuild for organisations whose current site no longer serves them. We audit what exists, keep what earns its place, rebuild the rest on modern foundations, and migrate with safeguards so nothing of value is lost in transit.

Discuss this project

What is Website Rebuild?

A Website Rebuild replaces a dated or fragile site with a tested, multilingual one on modern foundations, while mapping and redirecting the legacy content and URLs so nothing of value is lost. It begins with a written audit that states what is worth keeping before any design work starts.

Choose this if

The current site is slow, dated, hard to maintain or stuck in one language
Years of content, URLs and search visibility exist and must survive the change
You cannot afford a gap in service during the switchover
You want a documented redirect map, not a blank page and a hope

Choose something else if

Platform Build — when the rebuild uncovers a need for payments, bookings or portals.
Website Care — when the site is sound and simply needs maintaining and improving.

Designed for

Organisations with an existing site — dated, slow, hard to maintain or stuck in one language — that they have outgrown but cannot afford to break.

The problem

Most rebuilds start from a blank page and quietly discard years of content, URLs and accumulated search visibility. The old site gets treated as an embarrassment instead of a dataset. The result is often a prettier site that does less than the one it replaced.

The intended outcome

A rebuilt, tested, multilingual site on modern foundations, with legacy content and URLs mapped, redirected and verified — live without a gap in service.

Integrated scope

What the engagement can cover.

01Full audit of the current site: content inventory, URL map, analytics and technical review
02Content and redirect mapping — every legacy URL gets a documented destination
03Structured scraping of legacy content, as used on the BATD Academy rebuild
04Redesign and rebuild on modern foundations, built with AI coding agents and covered by automated tests
05Multilingual restructuring, including languages the old site never had — Arabic with full RTL included
06Technical SEO rebuilt in: hreflang alternates, structured data, pre-rendered pages
07Migration safeguards: staged environments, noindexed staging, redirect testing before cutover

Deliverables

Concrete outputs, agreed before work begins.

A written audit and migration plan before any build work starts
A complete redirect map, implemented and tested
The rebuilt site, live on your domain, with automated tests on critical paths
Content migrated and restructured, not pasted into a new template
A dev → test → production pipeline the site keeps after launch
A cutover checklist and post-launch verification of every mapped URL

Service process

Four stages with one decision trail.

The audit is the first milestone and fixes the scope of everything after it. Rebuild length depends on how much of the old site survives the audit; the migration plan states the estimate and names the planned cutover date.

Audit

We inventory the current site: every page, URL, language and integration. The audit states plainly what is worth keeping, what is broken, and what the rebuild must not lose.

Mapping

Content and redirects are mapped before design begins. Where it saves weeks of manual work, legacy pages are scraped into structured content — the approach running now on the BATD Academy rebuild.

Rebuild

The new site is built with AI coding agents on staged environments, with staging kept noindexed so search engines never meet half-finished work. Automated tests cover navigation, forms and language switching.

Cutover

Redirects go live with the new site in one planned switchover. Every mapped URL is verified afterwards, and a support window covers anything the plan missed — the discipline that carried Alberr's platform from prototype to production.

The practice owns

The audit, the redirect map, and the honesty of both
Design, rebuild and automated testing of the new site
Migration tooling, including structured extraction of legacy content
Accessibility and technical SEO implementation on the rebuilt pages
The cutover itself, and verification after it

You provide

Access to the current site, its hosting, DNS and analytics
A decision-maker willing to retire content — a rebuild that keeps everything rebuilds nothing
Source material for new or corrected content, and sign-off on translations
A list of what must not change: printed URLs, QR codes, links in donor or customer letters
Advance notice of campaigns or events that constrain the cutover date

Not included by default

Ranking guarantees. Careful redirect mapping protects against avoidable loss; nobody can promise search positions, and we do not.
Platform features. If the rebuild uncovers a need for payments, bookings or portals, that is Platform Build — scoped as its own project.
Wholesale copywriting. We restructure, edit and migrate what exists; writing a site's content from nothing is quoted separately.
In-house photography and video. Where the rebuilt site needs new imagery, we plan it with trusted production partners.
Rescuing the old codebase. We rebuild on modern foundations; we do not patch legacy code indefinitely.

Relevant proof

The proof is live, not promised.

Five live client properties are linked from the work page—open them, click through them and inspect them. El-Sultan Web does not attach invented outcomes or borrowed metrics to any service.

See live client work

Common questions

Website Rebuild, answered directly.

Every answer states a boundary as well as a capability. Broader questions about timelines, ownership and what happens after launch are on the FAQ page.

Will a rebuild damage my search rankings?

Careful redirect mapping protects against avoidable loss: every legacy URL gets a documented destination, implemented and verified after cutover. Nobody can promise search positions, and no such guarantee is given here. What is guaranteed is that no mapped URL is left to break silently.

What happens to the content on my current site?

It is inventoried first. The audit states plainly what is worth keeping, what is broken, and what the rebuild must not lose. Content is migrated and restructured rather than pasted into a new template, and where it saves weeks, legacy pages are scraped into structured content.

Can you add languages the old site never had?

Yes. Multilingual restructuring is part of the scope, including Arabic with full right-to-left support, with hreflang alternates and structured data rebuilt in rather than patched on at launch.

How do you avoid search engines seeing the half-finished site?

Staging is kept noindexed for the whole build, and the environment emits a noindex robots directive and an empty sitemap. Redirects go live with the new site in one planned switchover, and every mapped URL is verified afterwards.

Project fit

Could Website Rebuild fit the challenge?

Twenty focused minutes: what you need built, in which languages, and what a prototype-first timeline looks like for it. If the project is not a fit for this practice, you will hear that plainly.

Book a project fit call

Initial qualification only. Not a free audit or commitment to purchase.