How We Rebuilt HopSkipDrive's 570-Page Website Without Breaking a Thing
There's a version of a website rebuild that goes badly. The old site goes dark. The new one launches with broken redirects, missing content and a content team that doesn't know how to use the CMS. Six months later, organic traffic has collapsed and no ones quite sure what happened.
We've built a methodology specifically to avoid that outcome. When HopSkipDrive came to us with 570+ pages, 400+ blog posts and a live site serving a fast-moving US school transportation business, the stakes were real.
Here's how we approached it.
By Nick Randell.
Starting With the Right Foundation
HopSkipDrive is a technology company solving one of the most complex logistics challenges in American education - getting kids to school safely and reliably, at scale. Their website had to reflect that operational seriousness while also serving multiple distinct audiences: school districts, parents, and drivers.
For a content site at this scale, we recommended Next.js on Netlify. Next.js handles server-side rendering and static generation cleanly - critical for page performance when you're dealing with hundreds of unique page types. Netlify gives the content team deployment confidence: changes can be previewed, tested, and rolled back without engineering intervention.
New Functionality With Real Impact
A rebuild is an opportunity to add capability that the old architecture couldn't support. For HopSkipDrive, the highest-value addition was an intelligent blog search - type a keyword and get instant, relevant results across 400+ posts. It sounds simple. It required careful indexing, relevance tuning, and performance work to feel fast and accurate.
The outcome validated the approach. The new site delivered a 46% increase in operational efficiency — a metric that reflects the combined impact of faster page performance, cleaner content management, and improved navigation for all three audience types.
Migrating 400+ Blog Posts
This was the most technically demanding part of the project, and the part most rebuilds underestimate. Moving 400+ blog posts isn't a copy-paste operation. Each post carried metadata, tags, author information, internal links, and an established URL that search engines had indexed.
We built a custom migration pipeline that preserved all of that data, remapped every URL to its new equivalent, and set up 301 redirects to protect the existing SEO equity. Every post was validated against its original before the old site was retired. The content team kept publishing throughout - the migration happened in parallel, not in place.
The Launch
We built the new site on a separate hosting environment so the existing site stayed live and fully functional until the moment of switchover. The cutover itself was coordinated across DNS, CDN, and the CMS - a staged process with rollback capability at each step.
A Smooth Hand-Off
A technically excellent website that a content team doesn't know how to use is a failed project. After launch, we ran structured handover sessions covering the CMS, deployment workflow, and the logic behind the key template structures. The goal was a team that could work confidently and independently - not one that needed to come back to us every time a new page type was needed. That handover is part of the build, not an afterthought. It's what turns a good launch into a lasting asset.
About the piece: Article by Nick Randell co-founder at SE Studio, a branding, design and technology agency based in London and San Francisco.
