Imagine someone’s looking for outpatient care on a phone. They reach a behavioral health organization's home page and see a welcoming message, a large photograph, and a “Get help now” button. Can they tell whether outpatient care is offered? At which location? What happens if they press the button? A polished page can still leave those questions unanswered.
Good website design makes the answers findable and lets people act without being pushed toward a choice they are not ready to make. The same site may also serve a family member gathering information and a professional making a referral. Their paths should meet where the information overlaps and separate where their questions differ.
Here is a practical way to plan and test those paths. The example is illustrative; any real site's content and workflow must reflect the provider's services.
Key Takeaways
- Help visitors understand the care offered and where to find it. A welcoming photograph cannot answer those questions on its own.
- Give people seeking care, families, and referrers clear routes to verified program information and an appropriate next step.
- Test essential tasks on real phones and by keyboard. Confirm that forms reach the intended team and phone links reach the right number.
- Preserve useful content and working URLs during a redesign. Judge the result through task completion and inquiry relevance, with an appropriate review of tracking and data sharing.
Begin with the questions people bring to the site
The hypothetical visitor needs to know whether outpatient care is available, whom it serves, where it is offered, and how to ask about access. A family member may first need to understand the program and how to support someone without making a decision for them. A referrer may need the service scope and a referral contact. Put those needs on one page before sketching the navigation.
For every major program, confirm the facts with staff who know the care and admissions process. Then build a page that tells visitors:
- what the program is, in terms a person outside the organization can understand;
- which actual location offers it and whom it is intended to serve;
- what can be explained online and what requires a conversation;
- how to ask about access, including a non-emergency contact route; and
- what the organization will do after an inquiry, if it can describe that process accurately.
Do not promise a treatment result or imply that reading a page establishes clinical fit. A website helps someone decide whether to ask a question; it does not make a clinical assessment. Health Literacy Online recommends actionable content, plain language, meaningful headings, and putting important information first. Those are useful design requirements, not merely writing preferences.
Give different visitors a clear route without multiplying confusion
A person seeking care may start at a program page. A family member may start at a “supporting someone” page. A referrer may enter through a page describing referral steps. Each route can point to the same verified program details and the appropriate contact channel.
Use navigation labels people recognize: “Programs,” “Locations,” “How to Get Started,” or other terms that accurately reflect the site. Internal department names can appear where needed, with a short explanation. Avoid making a visitor choose among vague labels before learning what the programs are.
On the hypothetical outpatient page, the primary action might be “Ask about outpatient care” if that accurately describes the destination. A secondary action could be “See program details.” A referrer might need “Referral information.” The contact choices do not have to be equally prominent, but each should lead where its label promises. If a phone number reaches a general line rather than an admissions specialist, say so.
Explain when an online form is monitored and how a response normally works, if the organization has an approved, accurate statement. Do not present a form as an emergency route unless there is a real process to support that use. Emergency language should be written and approved for the provider's circumstances.
Test the task on a real phone and with a keyboard
Design approval cannot stop at a desktop mockup. Ask someone unfamiliar with the site to complete a task: find the outpatient program, confirm the location, find how to inquire, and identify what happens next. Watch where they hesitate. Repeat with a family-member task and a referral task.
Then check the basics across screen sizes and input methods. Can someone reach every menu item, link, and form field by keyboard? Do fields have clear labels and explain required information? Are error messages understandable? Do headings make sense when read out of visual context? Is important text readable at phone width without awkward horizontal scrolling? W3C's preliminary checks offer a practical starting list for headings, keyboard use, labels and other barriers. A preliminary check is useful but does not certify compliance with an accessibility standard or law.
Try the contact action end to end in a test environment, including the confirmation message and the team's actual receipt of the inquiry. The page should not announce success merely because a button was pressed. If someone uses a phone link, check that it reaches the intended number. Repeat after changes to navigation, forms or content.
Make trust visible through accurate details
Trust is built by what a site helps someone verify. Program descriptions, location information, staff or organizational details, privacy information, and contact instructions should agree with one another. A page that says “call our admissions team” while the number reaches an unrelated office creates a real problem, even if every component is attractive.
Clinical and operational reviewers should approve descriptions of services, eligibility, access steps, and any statement that could influence a care decision. Give each important page an owner and a review date. A useful publication workflow records what changed and who confirmed it. This reduces the chance that an outdated claim remains live until the next redesign.
Photography and illustration can support a calm, legible experience. They should not imply that a pictured person is a patient, staff member, or documented outcome if that is untrue. Alt text should describe informative images; decorative images can be treated as decorative. A hero image alone cannot communicate which care a provider offers, so the heading and nearby copy must do that work.
Decide what you need to measure before adding tracking
The organization may want to know whether visitors find program details and complete contact actions. Define those questions first. A count of page views or button taps is not the same as a qualified inquiry; a qualified inquiry is not an admission. Set baseline measures that the team can interpret, then compare them after changes while accounting for campaigns, seasonality, service changes, and capacity.
For the hypothetical outpatient page, a sensible review might ask: Did relevant visitors reach the page? Did they find the location and access details? Did the form or call path work? How many inquiries concerned the actual program? If contact actions rise but relevant inquiries do not, investigate the page promise and the admissions process before claiming the redesign succeeded.
Healthcare tracking needs an explicit data-flow review. What information do forms, analytics scripts, call systems, and ad platforms receive? Who can see it, and how long is it kept? HHS's guidance on online tracking makes clear that the analysis depends on the entity, page, and information involved; it also notes a 2024 court decision affecting a narrow public-page scenario. Have appropriate privacy and legal reviewers assess the actual setup. A “privacy-safe” label on a vendor pitch is not evidence about this website.
Plan the redesign as a series of verifiable changes
Before rebuilding pages, inventory the current URLs, main visitor tasks, program facts, contact methods, and baseline measures. Mark what is already useful. A redesign should preserve working explanations and links while repairing gaps. Use a short priority list based on task importance and evidence; do not rebuild a low-impact page merely because it looks dated while a major program path remains confusing.
An example launch record could include:
| Decision | Owner and evidence to record |
|---|---|
| Program facts are current | Clinical and operations reviewers approve the page's service, location, and access details. |
| Essential tasks work | Design and development test the program, family, and referral paths on a small phone, larger phone, and desktop, including keyboard use. |
| Contact routes work | Operations confirms calls, forms, confirmation messages, and response handoff. |
| Existing URLs remain usable | Development maps changed URLs to direct permanent redirects and updates internal links, canonicals, and the sitemap. |
| Measurement is appropriate | Marketing and privacy reviewers document the events, data flows, and limits of interpretation. |
After launch, rerun the same tasks. Compare observations with the baseline and note what else changed. If visitors still cannot find the outpatient program, the navigation needs another pass. If the path works but inquiry quality is low, review whether the page accurately represents the care and whether the admissions team is categorizing inquiries consistently. A launch is a checkpoint, not proof of an outcome.
Morpheus Consulting Inc. works on website design alongside search, content, and measurement for organizations making complex decisions. If your team is planning a redesign, contact Morpheus Consulting with one task your current site makes difficult. That gives the first discussion something concrete to examine.
Questions about behavioral health website design
What should a behavioral health program page include?
It should accurately explain the program, where it is offered, whom it is intended to serve, what a visitor can learn online and how to ask about access. Use plain language, and have clinical and operations staff verify details that affect care decisions.
How should a site serve patients, families, and referrers?
Give each audience a clear entry point and the information it needs, while sharing one verified source for core program facts. Patients may need care and access details; families may need guidance; referrers may need service scope and referral steps. Link routes where the questions overlap.
Can a website determine whether a visitor is a fit for a program?
No. It can explain what a provider offers and how to ask about access. It should avoid presenting its copy or a simple form as a clinical assessment or promising a treatment result.
What accessibility checks matter before launch?
Test key tasks on different screen sizes and by keyboard. Check heading structure, link labels, form labels, error messages, contrast, and the ability to complete contact tasks. Use W3C guidance as a starting point, then complete the level of accessibility and legal review appropriate to the organization.
How can we tell whether a redesign helped?
Record a baseline for essential tasks, working contact routes, and inquiry quality. Rerun those tasks after launch, compare relevant measures, and account for campaign and operational changes. More visits or button clicks alone do not prove that a site is serving people better.
What happens to existing pages and URLs during a redesign?
Inventory them before changing the site. Preserve useful content, and map changed URLs to appropriate replacement pages with direct permanent redirects. Update internal links, canonicals, and the sitemap, then test the routes after launch.
How often should the website be redesigned?
There is no universal interval. Review program facts and essential tasks regularly. Small improvements may solve a problem without a full rebuild; a larger redesign may be warranted when structure, technology, or content repeatedly prevents visitors from finding accurate information and completing the right task.




