Indexability
Detect a new noindex directive, X-Robots-Tag change, or site-wide wildcard robots block.
Scan a public page now, then scan the same URL again later. RankLatch compares stable SEO fields—not pixels or every line of source—and shows the previous value, current value, severity, and next action.
A CMS setting, deployment, plugin, redirect rule, or routine edit can move a search-critical field without creating an obvious visual failure.
Detect a new noindex directive, X-Robots-Tag change, or site-wide wildcard robots block.
Compare the resolved canonical URL and catch removed, duplicate, or off-domain declarations.
Record exact title and meta-description text so approved copy is not lost silently.
See when a healthy URL becomes a redirect, error, unavailable response, or different destination.
Compare ordered H1 text and meaningful copy-volume movement without archiving HTML.
Track social-preview fields, schema-block count, newly missing alt attributes, and homepage favicon declarations.
RankLatch identifies the protected field and preserves both values. Severity is rule-based: gaining noindex, losing a title, changing canonical domains, or becoming unavailable is treated differently from a minor metadata edit.
Review every comparison rule →The manual tool is deliberately transparent about storage and scope. Automatic monitoring is available only when you want RankLatch to return on its own.
RankLatch extracts bounded public fields and saves the snapshot locally in this browser. Page HTML is not stored.
The prior snapshot is submitted with the same URL and compared using the production monitoring rules.
See every meaningful protected change, or confirm that the extracted fields still match the earlier state.
The free checker proves the comparison. RankLatch monitoring adds scheduled daily checks, approved baselines, email alerts, and evidence history. One site with up to 10 pages remains free after the full trial.
See free SEO monitoring →This is a focused temporal comparison of public SEO fields—not a ranking forecast, visual regression test, or hidden full-site crawl.
It compares the same public page’s response status and redirect destination, indexability directives, site-wide robots block, canonical URL and declaration count, title, meta description, H1 text, meaningful copy-volume shifts, social-preview metadata, structured-data block count, newly missing image-alt attributes, and the homepage favicon declaration where applicable.
The first scan checks the page’s current public SEO signals and saves a bounded snapshot in this browser. Because no earlier snapshot exists, it cannot report a change yet. Scan the same page again later to create the comparison.
Up to ten extracted public-page snapshots are kept in local browser storage. RankLatch does not save the page HTML there. Clearing RankLatch site data in the browser removes those snapshots.
No. This checker deliberately compares the same requested page at two points in time. It rejects a previous snapshot captured for a different requested URL so unrelated pages cannot produce misleading change evidence. If the same requested URL begins redirecting somewhere new, that destination change is reported.
No. The free checker compares only when you return and run it again. RankLatch monitoring checks approved pages daily, retains server-backed evidence history, and emails meaningful alerts without requiring the browser to return.
No. It compares observable page signals, not rankings, clicks, impressions, or Google’s index selection. Use Search Console and analytics alongside change evidence when investigating a traffic movement.
No. RankLatch reads the bounded public server response and extracts stable SEO fields. It is not a screenshot diff, full DOM archive, JavaScript interaction recorder, or whole-site crawl.
No. The checker is read-only. It does not authenticate, install software, submit forms, or edit the submitted page.