The telehealth website launch checklist: content, code and compliance

Everything to test the week before your telehealth site goes live, including the code nobody reads.

Written by Kevin MatthewsHead of Development

Checklist3 min read

Start reading
A contact page showing a correct phone number while the code links to the wrong one, a cache versus origin test, a 44 check launch list and a retest table
Check the code behind the screen, test against the origin and retest every fix before launch.

This is the list we run the week before every telehealth launch, built from the problems we keep finding on live clinic sites: placeholder text in the Terms, phone buttons that dial an old number, medicine names in image file names, questionnaires that turn everyone away. Most of these are invisible from the homepage, which is why they survive. Work through each section, and mark anything that needs a decision from the clinic, a lawyer or a clinical lead separately from fixes a developer can make.

1. Identity and contact

// checklist0 of 4 done

2. Content and claims

// checklist0 of 8 done

3. The code nobody reads

Most TGA problems we find live here. Search the page source and CMS for medicine names, ingredients and nicknames related to your services, and check:

// checklist0 of 8 done

The rules behind this are in TGA advertising rules for clinic websites.

4. Booking and questionnaire

// checklist0 of 7 done

5. Privacy and tracking

// checklist0 of 5 done

// checklist0 of 3 done

The full consistency check is in Terms, FAQs, refund and booking rules that contradict each other.

7. Security and infrastructure

// checklist0 of 6 done

8. Test the right thing

// checklist0 of 3 done

9. Looks fixed, isn't: the retest

After fixes, we mark every issue as fixed, partly fixed, looks fixed but isn't (the text changed but the link or function didn't), not fixed, or lost in the rewrite (something good that disappeared). The third one is the most common: a phone number updated on screen while the tel: link still dials the old one. Retest until every item is fixed.

If you'll advertise on Google, run the LegitScript requirements checklist too.

Want us to run this before your launch? Start on Connect.

Finished this read?

  1. OpenedToday
  2. FinishedNot yet

Written by

Kevin MatthewsHead of Development

Kevin leads engineering at SingletonTec and has spent 10+ years building production-grade websites, apps and systems for businesses.

Ask Kevin a questionMore from the lead engineer

// questions about this read

Still wondering?Start with these.

Short answers from Kevin and the team. Not here? Ask Kevin directly.

  1. Identity and contact details, content and claims, the code behind the pages, booking and questionnaire tests, privacy and tracking, legal pages, security, and a retest of every fix.

    Telehealth clinic websites: how to launch one regulators won't flagAsk an engineer to run the checklist

  2. Because medicine names, old phone numbers and placeholders hide in URLs, alt text, meta tags, schema and link targets that you never see on screen but Google, regulators and reviewers do.

    TGA advertising rules for clinic websites: where builds go wrong

  3. A fix that changed what's displayed but not what happens, like a new phone number on screen with the old number still in the link. Retest the function, not the text.

  4. Run every exclusion, flag and normal path with test data on real phones, and confirm answers arrive in the practice platform.

  5. Yes, the download is on this page. Use it before launch and again after any big change.

    Healthcare websites and platformsBook a 10-min call