Support & operations · Practical guide

Verify old links on the live website after a release

The preview environment applies a rule that production does not recognise. The release check never exercised the actual website domain.

Healthcare website support desk with a system checklist, telephone and orange notebook.
Know who to call and what help your support arrangement includes.

What to change

Preview and production can have different routing capabilities or configuration loading rules. Ask the hosting owner to identify which actual production setting implements the agreed move. Test the incoming address on the public website domain after deployment and retain the returned destination as evidence. If preview behaviour differs intentionally, document that difference so future reviewers know which environment can and cannot prove the live route works.

A worked example

Illustrative example

Illustrative test: Test a harmless legacy path through both environments after deployment. A legacy guide may move correctly in the supplier's preview but still fail at the practice's public domain. The hosting owner identifies the live setting that should apply the move and corrects its deployment. Your team retests the original address publicly and records its final destination. The preview remains useful for preparation, while the handover explains why that environment alone could not prove the production routing worked.

Healthcare website maintenance with infrastructure, a status panel, tools and an operational checklist.
Monitor the useful journey, not just whether a server responds.
Healthcare backup and recovery illustrated by storage copies, an archive folder and a restoration route.
Test whether a backup can restore a usable service.

What this means for your practice

A rule can work in preview but fail on the public hosting setup. For an address change, the decisive demonstration is the old link on the actual public domain after publication. Ask the supplier to explain any difference between preview and live routing, then identify the setting that implements the move publicly. Keep the observed final destination with the release record. A screenshot of the preview is useful for preparation, but it cannot establish the live incoming journey. Your team can use a harmless old test route or an approved legacy link to review the result without learning the hosting platform's configuration language.

How to check the result

Production follows the approved mapping and the configuration difference is understood.

A mistake to avoid

A screenshot of the preview destination is not a production routing test.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore support & operations services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.