Skip to main content
  • Check that Settings → RankRaft AI → Status shows logging on and the right site key.
  • Click Test connection. Site key rejected. Copy it again from the RankRaft dashboard. means the key is wrong or was replaced.
  • Make sure your host allows outbound HTTPS to ingest.rankraft.ai.
  • Check Last error and Queued logs on the Status tab.
A cache is probably serving pages before WordPress runs. Click Check cache bypass on the Status tab, and see CDN and page caching.
Logs are sent by WP-cron every minute. If DISABLE_WP_CRON is set, point a system cron at wp-cron.php every minute. The Status tab shows the exact command, for example:
Your site is behind a proxy or load balancer the plugin doesn’t trust yet, so it’s reporting the proxy’s IP. Add it with the rankraft_aa_trusted_proxies filter. See Trusted proxies.
Logs are queued while RankRaft AI is unreachable or WP-cron isn’t running. They’re sent automatically once it is. After three failures in a row, sending pauses for 30 minutes before trying again. Queued rows are kept for 7 days.
Your RankRaft AI subscription is inactive or the site was paused from the dashboard. Nothing is queued or sent while paused. Update billing, or resume the site under Integrations → Advanced. RankRaft AI notifies the plugin with a signed request and logging resumes on its own. Test connection re-checks immediately.
The key is being stored unencrypted. Ask your host to enable Sodium, or define RANKRAFT_SITE_KEY in wp-config.php instead.

Advanced: delivery tuning

Developers can adjust delivery with filters. Every value is clamped to a safe range.