From a quiet change to a clear next step
Know what changed. Know what to check.
Follow the monitoring workflow from an approved baseline to a confirmed change and recovery. Select a stage in the example below.
Try the example
One page.
Three moments.
Select each stage to see how a normal page, a changed directive, and a recovery should be explained.
- Baseline · 09:00 UTC
The expected meta robots value is approved as index, follow.
- Change · 09:15 UTC
The page still returns HTTP 200, but now asks search engines not to index it.
- Recovery · 09:30 UTC
A subsequent check finds the expected value again.
Your page is up. But its indexing directive changed.
A noindex directive asks search engines not to index this page. This is a risk signal, not proof of removal from search.
index, follownoindex, followWhat to investigate in this example
Inspect the page’s HTML and X-Robots-Tag response header. Check whether a recent deployment or CMS setting introduced the directive. Confirm that the change was unintended before removing it, then recheck the page.
Search engines determine their own indexing behavior. Removing a directive does not guarantee immediate indexing or restored rankings.
Before monitoring can begin
Sign in with an email link, create or select a workspace, and verify domain ownership with the supplied DNS TXT record. Add the important URLs you want to monitor. Your plan controls URL limits and check frequency; opt-in email alerts report confirmed changes. Public tools provide a one-time check without enrolling a monitor.