Resources

Our own website / Internal project record

How We Checked a Change to Our Own Website

A practical example of agreeing what must keep working, checking the change, and recording what the evidence shows.

This record concerns Physicians Solution’s own public website. We changed how its pages were built and presented, then checked that visitors could still find information and contact us. It is an internal project, not a medical-practice client case or an independent review.

Start here.

  • Define the pages, links, and inquiry steps that must keep working.
  • Check the built site and published pages before testing a real inquiry.
  • Record email delivery and Analytics receipt as separate results.

1. Start with what visitors need

Visitors needed to reach the existing pages, read the service information, follow useful guide links, and use the Contact form. Page titles and search references also needed to remain consistent. These became checks for accepting the change.

The owner approved and published the illustrated site update and a follow-up change. The follow-up clarified our working process, added relevant service links to guides, and used company attribution for the buyer guide.

2. Check the site in stages

We checked the code, the finished site files, and the local hosting behavior before reviewing the published pages. Automated checks also exercised controlled inquiry responses. Those simulated responses tested specific paths without sending a real message.

The release checks passed on October 28, 2026, for version 0b7e072. That release covered 27 public pages. Production page checks confirmed expected headings, search references, the Contact form, the revised process section, guide links, and company attribution. Our dated first-party summary records the public page checks. The current sitemap describes today’s catalogue; it does not prove the historical count or Google’s index coverage.

3. Follow one controlled inquiry

With separate owner approval, one synthetic inquiry displayed an acceptance message and reset the form. One matching email reached the monitored business inbox. One lead event appeared in Google Analytics. We checked email delivery and Analytics receipt separately.

The inquiry used no real patient or customer data. We did not repeat the send or create a manual lead event. This demonstrated one live positive result at that time.

4. Keep the limits with the result

This first-party record covers one positive test on our own website. It does not show customer growth, healthcare-client outcomes, or every live failure path. Detailed deployment, email, and Analytics records remain private. The dated summary lists the checks and their limits.

Plan the checks for your change.

For a proposed change, agree the scope, acceptance checks, responsible people, and unresolved limits before deciding it is complete. Our getting-started process describes that conversation. Managed IT Support explains the ongoing support scope to discuss separately.

Discuss your practice’s needs

Sources

Sources checked on . The dated summary is a first-party record, not an independent audit. The other links describe current website arrangements. Detailed deployment, email, and Analytics records remain private. The source-review date is not a publication date.