The company's website, and not a single line of its code in the company's hands
The website was built by a single developer, and its source code sat in his personal repository. After he left, he could not be reached, and the code couldn't be recovered. The site couldn't be changed or moved, and nearly half its content was rendered only in the browser, so it didn't appear in the static source at all.
- Client
- Healthcare marketing consultancy
- Scope
- Digital assets
- Key result
- Full ownership back with the company
The problems we found
- The source code was in the former developer's personal repository, so it couldn't be changed or moved
- The website was effectively in someone else's hands, with no way to make any change
- Nearly half the content (the headline carousel, FAQ and team section) was rendered only in the browser and didn't appear in the static source at all
What we changed
- Reverse-engineered a 1:1 rebuild from the live site, using rendered-page comparison to make sure nothing was lost
- Tracking codes and site verification IDs managed in one place, so switching accounts means editing one file
- The GA4 / Search Console transfer procedure documented
- Code moved into a GitHub organization the company owns
Results
- Website, code, data and deployment accounts: for the first time, ownership is fully back in the company's hands
The most valuable part of this case isn't the technology, it's the lesson. Take stock: who holds the logins for your company's website, social media pages, domain and data right now?
Who holds the logins for your website, domain and data right now?
Start with a free 30-minute call about how the work runs today, and we'll judge whether a closer look is worthwhile. Finding where it really gets stuck means looking at the actual workflow.