How measurements work
RankMeOff methodology and limits
RankMeOff checks public URL responses and, for supported paid tasks, records search-result observations. A page fetch, a protocol notification, a search result, and an engine’s internal index record are different kinds of evidence.
Last reviewed: 24 September 2026
Current availability
Free diagnostics are available inside the app with a RankMeOff account. Public tool pages describe each check; create an account to run one. Paid task availability is checked live and can change; use the task form or product catalog for the current state. Rates and workflow descriptions below explain how the service works when available.
Checking current task availability…
Page fetches and backlink checks
A URL fetch records the response the RankMeOff worker received, including status and redirects. It is not a Googlebot visit or a request that Google index the URL. The backlink checker reads the donor server’s HTML, resolves relative links against the final donor URL, compares exact target destinations, and records anchor, rel, rough placement, canonical, noindex, and response evidence. It does not run JavaScript or assign domain authority or spam scores.
Search-result observations
Observed means the exact URL was found in the checked engine response for the recorded query. Not observed means the check completed but did not find that URL in those results. Unknown means the check lacked trustworthy evidence, such as a blocked response, CAPTCHA, timeout, or parser failure. Not observed and unknown are not proof that a URL is absent from an engine’s index.
Reports identify the engine, check time, query, and response class where available. For a site you own, a verified Search Console URL Inspection result provides a different, owner-scoped view; RankMeOff does not have access to that private record for arbitrary URLs.
Report timing and tokens
Under the planned result-based tariff, tokens are held when a task is accepted, and the final settlement uses the scheduled report deadline after delivery. A URL with no observed result or an unresolved check returns its held tokens once. A completed checker query is charged for the check; a check that cannot be verified by its deadline is refunded. A pay-per-submission tariff, if enabled later, would charge for processing rather than a search result. The task report and token ledger are the account-specific records of each outcome.
These rules describe product accounting; they do not guarantee a search-engine action or ranking change. Review the refund policy before making a purchase when paid service reopens.
Owner-supported discovery
A sitemap and internal links can help an owner expose preferred URLs. Google’s old unauthenticated sitemap ping endpoint is discontinued. Search Console recrawl requests require an owner or full user of the property and do not guarantee inclusion. IndexNow requires a key file on the submitted host and is for participating engines; a response only confirms receipt. RankMeOff does not submit third-party URLs to Google or use a shared IndexNow key for unrelated hosts: an account can prove ownership of a domain by hosting a per-account key file. Real IndexNow submission to Bing and Yandex for verified domains is coming soon; until then every indexer task, verified domain or not, gets the same fetch-and-verify check. Google is never submitted via IndexNow or any other automated indexing request, for any domain, verified or not.
Guides
- URL indexability checklist — Check access, status, redirects, robots rules, noindex, canonical, and discovery before interpreting search visibility.
- How to validate a sitemap — Validate sitemap XML, discover child sitemaps, and compare listed URLs with the pages you actually want indexed.
- Robots and noindex diagnosis — Understand why a robots.txt block, HTML meta directive, or response header changes what crawlers can see.
- How to verify a backlink — Check the donor response, exact target, anchor, rel attributes, and page directives without confusing a placement with search value.
- IndexNow for verified site owners — Understand the host key file, accepted response, and ownership boundary before notifying participating engines.
- How to interpret index checks — Read observed, not observed, and unknown outcomes with the query, time, and response class that produced them.