Meta robots drift
Record when a page-level robots directive changes from an indexable state to noindex.
A staging setting, migration, plugin toggle, or routine edit can tell search engines to exclude a page. RankLatch checks the approved public state daily and captures the evidence when indexability changes.
A successful launch check only proves the page was correct at that moment. Continuous monitoring closes the gap between that approval and the next audit, client report, or Search Console investigation.
Record when a page-level robots directive changes from an indexable state to noindex.
Capture indexability instructions delivered in the public HTTP response, not only visible page copy.
Tie every event to the precise monitored page so the team knows where to verify the problem.
Keep the previous directive beside the new value instead of sending a generic changed-page notification.
Treat newly excluded approved pages as high-impact drift worthy of an email interruption.
Show the direct next step while leaving the actual site change in your team's control.
RankLatch can prove that a monitored public directive changed. It does not claim that Google has already removed the URL or that one tag explains every traffic movement.
See the exact methodology →RankLatch keeps the workflow deliberately small. Your team stays in control of every site and receives evidence only when a protected field moves.
Add the client site and review the public signals RankLatch found on each monitored page.
The monitor requests the page again and evaluates the same normalized indexability fields.
If an approved page gains noindex, the incident shows the URL, the old directive, the new directive, and what to restore.
These limits are intentional. RankLatch protects specific public SEO signals; it does not pretend to explain every ranking movement.
RankLatch captures public indexability directives and compares the current state with the preceding approved state. When a page gains noindex, the event records the exact before and after values.
Paid monitoring runs on a daily schedule. It is intended to shorten an unnoticed problem from potentially weeks to the next scheduled check, not to provide second-by-second uptime monitoring.
No. RankLatch never edits a monitored site. The alert identifies the affected URL and supplies a restoration step so the person responsible for the website can make and verify the change.
No. Search Console reports Google's view of indexing and search performance. RankLatch checks the public page state directly. Using both can help distinguish a page change from a later search-engine outcome.
The first capture becomes a baseline for review. RankLatch alerts on drift after that point, so an intentionally excluded page does not need to create the same incident every day.
No. RankLatch reads public responses and does not require a CMS plugin, client login, tag manager script, or authenticated crawler.
Run the free homepage scan, trial up to three sites, then keep one site protected on Free without a card.
14-day full trial · Free after · no card