What to change
The public robots file acts as a pointer to the sitemap location. When that location changes, include the pointer in the same release and test it from the live hostname. Ask the supplier to follow the advertised address exactly, including any nested path. Keep a note of intentionally retained older locations so a future audit can distinguish compatibility support from an overlooked stale reference.
A worked example
Illustrative example
Illustrative test: Open the advertised location after a clean deployment. Repeat the check through the public hostname after deployment rather than relying on the local file.
How to check the result
The robots pointer resolves to the current intended inventory.
A mistake to avoid
Changing only a local robots file leaves the public pointer unchanged.
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.
Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.
Further reading
These primary sources provide additional context for the project decisions above.
Related decisions
Turn the brief into a working service
Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.
Explore marketing & search services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.