App indexing and search engine visibility

The CalmCompliance app is intentionally crawlable but not indexable by search engines. Every route returns an X-Robots-Tag: noindex header, and /robots.txt allows crawling so search engines can fetch pages and honour that directive.

How the app is deindexed

All app routes return a global X-Robots-Tag: noindex response header. This tells search engines that they may fetch a page but should not include it in their index.

The app also serves a /robots.txt file with a single rule:

• User-agent: *

• Allow: /

There are no Disallow rules. Blocking crawling entirely would prevent search engines from seeing the noindex header, which could cause externally-linked URLs (such as shared scan links or sign-up pages) to appear as URL-only snippets in search results.

Why crawling remains allowed

A Disallow: / rule in robots.txt would stop search engines from fetching pages, but it would also stop them from reading the noindex header. That means pages that are linked from elsewhere on the web could still be indexed without their content. Allowing crawling while signalling noindex is the standard and reliable pattern for removing a site from search results.

When pages will disappear from search results

Pages that were already indexed before the deindexing change may take time to drop out of search results. Search engines recrawl at their own pace, and the exact timing depends on the engine and the page. You do not need to take any action inside CalmCompliance to speed this up.