Start with the visit, then pick the look
A mobile IV client is deciding whether to let a stranger with a needle into their home or hotel room. Before anyone opens a design tool, write down one plain answer to each question that person has:
- Do you come to my town, and is there a travel fee or a minimum?
- What will this visit cost me, all in?
- Who is coming to the door, and what are their credentials?
- How soon can you come, and can I book it right now?
Those answers are your design brief. Hand them to your designer and judge every draft by how fast a stranger can find them on a phone. Colors and fonts matter, and they come after this. The mobile IV website checklist covers what belongs on the site. This guide covers how to arrange it around booking.
Lay out the first phone screen
Review the phone version first. Google says "Google uses the mobile version of a site's content" for indexing and ranking, so that version counts first. Before any scrolling, the first phone screen should show:
- A headline with the service and the place, such as the sample below.
- A line on how soon you can come, only if you can staff it. Same day is a promise once it is on the page.
- A large book button, with text and call beside it. Keep this bar fixed to the bottom of the screen as people scroll.
- A real photo of your nurse or your setup, sized small enough to load quickly.
Leave off the coupon pop-up. Google's page experience questions include "Do your pages avoid using intrusive interstitials?" A pop-up also sits right on top of the book button you just placed. Offer the discount in a line on the page instead.
Design the booking path around the home visit
A home visit has steps a lounge visit does not, so set up booking in this order. Ask your booking company whether it can check a town or ZIP first and add a travel fee. If it cannot, put your towns and fees right above the book button.
- Town or ZIP first. Tell people right away if you serve them and what the travel fee or minimum is. If they are outside your area, offer a text link so you can still say yes or no by text.
- Pick the drip, with the price shown. Add the travel fee so the total is clear before the calendar.
- Date and time, showing only slots your nurses can really reach.
- Address and access notes: gate code, hotel room number, where to park.
- Group option if you do them: how many people, and any group minimum.
- Deposit and cancellation terms, stated before the payment screen.
- A confirmation that says who is coming, when, and the number to text.
Test it this week. Hand your phone to someone who has never seen the site and ask them to book a visit to their own address. Stay quiet and watch. Each spot where they stop or ask you a question is a design fix, and it costs less to find it now than after you pay for ad clicks.
Drip pages and town pages
Use one layout for every drip page: what is in it, the price in real text, who it is for, how a visit works, and a book button at the top and bottom. Have your medical director approve any wording about what a drip may help with, and hold icons and badges to the same test. An immune badge beside a drip name makes the same promise a sentence would, and the FTC expects competent and reliable scientific evidence behind health claims.
Town pages need more care, because a design template makes them easy to copy. Google's spam policies list "Having multiple domain names or pages targeted at specific regions or cities that funnel users to one page" as an example of doorway abuse. Give each town page something true to that town: the travel fee, how soon you usually reach it, the hotels or neighborhoods you go to, and a question people there ask. If you have nothing different to say about a town, name it on your main service area page and skip its own page.
If you run the business from home, your footer can show your service area, phone and hours without a street address. Google tells businesses that do not serve customers at their address to remove it from their Business Profile, so the site and the profile should match.
Forms, tracking and health details
A pretty form can create a privacy problem, so give your designer these rules up front:
- Keep the general contact form to name, phone, town and what they are asking about.
- Leave health history and medication questions to the intake inside your booking or charting system.
- Check that the confirmation page address does not carry a name, phone number or drip choice in it. Google does not allow personal details like email addresses or personal mobile numbers to be sent to Analytics.
- List every tracking tool on the site, then read your privacy policy against that list.
That last check matters. If a hidden tracking tool shares sensitive health data in a way your privacy policy says it will not, the FTC calls that a violation of the FTC Act. Ask your booking company what its widget sends to ad platforms, and ask a health care attorney whether HIPAA applies to you and what your policy has to say. You still want to count booking taps. The conversion tracking guide shows how to set those up.
Speed and accessibility numbers for your designer
You do not need to know how these are measured. Send this list to your designer and ask for the results before launch:
- Main content appears within 2.5 seconds (Google calls this LCP).
- The page responds to a tap in less than 200 milliseconds (INP).
- The layout stays still as it loads, with a score under 0.1 (CLS). This catches a book button that moves as someone taps it.
- Normal text has a contrast ratio of at least 4.5:1. Pale wellness colors can miss this, so test your palette before you fall for it.
- Every button is at least 24 by 24 CSS pixels, and the main book button is far larger.
Run your homepage, IV menu and one drip page through PageSpeed Insights, which is free. If a page is slow, look first at background video and large photos. Then try booking with only the Tab and Enter keys, since the Department of Justice lists mouse-only navigation as a website accessibility barrier. Our free website checklist scores the rest in about two minutes.
What to ask a designer before you sign
- Can I see the phone version of two live IV or health sites you built, and try booking on them?
- Does your build work with my booking software, and where will the booking step live?
- Who owns the domain, the content and the code when we are done?
- Will each book, call and text button be tracked before launch?
- Who connects Search Console and my Google Business Profile?
- If I already have a site, will you redirect each old page to its new address? Google recommends permanent redirects for a move like this.
- How many revision rounds do I get, and what happens after launch when I change a price?
Here is how we answer two of them. You own your domain and your content, and the code once it is paid for, and you get two full revision rounds before launch. Run the same booking test on the live sites on our work page, and see what each package includes on our websites page. If you are starting ads before a full site, read landing page or homepage first.
The short version
- Write down the answers a client needs, then judge each design by how fast they can be found on a phone.
- Show the service, the place and a book button on the first screen, and skip the pop-up.
- Ask for the town or ZIP first in booking, and show the travel fee before the calendar.
- Give each town page something true to that town, or leave it on the service area page.
- Keep health questions out of general forms, and check your tracking tools against your privacy policy.
- Put speed and contrast targets in writing, then watch a stranger book on your phone.
Sources
- Google Search Central: Mobile site and mobile-first indexing best practices
- Google Search Central: Understanding page experience
- Google Search Central: Core Web Vitals
- Google Search Central: Spam policies
- Google Business Profile Help: Manage your service areas
- FTC: Health Products Compliance Guidance
- Google Analytics Help: Best practices to avoid sending personally identifiable information
- FTC: Collecting, using, or sharing consumer health information
- W3C: Understanding contrast (minimum)
- W3C: Understanding target size (minimum)
- U.S. Department of Justice: Guidance on web accessibility and the ADA
- Google Search Central: Site moves with URL changes