Use these checks to confirm that the pediatric website is technically reachable, appropriately secured, usable on mobile devices, and represented accurately in machine-readable data. Search performance should be evaluated separately from the pass/fail status of each implementation item.
Verify SSL Certificate and HTTPS Encryption | Evidence required: browser certificate details, redirect behavior, mixed-content review, and an external TLS test. | Pass/fail condition: pass when the production site consistently serves valid HTTPS without material mixed-content or redirect errors; fail when certificate, protocol, or page-delivery issues remain. | Severity: high for security or access problems. | Owner: web developer or infrastructure owner. | Corrective action: renew or correct the certificate, force consistent HTTPS, and remove insecure resource calls. | Validation step: retest representative pages and forms with browser tools and an independent TLS checker. Tools: Let's Encrypt, SSLLabs
Audit Lead Forms for HIPAA Compliance | Evidence required: form fields, transmission path, storage destination, vendor contracts, access controls, retention settings, and data-flow documentation. | Pass/fail condition: pass only when the responsible legal, security, and compliance reviewers approve the implementation for the practice's actual data flows; fail when sensitive information is collected or stored through an unreviewed process. | Severity: critical because privacy and regulatory exposure can extend beyond SEO. | Owner: privacy or compliance lead with IT and the form owner. | Corrective action: minimize collected data, secure transmission and storage, correct access controls, and replace or reconfigure vendors as required by responsible reviewers. | Validation step: document reviewer approval and test the live form from submission through storage and deletion. Tools: Jotform HIPAA, Formstack
Optimize Core Web Vitals for Mobile | Evidence required: field data where available, lab tests, device testing, template-level performance diagnostics, and parent-task usability checks. | Pass/fail condition: pass when critical pediatric pages are usable on representative mobile devices and material performance issues have been addressed; fail when slow loading, unstable layouts, or blocked interactions interfere with common tasks. | Severity: high for pages used to contact or evaluate the practice. | Owner: front-end developer or performance owner. | Corrective action: reduce unnecessary scripts, optimize images and fonts, improve caching, and fix layout or interaction problems. | Validation step: rerun tests after deployment and complete real-device task checks. Tools: Google PageSpeed Insights, GTmetrix
Implement MedicalBusiness Schema Markup | Evidence required: rendered page content, JSON-LD output, practice type, hours, location, and any other marked-up properties. | Pass/fail condition: pass when structured data is syntactically valid, appropriate to the page, and consistent with visible, current practice facts; fail when markup is inaccurate, unsupported, stale, or copied without verification. | Severity: medium. | Owner: technical SEO or developer with practice staff validating facts. | Corrective action: remove unsupported properties and align remaining markup with actual page content and current documentation. | Validation step: validate syntax and compare each marked-up value against the live page and practice records. Tools: Schema.org, Merkle Schema Generator