Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Healthcare website redesign for clinics, health platforms and healthtech companies

We plan and redesign websites for clinics and private practices, health platforms and healthtech companies. Each site is organized around the people who read it, whether patients, referring clinicians or partners evaluating a product, so each reader can find the right pages and a clear next step. Your clinicians or medical reviewers have the final word on every claim about care, and pages that already bring in search visits are carried into the new structure, at the same address or behind a redirect.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml plans, designs and rebuilds healthcare websites. Depending on the project, that covers a review of the current site and its search data, audience journeys, a page and URL plan, copy, a design system and page designs, motion, and the WordPress build or a handoff to your developers.

What a healthcare website redesign involves

Each project uses only the parts it needs. A practice may want the whole rebuild, while a design-only engagement ends with journeys, a page map and designs that another team builds. Structure is agreed before any visual design, and no page is styled until its content and its audience are settled.

Solution
Websites
  • Review of the current site and search dataWe list the current pages, the services or products each one covers, and which of them bring in search visits or enquiries, using your analytics and Search Console where they exist. Broken paths, outdated pages and slow templates are noted at the same time, so the redesign starts with a record of what the site does today.
    01
  • Audience journeys and user flowsFor each audience, such as a patient choosing a treatment, a clinician deciding whether to refer, or a partner evaluating a product, we map what they arrive needing, the questions they need answered and the action that should end their visit. The steps they share, and the points where their paths split, shape the navigation.
    02
  • Page map and URL planEvery page gets a job, an audience and an address. Research into how people search for each service, condition or product, including local searches for a practice, shapes which pages exist and what they are called. The plan leaves room for products added later, and every current address is marked to keep, merge or redirect.
    03
  • Copy your clinical reviewers approveService and product pages explain in plain language what each one involves, who it is for and what to expect, using material your team supplies. Every statement about treatment or outcomes goes to your clinicians or medical reviewers before the page is published, and the tone is agreed first so the site sounds like your organization.
    04
  • Design system and page designsKey pages come first, usually the homepage and one service or product page. On a product site, the homepage sets the order in which a visitor meets the problem, how the product works, the evidence and the next step. Remaining templates follow at desktop and phone sizes in Figma, with components in their hover, error and empty states.
    05
  • Motion where it helps the readerMovement is kept to places where it helps, such as presenting the steps of a process in order or confirming that a form was sent. It never suggests how a treatment or technology works beyond what your clinicians have approved, and each interaction is prototyped with its timing and a reduced-motion version.
    06
  • Routes to booking, enquiry or a demoEvery service or product page ends in one next step: your existing booking or scheduling tool, an enquiry form or a demo request. Forms ask only for what the next conversation needs and show each error beside the field it concerns.
    07
  • Build, migration and launchWe build on WordPress with a custom theme your team edits, or hand the Figma file to your developers and review their build against it. Redirects, page titles, structured data, page speed, analytics and Search Console are checked before launch.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need from you

  • Access by invitationEditor access to the current site, with viewer access to analytics and Search Console, each shared by invitation from accounts you own.
    01
  • Your plan and existing contentThe list of services or products, any sitemap, copy, FAQs or positioning work you already have, and the pages you know bring in patients or leads.
    02
  • A clinical reviewerThe clinician or medical reviewer who approves statements about treatment and outcomes, and any legal or compliance reviewer your organization uses. They review copy before design is final and again before launch.
    03
  • What you know about your audiencesResearch, the questions patients or clinicians ask your front desk or sales team, how referrals reach you, and anything else that shows how each audience decides.
    04
  • Brand files and referencesLogo files, colours, fonts and photography, plus a few websites whose look or structure you would like to borrow from.
    05
  • Booking and form detailsThe booking or scheduling tool you use, the forms the site needs and who receives each submission.
    06
  • Your build team, if not oursIf your developers or an agency build the site, their platform, how they name components, and the person who will take the handoff from us.
    07

