A redirect works on preview but fails publicly

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 hostname 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.

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.

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 recordCompare the preview rule configuration with the production deployment output.Request the old path from the real public hostname.Check whether the hosting platform loaded the intended rule file.

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.