imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Check index exclusions, as well as the results that should appear.

Public search can expose more than visible result cards. Generated resources may contain text, titles, filters or descriptions. Exercise exclusions with synthetic markers in an agreed environment. Never use real secrets to discover whether an exclusion works.

Four boundaries for a public search index
  1. Public

    Approved content should be findable.

  2. Draft

    Unapproved material must not be exported accidentally.

  3. Private

    Titles and metadata can also need protection.

  4. Removed

    New indexing and old resources need the right procedure.

Inspect delivered data, rather than only visible cards.

A private result card is hidden with CSS. Is its content excluded?

Not established. Inspect public search resources and keep private content out of the public export.

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 objectExpectation recorded beforehandEvidence inspected
Public referenceIntended text and metadata presentPositive control and working result
DraftNo prohibited content exportedBuild selection and generated index
Synthetic private objectNeither protected text nor metadata publicAll relevant search resources
Ignored elementExclusion covers agreed data typesText, filters, title and description separately
Removed test pageNew publication follows removal rulesCurrent 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.

Sources and further reading

Questions, answered

Is searching for the draft title enough?

No. Inspect exports, text, metadata and generated resources too, using a working positive control.

Does removing a result prove old index files are gone?

No. Current results, previous resource addresses and caches need assessment against the actual publishing environment.

IMBAHUB

Let’s plan your website

Prepare a public control marker and separate synthetic exclusion markers before the next index build.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.