Healthcare Website Redesign Guide. Planning, IA, Migrations, and QA

A healthcare website redesign is a six-phase project. Most practices that end up with a site they regret rushed or skipped one of those phases. The ones that launch on time, without ranking drops, and with a site the whole practice team is comfortable using started with thorough discovery and planning. This guide walks through each phase in detail so you know what to expect, what to ask your agency, and where the hidden complexity lives.

Phase 1. Discovery and Audit

Analytics Review

Before redesigning anything, you need to understand what the current site does well. Pull 12 months of Google Analytics data and answer these questions: Which pages get the most organic traffic? Which pages have the highest conversion rate (form submissions or phone click events)? Where do users drop off in the funnel from landing page to contact? What devices are your patients using (mobile vs desktop split)?

High-traffic pages with low conversion rates are your biggest redesign opportunity. High-converting pages that already work should be preserved structurally and improved incrementally, not completely overhauled. Low-traffic, low-converting pages may be candidates for consolidation or removal.

Competitor Analysis

Benchmark five competitors across four dimensions: page speed (run their homepage through PageSpeed Insights), design quality (subjective, but score their trust signals and patient journey clarity), content depth (are their service pages comprehensive or thin?), and technical SEO (check their domain authority, backlink count, and schema markup via a free Semrush or Ahrefs overview). Your redesigned site needs to be better than these benchmarks in the areas that drive patient acquisition, not just prettier.

Technical Audit

Run a full technical audit before the redesign, not after. Use Screaming Frog to crawl the current site and identify 404 errors, redirect chains, duplicate title tags, pages with thin content (under 300 words), and pages without schema markup. Run PageSpeed Insights on the top 10 traffic pages and document current scores. Run an accessibility audit with WAVE or axe. Check Google Search Console for existing crawl errors and coverage issues. This baseline tells you exactly what problems the redesign must solve.

Content Audit

Map every page on the current site to one of four decisions: Keep as-is (pages that rank well and convert well), Improve (pages that get traffic but underperform on conversion), Merge (multiple thin pages covering the same topic that should be consolidated), or Delete (pages with no traffic, no links, and no strategic value). The delete-and-redirect decision is particularly important. Do not delete pages that have backlinks pointing to them without implementing a 301 redirect to the most relevant equivalent page.

Stakeholder Interviews

The tension in healthcare website redesigns is that doctors want comprehensive clinical content, patients want to know if you can help them and how to book, and admin staff want the intake form to reduce phone calls. These goals are not incompatible, but they pull in different directions. Interview all three groups early. Doctors: what questions do patients ask before their first visit that the website should answer? Admin: what do callers ask about that is already on the site but they cannot find? Patients (via reviews and front desk feedback): what did they search for and what made them choose this practice?

Phase 2. Information Architecture

Sitemap Planning

The sitemap for a healthcare website follows a consistent pattern: Home, About (practice + individual providers), Services (one page per service or condition treated), Locations (one page per physical location for multi-location practices), Patient Resources (insurance, forms, FAQs, patient portal link), and Blog. The depth of the service section depends on how many distinct conditions or procedures the practice treats and which ones patients actively search for.

For SEO purposes, each service that has meaningful search volume should have its own dedicated page. A spine practice that treats six distinct conditions should have six service pages, not one “conditions treated” page with sections. Search intent is condition-specific. A patient searching “lumbar herniated disc treatment” is not looking for a general spine conditions page.

URL Structure Decisions

Decide your URL structure before you build anything. Common patterns for healthcare: /services/condition-name/ for service pages, /providers/doctor-name/ for provider bios, /locations/city-name/ for location pages. Keep URLs lowercase, hyphenated, and descriptive. Avoid URLs with query parameters, session IDs, or dates (for service pages). If your current site has URLs that rank well, preserve them exactly or implement 301 redirects. Changing a URL that ranks on page one for a competitive healthcare term is a significant risk that needs to be managed carefully.

Navigation Hierarchy

Healthcare websites serve two user journeys that need separate paths: patients finding services and booking appointments, and referring physicians looking for information about the practice’s clinical capabilities and referral process. Main navigation should prioritize the patient journey. Secondary navigation or a dedicated “For Providers” section serves the physician referral path. The appointment booking CTA should be in the header and accessible from every page, not just buried on the contact page.

Phase 3. Design

Wireframes to Mockups

The wireframe phase defines page structure and content hierarchy before visual design begins. For healthcare, wireframes should specify the position of trust signals (provider photos, review widgets, accreditation logos), the appointment booking CTA in relation to primary content, the mobile navigation pattern, and form placement on key conversion pages. Getting wireframe sign-off before visual design prevents expensive revisions later when a client realizes the booking form is not where patients will naturally look for it.

Mobile-First Design Review

Design healthcare websites mobile-first. More than 60% of healthcare searches happen on mobile. The mobile design should be reviewed and approved before desktop layouts are finalized. Key mobile-specific considerations: phone number tap-to-call prominently above the fold, appointment form fields large enough to tap accurately on a phone keyboard, navigation accessible within thumb reach, images that do not reduce to unreadable thumbnails on small screens.

