Share the Post:

Table of Contents

Testing and QA for medical sites: pre-launch and post-launch checklist

Engineer running Lighthouse tests and medical site QA checklist

Introduction

The success of a redesign is not only measured by its aesthetics: a single broken URL or a form that does not submit can cost patients and damage your ranking. This checklist of Testing & Quality Assurance (QA) guides clinics and agencies step-by-step before clicking "Publish" and during the first 14 days after launch.

1 Pre-launch checklist

1.1 Functional tests

Contact Form
- Send correct data to CRM and email notification.
- Displays success message and redirects to "Thank you" page.

CTA buttons
- Verify all links to WhatsApp, tel: and mailto:.
- Checks GA4 events (conversions) firing correctly.

Navigation and internal links
- Scroll through menus, breadcrumbs and in-page links; there should be no 404s.
- Validate 301 redirects if you changed old slugs.

1.2 Performance tests

Core Web Vitals (lab)
- LCP < 2.5 s (Desktop and Mobile).
- FID (INP in Lighthouse v10) < 100 ms.
- CLS < 0.1.

Image upload
- Weight < 200 KB, WebP format, attribute loading="lazy".
- Defined dimensions (avoids shifting).

1.3 Compatibility tests

Devices and browsers
- Desktop: Chrome, Firefox, Edge, Safari.
- Mobile: iOS Safari, Android Chrome.
- Critical resolutions: 1366×768, 1920×1080, 375×667, 414×896.

Quick accessibility (WCAG AA)
- Minimum contrast 4.5 : 1.
- Keyboard navigation (Tab) to key CTA.
- ARIA labels in menus and forms.

1.4 SEO testing and structured data

Meta tags and canonical
- Title ≤ 60 c, description ≤ 155 c, single canonical per page.
- Robots meta = index,follow (remove noindex in production).

Schema
- MedicalOrganization in /about-us.
- MedicalService in treatment landings.
- FAQPage in the FAQ sections.

XML Sitemap
- Generated and sent to Search Console.
- Update lastmod after adjustments.

1.5 Safety and legal

SSL active (HTTPS) and no mixed content.
Forms with reCAPTCHA or honeypot to avoid spam.
Cookies and tracking scripts declared in the consent banner.
Privacy notice and terms visible in footer.

2 Launching plan

Full backup
- Database and compressed files.
Freez" window
- Freeze changes 24 h before, only critical fixes.
DNS + CDN
- Low TTL (300 s) 48 h before to propagate fast; reset to 3600 s after.
Final checklist
- Run list 1.1-1.5 again in production.

3 Post-launch checklist (Day 0-14)

3.1 Real-time monitoring

Search Console
- Detects coverage, 404 and Mobile Usability errors.
GA4 and Looker Studio
- Review conversion events, sessions, time on page.
Uptime robot
- Alerts if drop > 1 min.

3.2 Field Core Web Vitals

CrUX Dashboard (Looker Studio)
- Observe LCP, INP and CLS with real data.
- Adjust images or scripts if metrics red after 7 days.

3.3 Conversion reviews

Form submission rate
- Initial goal ≥ 8 %. If < 5 %, simplify fields or revise copy.
Clicks to WhatsApp
- Validate which URL you use wa.me with pre-filled parameter.
Calls tracked
- Check dynamic number if you use DNI (Dynamic Number Insertion).

3.4 Reviews and user feedback

Ask 5 patients if they had any problems when booking.
Monitor chat/messaging flows: frequent questions = adjust FAQ or copy.

3.5 Quick settings

- Corrects missing internal links.
- Compress images uploaded by the team after go-live.
- Optimize third-party scripts (chat, heatmaps) if they block FCP.

4 Success metrics (30 days)

MetricsTargetTool
Full URL indexing100 %Search Console
Field Core Web VitalsAll greenCrUX
CVR landing≥ 10 %GA4
Bounce rate Home< 45 %GA4
Total leadsMonthly KPI targetCRM

Next step

Integrate this checklist in your project manager before scheduling the release date. Designate people responsible for each area and block specific test windows. With QA discipline, your new medical site will go live with no surprises and stable conversions from day one.

Share the Post:
Scroll al inicio