Website Rebuild: Signals, Inventory, and the Safe Launch
Two opposite tragedies haunt rebuilds. Business A refreshes a healthy site out of boredom and torches years of search equity overnight. Business B nurses a site past its expiry date, losing customers monthly to “we’ll fix it someday.” Same question, both times: when — and how — do you rebuild? 🏗️
A website rebuild is justified by signals, protected by inventory, and executed through a redirect map and launch protocol. Done in that order, the new site launches richer than the old; skip the order, and launch day becomes an invisible demolition.
This guide covers the four rebuild signals, the pre-project inventory trio, the 301 redirect map, and the launch-day protocol. Rebuild like a surgeon, not a decorator. 🩺
Website Rebuild: The 4 Signals That Justify It
BU BÖLÜMÜN ÖZETİ
- Signal 1: the technical dead-end
- Signal 2: business drift
- Signal 3: the conversion floor
- Signal 4: maintenance hostage
Boredom isn’t a signal; these four are. Two together put the rebuild on the agenda legitimately. 🚦
The website rebuild signals: technical dead-end (the platform blocks needed work — speed, security, integrations), business drift (the site describes a company you no longer are), conversion floor (repairs done, mobile fixed, numbers still flat), and maintenance hostage (every small change costs disproportionate money or fear).
Signal 1: the technical dead-end
When the honest answer to “can we fix this on the current base?” becomes no — after real repair attempts, not before them. The three-wave repair test comes first; see mobile-friendly website.
Signal 2: business drift
New services missing, dead ones starring on the homepage, prices from another era. When the site lies about you, it works against you.
Signal 3: the conversion floor
Traffic exists, actions don’t — and the fixable causes are already fixed. Structural problems earn structural answers.
Signal 4: maintenance hostage
“Don’t touch it, it breaks” as company policy. A site you fear is a site you’ve already lost. 🔒
Website Rebuild Inventory: What You Must Not Lose
BU BÖLÜMÜN ÖZETİ
- The URL inventory
- The content verdicts
- The equity ledger
- The access sweep
Before any design mood-board: the inventory trio. Rebuilds fail by forgetting, not by building badly. 📦
The trio: the URL inventory (every address that earns traffic or links), the content inventory (pages, files, reviews — keep/rewrite/retire verdicts), and the equity inventory (search rankings, backlinks, indexed assets — the invisible wealth the new site must inherit).
The URL inventory
Export every live address; tag each with its traffic and inbound links. This list is the redirect map’s raw material — and the launch’s insurance policy.
The content verdicts
Page by page: keep as-is, rewrite, or retire. Retired pages still need redirect homes; orphaned addresses become 404 leaks.
The equity ledger
Which pages rank, which earn links, which queries feed the business — read from Search Console before a single wireframe. The new site is designed around this wealth, not despite it.
The access sweep
Domain, hosting, analytics, mail — ownership confirmed in the business’s name before the project. Rebuild moments expose hostage arrangements. 🗝️
The Website Rebuild 301 Map: Moving Without Losing
BU BÖLÜMÜN ÖZETİ
- One-to-one discipline
- The priority tiers
- The staging rehearsal
- The keep-forever rule
The rebuild’s most technical and most decisive document: the redirect map. Old addresses must hand over their equity, not abandon it. ↪️
The 301 map pairs every old URL with its new home, one-to-one wherever possible: old service page → new service page, old article → its successor. Retired content redirects to the nearest relevant parent — never everything to the homepage, which reads as demolition, not a move.
One-to-one discipline
Equity transfers best along matching meaning. Bulk homepage redirects squander years of accumulated standing.
The priority tiers
Map the traffic-and-link earners first and verify them personally; long-tail addresses follow in batches.
The staging rehearsal
The full map runs on the test copy before launch; a crawler walks every old address and confirms its landing. Launch day is a performance, never a rehearsal.
The keep-forever rule
Redirects stay live for the long haul — equity transfer is a process, not a day. Deleting the map months later reopens every wound. 🩹
Website Rebuild Launch: The Protocol and the First Month
BU BÖLÜMÜN ÖZETİ
- Switch-day sweep
- The watch month
- The comparison scorecard
- Who runs all this
Content migrated, map rehearsed — launch is a checklist, not a champagne moment. 🚀
The protocol: pre-switch freeze (content changes stop), the switch window (low-traffic hours, rollback ready), the immediate sweep (forms, phones, checkout, redirects — tested live), and the watch month (daily error scans, weekly query readings, conversion tracking verified).
Switch-day sweep
Every money action tested as a real user within the first hour: form submission arrives, phone taps dial, payments clear. The classic launch wound is a silently broken form.
The watch month
Crawl errors reviewed daily at first, indexing and query trends weekly. Small ranking turbulence is normal; unmapped 404s are not — they get redirect homes same-day.
The comparison scorecard
Old-site baselines (traffic, conversion, speed) sit beside new-site numbers monthly; the rebuild’s verdict is read at day 90, not day 3.
Who runs all this
The build team builds; an independent eye owns inventory, map, and protocol — the division of labor described in web consulting process, with costs framed in web consulting fees. 🤝
Field Notes 📝
The saddest file we open is the post-launch panic case: a beautiful new site, traffic halved, and no 301 map ever made — old addresses dying as 404s while the team celebrated the design. Recovery takes months; the map would have taken days. In rebuilds, the invisible document outranks the visible design.
Quick Glossary 📖
301 redirect: the permanent old→new address handover. Equity: accumulated search standing and links. Staging: the pre-launch test copy. Rollback: the prepared return path if launch fails.
Quick Summary ⚡
- A website rebuild is justified by four signals — technical dead-end, business drift, conversion floor, maintenance hostage — two together.
- The inventory trio precedes design: URLs, content verdicts, and the equity ledger from Search Console.
- The 301 map pairs old→new one-to-one, rehearses on staging, and stays live long-term.
- Launch is a protocol: freeze, low-traffic switch, money-action sweep, and a 30-day watch with a 90-day verdict.
Next Step 🎯
Rebuild on the horizon? We’ll run the signal check and build your inventory trio before any design money moves. Visit our web consulting page or get in touch.
Sık Sorulan Sorular
When two of four signals coincide: a technical dead-end after real repair attempts, business drift (the site misdescribes you), a conversion floor despite fixes, or maintenance hostage where every change costs fear and money.
Inventory first (URLs, content verdicts, equity ledger), then a one-to-one 301 map from every old address to its matching new home, rehearsed on staging, verified at launch, and kept live long-term — never bulk-redirected to the homepage.
The protocol sweep: every money action tested live (forms arriving, phones dialing, payments clearing), redirects spot-checked, then a 30-day watch of crawl errors daily and queries weekly, with the rebuild judged at day 90.