It is not the same as blocking a page in robots.txt. A robots.txt disallow stops the crawler from fetching the page, which means it never sees a noindex on it. If you want a page out of the index, it has to stay crawlable long enough for the noindex to be read.
On a large site, noindex is a tool for restraint. Many pages are useful to visitors but too thin to deserve a place in search: a title, an embed and a few words. Keeping them out stops them from diluting the pages that should rank. Those pages should also be left out of the sitemap, so the two signals agree.
The risk is the noindex nobody meant. A tag left on a template after a staging build can quietly remove a whole section. In the Search Console coverage report, “excluded by noindex” is a list worth reading line by line. The only question is whether each one was a choice someone made. Read it again after every release that touches templates.
An example from our own work
Videojam, our own video platform, has an indexation gate: a stored flag for video pages and noindex rules for hub pages keep thin pages out of the index and the sitemap. In its coverage report dated 23 October 2026, 367 pages are excluded by noindex, on purpose. On audacian.eu, a /work topic page with fewer than three distinct items stays live and linked but carries noindex and is left out of the sitemap and llms-full.txt; it comes back on its own once it has enough work in it. Our 404 page carries noindex, and removed pages answer 410 Gone with an X-Robots-Tag noindex header.