A protected page is accidentally included in discovery

What to change

Public discovery files should reflect the access decision already made by the resource owner. Ask the supplier to trace how the protected route entered the library, whether through a source list, automatic scanner or copied link. Remove that public reference at its origin and confirm regeneration does not recreate it. The protected destination must retain its access policy throughout the correction.

A worked example

Illustrative example

Illustrative test: Open the public resource directory in a signed-out session and follow relevant links.

How to check the result

Public indexes contain only intended public destinations and restricted content remains inaccessible.

A mistake to avoid

Making the page public just to clear a crawler error reverses the requirement.

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 recordFind every public navigation and sitemap reference to the protected route.Confirm the resource owner still wants the material restricted.Regenerate public discovery files and verify the route stays protected.

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.