A URL is a page's address, a redirect is a server instruction that sends an old address to a replacement, and an internal link is the route a visitor follows within the site. Keep stable URLs when possible and map every necessary change to a relevant final page.
These three elements are often discussed as technical SEO details. In practice, they shape whether a person arriving from search, a saved bookmark, a directory, an email, or another page reaches the answer they expected. The migration plan should protect that expectation before launch.
Why keep an existing URL?
Keep an existing URL when the page's purpose remains valid, the address is serviceable, and changing it offers no clear benefit. A new visual system does not require new paths. Stable routes reduce the number of redirects, link updates, analytics changes, and external references the team must manage.
Document the current page role and intended reader. If both remain stable, improve the page at the same address. If the role changes materially, decide whether the old route has a true replacement or should end with an honest not-found response.
A useful URL is understandable but not disposable
Readable paths help humans and systems interpret a site's structure. They should reflect durable concepts rather than campaign slogans, internal department names, or temporary design labels.
Google recommends simple, logical URLs that use readable words and notes that URL paths are case sensitive. That guidance supports understandable addresses, but it does not justify renaming every existing page during a redesign. A familiar, useful route can be better than a cosmetically cleaner path that creates avoidable migration risk.
Choose lowercase, consistent patterns for new routes. Keep identifiers stable enough that a future navigation change does not require another migration.
What does a redirect actually do?
A redirect tells the server to send a request for one URL to another URL. It does not merge content, repair a weak page, or prove that the destination satisfies the visitor's original intent.
Google recommends a permanent server-side redirect when a page has permanently moved and identifies HTTP 301 and 308 as permanent redirect status codes. A temporary redirect serves a different purpose because it signals a temporary destination. Neither type chooses the correct healthcare content destination for the team.
Use a permanent redirect only after the replacement is approved. Use a temporary redirect for a genuinely temporary condition, such as a short-lived service interruption, with a page that explains what the visitor can do next.
Match old pages to equivalent destinations
Create a row for every changing URL. Place the old page purpose beside the proposed new page purpose, then ask whether the new page answers the same core question with equal or better specificity.
Classify every row before approving the route:
- Keep the address when the page purpose remains stable and the route is serviceable.
- Redirect it when a genuinely equivalent final destination replaces the old page.
- Return an honest missing-page state when no relevant replacement exists.
- Investigate further when the team cannot yet explain the visitor expectation or destination.
A discontinued provider page should not automatically go to a generic provider directory. A retired location page should not automatically go to the homepage. The correct decision may be a relevant replacement, a useful explanation, or a real not-found state. Convenience is not equivalence.
Build the Address Destination Reason Test Map
The Address Destination Reason Test Map is a four-part migration record. Address is the old route. Destination is the final approved route or the chosen no-replacement state. Reason explains the editorial and operational decision. Test proves the behavior in production.
Add supporting columns for owner, page purpose, redirect type, internal-link sources, canonical reference, sitemap status, and last verification. The four core fields keep the record understandable to practice leaders while the additional fields make it executable for the delivery team.
Reject any row with a vague destination such as “closest page.” The map should name the exact URL and why a visitor arriving through the old address will recognize it as relevant.
Internal links should skip the detour
After a URL changes, update links in navigation, body copy, related-content modules, provider and location relationships, footer groups, campaigns, emails, profiles, and reusable components. Do not leave the old address in place just because the redirect works.
Google recommends crawlable anchor links with href attributes and descriptive, reasonably concise anchor text. It also advises linking important pages from at least one other page. A redirect can rescue an old route, but direct internal links still give visitors and crawlers the clearest current path.
Anchor text should explain the destination in the current sentence. Avoid generic labels when the reader needs to distinguish a service, provider, location, method, or policy.
A canonical reference is not a substitute for a redirect
A canonical reference indicates which URL a site prefers for substantially duplicate or similar content. It does not send the visitor from an old address to a new one. A redirect changes the request path; a canonical reference stays in the page markup.
During migration, confirm that final pages use the intended self-reference and that internal links and sitemaps agree with it. Conflicting signals make troubleshooting harder even when each element looks valid by itself.
Avoid redirect chains and loops
A chain occurs when an old URL sends the visitor to an intermediate URL before reaching the final page. A loop sends the request back to a URL already visited. Both conditions create avoidable delay and failure risk.
Point each old address directly to the final approved destination. When a later migration occurs, update earlier redirects as well as current links. Test with an automated route list, then manually inspect a representative sample of services, providers, locations, articles, and forms.
How should deleted content behave?
If no relevant replacement exists, an honest missing-page response can be better than an irrelevant redirect. The page should explain that the resource is unavailable, provide useful navigation, and avoid suggesting that a discontinued service or provider is still offered.
Separate the server response from the human recovery experience. A correct status without useful navigation frustrates people. A friendly page that returns the wrong technical status can confuse monitoring and indexing.
Test the complete visitor path
Migration acceptance should begin outside the new website. Test old search-result links where available, saved URLs, campaign links, directory profiles, and known referrals. Confirm the final content, navigation, phone link, form, scheduling handoff, and recovery state.
Store the map after launch and assign an owner for later changes. A healthcare content marketing owner should review whether each destination preserves the intended answer, while a technical owner verifies the route behavior. Teams planning healthcare website design and migration should treat the address map as a controlled product artifact, not a launch-day spreadsheet that disappears.