Use production evidence rather than assumptions for this part of the review. Collect live crawl data, browser behavior, deployment records, network captures, and the clinic's approved privacy documentation.
A technical pass does not establish that data collection is appropriate, and a privacy-approved measurement design does not establish that pages are crawlable or usable.
Checkpoint: Secure delivery across patient-facing hosts
Evidence required: A crawl of intended indexable hosts and subdomains, browser security checks on representative service, provider, location, education, and form templates, plus the clinic's current domain inventory.
Pass condition: Patient-facing pages and intended indexable assets load through the clinic-approved secure configuration, with no mixed resource defect that breaks or materially degrades the user journey.
Fail condition: Important pages resolve through an unintended insecure path, mixed resources interrupt function, or legacy host variants create duplicate or unsafe routes. Severity: critical
Owner: Web engineering, with infrastructure or security support where the clinic assigns it.
Corrective action: Normalize approved host behavior, repair mixed resources, update internal references and canonical handling where needed, and document redirect logic before release. Validation step: Re-crawl the same host set, retest representative pages and forms in a browser, and compare the deployed host behavior with the approved production inventory.
Checkpoint: Measurement design and sensitive-data handling
Evidence required: A complete tag inventory, request logs or debugger captures, form-field mapping, destination inventory, consent behavior where applicable, and written review from the clinic's responsible privacy or legal team.
If Google Analytics 4 is present, inspect the events, parameters, destinations, and trigger conditions actually implemented rather than assuming a default setup is acceptable. Pass condition: The clinic can explain what is collected, why it is needed, where it is sent, when it fires, and which responsible reviewer approved the design for the actual patient journey.
Fail condition: Unknown or unnecessary tags run on sensitive paths, patient-adjacent data is transmitted without a documented review path, or the responsible teams cannot reconcile observed payloads with the approved specification.
Severity: critical
Owner: Analytics or marketing operations and web engineering, with the clinic's responsible privacy or legal reviewers. Corrective action: Remove unnecessary collection, minimize payloads, separate sensitive journeys where appropriate, document destinations and vendors, and implement only the measurement pattern the clinic has approved.
Validation step: Repeat network and tag inspection after deployment, compare observed payloads with the approved specification, and retain the review evidence with the change record. This guide cannot guarantee compliance, and responsible legal, medical, or regulatory reviewers remain required for clinic-specific decisions.
Checkpoint: Mobile rendering and Core Web Vitals defects
Evidence required: Field data when available, lab results for major templates, mobile browser recordings, and an inventory of scripts, fonts, media, embeds, and consent components that affect loading or interaction.
Pass condition: Important information and contact actions render reliably on mobile, known blocking defects are absent, and performance findings are tied to a reproducible template or interaction rather than a single aggregate score.
Fail condition: Essential content is hidden or delayed, layout movement disrupts a task, tap or form behavior fails, or a reproducible performance defect obstructs an important patient journey. Severity: high
Owner: Web engineering and design, with marketing or patient-access teams identifying priority journeys.
Corrective action: Reduce unnecessary payloads, optimize delivery of media and fonts, defer nonessential execution when technically appropriate, and simplify interaction patterns that block completion.
Validation step: Retest the same templates under comparable conditions, confirm the original defect no longer reproduces, and continue to observe field data without presenting the correction as a promised ranking gain.
Checkpoint: Broken URLs, 404 responses, and internal-link continuity
Evidence required: A site crawl, available server or analytics evidence for frequently requested missing paths, and manual samples of important treatment, provider, financing, and location journeys.
Pass condition: Internal links reach the intended live destination, retired pages have an approved disposition, and missing URLs return appropriate behavior without stranding users in key journeys. Fail condition: Internal links reach missing resources, retired paths redirect to unrelated pages, or broken navigation interrupts the route to clinically or operationally important information.
Severity: high
Owner: SEO or content operations for discovery and mapping, and web engineering for implementation. Corrective action: Repair links, restore a page only when it remains accurate and useful, redirect only to a genuinely relevant replacement, and remove obsolete references from templates and navigation.
Validation step: Re-crawl affected paths, manually repeat representative journeys, and verify that each redirect, restoration, or removal matches the approved content map.
Checkpoint: XML sitemap scope and indexation signals
Evidence required: Published sitemap files, crawl output, indexation reports, canonical targets, robots directives, and an approved inventory of treatment, provider, education, and genuine location pages intended for search discovery.
Pass condition: Sitemaps list canonical, indexable URLs the clinic intends search engines to discover, while redirected, blocked, duplicate, retired, or noncanonical pages are not promoted through sitemap output.
Fail condition: Sitemap files contain invalid or unintended URLs, omit important canonical pages because generation rules are incomplete, or conflict with the site's canonical and robots configuration.
Severity: medium
Owner: SEO and web engineering. Corrective action: Align sitemap generation with the clinic's canonical and indexation policy, remove invalid entries, and divide sitemap groups only when that improves maintainability or diagnosis.
Validation step: Fetch the deployed sitemap set, compare it with the approved canonical inventory, and inspect processing in search tools after recrawl without assuming immediate discovery or indexing.