Executive Summary

A Midwestern health network needed to consolidate roughly two dozen hospital and partner websites into one authoritative domain without sacrificing organic visibility, patient access, or local search performance. The migration required careful SEO planning, detailed URL mapping, and close coordination across technical, marketing, and operational teams.

By implementing a structured 301 redirect strategy and preserving the strongest signals from legacy domains, the network was able to transfer authority into the main website. Although organic traffic dipped temporarily after launch, it rebounded as search engines processed the redirects and began recognizing the consolidated domain structure.

The result was a stronger, simpler web presence: improved domain authority, better local search visibility, more high-intent organic traffic, and lower operational complexity through one domain and one CMS.

How We Facilitated a Site Migration for a Health Network Using Best Practices for SEO

When I worked with a digital marketing agency, I provided SEO guidance for a Midwestern health network as it consolidated a large, fragmented web presence into a single domain. The organization had been online for decades and had launched its first website at a time when many health systems still relied on printed pamphlets and radio advertising.

Please note: In this case study, I’m hiding the identity of the client by referring to them with the pseudonym “MidwestHospitalClient.com” and sub-sites as "HospitalX.com". However, all other details are from direct experience of many site migrations in my SEO career.

Over time, the network partnered with many regional hospitals, each with its own website, platform, and governance model. By the time my agency began working with the client, the organization owned roughly two dozen separate sites. The goal was to consolidate that authority into one primary domain, but the legacy sites had not been designed with a future migration in mind.

The migration required coordination across multiple organizations, development teams, marketing groups, and operational leaders. Everyone needed to agree on the redirect strategy, content mapping, implementation timeline, and success metrics.

The Value of a Multi-Site Migration

A successful migration would bring the subsidiary hospital and health-network sites into one authoritative destination. Instead of spreading link equity, content, and search visibility across many disconnected domains, the network could concentrate those signals within a single site. 

The Cost and Risk of Getting It Wrong

Before the migration could happen, every page on every subsidiary site needed to be accounted for and assigned a new destination. For example, HospitalX.com served patients in western Pennsylvania and eastern Ohio. After the migration, the content from HospitalX.com would live in a subfolder on the primary domain: MidwestHospitalClient.com/HospitalX. Visitors who typed HospitalX.com would automatically be redirected to the new location.

Search engines also needed clear signals about where each page had moved. If the redirects were incomplete or inconsistent, the network risked losing organic visibility, frustrating patients, and sending users to competitors when they could not find the information they needed.

The scale made the risk significant. HospitalX.com alone had thousands of pages covering physicians, services, press releases, departments, and patient resources. Years of third-party links had helped Google understand the hospital’s authority, location, and relevance. Preserving that trust required precise page-to-page mapping.

The SEO Redirect Strategy

For each legacy site, we mapped every important URL to the most relevant page on MidwestHospitalClient.com and implemented permanent 301 redirects. 301 redirects are the clearest way to tell search engines that content has moved permanently and that ranking signals should transfer to the new destination.

Not every legacy page had a one-to-one replacement. In some cases, departments had been renamed, consolidated, or folded into broader service lines. When that happened, we redirected the old pages to the closest relevant destination, such as a higher-level service landing page, rather than allowing users or search engines to encounter a broken page.

We also had to account for existing redirect chains. For example, an outdated biography page for a physician in HospitalX.com might have an existing redirect to a newer profile page in another location on HospitalX.com. During the migration, those redirect chains needed to be flattened so each old URL pointed directly to its final destination on MidwestHospitalClient.com. This helped preserve crawl efficiency and reduced the risk of search engines dropping signals across multiple redirect hops.

Now, imagine that same process had to be repeated across roughly two dozen websites, and you’ll have an idea of how complex this operation was. This made governance, QA, and cross-team coordination just as important as the technical redirect work.

Site Migration Goals

The migration had two primary goals:

1. Protect the user experience by making sure visitors looking for information on legacy sites could still reach the right content quickly and reliably.
2. Preserve and consolidate link authority from partner domains so the central MidwestHospitalClient.com site could gain search visibility, reduce internal competition, and lower the cost of maintaining separate web properties.

How Organic Traffic Changed After the Migration

At First: A Temporary Dip in Traffic and Rankings

After launch, combined organic traffic dipped for about 60 days. This was expected, and we had prepared the client for it in advance. Search engines do not process hundreds of thousands of 301 redirects instantly; they crawl sections of the web over time, recalculate authority in stages, and rankings will fluctuate during this time as search engines compare the new pages against competing results.

During this phase, we needed to make sure search engines discovered all of the redirects. To do this, we kept the old XML sitemaps on the old partner sites available for several months after the site migration. This way, Google could continue crawling legacy URLs and find their new 301 destinations. We used Google Search Console to monitor the progress of the migration. We saw clicks and impressions decline in the first sixty days for the old domains as Google confirmed the new locations and transferred visibility to MidwestHospitalClient.com. When clicks and impressions reached zero on Google Search Console for the old sites, we could be certain that the indexation process had completed.

Then: Organic Traffic Rebounded and Grew

After the initial dip, organic traffic rebounded and then climbed steadily. Consolidating the two dozen or so individual domains such as HospitalX.com and HospitalY.com into a single MidwestHospitalClient.com domain created the visibility lift we had planned for.

Once Google crawled and indexed the redirects, the new domain began to benefit from the combined authority of the partner sites. Because we had a complete map of all URL redirects in place, link equity flowed to the right destination pages, and the new pages on MidwestHospitalClient.com began ranking quickly.

The migration also strengthened local search performance. Instead of competing with one another, the regional hospital sites now supported a shared domain structure. Their new subfolders inherited the broader authority of MidwestHospitalClient.com, which helped the network attract more high-intent organic traffic from people searching for local doctors, treatments, and appointment scheduling.

Operationally, the consolidation reduced the cost and complexity of managing the organization’s web presence. With all sites housed under one domain and managed through a single CMS, the team could update pages more efficiently and coordinate marketing activity across the network.

Summary of Site Migration Results for the Health Network Website

Key outcomes from the site migration and consolidation of my client’s site included:

• Improved domain authority through the consolidation of legacy site equity.
• Stronger local search visibility for regional hospitals and service lines.
• More high-intent organic traffic from users searching for doctors, treatments, and appointments.
• Lower overhead and simpler web governance through one domain and one CMS.