Week one of a full website rebuild is always a strange mix of excitement and controlled chaos, and this week we kicked one off for a client whose current site is, in their own words, "held together with digital duct tape." That's not an exaggeration, and today's update is about what week one of fixing that actually looks like.
How We Got Here
This client, a specialty equipment rental company, had grown quickly over the past three years, and their website grew with them the way a lot of fast-growing businesses' sites do: pages bolted on as needed, a redesign half-finished by a previous freelancer two years back, and a content management system that, by the team's own admission, none of them fully understood anymore. Rather than another patch, they came to us wanting a proper rebuild.
Full rebuilds are risky from an SEO standpoint if they're not planned carefully, and we've written before about exactly what can go wrong during a technical migration when redirects and URL structure aren't mapped properly ahead of time. So week one wasn't spent designing anything visual at all. It was spent making sure we understood exactly what we were about to replace.
Day One and Two: The Full Site Inventory
Before any design work starts, we run a complete inventory of the existing site, every indexed URL, its current traffic and ranking data, and its backlink profile, similar in spirit to the process in our own SEO audit checklist but scaled up to cover an entire domain rather than a single page. For this client, that meant cataloging just over 300 URLs, a mix of genuinely valuable pages earning real traffic and a fair number of dead weight pages that had accumulated over the years with no purpose anyone could still identify.
We found eleven pages carrying meaningful backlink equity that weren't even linked from the current site's navigation anymore, essentially orphaned but still ranking on the strength of old external links. Those went straight onto our "must preserve" list, since losing them in the rebuild would mean throwing away earned authority that took years to accumulate and can't easily be rebuilt.
Day Three: The Uncomfortable Content Audit
Day three is usually the hardest conversation in any rebuild, because it involves telling a client that a meaningful chunk of their existing content needs to be cut, not carried forward into the new site. For this client, that meant recommending we drop about 60 pages entirely, old blog posts with zero traffic and no ranking value, duplicate service pages created during that half-finished redesign attempt two years ago, and a handful of pages so outdated they actively misrepresented services the company no longer offers.
Nobody enjoys hearing that a page they paid someone to write is getting cut, and we spent real time walking through the data behind each recommendation rather than just presenting a list and expecting trust on our word alone. By the end of the conversation, the client's own marketing director was the one pushing to cut a couple more pages we'd actually left off our list, once she saw how clearly the traffic data told the story.
Day Four: Building the Redirect Map
This is the unglamorous, absolutely critical work that determines whether a rebuild preserves rankings or torches them. Every single URL being removed, renamed, or restructured gets mapped to its correct destination on the new site, one to one, not a lazy blanket redirect sending everything to the homepage, which search engines increasingly treat as barely better than no redirect at all.
For 300-plus URLs, this took the better part of a full day, cross-checking against the traffic and backlink data from day one to make sure nothing valuable got mapped incorrectly or, worse, forgotten entirely.
Day Five: Finally, the Design Kickoff
Only once that foundation was solid did we sit down with the client for an actual design kickoff conversation, informed by everything we'd learned that week. Their most valuable pages, the ones actually driving business, are getting the most design and content investment in the new structure. The dead weight isn't coming along for the ride. And every redirect that needs to exist on launch day is already mapped out, ready to implement rather than scrambled together the night before going live, which is how most botched migrations actually happen.
Why I'm Sharing an Unfinished Project
I could wait months and write about this once the new site is live with a tidy before-and-after story. I'd rather write about it now, because the part that actually protects a client's rankings through a rebuild is exactly this unglamorous week one work, not the final launch day everyone gets excited about. If you ever hear an agency talk about a website rebuild and design is the first thing they mention, that's usually a sign this part got skipped.
What We Still Have Ahead of Us
Week one only gets a rebuild this far, and there's real work left before this client's new site goes live. Design and development still need to happen across every template we scoped, content needs to be rewritten rather than just carried over verbatim for the pages we're keeping, since several of them were written years ago in a voice that no longer matches how this company actually talks to customers today. And once a staging version exists, we'll run a full pre-launch technical check, verifying every redirect actually fires correctly, confirming structured data is intact, and testing page speed against the same Core Web Vitals thresholds we've written about before, all before this client's audience ever sees the new site.
I'll keep sharing pieces of this project as it moves forward, partly because I think it's useful for other business owners staring down their own overdue rebuild to see what the process actually looks like in practice, not just the polished launch announcement at the end.
Planning a rebuild and worried about protecting what you've already built? Talk to Rafenthic's team before you touch a single page.
— Abdullah Abid, Founder, Rafenthic