Should a retained reference copy become a discovery candidate alongside service pages? Reading the actual archive headers and commercial-page structure led me to separate retaining a document from announcing it for search.
Retention and visitor intent differ
The source project contains reference copies alongside pages explaining a service. Retaining production evidence is a different purpose from asking search visitors to treat that copy as the representative service document. Existence alone should not make every file belong in the same sitemap.
The new module distinguishes public, archive and private audiences, including only public documents in its expected sitemap. It contains no original reference copy or third-party page. What is shared is a way to declare purpose in an owned document inventory.
Noindex is not an access permission
Archive rows are non-indexable in policy but do not require authentication. This distinguishes a publicly reachable reference copy from a private document needing access control. The function installs no server header and promises no immediate removal from search results.
Private rows declare authentication as necessary, but the module implements neither login nor file serving. A deployed service must enforce and test that declaration separately. Absence from a sitemap must not be presented to an operator as evidence that a document is secret.
Find unexpected discovery from the same manifest
All files may exist while an archive route accidentally appears in discovery. Reconciliation expects public routes only, so an archive entry appears under unexpected sitemap paths. A missing public document appears separately. Equal total counts would miss a one-for-one substitution.
The check compares supplied inventories; it is not a whole-site crawler or robots evaluator. Its examples use fixed synthetic paths and disclose no actual archive location or client access address. Operational discovery still needs an observed inventory.
Review audience changes through the inventory
Changing archive to public can leave the file path unchanged while changing expected discovery. Changing public to private requires more than sitemap exclusion: actual authentication and prior cache exposure need separate verification. Audience changes deserve review even when document text stays identical.
The module does not execute that change. It derives a new expected inventory from the declaration, making it possible to explain which documents enter or leave discovery. Its purpose is to make publication responsibility inspectable rather than expose more source material.
As a website grows, references, public stories and internal operations can become mixed. Managing document purpose alongside actual serving paths is clearer than guessing from folder names. The declaration helps preserve different completion criteria for content publication and evidence retention.
Keep material rights as a separate responsibility
The module’s eight tests concern path and audience-policy consistency. They do not determine permission or the lawfulness of retaining material. Excluding discovery does not grant reproduction or publication rights, and this article interprets no particular site’s terms.
I want to distinguish files worth retaining from documents chosen to represent the service. Separating inventory, discovery guidance and access enforcement helps identify which verification remains missing. Reference organization is part of making a website’s production decisions explainable.
Deletion, discovery exclusion and private conversion are distinct operations. Actual removal would need separate reference and backup review. This article and module delete nothing; they derive expected inventories from declared purpose and leave operational enforcement explicitly unperformed.