Skip to main content

Allow or prevent search-engine indexing

Control the robots indexing preference for a verified custom-domain status page and understand what noindex does not protect.

Search-engine indexing is off by default. You can allow indexing only for an enabled status page served from a verified custom domain.

The shared status.uptimebasics.com address always remains noindex, even when its custom-domain version is allowed to appear in search results.

Change the preference

  1. Open the monitor's Public Status Page settings.
  2. Open Custom domain.
  3. Confirm the custom-domain request is enabled.
  4. Under Search engine indexing, choose:
    • Keep out of search engines
    • Allow indexing
  5. Select Save custom domain request.

When the custom page loads, Uptime Basics applies the selected robots directive to that hostname. The preference does not apply to the shared status-page URL.

When to keep noindex

Keep the default noindex setting when the page is intended only for customers with a direct link, the page is still being prepared, or you do not want incident and availability information appearing in general search results.

When indexing can help

Allow indexing when the custom status page is an official public support resource and you want customers to find it through search. Use a clear page title, brand name, and description so visitors understand who operates it.

Allowing indexing is a search-engine signal, not a guarantee of inclusion or ranking. Search engines choose when to crawl and index a page.

Noindex is not privacy protection

A noindex status page is still publicly accessible to anyone who knows or discovers its URL. It does not require authentication, encrypt page content beyond normal HTTPS, or prevent links from being shared.

Disable the status page if the information should no longer be public. Do not publish secrets or private URLs on a page merely because it is set to noindex.

Removing an indexed page

Change the setting to Keep out of search engines and save. Search engines can take time to revisit the page and remove an existing result. Disabling the page stops public snapshot delivery but can also take a short time to propagate through caches and search indexes.

Related articles

Did this answer your question?

Your response helps improve this Help Center.