Frequently asked questions

You can create indexing tasks, check search-result visibility, check backlinks, run a free site audit, connect your own Google Search Console account, manage workspaces, and review or export reports. Some paid task types may be paused during service checks; the live task form shows whether each type is currently available.

Availability is checked live when you open the task form and again when you submit. If a task type is paused, the page explains that it is temporarily unavailable and prevents submission. An estimate in the form shows the current token rate before you submit.

No separate provider purchase is required for the regular RankMeOff tools. An optional DataForSEO search-results fallback is an admin-controlled pilot, not a customer setting; it remains unavailable until the required deployment approval and provider credentials are configured.

No. Search engines control crawling and indexing. RankMeOff records checks and delivery evidence so you can see what happened; no task guarantees indexing, ranking, or traffic.

It checks each URL and records the result in a report. Google tasks use fetch-and-verify; RankMeOff does not use Google’s Indexing API to submit ordinary website pages. For Bing and Yandex, a real IndexNow notification can be sent only when the URL belongs to a host with a verified IndexNow key file. Other URLs receive fetch-and-verify checks.

Pay per result holds the estimated tokens while the task runs, then settles each URL from its recorded result. At settlement, a URL that was not observed as indexed is refunded only if no access fault was recorded. Examples of access faults that are not refunded include 404, 403, noindex, and redirect errors. Pay per submission charges the displayed flat per-URL amount for the task and does not promise indexing. The report and Refund Policy explain the recorded outcome and any returned tokens.

No. Google tasks perform a fetch-and-verify check. If you own the site, you can separately request inspection in your own Google Search Console account, subject to Google’s rules and limits.

IndexNow is a notification protocol for participating engines. RankMeOff can send a URL notification for an eligible, verified host. An accepted response confirms the notification was received; it does not confirm that the engine crawled or indexed the URL. IndexNow is not a Google submission method.

Add the domain in Domains, download its generated key file, and publish that exact text file at the public location RankMeOff provides. Then use Check key file. A DNS ownership record alone does not meet the IndexNow key-file requirement. Keep the file publicly available so the engine can verify it later.

Only use a real IndexNow submission for a host you control and have verified with its key file. URLs on other hosts are not sent through your key; they receive the available fetch-and-verify check instead.

It spreads URL processing across the number of days you choose instead of starting the whole list at once. The task form shows an approximate daily volume. Spreading a task out also extends its report window so later batches have time to be checked.

A task can contain up to 5,000 URLs. Duplicate entries are removed before processing. The form shows how many unique URLs it detected and the estimated token total.

It checks whether a URL appears in the selected engine’s public search results for the query used by the checker. This is a time-specific search-result observation, not direct access to the engine’s complete private index.

The checker supports Google, Bing, and Yandex. Each engine is checked separately; a result from one engine does not establish what another engine knows about the URL.

Observed means the URL appeared in the recorded results for that check. Not observed means it did not appear in that checked query and result sample; this alone does not prove it is absent from the engine’s index. Unknown means the check could not produce reliable evidence, for example because of a challenge, timeout, or other response problem.

The checker may have received a search challenge, blocked response, timeout, or unreadable result page. Open the row’s evidence details to see the engine, query, response class, and any available explanation. Unknown is inconclusive, not a negative indexing verdict.

When you choose optional Google Search Console evidence, the report records the exact property used for that inspection. This helps you confirm the check used the property you selected.

Each RankMeOff user connects their own Google account. The property list contains properties that account can access. To inspect a client’s property, that Google account must first be granted the appropriate access by the client.

It requests read-only URL Inspection evidence from a property available to your connected Google account. It does not submit or request indexing. Google’s property type and URL-prefix scope determine which URLs it can inspect; URLs outside that scope are disabled or reported as out of scope.

No. It is optional owner evidence. Connect Google, choose a property, and request an inspection for the report URLs you want to review. RankMeOff cannot inspect private Search Console data for a site unless the connected account has access.

It samples public crawl and sitemap signals, including HTTP responses, redirects, canonical and noindex signals, robots.txt, and sitemap entries. It checks up to 6 pages and reads up to 2 child sitemaps. These observations do not prove whether a search engine indexed a page.

Site audit results remain in the current browser session. You can export the findings as CSV before leaving or refreshing the page.

It fetches each source page and checks its returned HTML for a link to your exact target URL. The report can show link presence, anchor text, rel attributes, placement, HTTP status, canonical, and noindex evidence.

No. It checks the HTML returned by the source server and does not run the page’s JavaScript. A link injected only after the browser executes scripts may not be detected.

No. It checks the link evidence described in the report. It does not calculate domain authority, spam scores, ranking impact, or whether a search engine has credited the link.

Tasks & reports lists your task history. Search by task title, domain, or reference, and use the status and workspace controls to narrow the list. The list is paginated so large histories remain manageable.

Open a task to see its summary and per-URL rows. Expand a row to inspect its evidence and details. Large reports are paginated; use the page controls to move through the URLs.

Depending on the report, you can export it as PDF or CSV and share its app link. On a phone, the browser’s share sheet is used when available; otherwise RankMeOff copies the link.

A workspace is a way to group future tasks and reports by client or project. You can create, rename, archive, and assign tasks to workspaces, then filter task history by workspace. Existing unassigned reports remain available in Unassigned.

Yes. Tasks can be assigned individually or selected and assigned in bulk from Tasks & reports. Changing a workspace assignment organizes the report; it does not change the task or its evidence.

A task can still be processing or waiting for evidence. Check its status and report deadline. Some results may remain unknown if a reliable observation is not available by the deadline; the report labels that as inconclusive.

Rates are shown in tokens per URL in the task form, and the estimated total updates as you add URLs or change engines and task modes. The live catalog and form are the source of current rates; check them before submitting.

No. Token packs are one-time purchases through Stripe; there is no subscription or monthly token reset. The Billing page shows the available packs and checkout price.

No. Purchased tokens do not expire.

The task form and report show the charging mode, estimated cost, per-URL outcome, and any tokens returned during settlement. The rules differ by task type and result. See the Refund Policy for the exact exclusions and process.

A person who registers through your referral link receives 200 signup tokens. You earn 15% of their eligible deposits as referral rewards. Withdrawals can be requested once the available balance reaches the minimum shown on the Referral page.

Contact Support with the task reference or payment receipt and a short description of what happened. Never send your password, API key secret, or Google account credentials.

Yes. RankMeOff provides API keys and an MCP connection for supported AI agents. Create a key in AI agents, follow the setup instructions for your client, and keep the secret private. Access and task availability follow your account and the same service rules as the dashboard.

Key settings include usage controls. Review each key’s configured limits in AI agents and create separate keys when you want to isolate usage or revoke access independently.

For tasks created through an API-key or MCP integration, you can enable email notifications and configure a webhook on that key. Webhook deliveries are signed. Tasks created in the dashboard do not currently use those API-key notification settings.

That key can no longer authenticate new API or MCP requests. Update any connected agent or integration to use another active key. Treat a key secret like a password and rotate it if it may have been exposed.

No. Google credentials are connected per RankMeOff user. Other users do not inherit access to your Google account or its properties through RankMeOff. See the Privacy Policy for details about stored connection information.

Open Settings from your account menu and choose System, Dark, or Light under Preferences. Your choice is saved to your account and this browser.

Open Support from the app sidebar. Include the page, task reference, and steps that led to the issue so the support team can investigate it.