Plan a Dental Website Migration Without Losing Your Strongest Pages
Key takeaway
Before approving a dental website migration, inventory the service, location, resource, form, and other pages that matter, then map every retained old URL to its most relevant new destination. Assign ownership for redirects, assets, testing, and data-flow review, and verify the live site after launch rather than expecting instant unchanged visibility.
A website migration can change URLs, forms, files, analytics, and the routes patients use. The risk is losing service, resource, or location pages that search engines and referrers already know.
The goal is continuity: give each valuable old page a sensible home on the new site, retain the assets needed to run it, and verify the experience after launch. Google notes that significant moves can cause temporary fluctuations while pages are recrawled and reindexed, so a migration should not promise identical visibility on day one.
Define which dental pages must survive
Start with pages that earn organic attention or referral links, support priority services, answer common patient questions, or provide important paths. Provider, treatment, form, and location pages can all be entry points.
Build a baseline before the design changes. Export the sitemap, list public CMS URLs, and review recent analytics and Search Console information. Google’s site-move guidance identifies sitemaps, analytics, Search Console links, the CMS, and server logs as useful sources for finding important URLs. Keep the page title, core copy, files, internal links, and intended visitor action with each record.
That inventory also improves a dental web design project. The practice can name the pages and journeys the new structure must protect instead of asking for “the same site but modern.”
Build a URL map before the new design takes over
For every retained old URL, choose an appropriate new destination. A page-to-page map matters: an old dental-implant page should lead to the corresponding implant page, not automatically to the homepage. A simple spreadsheet with old URL, new URL, redirect type, owner, and test status makes omissions visible before launch.
Use permanent, server-side redirects when a page has moved for good. Google says permanent redirects signal the new canonical target and recommends server-side redirects where possible; its redirect documentation identifies 301 and 308 as permanent moves. Avoid redirect chains, which add delay and make troubleshooting harder.
If a service is no longer offered or content is truly retired, record that decision in the map. It may be more accurate for the old address to return an appropriate not-found or gone response than to send visitors somewhere unrelated.
Stage the rebuild as a complete operating site
A staging site should test the real migration, not only a visual preview. Check planned destinations, titles, headings, internal links, canonical signals, image and PDF links, contact routes, and mobile behavior. The new sitemap should list the new canonical URLs, while normal navigation should link directly to them.
Also inventory forms, patient-portal links, analytics tags, chat tools, scheduling handoffs, and payment links before copying them into a new template. This is not a claim that every anonymous visit is protected health information. HHS explains that the status of tracking data is context dependent; an IP address associated merely with a visit to a page listing providers is not, by itself, enough to make data individually identifiable health information in the situation described in its online-tracking guidance. Authenticated areas and information a user enters need more careful review.
A privacy policy or cookie banner alone does not settle those questions. Have appropriate privacy or compliance advisers evaluate the specific data flow, vendor role, and applicable rules. Make that form and vendor inventory part of the privacy architecture discussion, not a last-minute design task.
Launch in a controlled sequence
Turn redirects on when the new site is ready. Test a representative set of high-value old URLs, including direct visits on a phone. Confirm that each lands on the intended final page and that the browser does not encounter a loop or chain. Remove any development-only noindex instruction before release, and confirm the live robots.txt rules fit the pages the practice wants crawled.
Update internal navigation, campaign landing pages, directory profiles the practice controls, and the XML sitemap to use new URLs. If the domain or subdomain changes, review the relevant Search Console process. Google advises keeping redirects as long as possible, generally at least a year, while it processes the move.
After launch, compare how old and new URLs are reached, watch for unexpected not-found errors, and verify intended measurement before relying on reports. This supports future SEO and AEO work; it does not guarantee unchanged rankings or inquiry volume.
Confirm ownership and privacy-related scope
Before work begins, make the handover scope concrete. The practice should know who controls the domain, DNS, hosting, CMS, source files, content, analytics access, and third-party accounts. Ask the provider to state what will be moved, rebuilt, or retired, and who handles redirects and post-launch testing.
Use this small scope and asset checklist before approving work:
- Current domain, DNS, hosting, CMS, and billing-account access are identified.
- The page inventory, URL map, files, and redirects have named owners.
- Forms, portal links, tags, and vendor handoffs are listed for review.
- Credentials and exported site assets have a documented delivery path.
- The launch test, monitoring period, and final handoff are in the stated scope.
This is an operational checklist, not legal advice or a substitute for contract review. For a specific agreement, ownership question, or privacy obligation, ask a qualified professional to review the terms and the practice’s circumstances. Clear scope makes a redesign easier to manage and the next change less likely to put strong pages at risk.
Sources
Is AI recommending your practice?
A personalized review of your practice’s AI visibility. Report delivery target: 7 days after we receive the required practice information. Free, no strings.