stillindexedStart monitoringOpen the app

Accidentally noindexed your site? Find and fix it fast

How to confirm an accidental noindex in the live HTML and the response headers, find what put it on, fix it, and get the page back in the index without waiting on Search Console.

A page on a site you manage has silently dropped out of Google. You suspect noindex, but you’re not sure, and you can confirm it in the next minute. Open the live page in the indexability checker, which reads the meta robots tag AND the X-Robots-Tag header in one request, or, if you want the header alone, the X-Robots-Tag checker. You’re looking for one word: noindex, in the meta or in the response header. Either one takes the page out of the index.

Check the page, not the Search Console report

Search Console reports on Google’s crawl-and-index schedule, measured in days. It is the last place you learn about this. The page itself answers now:

  • The meta case: a <meta name="robots" content="noindex"> tag in the HTML head, visible in view-source.
  • The header case: an X-Robots-Tag: noindex response header, invisible in view-source, which is exactly why it’s the one people miss. curl -sI https://example.com/pricing shows the response headers; check for x-robots-tag: noindex. The two free tools above do this without curl.

Most free checkers read the HTML only. The header is where a silent noindex hides.

Where the accidental noindex usually comes from

The mechanisms are routine, not exotic:

  • a staging noindex snippet merged into production, or a staging edge rule promoted with it;
  • a CMS toggle flipped for one page and applied sitewide, or a template that prints noindex when a condition is met;
  • a plugin or cache layer serving a stale X-Robots-Tag captured from another response;
  • a CDN / edge rule that adds X-Robots-Tag: noindex to matching responses.

The practical point: the header variants live in server and edge config, so fixing the HTML alone won’t clear them. The header check is not optional.

How to fix it

Remove the directive at its source, whether that is the tag, the template, the cache or the edge rule, then redeploy, and re-check the page through the indexability checker until it reads clean for both meta and header. A page is blocked if EITHER one says noindex; clearing only the meta while the header still fires changes nothing.

How long re-indexing actually takes

Once the live page reads clean, Google has to re-crawl, re-process, and re-admit the URL. That is days to weeks, varying with crawl rate and site size. That is not something a fix can rush. You can nudge it with Search Console’s URL Inspection and Request Indexing, but that only asks; the schedule is Google’s. Monitoring is what tells you the fix actually landed while you wait.

How to make sure it never silently happens again

A silent noindex is a semantic directive change, and the fix is watching the directives. That means fetching the URL like a search engine would, reading the raw HTML and the response headers, and alerting on a directive flip rather than text churn. stillindexed.com does this as often as every 15 minutes and pages you on Telegram and email when a noindex appears. noindex isn’t the only silent deindexer. Robots.txt changes can take down whole sections. If you’re still learning the mechanics, start with how noindex works.

The tools here are free and need no account. Continuous monitoring of the page that just scared you starts at $29 a month.

Questions

How do I check if a page is noindexed?
Look in two places, because a noindex can live in either. In the HTML head, search the source for a meta robots tag containing noindex. In the response headers, look for an X-Robots-Tag header, which view-source will never show you. A page can carry either one, or both, and one is enough to block it.
Why can I not see the noindex in view-source?
Because it is probably in the response headers rather than the HTML. X-Robots-Tag is sent by the server, so it is invisible in the page source and invisible to browser extensions that only read the document. Check the headers of the final response after redirects.
How long does it take to get back in the index after removing a noindex?
Days to weeks. Google has to re-crawl the page, notice the directive is gone, and re-admit the URL. Crawl rate and site size drive the timing, and nothing you do makes it instant. Requesting indexing in Search Console can help for a handful of important URLs.
Will Search Console tell me a page was noindexed?
Eventually, under Pages as "Excluded by noindex tag", but the report lags by days and only reflects what Google has already processed. It confirms the damage rather than warning you about it.