Prepare separate markers for a controlled sample
Create an intended public test page, a draft and a synthetic private object. Give each separate body-text and metadata markers. Record which objects may exist in the public build directory before indexing runs.
The public object is a positive control. If no markers are found because search is broken, correct exclusion has not been established. Draft and private objects need explicit expectations for text, title, description and filters.
Distinguish text exclusion from metadata exclusion
Indexing tools can treat body text, filters and metadata differently. Pagefind documents, for example, that an ordinary ignored element may still contribute metadata, while its full exclusion behaves differently. Read and exercise the configuration your actual version uses.
Review visible responses and the generated resources a client can fetch. Hiding a result card does not establish that its information is absent from published material. This matters particularly when the search index is delivered to the visitor's browser.
| Test object | Expectation recorded beforehand | Evidence inspected |
|---|---|---|
| Public reference | Intended text and metadata present | Positive control and working result |
| Draft | No prohibited content exported | Build selection and generated index |
| Synthetic private object | Neither protected text nor metadata public | All relevant search resources |
| Ignored element | Exclusion covers agreed data types | Text, filters, title and description separately |
| Removed test page | New publication follows removal rules | Current index and old resource routes |
Test removal through the publishing chain
First publish the permitted test page and verify its marker. Remove or unpublish it under the test plan, rebuild and publish to the agreed preview. Check the same query and the index version actually fetched.
Inspect old search resources and caches under your control too. A missing current result does not automatically mean previously published files are inaccessible. Document the environment's actual removal and caching procedures rather than assuming them.
State what a public index must never protect
An indexing exclusion is not access control for the original resource. Private content needs to remain outside public exports and have appropriate protection on its own delivery route. Removing a result does not erase copies others already fetched.
Record markers, source, configuration, build version, published resource paths, observations and retest owner. Remove synthetic material under the plan. This is a focused indexing exercise, rather than complete security certification.