Skip to content

Public beta: some things may break while we finish them.

RankMeFast, public beta
Troubleshooting

Start here

Troubleshooting

Common problems and how to fix them.

Troubleshooting

Audit failed or unavailable

An audit fails when we cannot reach your site or the crawl provider timed out. Common causes:

  • Your site is behind a Cloudflare "under attack" rule blocking crawlers.
  • Robots.txt blocks user-agent RankMeFastBot or "*".
  • Origin returned 5xx for our first requests.

Try again in a few minutes. If it keeps failing, adjust firewall/robots.txt to allow our bot.

Rank check unavailable

A single keyword can come back unavailable if the SERP provider is rate-limited or Google served a captcha. It is temporary — the next scheduled run retries. Nothing to do.

Search Console asks you to reconnect

Google invalidated our token. On the site's Google tab, the Google Search Console card shows Your Google connection needs to be reconnected; select Reconnect. This can happen if you changed your Google password or revoked the app.

Cap reached

See Plans, limits & credits. Options are: upgrade tier, buy a small credit pack, or wait until the next billing period.

Cap reached on a research surface (402)

The response names the exact unit that ran out — for example keyword_lookups or audience_research_runs. Wait for the monthly reset, buy a credit pack where one exists, or upgrade; Audience Research runs have no pack.

Partial results on a research surface

Some engines or sources answered, others did not. The result ships with what arrived and is labeled partial results — the missing part is named, never zero-filled.

Unsupported for this engine / market

The check cannot run for that engine or market. The unsupported part is excluded from the result — it is never displayed as a zero.

Unavailable (not zero)

No data came back for the window. unavailable ≠ 0: treat it as unknown, not as a drop to zero. You will see this on share-of-voice and Search Console generative-AI cards.

"Search Console isn't connected" on analytics or generative-AI cards

These cards show Search Console isn't connected or Google Analytics isn't connected when no working Google connection exists, including after Google invalidates the token. If Google was connected before, the cause is the same as the Search Console reconnect above. Reconnect from the site's Google tab; the cards recover on the next read.

Verification email missing

Check spam. The link expires after 24 hours. If it truly did not arrive:

  • Confirm you typed the address correctly (typos are the #1 cause).
  • Try Google sign-in instead if your address is Gmail.
  • Contact support if the address is a corporate one — the mail may be filtered upstream.

AI summary shows "shortened"

Long audits are truncated before we send them to the model — the summary is still valid, just from a shortened view. Click Regenerate if you want another take.

Report screen loops loading

Hard-refresh the page (⌘/Ctrl + Shift + R). Clear the local cache if that does not help. If the issue persists, it usually points at a mismatch between an in-flight audit and the report snapshot — support can force-refresh from their side.

Back to the docs index