Check Core Web Vitals and real-user performance
Evidence required: Google Search Console and PageSpeed Insights reports for representative treatment, admissions, clinician, and location templates, including LCP, INP, CLS, mobile field data where available, and reproducible lab diagnostics.
Pass condition: Priority templates are crawlable and usable, major performance regressions have an accountable owner, and measured issues are documented rather than inferred from a single score. Fail condition: Key pages show persistent loading, interaction, or layout problems that materially impair access, or the team cannot reproduce and own known regressions.
Severity: high
Owner: Technical SEO lead with engineering or web development. Corrective action: Fix bottlenecks in templates, media delivery, scripts, caching, rendering, or third-party code according to measured evidence, then retest representative URLs.
Validation step: Compare the same template set after deployment and document whether the affected metrics and user-facing problems improved. Tools: Google Search Console, PageSpeed Insights
Review privacy-sensitive forms and data handling with the responsible specialists
Evidence required: Inventory of forms, requested fields, transport security, approved privacy notices, analytics and tag behavior, access controls, and the organization's documented privacy and security decisions for the public website.
Pass condition: Public forms and tracking match the practices approved by the responsible privacy, security, legal, or regulatory owners, and SEO copy does not make unsupported HIPAA or security claims.
Fail condition: Forms collect sensitive information without clear approved handling, marketing claims compliance it cannot substantiate, or website behavior differs from the reviewed privacy documentation.
Severity: critical
Owner: Privacy or security owner with legal or regulatory review as applicable, plus web engineering for implementation. Corrective action: Remediate the underlying form, tracking, notice, access, or transport issue; do not substitute a badge or hosting claim for a documented review.
Validation step: Retest the live workflow and obtain sign-off from the accountable reviewer on the corrected public implementation. Tools: SSL Labs, Security Headers
Validate facility and medical structured data against visible content
Evidence required: Rendered page content, current structured data output, entity names, addresses, phone numbers, service descriptions, clinician information, and eligibility for the schema types actually used.
Pass condition: Markup accurately reflects visible page information and uses appropriate vocabulary without inventing credentials, locations, ratings, services, or organizational relationships. Fail condition: Markup conflicts with visible content, contains unsupported fields, or is added solely because the team expects a ranking advantage.
Severity: medium
Owner: Technical SEO lead with content or clinical owner for factual fields. Corrective action: Remove unsupported properties, align remaining markup with visible content, and select the most defensible entity types.
Validation step: Revalidate the rendered output and spot-check that search-facing data matches the page after deployment. Tools: Schema.org, Validator.schema.org
Verify mobile access and task completion on priority pages
Evidence required: Device testing for navigation, tap targets, form completion, click-to-call behavior, media rendering, and page performance across the main acquisition templates.
The previously published claim that Over 70% of initial searches occur on mobile lacks a supporting source URL in this JSON and should be treated as an internal or historical figure requiring reconciliation.
Pass condition: A user can read core information, navigate treatment and admissions content, and complete intended contact actions on common mobile viewports without broken layout or hidden critical content.
Fail condition: Mobile users encounter blocked content, unusable controls, inaccessible forms, or materially different information from desktop. Severity: high
Owner: Web product or engineering owner with SEO and accessibility review.
Corrective action: Repair responsive templates, navigation, forms, media, and interaction issues based on reproducible device evidence. Validation step: Repeat the same mobile task set after deployment and record results for the affected templates. Tools: Google Search Console, PageSpeed Insights