Sometimes, and usually late. Search Console emails the owners and users of a property when it finds a new issue in a report, such as a new reason in Why pages aren't indexed. It only finds that issue after Googlebot recrawls the page and the report is updated, which can be days after the change went live.
This page sets out what Search Console tells you, what it can't, and where a separate daily check fits.
Checks the live URL now: status, redirects, meta robots, X-Robots-Tag, canonical and robots.txt for Googlebot. Free, no signup.
Why the email comes days later
Search Console reports what Google saw on its last crawl. If a deploy adds noindex to your category template on Monday, nothing changes in the Page indexing report until Googlebot fetches those pages again and the report is refreshed. Pages Google crawls often show up first. Pages it visits every week or two can sit there for longer, and the email follows the report.
By then Google may already have dropped some of the pages. Undoing the change is quick; getting them recrawled and back in the index takes time again.
Changes that may not send an email at all
The emails are about issues that are new to the property. Many sites already have URLs under Excluded by 'noindex' tag or Blocked by robots.txt on purpose: filtered pages, tag archives, internal search. When a page you care about joins a reason that is already listed, you may not get a separate message for it.
Search Console also only covers Google, only covers properties you have verified, and only reports what Googlebot crawled. A robots.txt rule that blocks Bingbot, or a canonical that starts pointing to the staging host, shows up late or not at all.
What each one tells you
| Question | Search Console | Daily crawl check (NoindexWatch) |
|---|---|---|
| Is the page in Google's index? | Yes, from Google's own data | No. It checks what the page tells crawlers, not what Google decided |
| Which canonical did Google choose? | Yes, in URL Inspection | No. It reports the canonical the page declares |
Did a noindex appear in the HTML or an X-Robots-Tag header? | After the next crawl and report update | At the next check: daily on the free plan, hourly on paid plans |
| Did robots.txt start blocking the URL? | For Googlebot, after it rereads robots.txt and recrawls | For Googlebot and Bingbot, at the next check |
| Did the page start returning 404, 5xx or a redirect chain? | After the next crawl | At the next check |
| Did the URL drop out of the XML sitemap? | Sitemap totals in the Sitemaps report, not per URL | Per URL, at the next check |
| Did the AI crawlers you allow change? | No | Yes, for 14 AI crawlers |
| Needs access to the property? | Yes, a verified owner or user | No. It fetches the public URL like a crawler |
Keep using Search Console. It is the only place that shows what Google actually indexed, rendering problems, manual actions and search performance. A crawl check sits in front of it and tells you that something on the page changed, before Google acts on it.
If you look after client sites
Agencies often don't have Search Console access to every site they work on, or have it on an account nobody reads. A crawl check works from the public URL, so you can watch a client's key pages without asking for access, and send alerts to a shared Slack or Discord channel instead of one person's inbox.
Hear about a noindex the same day
NoindexWatch checks the URLs you choose for noindex in meta tags and headers, robots.txt blocks, error status codes and redirect chains, canonicals that point elsewhere, URLs missing from the sitemap and AI crawler changes. You get an email, or a Slack or Discord post, when something changes, and nothing in between. The free plan covers 1 site with up to 20 URLs, checked daily, no card.
Sources: Google Search Console Help on email notifications, the Page indexing report, URL Inspection and the Sitemaps report. Related: Excluded by 'noindex' tag ยท Blocked by robots.txt.