Move an old healthcare page only when it still serves a necessary reader task and has a clear role on the new site. Classify every URL as preserve, improve, merge, retire, or rebuild, then record the destination and redirect decision before development begins.
The safest migration is not the one that copies the most pages. It is the one that preserves useful answers and established routes while removing duplication, correcting weak material, and making every change traceable. Design should begin after the page inventory has owners and decisions, not before.
Build the inventory from more than the navigation
The visible menu rarely represents the whole site. Old campaign pages, provider biographies, PDFs, hidden location pages, news posts, and outdated form routes may still receive visits or links. Start with a combined crawl and data inventory rather than a hand-built list from the header.
Google's site-move guidance recommends building an inventory of old URLs from sources such as sitemaps, analytics, server logs, the content management system, and link data. It then calls for mapping old URLs to appropriate new destinations, updating internal links, testing redirects, and monitoring the move. That process does not decide whether an old healthcare page is accurate, useful, or safe to preserve.
Add fields for status code, canonical URL, page title, content owner, last meaningful review, internal links, incoming links, traffic evidence, and the reader task. The inventory becomes a decision tool only when technical and editorial facts sit on the same row.
What reader job does the page still perform?
A page earns a place on the new site by resolving a distinct question or action. Ask what the visitor expects from the URL, whether another page already handles that task better, and what would be lost if the page disappeared.
A low-traffic page may still be essential if it explains a niche referral pathway or a location-specific service. A high-traffic page may still need a complete rewrite if it attracts the wrong intent or contains stale information. Preserve purpose before preserving wording.
Treat search data as evidence rather than a verdict
Search data helps identify pages that are discoverable and the language searchers use. It does not establish that the content is complete, clinically current, or conversion-ready.
Search Console can group Google Search performance by page and query, helping a team see which URLs receive impressions or clicks and which queries surface them. Google also cautions that timing alone does not prove a page change caused a performance change. Search data is therefore one input to the migration decision, not an automatic preserve or delete command.
Pair search evidence with onsite usage, enquiries where measurement is valid, content review, stakeholder knowledge, and a manual reading of the page. Note missing or limited data rather than converting absence into a claim that the page has no value.
Apply the Page Migration Decision Matrix
The Page Migration Decision Matrix assigns one disposition after evaluating five dimensions: reader purpose, unique information, current evidence, accuracy risk, and future ownership. Each dimension needs a short note, not merely a score.
Use these dispositions consistently:
- Preserve when the page has a clear role, dependable content, stable ownership, and no stronger replacement.
- Improve when the role and URL remain useful but the answer, hierarchy, or next step needs work.
- Merge when several pages split one task and a stronger combined destination can serve it without losing necessary distinctions.
- Retire when the page has no current purpose or replacement and should return an honest not-found or gone response.
- Rebuild when the reader task remains necessary but the old page cannot safely supply the new answer.
The matrix should include the person approving the disposition and the evidence date. A decision without an owner is only a suggestion.
Merge only when one destination truly replaces the others
Merging is useful when pages repeat the same decision and can become one clearer resource. It is harmful when a convenient category page replaces distinct provider, service, or location answers.
Write the proposed destination beside every source URL. Then ask whether a visitor arriving through the old route will recognize the new page as the answer they expected. If the destination is merely the homepage or a broad service index, the mapping is probably too weak.
Keep accuracy review separate from copy transfer
Moving text into a new template does not make it current. Flag clinical statements, insurance language, preparation instructions, availability claims, credentials, policy descriptions, and time-sensitive operational details for the appropriate review.
The migration sheet should show the reviewer role, what must be checked, and whether the page can launch without completion. Never infer clinical or legal approval because content existed on the old site. Old publication is not proof of current accuracy.
Decide the URL before rebuilding the page
Preserve a useful URL when its role remains stable and change is unnecessary. If the route must change, document the exact new destination and redirect before implementation. This lets development, content, analytics, and quality assurance work from the same map.
Update links in navigation, body copy, sitemaps, structured references, campaigns, profiles, and reusable components. A redirect protects an old route, but internal links should point directly to the final destination so visitors do not take an avoidable detour.
Create an acceptance test for every disposition
Every row needs a test that proves the decision reached production. Preserved and improved pages should return the intended content and metadata. Merged pages should route to the approved equivalent. Retired pages should not send visitors to an irrelevant destination. Rebuilt pages should answer the recorded task.
Sample both desktop and mobile journeys. Check contextual links, calls, forms, scheduling handoffs, canonical references, indexability, and page ownership. Record failures against the inventory row so repairs do not become disconnected tickets.
Hand the content map to design before wireframes
The inventory determines what page types the new system must support, which relationships matter, and which facts need controlled reuse. It prevents a visual sitemap from becoming the source of truth for content decisions.
When the matrix is complete, the team can estimate templates, migrations, rewrites, reviews, and redirects honestly. A healthcare content marketing team can also see which answers require preservation instead of treating every old page as interchangeable. Conversion website planning becomes more reliable when the old site has been classified before the new interface is designed.