Medical and practitioner structured data
Evidence required: Export the structured data rendered on the clinic, practitioner, service, and location templates and compare every factual property with visible page content and the clinic's approved source records.
Pass condition: The markup is syntactically valid, uses an applicable type, identifies the same entity shown on the page, and contains no unsupported qualifications, ratings, services, locations, or claims.
Fail condition: The markup conflicts with visible content, describes the wrong entity, includes invented or stale facts, or is implemented only because the team expects a ranking or special-result benefit.
Severity: High when inaccurate entity data could mislead users or search systems; otherwise Medium for implementation defects. Owner: Technical SEO or developer with clinic administration and clinical review for factual fields.
Corrective action: Remove unsupported properties, align the schema with the actual clinic or practitioner page, and document the source for every material field. Validation step: Re-test the rendered markup, inspect the final page source, and compare machine-readable facts with the live page and approved clinic record.
Core Web Vitals and mobile usability
Evidence required: Collect field data where available, lab diagnostics for representative templates, and task-based checks for calling, booking, reading service information, and navigating on a mobile device.
Pass condition: Important pages are usable on common mobile viewports, critical controls remain accessible, and measured performance issues have reproducible test cases and assigned owners. Fail condition: Heavy media, unstable layouts, blocked controls, delayed interaction, or template regressions interfere with access to clinically or operationally important information.
Severity: High when defects obstruct contact, booking, directions, or core service information; otherwise Medium. Owner: Developer or performance owner. Corrective action: Reduce unnecessary scripts and media weight, optimize delivery and caching, reserve layout space, simplify blocking components, and correct template-specific problems.
Validation step: Re-run the same pages and tasks after deployment and compare like-for-like measurements instead of relying on a single score.
Internal links to osteopathic services and patient education
Evidence required: Crawl the site for broken links, redirect chains, orphaned pages, misleading anchors, and important condition or service pages that cannot be reached through relevant navigation or contextual links.
Pass condition: Users and crawlers can reach current practitioner, service, condition, and genuine location pages through accurate links that resolve to the intended destination. Fail condition: Important pages are orphaned, links lead to errors or obsolete destinations, or anchors imply a service or clinical relationship that the destination does not support.
Severity: High for broken paths to booking, location, or core clinical information; Medium for weaker contextual linking. Owner: SEO lead with CMS editor or developer. Corrective action: Repair broken destinations, update obsolete links, remove misleading anchors, and add contextual links only where they help the reader understand a relevant relationship.
Validation step: Re-crawl the affected templates and manually test representative patient journeys on desktop and mobile.
HTTPS, privacy, and patient-data workflows
Evidence required: Inventory all forms, booking widgets, chat systems, analytics tools, call tracking, uploads, cookies, and integrations that may process personal or health-related information, including where data is transmitted and stored.
Pass condition: The clinic's responsible privacy, security, legal, or regulatory reviewers have assessed the actual configuration and the live implementation matches the reviewed process. Fail condition: The marketing team cannot explain the data path, deployed tools differ from the reviewed setup, or a generic badge or scanner is being treated as proof of compliance.
Severity: Critical when sensitive information may be exposed or processed outside the approved workflow. Owner: Clinic privacy or security lead with the web owner and relevant vendors. Corrective action: Document the real data flow, remove unnecessary collection, secure transmission and access, correct vendor configuration, and route the setup through the responsible reviewers.
Validation step: Use non-patient test data to verify the expected submission, storage, access, and deletion behavior and retain the appropriate review record.