How a healthcare website redesign runs

  1. [Review]

    We go through the current site, its analytics and search data, and the plan or content you already have, then agree with you what the redesign has to keep.

    Step 01
  2. [Journeys, page map and wireframes]

    Audience journeys, the page map and wireframes for the key pages are agreed next. We walk typical questions from each audience through the proposed navigation, such as a patient looking for a treatment or a clinician looking for referral details, and change any label that leads to the wrong page.

    Step 02
  3. [Copy and clinical review]

    Copy for the key pages is drafted with your team and goes through your clinical reviewer before the designs are final.

    Step 03
  4. [Design]

    Key pages are designed first, then the remaining templates at desktop and phone sizes, with motion prototyped where it is planned. A design-only project ends here, with the Figma file handed to your team.

    Step 04
  5. [Build or build review]

    Our team builds the WordPress theme on a staging copy, or your developers build from the file and we compare their pages with the designs at phone and desktop widths.

    Step 05
  6. [Launch checks]

    Redirects, forms, booking routes, page titles, analytics and Search Console are checked on the live site. When the current site already brings in patients through search, it can go live in stages, each checked before the next.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions

Can you handle medical, regulatory or compliance review?
We plan for that review, but we don't perform it. Norml is a design and engineering studio, not a regulatory consultancy, so what the site says is decided by your clinicians and any legal or compliance reviewers you work with. Their reviews are scheduled into the project, and only approved copy goes live. Questions about HIPAA or other regulations belong with your compliance owner or counsel.
We run a clinic or private practice. Is this only for healthtech companies?
No. A practice site uses the same method with a different reader in mind. Pages follow how patients look for care, with one page per service or condition in plain language.
Our site already brings in patients from search. How do you protect that?
Before any address changes, we list the pages that receive search visits and enquiries. Each one keeps its address where it can; otherwise it is redirected to the new page that covers the same service. Search Console is checked for errors and missing pages after launch. We don't promise rankings.
Can booking stay in the scheduling system we already use?
Yes. The website explains each service and then sends the patient to your existing booking tool, through a link or the tool's own embed where it offers one. We don't rebuild scheduling or payments.
We already have a sitemap and content. Will you start over?
No. We work from what you have prepared, keep what works and suggest changes only where search research or the audience journeys point to a different page or label. You decide on each suggestion before design begins.
We are an agency with a healthcare client. Can you work inside our team?
Yes, on strategy, journeys, information architecture and design. We work in your Figma files and naming, join your internal reviews and hand over in the format your developers expect, while your agency keeps the client relationship.
Our site covers one product and more are coming. Can the structure grow?
Yes. The page map separates what every audience shares, such as the company, the evidence and support, from the pages for each product or solution. Clinicians and patients each get their own route to the products that apply to them, and every new product uses the existing page templates.
Can you design and build the front end, including the motion?
Yes. The same team designs in Figma and builds on WordPress, so the motion approved in the prototype is the motion that ships, checked at phone and desktop sizes. If your developers build on another platform, they receive written motion notes with triggers, timing and the reduced-motion behaviour.
How do you handle accessibility?
Accessibility requirements go into the brief before design starts. Readable text sizes, colour contrast, visible form labels and clear error messages are set in the design system. If you work to a named standard, your reviewers or an accessibility specialist decide whether the site meets it; we don't certify conformance.
Who owns the accounts and files?
You do. The domain, hosting, website, analytics, Search Console and business profile stay in your name, and we work through the access you grant. At handover you receive the design files, plus the theme code for any site we build.
What stays outside this work?
Medical, legal and regulatory advice stays with your clinicians, counsel and compliance owner, and rebuilding booking, payment or patient-record systems is outside this work. Ongoing SEO, content production or advertising after launch is a separate engagement or stays with the providers you already use.

See more of our website work

Each case study covers the starting point, our part of the work and what changed after launch.

See all case studies