Not getting calls from Google? Find out why. See how it works →
Skip to main content
Troubleshooting

Contact RnkRocket Support: How to Get Help Quickly

Last updated 11 March 2026

Contact Support

We are a small, focused team and we genuinely want RnkRocket to work well for you. If you run into a problem that the help articles do not solve, please get in touch.

How to Reach Us

Email: hello@rnkrocket.com

This is the best and fastest way to reach us. We check this inbox regularly throughout the working day.

Response time: We typically reply within 24-48 hours on business days (Monday to Friday, UK time). During busy periods it may be slightly longer, but we will always get back to you.

Before You Contact Us

A quick check through the following can often save you waiting for a reply:

  1. Read the relevant help article — The help centre covers the most common questions. Try searching for keywords related to your issue.
  2. Try a hard refresh — Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac). This clears your local cache and fixes a surprising number of display issues.
  3. Check the Common Issues pageCommon Issues & Fixes covers the most frequently reported problems and their solutions.
  4. Wait a few minutes — Some analyses and data syncs take a few minutes to complete. If something looks stuck, give it 5-10 minutes and refresh.

What to Include in Your Message

The more information you include, the faster we can help. Please try to include:

  • Your account email address — so we can look up your account quickly
  • Which page or feature the issue is on — for example, "the Keywords page" or "GEO Hub analysis"
  • What you expected to happen — describe what you were trying to do
  • What actually happened — describe the result you got instead, including any error messages you saw
  • When the issue started — approximately when did you first notice the problem?
  • Screenshots or screen recordings — these are enormously helpful, especially for visual or layout issues
  • Your browser and device — for example, "Chrome on Windows 11" or "Safari on iPhone"

The more specific you are, the less back-and-forth we need, and the quicker your issue gets resolved.

What Happens After You Contact Us

  1. You will receive an automatic confirmation email to confirm we received your message.
  2. A member of the team will review your issue and reply within 24-48 hours.
  3. In some cases, we may ask follow-up questions before we can investigate further.
  4. If your issue requires a fix on our end, we will let you know once it has been deployed.

Feature Requests and Feedback

We actively want to hear your ideas. RnkRocket is shaped by the people who use it, and most of our recent features have come directly from user feedback.

If you have a suggestion for a new feature, a change to how something works, or something that has been frustrating you, please include it in your email. We read and discuss every piece of feedback, even when we cannot reply to every message individually.

You are not just a user — you are helping to build the product.

You can also browse the getting started guides or feature documentation for step-by-step instructions.

Billing Queries

For billing questions (invoices, refunds, plan changes, failed payments), email hello@rnkrocket.com with your account email and a brief description of the issue. Refund requests are handled case by case and we aim to be fair. For plan and billing questions specifically, check Billing & Subscriptions first.

For urgent billing issues such as unexpected charges, please mark your email subject as [Billing - Urgent] so we can prioritise it.

Accessibility and Inclusion

We are committed to making RnkRocket accessible to everyone. If you have difficulty using any part of the platform due to a disability or accessibility barrier, please let us know at hello@rnkrocket.com. We take accessibility feedback seriously and will work with you to find a solution.

You can also review our accessibility scanning feature which checks your own website for WCAG compliance issues.

Was this article helpful?