Do not scope a healthcare website rebuild by multiplying the old page count by a single migration price. First decide what should happen to each URL, then price the distinct work: template creation, structured migration, substantial rewriting, clinical or legal review, media handling, redirects, and quality assurance. A 500-page site may contain only a few dozen page patterns, while 40 high-risk service pages may require more expert effort than hundreds of simple profiles.
In healthcare website design, the goal is not to keep every old page or to delete aggressively. It is to pay for the version of the site the organization actually needs.
Build an inventory that shows more than URLs
Export all discoverable URLs from the content management system, XML sitemaps, analytics, backlink data, and a crawl. Add pages known to staff but blocked from search, such as campaign landing pages or archived resources.
Give every row these fields:
- current URL and page title;
- page type or template;
- intended audience and task;
- service, location, provider, or topic owner;
- current factual owner;
- traffic and meaningful external-link context;
- last verified date;
- required review type;
- media or downloadable files;
- proposed action;
- proposed destination if redirected;
- unresolved questions.
Traffic is context, not the sole decision. A low-traffic pre-procedure instruction may be operationally important. A high-traffic article may be outdated, misleading, or irrelevant to current services.
Assign one disposition to every page
Use actions that describe actual production work rather than vague labels such as “migrate later.”
Disposition • Use it when • Work that should appear in the estimate
- Keep with light edit | Purpose, facts, and structure remain useful | Copyedit, owner check, migration, link and display QA
- Rewrite | The task remains but the answer is weak or outdated | Research, draft, expert review, edit, migration, QA
- Merge | Several pages answer the same need incompletely | Consolidation plan, new page, redirects, link updates
- Rebuild from data | Many instances share a stable schema | Content model, data cleanup, import, template QA
- Redirect | A useful successor covers the same intent | Destination approval, redirect map, post-launch crawl
- Retire | No current reader or operational need remains | Approval, removal, link cleanup, status handling
- Hold for verification | Facts, obligations, or ownership are unclear | Investigation before scope is finalized
Avoid sending every retired URL to the homepage. Google’s site-move guidance recommends mapping old URLs to relevant new destinations and testing redirects. A redirect is appropriate only when the destination genuinely continues the old page’s purpose.
Count templates and instances separately
A provider profile, location page, service page, article, and campaign landing page may each need a different design and content model. Price the reusable pattern once, then price the work required for its instances.
For example, 80 provider profiles may be generated from consistent fields after the data is cleaned. That work is different from rewriting 12 service pages with unique clinical explanations and approval routes. A useful estimate might separate:
- Discovery and information architecture.
- Design and development for each template.
- Data modelling and import preparation.
- Light-touch migration by instance.
- Substantive editorial work by page.
- Specialist review.
- Redirect implementation.
- Accessibility, device, form, and content QA.
This prevents a vendor from hiding costly writing inside a vague “content migration” line or charging bespoke-page rates for structured records.
Sample the hard pages before fixing the price
Choose a representative slice of the existing site before finalizing scope. Include:
- one simple page from each major template;
- one page with tables, accordions, forms, or downloads;
- one clinically dense service page;
- one page with disputed or missing ownership;
- one multilingual or accessibility-sensitive case, if applicable;
- one page with embedded third-party functionality;
- one merge candidate;
- one retirement and redirect candidate.
Perform the proposed work on those samples. Measure how long fact verification, rewriting, review, migration, and QA actually take. The sample exposes hidden problems such as broken source documents, inconsistent provider data, inaccessible PDFs, duplicate media, or review delays.
Do not extrapolate from the easiest page. Use a range for each effort class and state the assumptions behind it.
Protect clinical and operational truth during consolidation
Two pages that target similar search terms are not necessarily duplicates. They may serve different audiences, describe different pathways, or carry distinct safety information. Before merging, ask the factual owner to identify what must survive.
Create a short preservation note for each merge:
- the reader question the new page must answer;
- unique facts from each source page;
- wording that needs clinical review;
- current contact, access, and location details;
- downloads or instructions that remain required;
- internal links that need a new destination;
- material that is intentionally retired.
This makes consolidation auditable. It also stops a writer from producing a smoother page that silently drops an important condition.
Turn unknowns into priced assumptions
An estimate should not pretend uncertainty has disappeared. Put material assumptions next to the price. Examples include:
- “The practice will provide approved provider data in the agreed spreadsheet.”
- “Thirty service pages require substantive rewriting; the remainder receive light edits.”
- “One review cycle by each named specialist is included.”
- “Translation, formal accessibility conformance assessment, and new photography are separate.”
- “The client will decide archive obligations before the redirect map is approved.”
For each assumption, state what changes if it is false. This is more useful than a large contingency with no explanation.
Google’s technical SEO guidance can inform crawlability, URLs, and search-facing migration checks, but search guidance does not decide which healthcare content is accurate, legally required, or valuable to a patient. Those decisions need the relevant subject owners.
Require concrete migration deliverables
Before signing, make sure the proposal names what you will receive. At minimum, ask for:
- the final inventory with dispositions;
- page and field ownership;
- approved information architecture;
- content models and template list;
- page-level editorial scope;
- review responsibilities and turnaround assumptions;
- redirect map;
- file and media migration plan;
- pre-launch acceptance checks;
- post-launch crawl and defect period;
- a list of excluded work.
“Migrate content” is not a deliverable unless it defines what moves, how it is transformed, who verifies it, and what counts as complete.
Use a small calculation that can be challenged
Build the cost from quantities the team can inspect:
Work unit • Quantity • Effort range • Owner of the assumption
- Unique templates | Count after inventory | Design and build range | Product or web lead
- Structured records | Instances by clean schema | Cleanup and import range | Data owner
- Light edits | Pages with verified facts | Editorial and QA range | Content lead
- Full rewrites | Pages with reader-value gaps | Research, writing, review range | Editorial owner
- Specialist reviews | Pages by risk type | Review cycles and response time | Clinical or legal lead
- Redirects | Approved mappings | Implementation and crawl range | SEO or web lead
When the quantity or assumption changes, the estimate changes visibly. That gives the practice control over scope instead of forcing a choice between recreating everything and accepting an unexplained lump sum.
The final scope should tell you which pages will exist, why they deserve work, which facts must be verified, and how the migration will be tested. If you need help carrying that inventory into design and build, see custom conversion websites.