A deployment succeeds but the public hostname is unchanged

What to change

Confirm where the successful deployment was actually attached. Ask the hosting owner to distinguish the preview address, deployment address and public custom hostname, then test the public destination directly. Compare a harmless revision marker or known changed content to establish which release visitors receive. The acceptance record should name the hostname that was verified, avoiding an ambiguous green status that proves only that some environment accepted the files.

A worked example

Illustrative example

Illustrative test: A reviewed text change appears on the actual public domain, not only the deployment preview.

How to check the result

The hosting status and visitor-facing release agree.

A mistake to avoid

A successful upload does not prove the main hostname serves that upload.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordRecord the successful deployment's target environment.Compare its output with the organisation's public hostname.Verify the intended release through a fresh public request.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.