You have approval, budget, and a launch date. The new site looks sharp. And somewhere in the back of your mind is the question nobody on the project plan wants to own: what happens to our Google rankings the day we flip the switch?
It’s a fair worry. A redesign can cost you organic traffic, and for a university that depends on inbound interest from prospective students, that traffic is rarely something you can afford to rebuild from scratch. The good news is that the loss most teams fear is almost always preventable. The schools that drop in rankings after a relaunch usually lost them to a handful of avoidable decisions, not to the redesign itself.
What follows is the approach we use to take a higher ed site through a redesign with its search authority intact. Some of it is technical. Most of it is sequencing the work so SEO is part of the plan from the first wireframe, instead of a panicked audit the week before launch. If you’re still at the planning stage, the earliest place to protect your rankings is in how you scope the project, and it’s worth building these requirements into your website redesign RFP before a single vendor responds.
Even a flawless migration usually sees rankings wobble for a few weeks while Google recrawls and reindexes the new site. That dip is normal and typically temporary.
Does a website redesign actually hurt your SEO?
It can, and it’s worth being clear about why. A redesign changes three things search engines care about: your URLs, your content, and your code. Move a page without telling Google where it went, and the authority that page earned over years can vanish. Cut the word count on a page that was ranking, and you can quietly hand its position to a competitor. Launch on a slower platform, and you can lose ground even on pages you never touched.
There’s also a short-term effect that catches teams off guard. Even a flawless migration usually sees rankings wobble for a few weeks while Google recrawls and reindexes the new site. That dip is normal and typically temporary. The permanent losses are the ones you can prevent, and prevention starts long before launch week.
The first redesign deliverable that protects your SEO has nothing to do with design. It's a complete inventory of what you already have and what it's worth.
Start with an inventory
The first redesign deliverable that protects your SEO has nothing to do with design. It’s a complete inventory of what you already have and what it’s worth.
Pull every URL on the current site alongside the keywords it ranks for, the traffic it brings, and the conversions it drives. You’re looking for the pages that quietly carry your organic performance: program and degree pages, a few high-authority blog posts, the admissions and tuition pages that prospective students land on directly from search. These are the pages you protect at all costs.
This inventory becomes your reference document for the entire project. When someone proposes consolidating ten program pages into three, you’ll know exactly which rankings are on the line. A structured content audit is the natural home for this work, and it’s far easier to do now than to reconstruct after traffic has already dropped.
Map every URL before you move anything
If your URLs are changing, and in most redesigns they are, every old address needs a destination. This is the single most important SEO deliverable of the project, and it’s the one most likely to get rushed.
A few rules that save teams from the worst outcomes:
- Redirect one-to-one wherever you can. Each retired URL should point to its closest equivalent on the new site, using a permanent 301 redirect. The closer the match in content, the more authority carries over.
- Resist the urge to send everything to the homepage. Bulk-redirecting orphaned URLs to the homepage tells Google those pages no longer have a real equivalent, and the ranking signals tend to evaporate.
- Watch for redirect chains. An old URL that redirects to another redirect that redirects again wastes authority and slows everyone down. Point the original address straight at the final destination.
- Keep the map alive. As the new site’s structure shifts during the build, the redirect map has to shift with it. A redirect map built in month one and never updated is how live pages end up pointing nowhere.
Treat your redirect map as a working document that the whole team can see and update.
A redesign is a fine time to improve these elements. It's a terrible time to lose them by accident.
Protect the pages that already earn their keep
Your inventory told you which pages bring in traffic. The redesign is the moment to protect them deliberately.
When a high-performing page moves to the new site, keep its substance intact. If a program page ranks because it answers real questions about curriculum, outcomes, and cost, don’t trade that depth for a cleaner layout with half the content. You can absolutely make it more attractive and more usable. Just don’t gut the material that’s doing the ranking.
Carry the on-page signals over with the same care. Page titles, H1 headings, and the keyword-relevant copy that helped a page rank should survive the move, even if everything around them gets a fresh design. A redesign is a fine time to improve these elements. It’s a terrible time to lose them by accident.
Don't quietly undo your on-page SEO
Platform migrations can add specific challenges to SEO retention. When you move from one CMS to another, whether that’s Drupal, WordPress, or a SaaS platform, the new system doesn’t automatically know how the old one handled SEO. Sometimes structured fields that were populated for years can come across empty with an automated CMS migration.
Before launch, confirm that the new build preserves:
- Title tags and meta descriptions on every page that had them, especially your top performers.
- Heading structure, so a single, descriptive H1 still leads each page.
- Image alt text, is .
- Canonical tags, so the new CMS isn’t quietly creating duplicate versions of the same page.
- Structured data, so the schema that earned you rich results doesn’t disappear in the move.
Page speed belongs on this list too. A redesign that ships heavier pages or weaker Core Web Vitals can lose rankings even where the content is identical. Performance is part of the user experience prospective students judge you on in the first few seconds, and search engines weigh it as well.
A redesign is a great moment to prepare your site for how search is actually changing.
While you're rebuilding, build for AI search too
A growing share of prospective students start in AI tools and AI-generated overviews rather than a classic list of blue links. The good news is that the work that protects traditional rankings, clean structure, accurate schema, and content that answers questions directly, is largely the same work that helps AI systems understand and cite your institution. Getting it right during a rebuild costs a fraction of what it costs to retrofit later. If you’re weighing how much to invest here, our take on how GEO and SEO actually differ is a useful place to calibrate.
A pre-launch checklist
Most relaunch challenges trace back to one or two missed steps at cutover. Here is a short list worth printing and taping to a monitor.
- Crawl the staging site first. Run a full crawl before launch to catch broken links, missing titles, and pages with no H1 while you can still fix them quietly.
- Have redirects ready to deploy at cutover. The redirect map should go live the moment the new site does, not a day later once someone notices the 404s.
- Check robots.txt. Staging sites are usually set to block search engines. Launching with that block still in place is the most common and most preventable SEO gaffe there is. Confirm the live site is crawlable.
- Update and resubmit your XML sitemap so search engines have a clean map of the new structure.
- Verify analytics and Search Console on the new site before launch, so you don’t lose visibility into what happens next.
- Spot-check your top pages right after launch. Pull up your highest-traffic URLs from the inventory and confirm each one resolves, redirects correctly, and kept its title and content.
None of this is complicated. It’s just easy to skip when the launch checklist is already forty items long and everyone wants to go home.
What's normal after launch, and what isn't
Even when everything goes right, give yourself realistic expectations. Rankings often fluctuate for a few weeks while Google recrawls and reindexes the new site, and traffic can dip before it settles. For a clean migration with intact redirects and preserved content, recovery typically lands within a few weeks to a couple of months.
The signs that something needs attention: traffic that shows no recovery after the first six to eight weeks, specific high-value pages that fell out of the index, or crawl errors that keep climbing in Search Console instead of trending down. Catching those early is the difference between a quick fix and a long, expensive recovery.
A redesign is a rare chance to come out faster, cleaner, and more visible than you went in. The teams that get there treat SEO as part of the build rather than a cleanup task. If you’d find it useful to have a second set of eyes on a redirect map or a pre-launch crawl, that’s the kind of work our SEO and analytics team does alongside higher ed teams every year. If you would like to make sure your next redesign thoughtfully retains your search authority, contact our team. We would be happy to support you.
Frequently asked questions about website redesigns and SEO
It can, but the damage is usually preventable. A redesign changes your URLs, content, and code, and mishandling any of the three can cost you rankings. A short ranking dip in the first few weeks after launch is normal as search engines recrawl the new site. Permanent losses tend to come from broken redirects, lost content, or a new CMS that dropped your on-page SEO, all of which you can plan around.
Start before design begins. Inventory every URL and the traffic it earns, build a one-to-one 301 redirect map from old URLs to their new equivalents, preserve the content and on-page signals on your top pages, and confirm the new platform carries over titles, meta descriptions, headings, alt text, canonical tags, and schema. Crawl the staging site before launch, check that robots.txt isn’t blocking the live site, and resubmit your sitemap at cutover.
For a clean migration with intact redirects and preserved content, rankings typically settle within a few weeks to a couple of months. If your most important pages haven’t recovered after roughly six to eight weeks, that’s a signal to investigate redirects, indexing, and crawl errors rather than wait it out.
Yes. The cheapest time to protect and improve your search performance is during the rebuild, when URLs, content, structure, and code are all in motion anyway. Bringing SEO in at the end turns it into damage control. Bringing it in at the start makes it part of the design.
Launching with the staging site’s robots.txt still blocking search engines, which can deindex the entire site, and deploying without a complete, tested redirect map. Both are fully preventable with a pre-launch crawl and a cutover checklist.
