Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

What is Noindex Directive?

A page-level rule delivered via a robots meta tag or an X-Robots-Tag HTTP header instructing search engines to exclude a crawled URL from their search results.

Updated · SEO & AI Search

Plain definition

Definition of Noindex Directive

A page-level rule delivered via a robots meta tag or an X-Robots-Tag HTTP header instructing search engines to exclude a crawled URL from their search results.

Formula / syntaxHTML meta robots: name="robots" content="noindex" | HTTP header: X-Robots-Tag: noindex

Worked example

Say a made-up form builder called FormLoom generates public thank-you confirmation pages, thin empty category hubs, and downloadable PDF receipts. None of those URLs should clutter Google Search results. On the HTML thank-you pages and empty hubs, FormLoom outputs a robots meta tag with content="noindex, follow" in the document head. For the PDF receipts, which have no HTML head section, its server sends the HTTP response header X-Robots-Tag: noindex.

Here is the crucial catch documented by Google Search Central: Googlebot can only obey a noindex directive if it is allowed to crawl the URL and read that tag or header. FormLoom deliberately leaves those paths open in robots.txt. The next time Googlebot fetches an empty category page, it reads the noindex rule and drops the URL completely from the index, while still following links on the page to discover real content.

Why it matters when you launch

When you ship an early SaaS, you often have half-finished areas: empty user directories, internal search result pages, beta staging URLs, or account onboarding screens. Letting search engines index hundreds of thin or empty URLs dilutes the perceived quality of a small domain and creates awkward search snippets for prospective customers.

Noindex also works as a clean launch gate. You can keep programmatic category pages set to noindex while they are sparse, exclude them from your XML sitemap, and automatically flip them to indexable once they accumulate enough real listings or content to deserve a search result.

Common mistakes

  • Blocking a URL in robots.txt at the same time you add noindex, which prevents Googlebot from fetching the page and seeing the noindex rule at all.
  • Forgetting to remove a site-wide noindex tag or X-Robots-Tag header copied from a staging or preview deployment after pushing to production.
  • Leaving noindex URLs inside your XML sitemap, which sends contradictory instructions to search engines about whether you want those pages indexed.
  • Using noindex as a security boundary for private customer files instead of enforcing server-side authentication and authorization checks.

Tools and guides that use it

Official sources

Pritam Ghosh runs Hauntboard and maintains this glossary.

Published · Updated

Building something real? Launch it in public.

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch