Start here because a page that cannot be reached, interpreted, or safely used should not be marked complete merely because its copy looks finished. Each control below requires evidence, a pass-or-fail decision, severity, an owner, a corrective action, and a fresh validation after the change.
Lead capture and submitted-information flow. Evidence required: a current inventory of forms, chat tools, booking widgets, analytics fields, destinations, notices, and every category of information a visitor can submit.
Pass when the responsible privacy or legal reviewer has evaluated the applicable handling requirements and the live configuration matches what was approved; fail when information can enter an unreviewed path, an unexpected destination, or a configuration that no responsible reviewer has accepted.
Severity: Critical where regulated or sensitive information may be involved. Owner: privacy or compliance lead together with the web owner. Corrective action: remove unnecessary fields, correct collection, storage, transmission, notice, or access settings, and move the flow to an approved process when needed.
Validation: submit non-patient test data and confirm the destination, access behavior, notices, and retention handling against the approved setup. JotForm HIPAA and FormDr are already referenced tools, but a product label is not evidence that the practice's own configuration is compliant.
Business and practitioner structured data. Evidence required: the rendered markup, the visible business and practitioner facts it describes, and the Schema.org types selected for the page. Pass when every published property is supported by visible, accurate information and the entity relationships match the page; fail when the markup invents, exaggerates, or conflicts with the content.
Severity: High. Owner: technical SEO or developer with editorial review. Corrective action: remove unsupported properties, correct entity relationships, and map the remaining fields to facts users can verify.
Validation: inspect the rendered output with Schema.org tooling and, where applicable, Google Rich Results Test. Treat successful validation as markup QA only, not as a promise that Google will display a feature.
Mobile performance and Core Web Vitals review. Evidence required: current mobile field or lab diagnostics for representative service, gallery, practitioner, and location templates, plus a note identifying any material template issue.
Pass when the reviewer can explain the measured condition and no important template problem is left without an owner; fail when blocked resources, oversized media, layout movement, or slow interaction repeatedly degrades key pages and has no documented response.
Severity: High. Owner: developer or performance owner. Corrective action: fix the measured bottleneck at the component or template that causes it instead of adding a generic speed plugin by default. Validation: rerun PageSpeed Insights after deployment and compare the affected templates. WP Rocket can be relevant on a compatible WordPress setup, but its presence alone cannot close the control.
Internal links and error handling. Evidence required: a crawl of broken internal destinations, redirect chains, orphaned service pages, and 404 responses, plus manual checks of important paths. Pass when relevant service, practitioner, and genuine location pages have working contextual links and intentional error behavior; fail when navigation or editorial links send users or crawlers to broken, accidental, or obsolete destinations.
Severity: High. Owner: SEO lead with developer support. Corrective action: repair or remove broken references, restore the correct destination when it should exist, and keep redirects limited to a clear purpose.
Validation: recrawl with Ahrefs or Screaming Frog and manually test representative journeys, including the aesthetician services hub.
Indexability and canonical consistency. Evidence required: rendered robots directives, canonical values, response status, sitemap inclusion, and representative search-console inspection for each template in scope.
Pass when pages intended for search are crawlable and internally consistent and excluded pages have a documented reason for exclusion; fail when conflicting directives, canonical mistakes, or template behavior make the intended index state unclear.
Severity: High. Owner: technical SEO or developer. Corrective action: reconcile directives and canonicals at the page and template level, then release only the intended configuration. Validation: fetch the rendered page again after release and verify the final status, directives, canonical output, and discoverability from the expected site paths.