Mobile SEO for a healthcare site means making the phone version of your website the complete version, because that is the one Google reads. Google began moving sites to mobile-first indexing in 2018, made it the default for new websites in 2019, and declared the switch complete in October 2023. Anything missing from your mobile pages is effectively missing from Google.
The rest of mobile SEO is about what patients do on a phone: tap to call, book an appointment, find directions and read your hours. And for any practice that takes Medicare, Medicaid or other federal funding, a 2024 HHS rule sets a specific accessibility standard for websites and apps, with compliance dates now in 2027 and 2028.
Mobile-first indexing: what it means for a medical site
Mobile-first indexing means Googlebot crawls and indexes your site as a smartphone user. Google's milestones, from its Search Central blog:
| Year | Milestone |
|---|---|
| 2016 | Mobile-first indexing experiments announced |
| 2018 | Rollout began |
| 2019 | Default for new websites |
| 2020 | Announced for the whole web |
| October 2023 | Declared complete |
So the often-repeated line that Google has used mobile-first indexing "since 2019" is accurate for new sites; older sites moved in batches until 2023.
Google's mobile-first indexing best practices come down to parity:
- Same content. "Only the content shown on the mobile site is used for indexing." Accordions and tabs are fine for fitting content on a small screen. Removing the conditions list, insurance section or provider bios from the mobile layout removes them from Google.
- Same structured data and metadata. Titles, meta descriptions and schema should match on mobile and desktop.
- No content that loads only on interaction. Google will not swipe, click or type to reveal primary content.
- Same images and alt text. Use stable image URLs and the same alt text as desktop.
- Same robots rules. Do not block CSS, JavaScript or images that Google needs to render the page.
Most practices now run a responsive site (one URL, one HTML, layout adapts to screen size), which handles parity by default. The risks come from page builders that let editors hide sections "on mobile," and from separate mobile plugins on older WordPress sites.
How to check your mobile pages
Google retired the Mobile-Friendly Test, its API and the Mobile Usability report on December 1, 2023, and pointed site owners to Lighthouse (Google Search Central). Today:
- Run PageSpeed Insights on the mobile tab for your homepage, top service page, one location page and the booking page.
- In Google Search Console, use URL Inspection and "View crawled page" to see the HTML Google fetched as a smartphone.
- Open each template on a real phone on a mobile connection. Try to call, book and get directions using only your thumb.
Speed is half of mobile SEO; our medical website speed guide covers Core Web Vitals in detail.
Patients search and act on their phones
Pew Research Center's 2025 survey found 91% of US adults own a smartphone, and 16% are smartphone-dependent, meaning they have no home broadband (Pew Research Center). For that group, your mobile site is your only site.
Health searches are often urgent and local: "urgent care near me," "dentist open Saturday," "pediatrician accepting new patients Denver." The searcher wants an answer and an action within a minute. Our mobile search statistics page collects the broader data with sources.
Click to call, booking and directions on mobile
The page has one job on a phone: turn a visit into a call, a booking or a trip.
Click to call
- Mark up every phone number as a
tel:link so it opens the dialler. - Put the number in the header, visible without scrolling, on every page.
- Show today's hours next to it, so the patient knows whether someone will answer.
- If you have separate lines (new patients, billing, pharmacy refills), label each one.
- Use the same number as your Google Business Profile, which also shows a Call button in Maps. See Google Maps for healthcare.
Booking on mobile
- A sticky "Book appointment" button at the bottom of the screen works well on phones. Keep it short enough that it does not cover content.
- Test the booking flow on a phone. Many practice management widgets open in a small iframe that is hard to use on mobile; if yours does, open it full screen or link to the vendor's hosted page.
- Keep forms short. Ask for name, phone, email, preferred time and reason for visit at most. Clinical detail belongs in the patient portal or a HIPAA-enabled intake form.
- Use the right input types (
tel,email,date) so phones show the right keyboard.
Directions and location
- Link the address to your Google Maps listing.
- Include parking, entrance and accessibility notes on each location page ("Entrance on 5th Street, step-free access, free parking behind the building").
- For multi-location practices, a location finder that uses the phone's location helps. Each location still needs its own crawlable page.
Mobile layout and usability checklist
| Check | Target | Why |
|---|---|---|
| Text size | Body text readable without zooming | Patients include older adults and people with low vision |
| Tap targets | Buttons and links large and spaced apart; WCAG 2.1 lists 44 by 44 CSS px as its AAA target | Prevents mis-taps on phone numbers and menus |
| Reflow | No horizontal scrolling at 320 CSS px wide (WCAG 2.1 SC 1.4.10, Level AA) | Required for AA; also stops content being cut off |
| Pop-ups | No full-screen interstitials covering content on arrival | Google's page experience guidance asks "Do your pages avoid using intrusive interstitials?" |
| Menu | Services, locations, insurance, book and call reachable in 2 taps | Patients scan for the same few things |
| Images | Sized for mobile, compressed, with alt text | Speed and accessibility |
| Forms | Labelled fields, right keyboard type, clear errors | Accessibility and completion rate |
Accessibility: WCAG, the ADA and the HHS Section 504 rule
Accessibility is now a legal requirement for many healthcare organisations, and it overlaps almost entirely with good mobile design. What follows summarises the rules; it is not legal advice, so check your obligations with counsel.
The HHS Section 504 rule (2024)
In May 2024, HHS published a final rule under Section 504 of the Rehabilitation Act that requires recipients of HHS financial assistance (which includes most hospitals and many practices that take Medicare or Medicaid) to make their websites and mobile apps meet WCAG 2.1 Level AA. The original compliance dates were May 11, 2026 for recipients with 15 or more employees and May 10, 2027 for those with fewer.
In May 2026, HHS issued an interim final rule extending both dates by a year (Duane Morris summary):
| Recipient size | Original date | Current date |
|---|---|---|
| 15 or more employees | May 11, 2026 | May 11, 2027 |
| Fewer than 15 employees | May 10, 2027 | May 10, 2028 |
The standard itself (WCAG 2.1 AA) did not change, and the rule covers content and apps provided through third parties, such as booking and patient portal vendors. Other Section 504 duties, such as making reasonable modifications for people with disabilities, were not extended.
The ADA
- Title II covers state and local government entities, including public hospitals and county health departments. The Department of Justice's 2024 rule also sets WCAG 2.1 AA, and in April 2026 DOJ extended its compliance dates by a year, to April 2027 for larger entities and April 2028 for smaller ones (JD Supra summary).
- Title III covers businesses open to the public, including private medical and dental offices. DOJ's guidance says the ADA's requirements "apply to all the goods, services, privileges, or activities offered by public accommodations," and it has taken the position since 1996 that this includes web content (ADA.gov). There is no Title III technical rule, and WCAG 2.1 AA is the standard most organisations work to.
The most common failures to fix first
WebAIM's 2026 scan of the top million home pages found detectable WCAG failures on 95.9%, with an average of 56.1 errors per page (WebAIM Million). The six most common:
| Error | Share of home pages | Fix on a clinic site |
|---|---|---|
| Low contrast text | 83.9% | Darken light grey text and text over photos; WCAG AA needs 4.5:1 for body text (W3C) |
| Missing image alt text | 53.1% | Describe provider photos and informative images; mark decorative ones as decorative |
| Missing form labels | 51.0% | A visible label above every contact and booking field |
| Empty links | 46.3% | Give icon links (phone, social, map) an accessible name |
| Empty buttons | 30.6% | Label menu, close and carousel buttons |
| Missing page language | 13.5% | Set lang="en" (or the right language) on the page |
Automated tools catch only part of WCAG. After fixing these, test with a keyboard only and with a phone's screen reader (VoiceOver on iPhone, TalkBack on Android) on your booking flow. Practices serving patients in several languages should also read our guide on multilingual patient education.
FAQ
What is mobile-first indexing?
It means Google uses the smartphone version of your pages for crawling, indexing and ranking. Google began rolling it out in 2018, made it the default for new sites in 2019 and declared it complete in October 2023. Content that appears only on the desktop version of your site is not used.
How do I check if my medical website is mobile friendly?
Google retired its Mobile-Friendly Test in December 2023. Use PageSpeed Insights on the mobile tab or Lighthouse in Chrome DevTools, and use URL Inspection in Search Console to see the page as Google's smartphone crawler fetched it. Then test calling and booking on a real phone.
Do medical websites have to be ADA compliant?
DOJ's position is that the ADA applies to the websites of businesses open to the public, which includes private practices, and public hospitals are covered by a specific 2024 Title II rule. Organisations that receive HHS funding, such as Medicare and Medicaid providers, are also covered by HHS's Section 504 rule, which sets WCAG 2.1 AA with deadlines of May 11, 2027 or May 10, 2028 depending on size. Ask your counsel which rules apply to you.
What WCAG level do healthcare websites need to meet?
Both the HHS Section 504 rule and DOJ's Title II rule set WCAG 2.1 Level AA as the technical standard. It is also the level most private practices work to under Title III.
Should a medical practice have a separate mobile site?
A responsive site, where one URL and one set of content adapts to the screen, is simpler to maintain and keeps mobile and desktop content identical for Google. Separate mobile sites (m.example.com) need careful canonical and redirect handling and often drift out of sync.
