How do I find where the noindex comes from?

Look in two places: the page source (` `) and the HTTP response headers (`X-Robots-Tag: noindex`). The header is set by the server, a CDN or a plugin — you won't see it in the page source.

How long until the page returns to the index after removing noindex?

After the crawler's next visit. You can speed it up by requesting indexing in URL Inspection. It usually takes from a few days to a few weeks.

Can I block the page in robots.txt instead of using noindex?

Not if you want it removed from the index. A robots.txt block stops Google from seeing the noindex — and a blocked page can stay in results without a description.

Excluded by ‘noindex’ tag

Google fetched the page, found a noindex directive — in meta robots or the X-Robots-Tag header — and, as instructed, left it out of the index. If that's intended (cart, account pages, test pages), all good. If not, remove noindex and request indexing.

What this status means

The page carries a noindex directive, so Google deliberately left it out of the index. The directive can be in two places:

in the HTML: <meta name="robots" content="noindex"> (or content="noindex, follow"),
in the HTTP response header: X-Robots-Tag: noindex — which is also how PDFs and images get excluded.

When it's fine

Noindex is right for the cart, checkout, customer account, internal search results, thank-you pages and test versions. If the report contains only such pages, there's nothing to do.

Common accidental causes

a template or configuration copied from staging to production together with noindex,
WordPress's "Discourage search engines from indexing this site" option left ticked,
an SEO plugin setting noindex for a whole content type, such as categories or tags,
a server or CDN rule adding an X-Robots-Tag header to too many URLs.

How to fix it

Check the page source and response headers — the redirect checker shows the final page's headers and meta robots.
Remove noindex where it comes from: template, CMS settings, plugin, server.
Make sure the page isn't blocked in robots.txt — otherwise Google won't see the change.
Request indexing in URL Inspection.

How to catch an accidental noindex right away

A noindex left over from staging is one of the most common causes of a sudden traffic drop after a release.

IndexRise checks meta robots and X-Robots-Tag on monitored pages every night. When a noindex appears that wasn't in the baseline, you get a critical "Page is no longer indexable" event with the cause — the next day, not weeks later in Google's report.