Accessibility Review in Design Stage

Catching accessibility issues in the design phase is far cheaper than fixing them after development. Review color contrast ratios (minimum 4.5:1 for normal text, 3:1 for large text) using a contrast checker before finalizing brand colors. Confirm heading hierarchy in page designs matches semantic meaning (one H1 per page, H2s for main sections, H3s for subsections). Verify all interactive elements (buttons, form fields, navigation links) are large enough for both mouse click and touch interaction (minimum 44x44px touch target).

Phase 4. Development

CMS Setup and Content Migration

For WordPress builds, the development phase starts with a staging environment, not a live server. Install WordPress, apply the theme, configure plugins, and build all page templates before migrating any content. Migrate content page by page rather than using automated import tools that often strip formatting or miss metadata. Each page migration should include: page content, featured image, SEO title and meta description, schema markup, and internal links verified to point to new URL structure.

Form Setup and Testing

Set up all forms in staging and test each one thoroughly: submit a test entry, verify it sends to the correct email address, confirm the auto-reply goes to the submitter, check that conditional fields work (fields that show or hide based on previous answers), and test on both mobile and desktop. For healthcare forms where data handling matters, confirm the form does not store submissions in the WordPress database, or configure encrypted storage if retention is required.

Analytics and Tracking Setup

Configure Google Analytics 4 and Google Tag Manager in staging. Set up conversion events for: appointment form submissions (thank-you page view or form success event), phone number clicks (tracked via GTM click listener), and live chat initiations if you use one. Confirm all events fire correctly in GA4 debug mode before launch. If your practice uses paid search, verify conversion tracking for Google Ads is set up separately from GA4 goals to prevent double-counting.

Schema Markup Implementation

Healthcare websites benefit from several types of structured data. MedicalOrganization or Physician schema on provider pages (name, credentials, specialty, address, phone). LocalBusiness schema on location pages (address, hours, phone, coordinates). MedicalCondition or MedicalProcedure schema on condition and treatment pages. FAQPage schema on pages with FAQ sections. Implement schema in JSON-LD format in the page head or footer. Validate each schema implementation in Google Rich Results Test before launch.

Phase 5. Quality Assurance

Browser and Device Testing

Test on real devices, not just browser emulation. The minimum testing matrix for a healthcare site: iPhone (Safari), Android (Chrome), iPad, desktop Chrome, desktop Firefox, and desktop Edge. Key things to verify on each: navigation opens and closes correctly, forms submit and display confirmation messages, phone numbers are clickable on mobile, images load at the correct size and aspect ratio, and no horizontal scrolling occurs on mobile.

Accessibility Audit

Run WAVE or axe on every page template (homepage, service page, provider bio, location page, contact page). Fix all critical errors (missing alt text, form fields without labels, insufficient color contrast, missing ARIA landmarks) before launch. Resolve as many warnings as possible. For healthcare organizations, WCAG 2.1 AA compliance is the target standard. An accessibility audit should be part of QA on every redesign, not an afterthought.

Speed and Performance Testing

Run PageSpeed Insights on the staging site for all major page templates. Target: mobile score of 85 or higher, desktop score of 95 or higher. If you do not hit these targets on staging, do not launch. Post-launch speed optimization is significantly harder than pre-launch optimization. Common fixes needed at this stage: image compression and next-gen format conversion (WebP), lazy loading for below-the-fold images, removal of render-blocking scripts, and deferring non-critical CSS.

301 Redirect Testing

Test every 301 redirect in the redirect map before launch. Use a redirect checker tool or Screaming Frog to bulk-test all redirects. Confirm each returns a 301 status code (not 302), and that the destination URL is the correct final URL (no redirect chains). Redirect chains add latency and dilute link equity. If your redirect for /old-page returns 301 to /intermediate-page which returns 301 to /new-page, flatten that to a direct 301 from /old-page to /new-page.

Phase 6. Launch and Post-Launch Monitoring

DNS Cutover

The DNS cutover is when your domain points to the new site’s server. Lower your DNS TTL to 300 seconds (5 minutes) 24-48 hours before launch to allow fast propagation. On launch day, update your A record (and CNAME if applicable) to point to the new host. DNS propagation takes anywhere from minutes to 48 hours depending on the registrar and the visitor’s DNS resolver. Have a rollback plan ready: keep your old site accessible on a staging URL for at least 30 days post-launch so you can revert quickly if a critical issue emerges.

Post-Launch Monitoring

The first 30 days post-launch require active monitoring. Check Google Search Console daily for 404 spikes (pages that used to exist that are now missing from the new site or have missing redirects), coverage issues, and any manual action warnings. Monitor rankings for your top 20 search terms weekly. Track conversion rate (appointment form submissions per 1,000 sessions) against your pre-launch baseline. A well-executed redesign typically shows ranking stabilization within 4-6 weeks and conversion rate improvement within the first 30 days.

For more on keeping your site secure and performing after launch, read our healthcare website maintenance guide. For guidance on what SEO elements to build into the redesign, read our healthcare SEO guide.